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 594544 - gedit shows strange characters if file will be saved with different encoding
gedit shows strange characters if file will be saved with different encoding
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2009-09-08 20:07 UTC by Leandro Martínez
Modified: 2018-04-14 23:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Leandro Martínez 2009-09-08 20:07:49 UTC
1 - Open Gedit (Accessories -> Text Editor)
2 - Save the file (empty or not), lets say, with the name "test.txt"
    at this point, the Character Coding is set to UTF-8. Save the file.
3 - Click on "Save As", change the character coding below, in my case
    the option is Western (ISO-8859-15). Choose the same name as before.

Result: The box warning about the existence of the file is open and
        strange characters appear in the place of the file name.

See this image: http://bugzilla.gnome.org/attachment.cgi?id=142487

This occurs in at least two different machines running Ubuntu Jaunty,
one 32 bits and other 64 bits, both of them with full up-to-date
systems.

It seems that I have the gtk-2.18 engine installed, since the
package name is gtk2-engines 2.18.1-0ubuntu1
Comment 1 Matthias Clasen 2018-02-10 05:12:18 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 2 Matthias Clasen 2018-04-14 23:58:04 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new