Quoting Nguyễn Vũ Hưng (vuhung16plus@gmail.com): > > You mean Debian Installer, as a start, in order to be able to relay > > Magic Clytie for this? > > Maybe, actually I have no idea how to translate po files in Debian. > > Myself, and probably, Nguyen Thai Ngoc Duy (cc'ed) think that if we > don't have svn access > to Debian's repo, we can get the po files commited by Debian people by > submitting bugs in Bugzilla. s/Bugzilla/Debian BTS (bugs.debian.org)....as the Debian BTS is not using Bugzilla. The Debian Bug Tracker is significantly different from Bugzilla (or Launchpad) as everything is more mail-driven than web-driven. > > I hope this is the wrong workflow? Translating by sending translations back to Debian BTS *is* the right workflow. The major difference between Debian and most FLOSS projects you may be familiar with is (besides the size of the project) that Debian has no centralized development. There is no central place (svn, git, bzr, whatever), with all packages sources. Every maintainer and maintenance team is free to use tools they want to maintain their packages. This is because of the very distributed nature of Debian development. Most package maintainers and maintenance teams *are* using VCS to maintain their packages. An interesting stat is available at http://michael-prokop.at/blog/2011/08/19/use-of-vcs-in-debian-packages-some-stats/ As you may imagine, it is impossible to anybody to have commit access everywhere, of course! So, the right workflow is sending translation updates and new translations as bug reports against the relevant package. To makje translators life easier, there are places where localized material is automatically gatherd and presented to translators. This is indeed the major duty of the i18n.debian.net server. You'll find links from http://www.debian.org/intl/l10n/ For instance, I can recommend you to look at the page listing the current status of "debconf" translations in Vietnamese. Thanks to Clytie's work, Vietnamese is ranked quite high there, not that far from the 7 top teams that are competing for 100% (I take care to keep French at the top, of course;.:-)). Such pages are great help for translators to spot targets for their work. I will not go into details in this mail, but I can get into it if enough ppl are interested. > > At first, I need people to have a look at Debian Installer i18n > > documentation and understand it, how things are organized, etc. Then, > > if a member of the team is willing to do the work, I'd be happy to > > validate her|him for commit access in Debian Installer SVN (we use SVN > > of localization though we use git for other stuff). > > > > http://d-i.alioth.debian.org/doc/i18n/ > > OK, I will read; very well documented :) Here, this is an example of a sub-project in Debian, where the team uses a common VCS. Moreover, this project has a very specific l10n infrastructure (which I'm mostly responsible for) to help out getting access to the material for the "levels" and "sublevels" of D-I. This is indeed what allowed Clytie to bring Vietnamese to full 100% for all D-I levels at some points...something I would really like to keep despite Clytie's difficulties to keep it up (which I'm very well aware of: we have private exchanges for years). > > Coordination of this can be done in debian-l10n-vietnamese. I can even > > subscribe to that list, in order to guide the involved people. The > > only requirement is that you don't speak Vietnamese to me (French is > > OK, obviously...but I know that French is somehow vanishing in Vietnam > > now)..:-) > > Some of us can speak French but myself and most of use, can't ;) > So let's stick with English. > > You can call me "Hung" OK. Should I assume that this is correct with most Vietnamese people to use the last component of their name as a "friendly but still polite enough" way to address them? I know that conventions wrt this change in different places of the world and I'm trying to do my best to respect them..! > > A sad (or good?) thing is that, Debian is less popular than Ubuntu in Vietnam. But that's not a big problem as people understand that localization work happening in Debian *will* end up in Ubuntu while the other way is much more difficult to organize. > But committing to Launchpad is not, so we want the translation to be > in the upstreams. > (Debian, Gnome, GNU or other sources) Exactly what's needed..:-) > > How to get commit access to packages other than Debian Installer? See above. The concept doesn't even really exist, indeed. > > Duy (Nguyen Thai Ngoc Duy) and myself want svn commit to Debian. > Please connect us to the right person. Still, I can certainly guide you through the processes you can follow. Maybe you first need to get an idea of *what* you'd intend to localize. Methods depend whether you want to work on D-I, debconfn translations, native packages translations (things like apt, dpkg, etc.), website translation, packages descriptions translations, etc.
Attachment:
signature.asc
Description: Digital signature