Dnia czw 3. lipca 2003 19:05, Beni Cherniavsky napisał:
> > I'm more afraid of requiring headaches from other people trying to
> > interface to C libraries.
>
> Please elaborate - interface from what to which C libraries? Do you
> mean here people writing C extensions to your langauge?
Yes. Of course it's not clear that anybody would want to use my language at
all, but if so, the choice of string representation affects interfacing with
C libraries more than anything other.
> Indeed. I wanted to ask how well should it work with the different
> versions of windows, especially win9x with it's close-to-none Unicode
> support?
I don't use Windows myself so I will be happy enough if choices made today
would potentially make i18n on Windows possible on the level of the OS itself
- i.e. if Win95 doesn't support Asian multibyte encodings, my language on
Win95 doesn't have either.
I'm pretty sure that all Windows versions since Win95 allow to convert between
UTF-16 and the encoding used for filenames, and WinNT allows to use UTF-16
filenames directly. So for filenames and the like, texts on screen, texts
exchanged with databases etc. any Unicode encoding can be made working, with
some advantage for UTF-16. I consider making this the default for Windows
because Microsoft already seems to do so. I hate UTF-16 personally but in
this case I can blame Microsoft for making harder to process characters
beyond U+FFFF. It's not harder than UTF-8 anyway.
--
__("< Marcin Kowalczyk
\__/ [EMAIL PROTECTED]
^^ http://qrnik.knm.org.pl/~qrczak/
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
