On Monday 25 August 2003 11:56, Jon Lapham wrote: > Eneko Lacunza wrote: > > By the way, your translation web looks very nice. Maybe being able to > > download .po and .pot files could be interesting as well :) > > It would be easy to do... I could make a link to the web CVS files. > However, the question is, do we want to make it *that* easy? > > It would be a pain if people started emailing in updates to the .po > files that didn't compile, or where they are going over the heads of the > maintainers, etc. I think it maybe is better if we "force" potential > translators to read the TRANSLATORS_HOWTO document... Anyone have an > opinion on this?
I disagree, even an improperly done translation (syntax-wise) can be fixed quickly and relatively painlessly. Id much rather fix the few mistakes of a new translator than have less translators. Anyway, they will are unlikely to make the same mistake twice once we explain it to them, and they are unlikely to make syntax mistakes at all if they use graphical translation tools like kbabel. However the document should stress quick turnaround times. I.E.: If you work for a few days on a translation and then stop; send in your chances. Once you resume working on it a few weeks later, grab a fresh copy. Otherwise, it will be a royal pain to merge changes if there have been other commits in the meantime. -- Benoit Gr�goire http://step.polymtl.ca/~bock/ _______________________________________________ gnucash-devel mailing list [EMAIL PROTECTED] http://www.gnucash.org/cgi-bin/mailman/listinfo/gnucash-devel
