Wireshark · Ethereal-dev: Re: [Ethereal-dev] patch to fix runtime problems with Visual Studio > 6

[Gerald Combs <gerald@xxxxxxxxxxxx>]

Ulf Lamping wrote:

> There's a problem with Unicode chars in the filenames, therefore the
> GLib conversion functions are used since GTK2.6.
> 
> See http://wiki.ethereal.com/Development/FilenameEncoding for some details.
> 
> As Gerald has recently implemented the WIN32 native file dialogs (which
> are currently not working with Unicode chars), I'm quite unsure about
> the way to go now.
> 
> Currently we are using UTF8 internally and converting it at the "outside
> corners", just as the Unix version does.
> 
> It might be better to use locale based filenames instead of UTF8 on
> Win32, which would make the least trouble AFAIK. There's only one
> disadvantage: characters other than the current locale won't work. But
> that might be acceptable.

I'd prefer to keep Ethereal UTF8 internally.  I've been playing with
#defining UNICODE at the top of config.h.win32, and adding calls to
MultiByteToWideChar() and WideCharToMultiByte() where needed.  Is there
a better way to get the native Windows routines to handle Unicode?

(It's 2006, BTW.  Shouldn't we have scheduled a worldwide Unicode
cutover day by now?)

> In general: yes. MSVC 6 is really outdated and AFAIK no longer supported
> by MS in any way.
> 
> However, switching would mean we had to compile all the libs we use on
> our own (which I personally wouldn't like to do) or wait until all the
> libs we use provide a MSVC 7+ version (which is unlikely in the near
> future).

Should a switch to VC 7 / VS 2005 be added to the post-1.0 section of
the roadmap?