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 437478 - locale named folders are not displayed properly with non-UTF8 locale
locale named folders are not displayed properly with non-UTF8 locale
Status: RESOLVED OBSOLETE
Product: baobab
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Baobab Maintainers
Baobab Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-10 15:14 UTC by Frederic Crozat
Modified: 2012-12-05 02:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Frederic Crozat 2007-05-10 15:14:28 UTC
to duplicate this bug :
-start a session with a non utf8 locale (for instance fr_FR.ISO8859-15 or any ISO8859-15 locale)
-export G_FILENAME_ENCODING='@locale'
-create a directory with locale encoded characters. For instance, 'Téléchargements'
-then run baoba to analyse this directory (or a parent directory).

This directory name will appear as T??l??chargements in treeview and pie chart. It seems check_UTF is doing strange things..

From a quick analysis, I don't really see the need for check_UTF since g_filename_display_basename is known to always return valid UTF-8. 

Moreover, string given to g_filename_display_basename is either obtained from gnome_vfs_unescape_string_for_display or gnome_vfs_format_uri_for_display, so in both case, it is already valid UTF-8 and should never be used as input for g_filename_display_basename which is expecting filesystem encoded strings (based on G_FILENAME_ENCODING).

The best way to get a correct basename would be to use eel_uri_get_basename or to copy its code (which is quite simple) in baoba, ie relying on GnomeVFSURI object.
Comment 1 Fabio Marzocca 2008-05-14 17:28:34 UTC
Baobab has been migrated to Gio and this problem should have been fixed. Could you pls confirm this is current development (trunk) version?
Comment 2 nodiscc 2012-12-05 02:11:10 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.