Re: linebreak in a shell script; was Re: What's wrong with this call to zip?
Re: linebreak in a shell script; was Re: What's wrong with this call to zip?
- Subject: Re: linebreak in a shell script; was Re: What's wrong with this call to zip?
- From: Doug McNutt <email@hidden>
- Date: Thu, 28 Feb 2008 15:24:16 -0700
At 08:29 +1100 2/29/08, Shane Stanley wrote:
>Be aware that there are some differences, though. Specifically, characters
>that aren't actually ASCII characters, like curly quote marks or chevrons,
>for example, return the MacRoman encoding number with ASCII number, but
>return the proper Unicode code point with id.
>
>Also, a linefeed following a carriage return is a single Unicode character
>(with two code points), so code using text item delimiters to do conversions
>may no longer work.
So what are Apple's future plans for more complete implementation of unicode "text" in AppleScript?
U+2028 is a line separator
U+2029 is a paragraph separator
Are we going to worry about those one day? Are they in use anywhere already? In a file name for instance? They certainly won't ever have an ASCII value as an unsigned char.
Is \r\n really a "single" unicode character U+0D0A? That seems to be undefined in OSX's international panes. Are those "two code points" really a 32 bit unicode value U+000D000A ?
--
--> Life begins at ovulation. Ladies should endeavor to get every young life fertilized. <--
_______________________________________________
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