File names was Re: Warning: Large Babel translation

Yoshiki Ohshima Yoshiki.Ohshima at acm.org
Sat Nov 15 04:55:00 UTC 2003


  Andreas,

> What we really need here is some way to query the VM about what it expects
> to see for "strings" and use it consistently. This may be different for
> varying platforms but it would most likely be UTF8 for all windows platforms
> (since it's trivial to convert UTF8 forth and back to the underlying code
> page). So my feeling here is that the most important primitive would be
> "please, dear VM tell me what you expect to see when I'm sending or getting
> a string". Hm ... thinking about this ... I might just implement it so that
> we get started into that direction. If enough people get bitten by the
> inability to write their umlauts/accents this may trigger a force large
> enough to get the "in-image issues" solved.

  That's more like it.  The subclasses of LanguageEnvironment in m17n
package implements various case-switch like methods that are called at
start-up to determine the concrete class(es) to instanciate 'string
interpreters'.  The primitives we need is to pin-point the class,
essentially.

-- Yoshiki



More information about the Squeak-dev mailing list