@Harbs <[email protected]> does your solution allow for switching locales once the app is running? A standard Canadian use case is to be able to jump from the English to the French version of the app without losing data or workflow. That is the feature of the standard method for localization that I have always relied on.
That said, I have long delayed writing either the docs or page in the getting-started tutorial about localization. I guess I should do that now! Could I draw on your wisdom; perhaps get you to review what I write? Andrew On Wed, Jul 1, 2020 at 6:53 AM Hugo Ferreira <[email protected]> wrote: > Very good. > I will follow the same approach. > Never liked the Flex way. > > Harbs <[email protected]> escreveu no dia quarta, 1/07/2020 à(s) > 10:49: > > > I don’t actually propagate changes. In my case, all localization is > > determined at launch time. I have a RuntimeOptions class which gets > runtime > > options from url parameters (using a ApplicationParametersCaseInsensitive > > bead). One of the runtime options in locale. > > > > Currently, I’m bundling all localized strings in the actual app. That > adds > > a non-insignificant weight to the app, so someday, I’ll probably pull the > > strings out and load them as-needed. > > > > Either way, here’s the current full LocaleManager class: > > https://paste.apache.org/17dzh <https://paste.apache.org/17dzh> > > > > I have some cruft from old implementations and some which will hopefully > > be improved in the future, but you should get the idea. > > > > IUIStrings contains all the definitions. > > > > > On Jul 1, 2020, at 11:33 AM, Hugo Ferreira <[email protected]> > > wrote: > > > > > > "this has the advantage of allowing me to make localeStrings a typed > > class > > > so I get type checking on the actual strings to prevent mistakes" > > > > > > That's a very good idea ! > > > I never liked the way that Flex deals with that and sometimes there are > > > type check errors that I can only see at runtime. > > > > > > Can you give an example, how the value changed (language value) in the > > > constant: LocaleManager.localeStrings.OK ? > > > > > > Harbs <[email protected]> escreveu no dia quarta, 1/07/2020 à(s) > > 07:32: > > > > > >> [ResourceBundle] has support, but I’m pretty sure that’s in mx. You > can > > >> probably use it even if you’re not using mx components (I think). > > >> > > >> I’ve always used my own home-grown method of loading locale strings > and > > >> construct them into an object which is read using keys. > > >> > > >> i.e. LocaleManager.localeStrings.OK > > >> > > >> Besides the fact that I hate “magic”, this has the advantage of > allowing > > >> me to make localeStrings a typed class so I get type checking on the > > actual > > >> strings to prevent mistakes... > > >> > > >> HTH, > > >> Harbs > > >> > > >>> On Jul 1, 2020, at 3:14 AM, Hugo Ferreira <[email protected]> > > >> wrote: > > >>> > > >>> What's the recommended approach for localization in Royale ? > > >>> An out of the box API that grabs a txt file with the key/values ? > > >> > > >> > > > > > -- Andrew Wetmore http://cottage14.blogspot.com/
