Anyway, this all relates to Subversion thusly:
There will be a default assumed encoding (whether UTF-8 or UTF-16 we
don't have to hash out now). But, a property can indicate that a
different encoding is being used, if/when that can't be told by
inspection. Thus, we will be able to do keyword substitution no
matter what.
-K
"Bill Tutt" <billtut@microsoft.com> writes:
> No it's not. UCS-4 has been limited to the # of bits encodeable by
> UTF-16.
> UTF-8 is arbitrarily expandable if you so wished.
>
> Bill
>
> -----Original Message-----
> From: Karl Fogel [mailto:kfogel@galois.collab.net]
> Sent: Thursday, December 21, 2000 1:41 PM
> To: Mo DeJong
> Cc: dev@subversion.tigris.org
> Subject: Re: UTF-8 (was: Re: property names)
>
> Karl Fogel <kfogel@galois.collab.net> writes:
> > In other words, there is no limit on the size of the Unicode character
> > set, but every time they add characters past a certain boundary, the
> > UTF encodings need to be updated so people know how to encode the new
> > ranges.
>
> Actually, that last part is probably wrong. The UTF-* encodings were
> planned from the beginning to handle numbers of arbitrary size.
>
> Think before post,
> -K
Received on Sat Oct 21 14:36:18 2006