[solved] Re: plist file and encoding format problem
[solved] Re: plist file and encoding format problem
- Subject: [solved] Re: plist file and encoding format problem
- From: Stéphane Sudre <email@hidden>
- Date: Mon, 26 Nov 2001 19:03:47 +0100
Le lundi 26 novembre 2001, ` 01:44 , Stiphane Sudre a icrit :
On samedi, novembre 24, 2001, at 04:51 , Chris Kane wrote:
'&' is needed because XML reserves '&' for special purposes. I
tried:
[...]
and got an array with an NSString "&foo;". You should make sure
you're storing the file (if you're editing it by hand) in the encoding
named in the encoding= directive in the XML banner. If there is no
encoding= and the file doesn't look like Unicode with a few tests,
UTF-8 will be assumed. If the encoding is an encoding unknown to
NSString/CFString, UTF-8 may be assumed too. Just use either plain
7-bit ASCII, or UTF-8, if in any doubt.
I'm currently making some test: writing the plist with the
CoreFoundation APIs and it's working.
I don't know what is happening with the problematic files. It might be
because of the numerous manipulations of the files between PB and the
Property List Editor and TextEdit...
The solution was simple.
I was moronly getting the text version of my strings instead of the html
version. I realized this when I changed the text in the file and it
didn't show in the result.
Stupid me.