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 308599 - Wrongly says a files has "invalid encoding"
Wrongly says a files has "invalid encoding"
Status: RESOLVED DUPLICATE of bug 314538
Product: nautilus
Classification: Core
Component: Views: All
2.10.x
Other All
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-22 03:59 UTC by Nicolás Lichtmaier
Modified: 2005-08-27 06:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Nicolás Lichtmaier 2005-06-22 03:59:10 UTC 
Please describe the problem:
I use my locale's encoding for storing files. Therefore I've always set
G_BROKEN_FILENAMES to 1 in .xsession, before exec'ing gnome-session.

I'm seeing that in some folders (and in others not!) Nautilus shows accented
characters as '?' and shows "(invalid encoding)" after the filename. I couldn't
find out when it does and when it doesn't succesfuly handle ISO-8859-1 chars.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Christian Neumair 2005-07-13 15:54:26 UTC 
Maybe you could check whether G_FILENAME_ENCODING is set?
Comment 2 Christian Neumair 2005-08-27 06:42:14 UTC 
No feedback, marking as duplicate of bug 314538, which has a patch attached.

*** This bug has been marked as a duplicate of 314538 ***