>> Date: Mon, 8 Sep 2008 20:40:29 -0700
>> From: Mike Dougherty <email@hidden>
>> Subject: Re: Internationalization help
>> To: OSX Java-dev <email@hidden>
>> Message-ID: <email@hidden>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Sorry, my bad. I'm used to using UTF-8 on things so I wrote that, but
>> meant to write unicode. I've run native2ascii on the file and ended up
>> with the following unicode:
>>
>> button.cancel=\u201e\u00c7\u2260\u201e\u00c9\u00a3\u201e
>> \u00c9\u2265\u201e\u00c7\u00aa\u201e\u00c9\u00b4\u201e
>> \u00c5\u00f4\u201e\u00c7\u00e3
I've translated applications to multiple languages in the past, but all of them used the latin alphabet so I'm not familiar with this problem. I have to say that it appears completely ridiculous to me that you have to write property files like this. Ideally you would have the translator just open a text editor and type in the translations...
-- Dennis Bijlsma
<<winmail.dat>>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
