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 155887 - queryimmodules.c: Replacing backslashes is breaking DBCS
queryimmodules.c: Replacing backslashes is breaking DBCS
Status: RESOLVED DUPLICATE of bug 150731
Product: gtk+
Classification: Platform
Component: Backend: Win32
unspecified
Other All
: Normal minor
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2004-10-19 21:02 UTC by Kazuki Iwamoto
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kazuki Iwamoto 2004-10-19 21:02:06 UTC
Please describe the problem:
The fix for Bug-152608 occurred the new problem.
In codepage 932, second byte of double-byte characters can be a backslash.
(Maybe codepage 936 and 950 is also...)
If replace backslashes in path, DBCS are broken.

For exsample of DBCS, analyse this Japanese path...
"C:\\document\\\x90\x7d\x95\x5c1.txt"
(43 3A 5C 64 6F 63 75 6D 65 6E 74 5C 90 7D 95 5C 31 2E 74 78 74)

Folder -> "C:\\document\\" (43 3A 5C 64 6F 63 75 6D 65 6E 74 5C)
Filename -> "\x90\x7d\x95\x5c1.txt" (90 7D 95 5C 31 2E 74 78 74)

Last backslash is NOT separator.
\x95\x5c (95 5C) is displayed as one character.


Steps to reproduce:
1. make folder whose name is DBCS which has a backslash.
2. install GTK+ in this folder
3. run gtk-query-immodules-2.0.exe


Actual results:
Paths are broken.

Expected results:


Does this happen every time?
codepage 932, 936 and 950

Other information:
Comment 1 Tor Lillqvist 2004-10-19 21:18:42 UTC
Yeah, well, I don't think we can do much about this right now. See also bug 
#101792. gtk-query-immodules-2.0.exe isn't really supposed to be run blindly 
without manually checking and correcting the output, at least not on Windows...
Comment 2 Tor Lillqvist 2004-10-20 07:13:50 UTC

*** This bug has been marked as a duplicate of 150731 ***