Hi Paulo,

On Mon, Jun 29, 2009 at 2:13 AM, Paolo Bonzini <bonzini at gnu.org> wrote:

>
>  And don't get me "but we need it for fonts". The only way to get nice
>>>>> fonts in Squeak is to avoid it and do it in C with char*.
>>>>>
>>>>  This is a very confused statement.  You better pass the font and
>>>> language information to the outside renderer to get the proper result.
>>>>
>>> I agree but you don't know how often I have gotten this answer when I
>>> suggested to simply drop #leadingChar.
>>>
>>
>>   Maybe you get the answer often because it makes sense?  I wrote this
>> a few times in last some years but if the goal is to make a
>> comprehensible personal computer environment, some information is
>> needed more than Unicode code points provides.
>>
>
> You're free to have your opinion on Han unification.  Many people share it,
> many people don't.  But the fact is, only Squeak does it this way and it
> does have as many problems as it solves.
>
> For another way to encode languages see
> http://www.isi.edu/in-notes/rfc2482.txt.


On reading this my first question us "what should at: do?".  Have you
thought this through?  Does at: have to search for TAG marks and skip over
them, or is the problem punted up to the client?  If TAGs are hidden how
does one find what TAGs are?  Are there two classes, TaggedUnicodeString and
UntaggedUnicodeString? etc...


>
> Paolo
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20090629/834269d9/attachment.htm