Re: Finding \t, \r, \n reliably
Re: Finding \t, \r, \n reliably
- Subject: Re: Finding \t, \r, \n reliably
- From: Shane Stanley <email@hidden>
- Date: Tue, 25 Oct 2005 08:02:24 +1000
- Thread-topic: Finding \t, \r, \n reliably
On 25/10/05 2:42 AM, "Christopher Nebel" <email@hidden> wrote:
> If you feed them something that's not
> representable in that encoding -- say, an aleph in MacRoman -- the
> results are not defined.
I guess that's what I meant by "nasty" -- they don't return an error even
though they can't handle the input correctly. I'm mildly surprised I can't
find this definition of "nasty" in tn2106.
> There is no official way to convert between Unicode code points and
> characters in AppleScript
There's no way to _tell_ if a character is ASCII or in the Unicode range. I
mean, you could always try to get the ASCII number and see if that...ooops.
--
Shane Stanley <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden