Re: TIDs, speed, (Unicode) text
Re: TIDs, speed, (Unicode) text
- Subject: Re: TIDs, speed, (Unicode) text
- From: "Mark J. Reed" <email@hidden>
- Date: Sun, 2 Oct 2005 16:44:48 -0400
A standard 32-bit character encoding already exists - it's called
UTF-32. Full Unicode is actually 21 bits wide; it's just that most
of the already-assigned characters are in the lower 64k of the code
space and so fit in 16-bit units. Since there are reserved 16-bit
values that can be used in pairs to get the characters outside of that
range when needed, it's much more efficient in terms of space to use
UTF-16 instead of UTF-32. As RAM space gets larger that becomes less
andless of an issue, so it may not be that long before OS APIs are
using UTF-32 natively.
On 10/2/05, jj <email@hidden> wrote:
> > On Sat, 01 Oct 2005 23:46:01 +0200, jj <email@hidden> said:
> >> So, perhaps the one who noticed decreasing speed using TIDs in Tiger is now
> >> really getting Unicode text as input from its source (?).
> >
> > The same phenomenon is observable in every milieu that used to use ASCII and
> > now uses Unicode (REALbasic, Perl, etc.). When a byte and a character are no
> > longer the same thing it takes longer to cycle through a string. m.
>
> So, now someone else should invent the byte with 32 bits. Do you know if
> MacIntel ships with 32-bits bytes? ;-)
>
>
> jj
>
> --
> http://www.macscripter.net/
> http://www.osaxen.com/
>
>
> _______________________________________________
> 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
>
--
Mark J. Reed <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