Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]

• Subject: Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
• From: has <email@hidden>
• Date: Tue, 25 Oct 2005 23:54:45 +0100
• Delivered-to: email@hidden
• Delivered-to: email@hidden

Shane Stanley wrote:

> > the major "downside" is simply that it doesn't do what
> > (I thought) Shane was asking for, which was to convert from the
> > character to the code point at run-time.
>
>Right. I guess I'm asking (pleading?) for a simple equivalent to ASCII
>character and ASCII number, but hopefully capable of dealing in strings
>rather than a character at a time (thereby ruling out "simple", I guess).

See TextCommands' 'unicode characters' and 'unicode numbers' commands:

http://freespace.virgin.net/hamish.sanderson/index.html#textcommands

HTH

has
-- 
http://freespace.virgin.net/hamish.sanderson/
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-users/email@hidden

This email sent to email@hidden

• Follow-Ups:
  • Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
    • From: Shane Stanley <email@hidden>

• Prev by Date: Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
• Next by Date: Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
• Previous by thread: Re: curl equivalence
• Next by thread: Re: Producing Unicode-only characters [was: Finding \t, \r, \n reliably]
• Index(es):
  • Date
  • Thread