Re: iso-8859-1 over UTF8 (was: Re: cString deprecated!)
Re: iso-8859-1 over UTF8 (was: Re: cString deprecated!)
- Subject: Re: iso-8859-1 over UTF8 (was: Re: cString deprecated!)
- From: Andrew Pinski <email@hidden>
- Date: Tue, 3 Sep 2002 00:17:43 -0400
On Monday, Sep 2, 2002, at 23:57 US/Eastern, Allan Odgaard wrote:
On tirsdag, sep 3, 2002, at 01:30 Europe/Copenhagen, Charles Srstka
wrote:
UTF8String is probably the best way to go - to the best of my
knowledge UTF8 is the same as plain ASCII encoding whenever special
characters aren't involved [...]
Yes, every 7 bit character keep its normal encoding.
However most of Europe make heavy use of accented letters and other
stuff which in iso-8859-1 is placed in the range of 160-256.
So what if I knew Japanese what would happen then when you try to
convert the string to iso-8859-1 aka Latin 1.
The entire BSD layer in OS X is also geared toward iso-8859-1, not to
mention that this has been the de-facto standard on all other
platforms than Mac for the last 10-20 years, and I also believe it to
be promoted somewhere as the internet standard (whatever that means).
The Mac used their own encoding because if I remember correctly there
was no standard when Apple made accents available in 1984.
Also Microsoft used their own encoding too because there was no
standard but they changed to the standard with some additions to which
were undefined in the standard aka `Windows Latin 1'.
Also the entire BSD layer in OS X is not geared towards iso-8859-1, it
is geared towards ASCII which is 7bits also the BSD layer does not care
about what encoding you used, except for file names because HFS+
requires them to be in UTF-8 with some other stuff (I forgot what).
In fact in the old days, modems and Internet connections were only 7bit
and that is why there exists programs such as HQX and uuencode.
Apple made an UTF-7 encoding for machines which could not handle 8bit
characters look for it is an RFC.
Thanks,
Andrew Pinski
So whenever I need a "char *" then I always go for iso-8859-1.
Why, just go for UTF-8 and files will work correctly and has the
ability to handle other languages than Roman/German based ones like
Japanese, Chinese, Korean, Arabic and other ones.
If for some reason you really need an iso-8859-1 encoded string go for
it but there should not be a reason for it except to send someone else
the string to be able to decode it right.
Thanks,
Andrew Pinski
--
http://www.diku.dk/students/duff/
_______________________________________________
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.
_______________________________________________
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.