https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1827
--- Comment #16 from Stephen Fisher <stephentfisher@xxxxxxxxx> 2008-11-02 16:16:18 PDT ---
The same problem happens on my Linux install (Fedora Core 9) as happens on
Windows. A hexdump of the ~/.wireshark/smi_paths on MacOS X shows that it
appears to be storing the character as two bytes, but I don't see how it is
working other than MacOS 10.5 is very unicode compliant (may need to copy and
paste this into a fixed width font window):
00000000 23 20 54 68 69 73 20 66 69 6c 65 20 69 73 20 61 |# This file is a|
00000010 75 74 6f 6d 61 74 69 63 61 6c 6c 79 20 67 65 6e |utomatically gen|
00000020 65 72 61 74 65 64 2c 20 44 4f 20 4e 4f 54 20 4d |erated, DO NOT M|
00000030 4f 44 49 46 59 2e 0a 22 2f 74 6d 70 2f 72 c3 a9 |ODIFY.."/tmp/ré|
00000040 73 65 61 75 22 0a |seau".|
00000046
This is looking like another one of those issues that is caused by us not using
unicode or character set specific strings to hold everything in :(.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.