gedit cannot automatically recognise document character encoding

Bug #557571 reported by igi on 2010-04-07
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Fix Released
gedit (Ubuntu)

Bug Description

Binary package hint: gedit

In my Ubuntu 10.04 Lucid Lynx beta1 installation, gedit does not automatically select the proper character encoding.
If I try to open a text document created with Windows (ISO 8859-15) the error status bar is shown instead of opening the document. So I have to manually select the original encoding and then the document is opened.

Till Ubuntu 09.10 (Karmic) GEdit worked properly.

Architecture: i386
DistroRelease: Ubuntu 11.04
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Package: gedit 2.30.4-2ubuntu1
PackageArchitecture: i386
 PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae
Tags: natty running-unity
Uname: Linux 2.6.38-8-generic-pae i686
UpgradeStatus: Upgraded to natty on 2011-04-29 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

igi (igor-cali) wrote :
Sebastien Bacher (seb128) wrote :

thank you for your bug report, could you add an example to the bug?

Changed in gedit (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
igi (igor-cali) wrote :

Here the screenshot attachment.
This is how gedit lloks when I try to open txt files created with Windows (different encoding).
At that point, selecting UTF8 encoding from the drop-down list (the one localized with the label "Riconoscimento automatico), and then clicking on the retry button, the document is properly shown.

This manual selection task has not to be done in Karmic.

Sebastien Bacher (seb128) wrote :

sorry if the previous comment was not clear but an example would be a file having the issue not a screenshot

igi (igor-cali) wrote :

Wooops, sorry ;>)
Here it is!

Changed in gedit (Ubuntu):
status: Incomplete → Triaged
Changed in gedit:
status: Unknown → New
Changed in gedit:
importance: Unknown → Medium
igi (igor-cali) on 2011-03-26
tags: added: maverick

apport information

tags: added: apport-collected natty running-unity
description: updated
description: updated
Alberto Torres (kungfoobar) wrote :

Also, gedit should open text files even if it can't recognize the encoding. If there is a bogus character in the file, that renders the file unopenable in gedit! The default and frequently the ONLY plaintext editor w/gui in ubuntu!

Oliver Joos (oliver-joos) wrote :

I agree that there should be at least an option to "open as ascii-bytes" or something.

@Alberto: If you want your wish to be heard you should open a new bug report about that - preferably on directly (if there is not already one). As alternative try the "scite" text editor.

dino99 (9d9) on 2013-05-29
tags: removed: maverick
tags: removed: natty
Changed in gedit:
importance: Medium → Wishlist
status: New → Confirmed
tags: added: trusty
Changed in gedit:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.