[squeak-dev] leadingChar proposal

Yoshiki Ohshima yoshiki at vpri.org
Fri Aug 28 04:29:53 UTC 2009


At Thu, 27 Aug 2009 21:09:48 -0700,
Andreas Raab wrote:
> 
> What I would propose to do here is to define that "leadingChar = 0" 
> which currently means "Latin1 encoding, language neutral" is being 
> redefined to "Unicode encoding, language neutral". What this does is 
> that "Character value: 353" and "Unicode value: 353" become the same, if 
> the environment is considered language neutral which by default it would be.

  Yes, if this is the basis, many things just follow.  For Pharo
people I once suggested something similar (merging Unicode
(EncodedCharSet be =0), thinking that they are less concerned with the
backward compatibility.  There will be backward compatiblity issue
(like even loading old Etoys projects, if the Etoys packaging work is
ever done) but I think that it is mostly solvable, and probably for
bigger Squeak community it is good.

> For the CJK languages (or other languages requiring support that has 
> been so far expressed via the languag tag) we can use this opportunity 
> and phase the use of the language tag out in favor of using text 
> attributes (which would have to be written first).

  Right.

> The main advantage of the proposal is that the people who would like to 
> use plain Unicode get to use it, and the people who care about the 
> language tag and its consequences can still use that as well.
> 
> How does that sound?

  Pretty good.

-- Yoshiki



More information about the Squeak-dev mailing list