Re: Accentued chars in EOGenerator variables

On 10 nov. 2010, at 01:46, Pascal Robert wrote:

> 
> Le 2010-11-09 à 19:38, Dev WO a écrit :
> 
>> Hello Pascal,
>> 
>> I'm not sure I understand it correctly. Are you saying the strings are written directly into the Java file?
> 
> Not directly, it's EOGen who write them.

So I'm not sure where do you get the strings from? database? Actually I would use a localizable string for this, coming from your Localizable.strings file.

Xavier

> 
>> If so, I think there's something wrong with UTF-8 Java file and accentuated strings. You have to get the string out to a text file in UTF-16 to have it work.
> 
> All our Java classes are in UTF-8, the only thing in UTF-16 we have is the Localizable.strings files. 
> 
>> Not sure if it's what you are looking ofr,
>> 
>> Xavier
>> 
>> 
>> 
>>> We are moving from WOLips 3.3 to WOLips 3.6 (v 3.6.6208), and I found a last minute problem. EOGenerator in the past was using ISO-Latin-1, but I think a year ago it was moved to UTF-8, which is good. So I changed the encoding of our templates to UTF-8, and that's fine. The problem is is that we have EOGenerator variable with value is :
>>> 
>>> Copyright © 2009, ACAIQ, Tous droits réservés.
>>> 
>>> It was still encoded in ISO-Latin-1 so I changed it, but when I generate the EOs, the copyright shows up like this :
>>> 
>>> Copyright © 2009, ACAIQ, Tous droits réservés.
>>> 
>>> If I open the .eogen file in BBEdit, I do see correctly and the file is really encoded in UTF-8, so I don't know why the variable content show up badly in the Java class :-( It's only the variable who is problematic, the accentued chars in the templates show up just fine.
>>> 
>>> Anyone having the same problem?
>>> 
>> 
> 
>