Re: cString deprecated!
Re: cString deprecated!
- Subject: Re: cString deprecated!
- From: Douglas Davidson <email@hidden>
- Date: Wed, 4 Sep 2002 09:19:47 -0700
On Wednesday, September 4, 2002, at 01:17 AM, Peter Sichel wrote:
If "fileSystemRepresentation" is the best choice for encoding
the names of file system objects, might not defaultCStringEncoding
be a better choice for encoding common BSD unix API strings? [Such
as BSD interface names, or user and group names]
That is, if your program were to actually encounter a system
where the defaultCStringEncoding mattered, would using the
defaultCStringEncoding be a better choice than imposing UTF-8
with no knowledge of the user's system?
If UTF-8 is always the best choice, why not just make it the
defaultCStringEncoding? Why shift the decision to each application
developer instead of the user or API maintainer?
The default encoding is primarily intended to support existing text
files and so forth created using script-dependent encodings, e.g. Mac
Roman for English and many European languages.
UTF-8 is the encoding of choice for most BSD layer APIs.
Douglas Davidson
_______________________________________________
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.