Have you tried to maintain several property files in several different languages
supporting both Windows and Linux (the tool is native)? I wouldn't call that
the correct approach. In practice, you would like your local clients to be able
to simply customize certain literals of the user interface with their local
editors and maintain only version of each property file.
-- Ilkka
>Isn't the "correct" approach for property files to use native2ascii, the
>program, encode the file?
>
>The load() command knows how to encode and decode from the \uxxxx format
>that is produced.
>
>> -----Original Message-----
>> From: Ilkka Priha [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, May 02, 2001 6:26 PM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [PATCH] Configuration
>>
>>
>> Now that Velocity has nice encoding support for templates, I
>> have a new wish
>> on my list. Please, be patient :). In addition to templates,
>> property files
>> are frequently used for defining certain standard string
>> literals in user
>> interface screens, like UI Manager skins in Turbine.
>> Unfortunately, the
>> java.util.Properties class has a hardcoded "8859_1" encoding
>> in its load()
>> method, which makes it difficult to use property files for
>> user interfaces
>> of non-latin languages.
** CUT **
http://www.surfeu.fi
