Re: Writing to file as UTF8 with BOM ?
Re: Writing to file as UTF8 with BOM ?
- Subject: Re: Writing to file as UTF8 with BOM ?
- From: Doug McNutt <email@hidden>
- Date: Fri, 27 Oct 2006 12:20:54 -0600
At 14:04 +0200 10/27/06, Yvon Thoraval wrote:
>Emmanuel wrote:
>>At 10:50 AM +0200 10/27/06, Yvon Thoraval wrote:
>>>i'de like to go further working with UTF-16 to enable working with asian "character" set (I'm an anciant chinese reader).
>>
>>Why do you expect UTF-16 to be better at that than UTF-8? Maybe you believe that UTF-8 describes less characters than UTF-16?
>yes, i don't know if i need UTF-16, just a guess. Particularly i'll use Traditional Chinese (Anciant) where their are more characters as today use.
UTF8 is fully capable of holding any characters that UTF-16 or UTF-32 support. It does it by increasing the 8-bit byte count for each character as required. Only a part of each byte is used for data. the other bits are flags to say "include the previous byte(s) with this character". For ASCII-like character sets UTF-8 produces smaller files. For Asian symbols UTF-16 will probably generate smaller files but it will not be "required".
And while I'm at it. . .
*.U08 for UTF-8 files
*.U16 for big endian UTF16
*.U61 for little endian UTF-16
*.U32 for big endian UTF32
*.U23 for little endian UTF32
Reserve *.txt, *.TXT, *.text and the like for good old ASCII. Where do the UTF guise get the idea that their formats can usurp the term TEXT? It's as bad as computer "scientists" usurping the term kilo.
It would be almost as good as the nice things like file type and creator that we are now denied.
--
--> Marriage and kilo are troubled words. Turmoil results when centuries-old usage is altered in specialized jargon <--.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/mailman//archives/applescript-users
This email sent to email@hidden