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 164795 - Gedit shall point at bad characters when loading/saving a file with a specific encoding
Gedit shall point at bad characters when loading/saving a file with a specifi...
Status: RESOLVED FIXED
Product: gedit
Classification: Applications
Component: general
3.2.x
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
: 324610 615106 641460 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-01-21 05:36 UTC by Yukinoroh
Modified: 2014-08-11 20:35 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Yukinoroh 2005-01-21 05:36:38 UTC 
I'm trying to edit a log file that is encoded into EUCJS Japanese encoding. I
select the proper encoding in the Open file dialog, and then Gedit tells me that
I don't have the proper encoding and stops there. It's annoying because it
doesn't tell me where in the file the problem is... It would be nice that Gedit
open the file anyway, and point at (like, highlight) the problematic parts of
the text, so that the user can fix them and then the file could be saved
properly. Currently, to compare, Kwrite can open that kind of file, but it will
refuse to save it. (I still don't know where the problem is...)
Comment 1 Yukinoroh 2005-01-21 07:16:14 UTC 
The same kind of feature would be helpful for saving files... If you insert only
one "bad" character in a huge file, it will refuse to save and won't tell you
where the character is...
Comment 2 Paolo Maggi 2005-01-21 13:42:54 UTC 
Nice idea.
I think we could behave like KWrite but pointing the user to the problematic
point in the text if the number of errors are small. 
In the case the number of errors is big we could suggest to open the file with
an hex editor as suggested by another bug report.
Comment 3 Paolo Borelli 2005-12-29 09:18:59 UTC 
*** Bug 324610 has been marked as a duplicate of this bug. ***
Comment 4 André Klapper 2012-08-01 12:14:58 UTC 
Still valid in 3.2
Comment 5 André Klapper 2012-08-02 09:15:56 UTC 
*** Bug 615106 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2012-08-02 09:34:41 UTC 
*** Bug 641460 has been marked as a duplicate of this bug. ***
Comment 7 Sébastien Wilmet 2014-08-11 20:35:46 UTC 
Invalid characters are highlighted with a red background color, and are displayed with their corresponding hexadecimal values.