> > Can the string replacement be applied to CSS stylesheets as well? Related > to it is how to deal with RTL "layout". Perhaps, it's asking too much to > expect (external) extension developers to have separate CSS entries with > 'dir=rtl'. What does Google Gadget do for RTL UI? It'll be also interesting > to see what Fx extensions localized to RTL languges do. >
External (to html file) CSS files would be placed in some_locale folder. I doubt that you would need more than two in total (one for all LTR languages, and one for all RTL, same as LTR but with dir=rtl). If that's too complicated for external developers, we could inject internal css with dir=rtl somewhere if we detect RTL layout? > Going a little bit tangential although still related, I wonder if we have > to expose some i18n apis for formatting date, time, region/language names. > Exposing them can prevent the inconsistency between Chrome and extensions > when it comes to formatting. It can also save some translation needs for > extensions. (how about plural formatting? aha.. it's a bit tough) > There are so many i18n APIs we could export - CLDR is very rich with data :). But yes, date/currency formatting could be useful. --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
