Hi Henri, I agree too that the community could improve translations, but the only thing we as developers/contributors can do at this point is file bugs so the translation team could translate. The process is as follows:
1. String gets added to a grd file 2. Translators are provided with the new grd files 3. Translations are created and new xtb files are generated 4. The new xtb files are checked into the Chromium source tree From: http://dev.chromium.org/developers/design-documents/ui-localization And when you file a bug, it will be dealt quickly. http://code.google.com/p/chromium/issues/entry?template=Translation%20Issue It will help us eliminate managing translations, since some party is responsible for that. But I get your point and it makes total sense for an Open Source project. - Mohamed Mansour On Wed, Nov 18, 2009 at 8:55 AM, M Henri Day <[email protected]> wrote: > Incomplete translations, are just that, «incomplete», hardly «great», as by > definition they don't suffice for users' needs. Erroneous translations are, > of course, «bad», just as is unidiomatic usage, e g, «put their > translations». Development of a system for receiving input would, of course, > require resources, but could have many positive repercussions, not limited > merely to this particular issue. As to how Google's systems for dealing with > matters like the above will develop, my knowledge of the inner workings of > the firm do not suffice to permit me to have an opinion. But I do feel that > a system which allowed for more community input would have greater > advantages than disadvantages.... > > Henri > > -- > Chromium Discussion mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-discuss > -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
