On Wed, Oct 21, 2009 at 3:48 PM, Miroslav Pokorny < [email protected]> wrote: > > It sounds like an alternative might be to have the compiler to spit > out properties files full of key value pairs with one per locale. > Naturally the compile would output shortened keys etc and record a > mapping file. A tool would be made available to update just these text > resources and the initial bootsrap code so it now picks up the newly > updated files. The exiting use of cache files as much as possible > would remain, but there would be less permuTation generated files. >
The problem is more than that. As mentioned above, the actual compiled code is frequently different depending on the messages, such as when the parameters are re-ordered in different locales or have different formatting patterns. Basically allowing them to be switched outside of a full compile means the format strings have to be parsed at runtime, which IMHO is an expensive price to pay. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
