> >One of my crazy ideas is how to solve the internationalization problem.
> >Use extended ASCII or some now 8-bit-wided character set, and declare
> >English to be the official international language of the platform. Screw
> >this Unicode crap.
> Great idea, Geoff. Oh, wait, there is already such a system... I think it
> starts with a U, the there's an X in the back...
And to make it worse, they introduced dozends of 8 Bit codes ...
> I welcome Unicode. Everyone should, since it would solve this
> internationalisation problem.
Jep. Unicode is, for most circumstances a real relif.
Even when you still do 8 Bit systems (8 Bit character
sets) it will help a lot - for example we can't convert
our application to 16 Bit characters, since on the /370
part this would require more than a few lines of code.
On the other hand we had to support different code sets
in different installations (from Arabic and Cyrillic
to Greek and Turkish and of course the funny French/
Spanisch accented caracters) while still manage a common
code base and online data exchange. Unicode did give us
a good base to define our codesets as subsets and to define
interchange rules.
Back to File Name Translation: does someone remember the
name translations GSOS 6 on the Apple did when reading
DOS or ProDOS Files ? AFAIR in DOS/ProDOS any character
was allowed in the file name.
Gruss
H.
BTW: the 9900 looks like a great Unicode machine - eventualy
one should drop all this unnecersary byte operation :)
--
VCF Europa 3.0 am 27./28. April 2002 in Muenchen
http://www.vcfe.org/
Received on Mon Jul 30 2001 - 05:53:01 BST