If you can do all formatting from Css, one idea to go is like this: - in your war directory, or one subdirectory of this (can be anywhere), have the locale-specific css files, given a specific naming convention (let's say "main-en.css", "main-fr.css" - for french locale). The idea is to name the files as a fixed prefix with a variable (locale based - en, fr, de, etc) suffix. - in your code (let's say at init time, before any widgets are constructed), simply read the locale from browser and inject the right css into dom (http://code.google.com/p/google-web-toolkit/wiki/ StyleInjector). If this doesn't work, you can try to manually write a Js function that appends the Css to dom (achievable, I've done it). Your only attention here is to supply the mapping (locale => url).
If you can't do everything from Css, along with the things above, you will need to supply localized widgets...I can think of a couple of ways, but i'm not sure you can do deferred binding for that. If not, you could have some sort of factory pattern that would provide you with the widgets. Hope that helps, Alex On Jun 28, 4:53 am, Dan <[email protected]> wrote: > Is it possible to localize the css in a CssResource so that during the > translation phase of product development, css tweaks can be made to > adjust for language specific spacing and formatting issues? > > if not, what's the current best practice to work around these issues? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/google-web-toolkit?hl=en.
