I forgot to say (it was probably obvious, but...) that we rely *heavily* on locale for dates and number formatting.
For dates, it means not only the typical MM, DD, YYYY order, but also the separator between them, and the "text form" (short or long) for days of week, and/or months. For numbers, it means the decimal and thousands separator, the minus sign position etc. We found that the localisation classes in Flex4 (spark) were globally adequate, although it was difficult to understand the relationship between the formatters and the "globalization" API...(especially for predefined date formats). Sometimes, we had to go back to a mx formatter to have the job done... Also, we absolutely need to be able to specify the locale when formatting dates or numbers (it can be different from the "user's current locale" : for example, we have german customers producing English-locale-formatted documents : it means that the user chooses the "output" locale at some point in the workflow and that "output-locale" is sometimes different from the current "application" locale). Hope this helps Nicolas Granon > -----Message d'origine----- > De : Alex Harui [mailto:[email protected]] > Envoyé : mardi 7 novembre 2017 18:51 > À : [email protected]; [email protected] > Objet : Re: Resources (I18N, globalization, localization) > > Thanks Nicolas. So some questions for you (and other users) > > 1) does your Flex app currently use the "fall-through" where not every > locale has every key? > 2) does your Flex app use @resource directive in MXML? > > Thanks, > -Alex > > On 11/7/17, 9:29 AM, "Idylog - Nicolas Granon" <[email protected]> > wrote: > > >Great ! > > > >That is one the features we cannot afford to miss... > > > >Nicolas Granon > > > > > > > > > >> -----Message d'origine----- > >> De : Alex Harui [mailto:[email protected]] Envoyé : mardi 7 > >> novembre 2017 18:24 À : [email protected] Objet : Resources > >> (I18N, globalization, localization) > >> > >> Hi, > >> > >> I just pushed a simple way of handling different locales in a Royale > >> app. > >> I purposefully did not call it ResourceManager for now since I don't > >> think it will be 100% compatible. I just wanted to get something > out > >> there to get a discussion going. > >> > >> It looks like there is PAYG features for what was called resources > in > >> Flex. In this implementation, you have to manual embed the > >> .properties files with a particular naming scheme, then the > >> implementation will lazily process the .properties files and pull > the > >> right string given a single locale. It is more code to have, for > >> example fall-through to another locale's bundle if the current > >> locale's bundle did not contain a value for a key. And even more > code to inject bundles at runtime. > >> > >> After I refactor the compiler, and any discussion on these > >> implementations settle down, we can look at having the compiler > >> automate whatever set of steps we settle on. For example, the > Royale > >> compiler doesn't handle @resource in MXML. Is anybody using > >> @resource?The compiler currently doesn't handle resource bundles. > >> And we have to come up with a scheme for knowing which bundles to > >> bundle if the bundles are declared in SWCs. > >> > >> Also, IMO, it should be a different set of beads that determine > which > >> locale should be primary at runtime. > >> > >> Thoughts? > >> -Alex > > > >
