The translation is not done inside the RC files but within a xml file xtb - look http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/resources/ - and the grit tools generate the rc files for windows from this xml files ...
So today I think they already have tools to deals with xtb ;-) In any case, the code have to be changed since on windows, they are relying on an IDS (#define with int value) to retrieve the string and with gettext, you have to use the english string to retrieve the translation. A quick workaround could be found by using the grit tools to generate a dictionnary between the IDS and the english version and next rely on gettext for translation : all is possible ;-) >From my point of view, there is two good points : * Tony said : "Basically, we need to figure out if we're going to use a cross platform solution or whatever makes the most sense on each platform." * Simon said : "If there exists _no_ cross platform lib for translation strings based on int/id, is that a sign of this being less useful, or a sign that i18n always comes in (too) late in a project?" Frédéric On 9 sep, 08:15, "Simon B." <[EMAIL PROTECTED]> wrote: > There's always the gettext lib (or libs?) that must get included > somewhere into Chromium? Also with gettext, aren't you storing the > english strings inside the binary? One strings file is ca 70kiB. > Compiled into a DLL, that becomes around 60kiB. Are those bulk-loaded > into a dictionary, or how are the strings accessed? How are gettext > strings accessed? > > Using gettext would allow using some nice translation tools. How is > translating with RC files done? > > (If there exists _no_ cross platform lib for translation strings based > on int/id, is that a sign of this being less useful, or a sign that > i18n always comes in (too) late in a project? Having done some > translating, I've seen some trouble from being English-focused, but > can't say if id/int would make this better or worse.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
