Re: Re: #leadingChar (Re: The future of Squeak & Pharo))

At Wed, 01 Jul 2009 01:11:33 +0200,
Paolo Bonzini wrote:
> 
> On 06/30/2009 07:33 PM, Yoshiki Ohshima wrote:
> > At Tue, 30 Jun 2009 09:56:38 +0200,
> > Paolo Bonzini wrote:
> >> #at: is not one of them, language tags should not be skipped just like
> >> soft hyphens (U+00AD, also known as hyphenation hint) should not.
> >
> >    If #at: should return a printable character, then the resulting
> > character (really a String) with proper language tag(s) externally
> > associated should be returned from #at:.
> 
> No, characters are characters are characters.  They should not have any 
> language tag.  The language tag, if of anything, could be returned as 
> part of the style if you're working on a Text.  The default language tag 
> could be extrapolated from the current user's locale.

  Yeah, so that is why I would say, printing a character would display
just a number is even sensible.

  But what about my question in regards to #at:put: and
#replaceFrom:to?  Do you think it is feasible, if the tag is in the
string as well?

> >    You can, but it is a real major change and good luck.
> 
> I'm not planning to do this of course.

  I'm not mistaken about it.^^;

> I'm just saying that there are 
> other possibilities that (as Philippe pointed out) collaborate better 
> with the rest of the Unicode world.

  Yes.

> Maybe starting from a clean slate 
> without #leadingChar, and working things out from there, would be better 
> than forcing Han-disunification down the throat.

  Maybe.  That would be an approach, but that wouldn't have been
considered Squeak.

-- Yoshiki