Re: en-dash, em-dash, and the like
Re: en-dash, em-dash, and the like
- Subject: Re: en-dash, em-dash, and the like
- From: Mitchell L Model <email@hidden>
- Date: Tue, 21 Jun 2016 14:58:21 -0400
| I thank everyone who has contributed to this discussion. I think I understand what’s going on now. (On the other hand I thought I understood what was going on before I encounter,ed Unicode in Safari tab names :-). What is so wonderful about Unicode is all the ways you can get tripped up by it.) I take away two lessons from this discussion: (1) Use "as «class utf8»” in AppleScripts that are writing to a file text that might contain non-MacRoman characters (2) OS X Applications differ as to how they handle non-MacRoman characters in both unencoded and UTF8-encoded files. Anyone want to add anything to that?
Once I pulled my scattered thoughts and haphazard posts together, I redid some of my experiment methodically. I wrote a gist summarizing the results of these experiments with different apps handling both encoded and unencoded files written from my AppleScript. It shows what each of several applications do with each kind of file for the three characters I have been using as examples in the discussions here. There are a few sidenotes in the gist, including the interesting things that happen when you add <html> to the beginning of a text file and go to save it.
|
_______________________________________________
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