meyers8686 / plist

Automatically exported from code.google.com/p/plist
0 stars 0 forks source link

non-ascii UTF-8 not parsed correctly #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Compile TestPList.java
2. Run it in a directory with Info.plist

What is the expected output? What do you see instead?

correct output:
75 105 100 8217 115 32 105 80 104 111 110 101

current library output:
75 105 100 8218 196 244 115 32 105 80 104 111 110 101 

the 8218 196 244 part is wrong.  That should be just 8217.

What version of the product are you using? On what operating system?

svn head, OSX 10.6.5, JRE build 1.6.0_22-b04-307-10M3261

Please provide any additional information below.

Patch: just replace the body of NSString(NSString) with "content = string".  
I'm not sure what the code you have there is intended to do, but it breaks 
straightforward UTF-8 reading.

Original issue reported on code.google.com by keith.ra...@gmail.com on 20 Mar 2011 at 3:49

Attachments:

GoogleCodeExporter commented 9 years ago
Fixed in r10. The code used there is intended to make sure that the string was 
stored in UTF-8 format, even if the parsed PList was not.

Original comment by daniel.dreibrodt on 17 Apr 2011 at 5:48

GoogleCodeExporter commented 9 years ago

Original comment by daniel.dreibrodt on 25 Sep 2014 at 5:51