Re: Localizable.strings German Problem
Re: Localizable.strings German Problem
- Subject: Re: Localizable.strings German Problem
- From: Bill Cheeseman <email@hidden>
- Date: Sat, 25 Jan 2003 13:45:28 -0500
on 03-01-25 11:19 AM, Lance Pysher at email@hidden wrote:
>
Since I changed to the latest version of PB I get this error when
>
trying to run my local German version. Even if I swap replace the
>
German version with the French or English version I get the error
>
again.However the error is not generated when runningin French or
>
English mode with the same files. Has anyone else had problems with
>
German localization?
>
>
CFLog (0):
>
CFPropertyListCreateFromXMLData(): plist parse failed; the data is not
>
proper UTF-8. The file name for this data could be:
>
/Volumes/Lance Pysher's iPod 1/iRad
>
1.3.5/build/iRad.app/Contents/Resources/German.lproj/Localizable.strings
>
The parser will retry as in 10.1, but the problem should be corrected
>
in the plist.
I get this error message whenever I add a non-ASCII character to one of my
.strings files. I'm not surprised that it might crop up in a German
localization but not in English or French, due to the potential for
different characters in German.
I believe the issue is because the latest version of PB defaults to MacRoman
encoding, whereas .strings files are supposed to be UTF-16 (or UTF-8)
encoding if there is a chance you might use non-ASCII characters. This is
discussed in the PB release notes. Convert the offending file to UTF-16 (or
UTF-8) encoding, and I'll bet that error message will go away.
There is a problem changing the encoding, however. PB won't let you change
the encoding of .strings files located in a localizable subfolder, such as
English.lproj. All the choices in the Format > Encodings menu are disabled,
and the File Encodings pop-up in the Show Info window is disabled and says
"Not applicable" -- which is plainly wrong. One workaround is to temporarily
move the .strings files out into the root level of the project folder --
then the Show Info pop-up will work (although the Format > Encodings menu
items are still disabled). When you're given the choice between
"interpreting" or "converting to" the new encoding, choose "converting to."
Hope this helps.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
The AppleScript Sourcebook -
http://www.AppleScriptSourcebook.com
Vermont Recipes -
http://www.stepwise.com/Articles/VermontRecipes
Croquet Club of Vermont -
http://members.valley.net/croquetvermont
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.