On 05.05.2008, at 18:20, Jens Alfke wrote:
I find it safest to go with the Windows encoding, because it's a
superset of both ASCII and ISO-Latin-1 that maps all 256 characters,
so it never returns nil. It's also the default encoding on Windows,
so there's a lot of text out there in the wild encoded with it.)
As the OP wants to create NSStrings with data created by his
application I'm pretty sure he will not want the the Windows encoding
- unless he parses text documents originating from Windows.
If the bytes come from MacOS text files he may want to use the
MacRoman encoding, otherwise creating UTF8 and passing around
NSStrings will be the way to go - especially in Europe where all that
äöüñá goodies exist.
Regards,
Tom_E
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
