Re: [Lynx-dev] UTF-8 MS Windows

[Thorsten Glaser]

Gisle Vanem dixit:

> The MS-convention (as we all know?) is that LPTSTR etc. maps to 'char *'
> or 'wchar_t *' depending on ASCII (default) or UNICODE. But the lynx-sources
> can never accept building with '-DUNICODE' because of such errors shown 
> above. 

Lynx doesn’t use wchar_t (UCS) but rather multibyte strings in
some given encoding – here, UTF-8. In my experience, it is
virtually impossible to use Windows® console applications
with UTF-8, since, to do this right, one has to use the Wide
char interface.

As Tom said: the curses library has to do the translation here.
This amounts to a complete rewrite of the curses library. It is
important that the curses library would also *not* use -DUNICODE
but rather call the various FooW() library functions directly,
because it would be called from code that does not use -DUNICODE
and has to retain API compatibility there.

bye,
//mirabilos
-- 
ah, that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour