[Caminol10n] Status update

[Tobias Stohr]

You can set a default setting, but I didn't even save the file in
Xcode. Just open it and it shows UTF-16 instead of the available
UTF-16BE.
I Just noticed: Xcode 2.5 doesn't offer UTF-16BE. Only 3 does.

We'll see the result...

ciao

2008/4/15 Marcello Testi <m.testi at gmail.com>:
>
>  Il giorno 14/apr/08, alle ore 20:05, Tobias Stohr ha scritto:
>
> > I just found out that iLocalize seems to be ignoring the choice made
>  > for the file encoding: while UTF-16BE is selected in iLocalize as file
>  > encoding, Xcode shows UTF-16 for the same file.
>
>  I just tried switching encoding for a file and TextWrangler detects
>  the encoding as set in iLocalize. I guess XCode has default settings
>  that override original encoding.
>
>
>
>  Ciao.
>  Marcello.
>
>  _______________________________________________
>  Caminol10n mailing list
>  Caminol10n at mozdev.org
>  https://www.mozdev.org/mailman/listinfo/caminol10n
>