On 2013-08-06, at 01:13, tim Rowledge <tim at rowledge.org> wrote:

> 
> On 05-08-2013, at 3:34 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
>> 
>> Switching to Squeak's i18n wouldn't make sense, you should continue to use Scratch's "home-grown". To make that work, I think you only need to throw out John's explicit UTF8/UTF32 stuff and let Squeak's automatic ByteString/WideString take over. You just need to find the "edges" of the system where you need to explicitly convert to/from utf8.
> 
> Err, maybe I've misunderstood but the explicit uft8/32 stuff *is* Scratch's homegrown. So I don't see how I could continue to use that and throw it away at the same time…
> What did I miss?


You missed that I make a distinction between "i18n" (how to translate between English and Other Human Languages) and the rather technical aspect of how to represent strings with more than 8 bits per character. For both of these Scratch has a solution different from main Squeak, but I'm saying the best way forward is to use Squeak's strings with Scratch's translation framework. A third part is displaying the translated strings for which I'd continue to use Scratch's way, at least for the time being.

Hope that's more clear?

- Bert -