In other words, as Jim was saying if you want to distribute localized script binaries you have to compile them for each localization of interest rather than have jaws perform some sort of run-time lookup (which seems like it would be quite useful, being able to change the localized script text without needing a script recompile). On 12/30/14, Raymond <rh.jansen@xxxxxxxxx> wrote: > Hi Jim, > > JAWS localizers have there own language folder in Settings. > So besides ENU we have another folder for our language. > > When you change the UI language in JAWS, JAWS switches to the corresponding > folder in the Settings folder. > > I guess most of you use the English JAWS and there is only the ENU folder > in > Settings. But I have also the NLD folder for the Dutch localized scripts. > > Best regards, > > Raymond > > -----Oorspronkelijk bericht----- > Van: jawsscripts-bounce@xxxxxxxxxxxxx > [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] Namens Jim Snowbarger > Verzonden: maandag 29 december 2014 21:43 > Aan: jawsscripts@xxxxxxxxxxxxx > Onderwerp: [jawsscripts] Localization > > I am curious how people do this. You create a JSM file which contains > messages written in a particular language. But, as far as I know, there is > no way to qualify the message based on the currently selected language. > The > only way I know to do it is to substitute a new JSM file with the correct > language, and recompile the script. > I'm sure that isn't the right way to do that. Can somebody set me straight > on the preferred technique? > > Thanks much. > > > > > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > -- Soronel Haetir soronel.haetir@xxxxxxxxx __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts