Hi Andreas

Andreas Raab wrote:

> 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). 
Trivial is possibly a bit exagerated but UTF8 is surely a good 
compromise to move ahead while keeping backward compatibility to ASCII.
So the English speaking world woudn't be have to bother about our 
European, Asian and African encoding problems.

> 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. 
Yes that's a good idea but plz synchronise a bit with John McIntosh

> 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.

This is a long standing problem which needs a good solution at the base. 
UTF-8 is such a solution.

Regards
Hannes