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 351627 - meld chokes on directory name with wrong character encoding (Wine)
meld chokes on directory name with wrong character encoding (Wine)
Status: VERIFIED DUPLICATE of bug 168760
Product: meld
Classification: Other
Component: dirdiff
1.1.x
Other All
: Normal normal
: ---
Assigned To: Stephen Kennedy
Stephen Kennedy
Depends on:
Blocks:
 
 
Reported: 2006-08-16 13:58 UTC by André Heynatz
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Heynatz 2006-08-16 13:58:02 UTC
Please describe the problem:
I have tried a configuration merge for Wine. A directory diff does not show all differences, if a directory name with wrong character encoding is part of one branch. On one side, in directory "All Users" there are "Start Menu" entries, one having a '?' in it, shown in a caret (no visual representation possible). If I remember right, it is the copyright symbol, in a Windows encoding. meld should not choke on that and continue with comparing the branches.


Steps to reproduce:
I don't know how to create such funny directory names. Changing the LANG variable let me show a '?' instead of a caret with '?' inside, but it does not change meld's behavior.
Installing Wine 0.9, then Might & Magic VI, copying away .wine, then updating to a recent version, diffing .wine and old .wine would reproduce it, but it is difficult to get the application which creates the name!


Actual results:
Differences are not shown from that point on.

Expected results:
All differences are shown.

Does this happen every time?
With this special file, yes.


Other information:
Better error handling might help, if the Python interpreter is able to detect it. This is more of a Wine problem because it does not map the charset correctly, but I wondered quite some time what is going on here.
Comment 1 Stephen Kennedy 2006-08-17 20:09:44 UTC
This looks like a dup. We need bug 350801 to be fixed.

*** This bug has been marked as a duplicate of 168760 ***
Comment 2 Stephen Kennedy 2006-11-19 11:06:06 UTC
Batch close of old bugs.