>I browsed the system locales installed on the Palm, and got these 5: >enEN, frFR, deDE, esES, itIT.
I think you mean 'enUS', not enEN. Plus there's jpJP for Japanese. >Given this, it only makes sense to generate overlays for these given >locales. Yes you can create and distribute a localized overlays for >application for any locale you choose, however the existing overlay method >provides no mechanism to use any overlay other than the 5 indicated above >given the existance of only 5 OS locales. Actually, with Palm OS 4.0 or later you can use an overlay for any locale, as long as the OS specifies that it's the current (typically the same as the system) locale. So if any of the various language hacks run on 4.0 and set up the appropriate features with the correct values, overlays will work with them. Also in the future there will be localizations of the Palm OS for additional locales, either created by Palm or one of Palm's licensees. >Other solutions: > >1. Completely separate localized builds using separate localized .rsrc >files. (possible and likely) >2. Put all localization into one .rsrc file and programmatically select >the correct resources at run time. (unlikely, lots of code change, big big >.rsrc and .prc, possibly a balky application) Actually it's easier to simulate overlays by creating separate PRCs, one for each language. Your app opens the correct PRC at launch time, based on the device's current locale. This would require minimal code changes. To further simulate overlays, you'd want to set the bundle bit in the localization PRC header attributes, and make sure that the localization PRC header version number matches that of your app (and bump your app's header version number every time you change its resources). -- Ken Ken Krugler TransPac Software, Inc. <http://www.transpac.com> +1 530-470-9200 -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
