Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 2513] New: compilation failure on non-european windows ( due to non-ascii char

[bugzilla-daemon@xxxxxxxxxxxxx]

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2513

           Summary: compilation failure on non-european windows (due to non-
                    ascii characters)
           Product: Wireshark
           Version: SVN
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: suz@xxxxxxxx


Build Information:
TShark 1.0.99-SVN-SUZ-20080419 (SVN Rev unknown)

Copyright 1998-2008 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GLib 2.16.1, with WinPcap (version unknown), with libz 1.2.3,
without POSIX capabilities, with libpcre 7.0, with SMI 0.4.5, with ADNS, with
Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT Kerberos.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5.

Built using Microsoft Visual C++ 8.0 build 50727

--
There are some non-ASCII characters in the following files.
- gtk/capture_if_details_dlg_win32.c
- epan/t35.c
- epan/dissectors/packet-e212.c

Since this leads to a compilation failure (Warning C4819: unexpected character
in the current code page) on non-european Windows, I'd like you to avoid using
non-ASCII characters in Wireshark code (even in comment).

Here's a patch to cope with this problem.  (I'd like you to confirm whether my
fix is appropriate in terms of German/French, since I'm not so familiar to
these languages.)


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.