Re: Bad Characters from Unicode
Re: Bad Characters from Unicode
- Subject: Re: Bad Characters from Unicode
- From: Doug McNutt <email@hidden>
- Date: Thu, 4 Oct 2007 18:46:52 -0600
At 02:13 +0200 10/5/07, Sander Tekelenburg wrote:
>And then I'd think that it's easier for most people to
>use something like file names ("index.utf8.html"). The syntax is easier to
>remember, and it can be used for all file types, not just HTML files.
>
>Returning to AppleScript: when you write text to a file, you could save it as
>filename.utf-16.txt (utf-16 being the default since Mac OS X). Or when you
>explicitly use some other character encoding, call it filename.utf-8.txt, or
>filename.mac-roman.txt. If you do that consistently you'll have an easier
>time working with those files later.
Best of all would be clearly setting the type codes to something other than TEXT and make everyone else in the world use Apple's HFS+ filing system.
Given that that would be difficult, why not
1) STOP using .txt, .TXT, .TEXT and similar for ANY unicode files.
The unicode folks are the newcomers. They have no right to steal old usage of words. (Well, the computer science folks did ruin the standard for a kilo. Sigh.)
2) Create some standards like:
.U08 for UTF-8 format
.U16 for UTF-16 format with net-standard (big endian) byte order
.U61 for UTF-16 with dyslexic ordering the opposite of what we do when we put volumes on a bookshelf but perhaps correct when we place the last page of volume 1 close to the first page of volume 2.
.U32 and .U23 for the others.
Perhaps AppleScripters could get together and make it happen.
--
--> Halloween == Oct 31 == Dec 25 == Christmas <--
_______________________________________________
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/archives/applescript-users
This email sent to email@hidden