[etoys-dev] composition input change

K. K. Subramaniam kksubbu.ml at gmail.com
Thu Oct 14 21:15:26 EDT 2010

On Friday 15 Oct 2010 1:23:10 am Bert Freudenberg wrote:
> What I'm worried about is this: If the locale is "de_DE.UTF-8" then the
> image will use Latin1Environment and UTF32InputInterpreter. That
> interpreter expects either a utf32 keycode or MacRoman. But if the VM now
> sends UTF-8 instead of setting the utf32 field, it would break, no?
Recent VMs generate keycodes in evtBuf sixth taking encoding into account for 
latin-1 but not Indic languages. In 
M17nInputInterpreter>>nextCharFrom:firstEvt:, I check for evtBuf sixth before 
falling back to UTF-8 so it should not affect Latin-1 input.

In any case, compositionInput uses direct method by default. For instance, I 
use UIM which defaults to direct method (us_intl layout). When I need to type 
an Indic character, I press SHIFT-CTRL to switch languages and SHIFT-SPACE to 
toggle on composite encoding for three-byte Indic characters and toggle it off 
for accented characters like ü or é.

If you have access to de_DE.UTF-8 systems, please give M17n a try. Just turn 
on composition input and add 'de' to M17nEnvironment>>supportedLanguages and 
    LanguageEnvironment resetKnownEnvironments; clearDefault.
    HandMorph clearInterpreters.

If input breaks, it is a major defect.


More information about the etoys-dev mailing list