Comment #7 on issue 27360 by smartgk: Implement i18n for extension manifests http://code.google.com/p/chromium/issues/detail?id=27360
>> I think we should just support the __MSG_* macros in these fields, and >> developers can do whatever they want. Yes. Developers generally need __MSG_*__ macros support, especially in static HTML portions. To create dynamic HTML, chrome.* API would be helpful which is working fine now. Right now, since there is no support for __MSG_*__, developers need to use either dynamic string creation using chrome.* calls or regular expression based replacement for the whole HTML/static sections. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
