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

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Eric Wedel" <ewedel@xxxxxxxxxxx>
Date: Tue, 7 Mar 2006 16:51:54 -0800
> Should a switch to VC 7 / VS 2005 be added to the post-1.0 section of
the roadmap?

Is it worth considering MinGW, or would all Windows developers
already have the MS compiler du jour? 

-----Original Message-----
From: ethereal-dev-bounces@xxxxxxxxxxxx
[mailto:ethereal-dev-bounces@xxxxxxxxxxxx] On Behalf Of Gerald Combs
Sent: Tuesday, March 07, 2006 2:48 PM
To: Ethereal development
Subject: Re: [Ethereal-dev] patch to fix runtime problems with Visual
Studio> 6

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?
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev