GNOME translation project
Dear developers, I would like to remind you that your project should be translated using the GNOME translation project in order to be coherent with the other translation of the GNOME project. Therefore when you receive some translated PO files by someone, you should submit this files to the appropriate team for the translation to be approved. See "Olivier Le Thanh Duong" translations for pdfmod : http://git.gnome.org/browse/pdfmod/log/?qt=grep&q=french See "Thierry Saliou alias Teza" translations for mistelix : http://git.gnome.org/browse/mistelix/log/?qt=grep&q=french Sincerely Bruno Brouard Coordinator of the GNOME French Team ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mistakes in doc translations
Le lundi 16 avril 2012 à 14:25 -0400, Shaun McCance a écrit : > Hi, > > Sometimes translators make markup mistakes in docs translations. > When it happens in modules I make releases from, I go ahead and > fix the mistakes when I can. I don't mind doing that. > > But recently, my fixes have been getting reverted. I don't know > what everybody's workflow is, but probably some translators treat > what's on their machine as canonical, and copy it over without > ever trying to merge. This is a very dangerous way to work with > a version control system. > I am sorry, i don't understand what you mean. Is it possible to have an example? Bruno > I don't mind fixing problems, but I don't want to make the same > fixes every single release. Please merge your po files with the > files on git.gnome.org. > > Thanks, > Shaun > > > ___ > gnome-i18n mailing list > gnome-i18n@gnome.org > http://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mistakes in doc translations
Le lundi 16 avril 2012 à 22:14 +0200, Andre Klapper a écrit : > On Mon, 2012-04-16 at 21:01 +0200, Bruno Brouard wrote: > > I am sorry, i don't understand what you mean. Is it possible to have an > > example? > > To put it into other words: > Shaun fixed something in Git, and the translators OVERWROTE the fix with > his/her next commit to Git. > Thank you again, I am not stupid :-) But Shaun speak specifically of "markup mistakes" and said "I don't know what everybody's workflow is, but probably some translators treat what's on their machine as canonical, and copy it over without ever trying to merge." I don't understand this previous sentence. Can HE give a concrete example of the error (that maybe i am doing)? As the message is intended to all commiters, i think it is better to be clearer, even if it is necessary to name someone. If i am doing mistake, i want to learn my mistake. I am just a human. Bruno > andre ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Mistakes in doc translations
Le lundi 16 avril 2012 à 18:34 -0400, Shaun McCance a écrit : > On Mon, 2012-04-16 at 23:04 +0200, Bruno Brouard wrote: > > Le lundi 16 avril 2012 à 22:14 +0200, Andre Klapper a écrit : > > > On Mon, 2012-04-16 at 21:01 +0200, Bruno Brouard wrote: > > > > I am sorry, i don't understand what you mean. Is it possible to have an > > > > example? > > > > > > To put it into other words: > > > Shaun fixed something in Git, and the translators OVERWROTE the fix with > > > his/her next commit to Git. > > > > > Thank you again, I am not stupid :-) > > > > But Shaun speak specifically of "markup mistakes" and said > > "I don't know what everybody's workflow is, but probably some > > translators treat > > what's on their machine as canonical, and copy it over without ever > > trying to merge." > > I don't understand this previous sentence. > > > > Can HE give a concrete example of the error (that maybe i am doing)? > > > > As the message is intended to all commiters, i think it is better to be > > clearer, even if it > > is necessary to name someone. If i am doing mistake, i want to learn my > > mistake. > > I am just a human. > > I have corrected markup errors in the French translations. See my > commits here: > > http://git.gnome.org/browse/gnome-user-docs/log/gnome-help/fr/fr.po > > But the errors are always new errors. As an example of my corrections > being overwritten, look at the Slovenian translations. Here's a commit > I made about two weeks ago: > > http://git.gnome.org/browse/gnome-user-docs/commit/gnome-help/sl/sl.po?id=34f54c24c2d69d94fdf4124436c84b2d977045e0 > > And here's the commit I made today: > > http://git.gnome.org/browse/gnome-user-docs/commit/gnome-help/sl/sl.po?id=4f68f59f5da11f193cc4eaa91c34c4c9f6e045b7 > > This is the workflow that usually leads to these kinds of problems: > > 1) Get the file from git and copy it to some folder somewhere. > 2) Edit the file. > 3) Update your git repository, or clone it fresh. > 4) Copy the file from some folder into the repository and commit. > > Using this workflow, you will never get merges of other people's work. > If anybody else edits the files you edit, you will always overwrite > whatever they do. > Now, before committing and pushing, i just do a (French Team= fr) git log fr.po As we are very few commiters in the team, this way i see who else has made changes to the po file... Bruno > And I realize many translators are used to basically owning their own > po files and not having to worry about other people editing them. But > module maintainers have to be able to fix syntax errors. And until we > get better tool support (like the kinds of checks you all already have > for format strings), we'll continue to see these mistakes. > > -- > Shaun > > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Question about committer versus coordinator
Le 03/10/2012 10:44, Chris Leonard a écrit : So what happens when a team has a coordinator, but not a committer (like Khmer)? The Coordinator has marked a number of PO files for commit in vertimus, http://l10n.gnome.org/languages/km/all/ui/ If a team does not have a committer, will someone else commit those on the Coordinator's request or does each team require a committer? Just ask on this list for help for the commit and someone will do the job. But please, join links to the modules marked as "ready for commit" Bruno Thanks for helping me learn more about how things work in the vertimus workfow. cjl ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Damned Lies and roles
Le 03/10/2012 14:13, Rūdolfs Mazurs a écrit : T , 2012-10-03 14:06 +0200, Gil Forcada rakstīja: You do not have to mark them as active, the activeness in D-L terms means when they have logged in. So just ask your team members to log in on D-L and they will become active again :) Seems login is not enough. Some other activity, like writing a comment is needed. hopefully ! Active state is not just to say to some friends "hey guy, look at here, i am working for you" ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: Damned Lies and roles
Le 03/10/2012 15:00, Rūdolfs Mazurs a écrit : T , 2012-10-03 14:48 +0200, Bruno Brouard rakstīja: Active state is not just to say to some friends "hey guy, look at here, i am working for you" I guess there is a big difference between "active translator" and "active damn lies user". Since committer can skip all the D-L proces and work with git directly, the system might just not notice the activity. I believe (see DL developpers) that only translator can be inactive. Reviewer and commiter are always active. ___ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
