| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Mar 30, 2004, at 11:49 PM, Jim Rankin wrote:
On Mar 29, 2004, at 7:57 PM, Shawn Erickson wrote:
You just need to read things in correctly using the correct encoding
(an encoding matching the source file).
Here's the one piece of the whole encoding puzzle that I've never been
able to figure out.
Your program is handled a file path or url that's ostensibly a text
file. From that point, how do you know the encoding of what you've
just been handed?
Probably missing something obvious...
No, you just can't without more information. That's why in TextEdit you can manually specify the encoding to use to open a file. That being said there are heuristics to guess a text encoding.
In one program I've simply used trial and error, using NSString's -initWithData:encoding: (which returns nil if it fails to create a valid string with the supplied data) and a small set of likely encodings with good results.
Or google for sniffer and encoding.
| References: | |
| >Converting ASCII to UTF-8? (From: "Huyler, Christopher M" <email@hidden>) | |
| >Re: Converting ASCII to UTF-8? (From: Shawn Erickson <email@hidden>) | |
| >Tao of string encodings (Re: Converting ASCII to UTF-8?) (From: Jim Rankin <email@hidden>) | |
| >Re: Tao of string encodings (Re: Converting ASCII to UTF-8?) (From: Marco Scheurer <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.