Heya, I just wanted to know in what way it complicates things for translators?
I maybe forgot to expressively mention that at this moment the translation is stored in the .XML based format which is converted to windows headers. We could also update the tool that does that to output these text files as well - or to output compiler constants.... The translators edit the same files they have to edit with the current solution and you only need an additional line in the makefile to output these localization files. -> Translators need no additional work -> Coders only need to incorporate it into Chrome On 25 Sep., 13:54, "Simon B." <[EMAIL PROTECTED]> wrote: > Arnaud, Nicely synthesized. Maybe you and some ppl corrently doing > compiling in Linux / mac could make a "test run" to find the first few > obstacles. Or if there are none, maybe there will be a patch coming up > for code review :). And you might need a "champion" inside > chromium.org. (Sorry for mentioning this if it was clear to you > already.) > > Oblivion - your code is nice and all, but since it complicates for > translators I can't support your solution... it's not personal :-). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to chromium-dev@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
