GNOME Bugzilla – Bug 574535
Cannot open xchat-gnome log file
Last modified: 2011-01-31 21:52:02 UTC
I've received an xchat-gnome log file. Opening it with Gedit displays a lot of binary garbage and chinese characters. Opening the exact same file with less, vim or Abiword works fine.
Created attachment 130270 [details] xchat-gnome log file
This file contains 0 bytes and when gedit tries to autodetect the encoding of the file, it seems utf-16 can convert it to something seemingly valid. Opening this with other encodings results in invalid conversions.
What do you mean by "0 bytes" ? The file contains all the log which is more than 0 byte (I admit that the interesting bits in the log might be 0 though ;-) I also reported the bug in xchat-gnome: http://bugzilla.gnome.org/show_bug.cgi?id=574537
I meant that it containes the byte '\0' before several new line bytes. At this time, gedit cannnot handle 'incorrect' files (e.g. which cannot be fully converted to utf-8). What we should do in this case is convert these broken bytes to something, and open the file read only so the user can still see it. Other people have complained about this iirc (also for opening binary files), but at the moment gedit cannot open these files.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 502947 ***