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 728181 - Encoding auto-detection problem when the file contains Null characters
Encoding auto-detection problem when the file contains Null characters
Status: RESOLVED WONTFIX
Product: gtksourceview
Classification: Platform
Component: File loading and saving
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
Depends on:
Blocks:
 
 
Reported: 2014-04-14 13:42 UTC by Vít Ondruch
Modified: 2018-05-26 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Textfile with Null characters. (7.94 KB, application/octet-stream)
2014-04-14 13:42 UTC, Vít Ondruch 		Details

Description Vít Ondruch 2014-04-14 13:42:50 UTC 
Created attachment 274271 [details]
Textfile with Null characters.

This seems to be poor idea to enter Null characters into supposedly text file, but GEdit should display something more useful then bunch of Chinese characters.

$ rpm -q gedit
gedit-3.10.3-1.fc20.x86_64

BTW I reported the error to the authors of RubyGems: https://github.com/rubygems/rubygems/issues/883
Comment 1 Vít Ondruch 2014-04-14 13:46:46 UTC 
BTW you can use less or vim to display the content of the file, since gedit cannot handle it ;)
Comment 2 Sébastien Wilmet 2014-04-14 14:13:42 UTC 
If you explicitly open the file in UTF-8, it works as expected. The problem is with the encoding auto-detection.
Comment 3 Sébastien Wilmet 2018-05-26 14:04:12 UTC 
It's unlikely that this feature is ever going to be implemented, so I close the bug.