After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 150731 - GTK+ should be double-byte charset aware for filenames on Windows
GTK+ should be double-byte charset aware for filenames on Windows
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.4.x
Other All
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
: 155887 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-08-21 17:13 UTC by Tor Lillqvist
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tor Lillqvist 2004-08-21 17:13:22 UTC 
See the text in bug #150730. The same issue presumably occurs in GTK+ code that 
handles filenames in the system encoding.
Comment 1 Owen Taylor 2004-08-21 18:23:11 UTC 
IMO, you should WONTFIX this and make the "system encoding" UTF-8 as discussed,
though perhaps it is relevant for the gtk-2-4 branch.
Comment 2 Tor Lillqvist 2004-08-21 18:57:20 UTC 
Hmm. Because of bug #150394 and bug #141124, which presumably have pretty much 
prevented GTK+ apps from working at all with CJKV file names on East Asian 
Windows machines, it's hard to say whether the double-byte and backslash thing 
is an issue or not.

(Maybe not. The "gtk-1-3-win32-production" GTK+ 1.3.0 branch certainly didn't 
contain any double-byte aware code, and it apparetly has been quite widely used 
(with GIMP 1.2.x) in Japan. Not that that proves anything.)
Comment 3 Tor Lillqvist 2004-10-20 07:12:39 UTC 
This is relevant for the 2-4 branch, so let's keep it open. In 2.6, the plans 
to fix #101792 will take care of this issue, as GLib and GTK+ won't manipulate 
filenames in the local codepage (multibyte) any longer.
Comment 4 Tor Lillqvist 2004-10-20 07:13:54 UTC 
*** Bug 155887 has been marked as a duplicate of this bug. ***
Comment 5 Tor Lillqvist 2004-12-11 22:09:02 UTC 
Resolving as WONTFIX. 2.6 with UTF-8 is here Real Soon Now, fixing this won't 
happen for 2.4.