GNOME Bugzilla – Bug 574537
Exporting log produces file that cannot be opened by gedit.
Last modified: 2009-11-18 19:10:30 UTC
It seems that log produced by xchat-gnome are not valid files. They can be opened by less or Abiword but not gedit. The bug in gedit : http://bugzilla.gnome.org/show_bug.cgi?id=574535
Created attachment 130272 [details] xchat_log try to open that log with gedit
It's valid UTF-8 at least. I can repro the problem; gedit seems to mistake it for chinese text, and if run with gedit --encoding=utf-8 it doesn't want to open it. Gedit bug?
Jesse said that the file was not valid (see the linked bug). Honnestly, I don't know that's why I reported it for both.
I can repro this and confirm this bug. Gedit and Geany both won't display the file correctly, where Abiword will.
I am not able to reproduce this with latest release of xchat-gnome. What is the language setting being used ?
I am using US English (en_us)
hi, How does one reproduce this issue ?
To reproduce: I save a log from Discussion -> Save Transcript, and save the file. I then double click to open with Gedit and get: gedit has not been able to detect the character coding. Please check that you are not trying to open a binary file. Select a character coding from the menu and try again. Character coding: Current Locale (UTF-8) with an option to change to: Western (ISO-8859-15) Which also doesn't work. I will attach a log of the #docs channel on GIMPNet which I just saved. Only Abiword seems to open the log correctly.
Created attachment 148059 [details] Xchat log
Created attachment 148067 [details] Log from #gnome on GIMPNet using Xchat-gnome After building Xchat-Gnome from git, Gedit will now open the log files, but displays the text as Chinese or Japanese characters. Trying to open a log with gedit --encoding=utf-8 \#gnome-2009-11-18-12h55.log does not work and displays the error in Gedit: Could not open the file /home/pcutler/#docs-2009-11-18-12h51.log using the Unicode (UTF-8) character coding
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report. If you still see this issue, you would need to "scrub" the older log files of "0x00". You can run the below command , courtesy of Stric for f in .xchat*/xchatlogs/*; do perl -pi -e 's/\0//g' "$f"; done