In general, this is a bad plan. The translated strings are designed to be used in a particular context, and while the words themselves might make sense in multiple contexts in one language, the same wouldn't be true for another. Encouraging people outside of the project to make the call about when it makes sense to use a string in a different context or not is going to be extremely error prone. Erik
On Tue, Jun 30, 2009 at 8:54 AM, PhistucK <[email protected]> wrote: > But now when I come to think about it, the Chrome strings are changing > sometimes, added or removed.This could pose a problem. Unless you want to > start a new ground rule - all of the strings must be maintained from now on > and never be removed - only added. > > > ☆PhistucK > > > > On Tue, Jun 30, 2009 at 18:49, Nebojša Ćirić <[email protected]> wrote: > >> We could probably expose them as >> __chrome_MSG_some_chrome_message__, but will wait for initial review to >> decide that. >> Thanks for the input, >> Cira >> >> On Mon, Jun 29, 2009 at 10:19 PM, PhistucK <[email protected]> wrote: >> >>> How about extending this support and also adding an option to use native >>> Chrome strings that are in use in the actual program so extension developers >>> could benefit from your own translations and corrections in the appropriate >>> cases? >>> ☆PhistucK >>> >>> >>> 2009/6/30 Nebojša Ćirić <[email protected]> >>> >>>> Hi all, I have initial draft for extensions internationalization >>>> effort. Take a look at >>>> http://sites.google.com/a/chromium.org/dev/developers/design-documents/extensions/i18n >>>> >>>> Regards, >>>> Nebojsa Ciric >>>> >>>> >>>> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
