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 171886 - broken display of 8-bit fs bookmarks
broken display of 8-bit fs bookmarks
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-28 17:26 UTC by albrecht.dress
Modified: 2005-04-01 05:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
screenshot showing the problem (14.69 KB, image/png)
2005-03-28 17:27 UTC, albrecht.dress
  Details
Probable patch (721 bytes, patch)
2005-03-31 19:29 UTC, Vincent Untz
none Details | Review
Better patch (906 bytes, patch)
2005-03-31 19:33 UTC, Vincent Untz
committed Details | Review

Description albrecht.dress 2005-03-28 17:26:48 UTC
Version details: 2.10.0 from garnome 2.10.0.1
Distribution/Version: YellowDog Linux 4.01

In the panel menus, bookmarked locations (from ~/.gtk-bookmarks) containing file
system locations with 8-bit characters which are not utf-8 encoded are cut and
pango complains about a string not being utf-8 clean. The interesting thing is
that the related *tooltip* shows the correct location. I guess there is a
g_locate_to_utf8 missing somewhere. The screenshot below illustrates the problem
for my "~/Persönliches" (in iso-8859-1) folder.
Comment 1 albrecht.dress 2005-03-28 17:27:48 UTC
Created attachment 39350 [details]
screenshot showing the problem
Comment 2 Vincent Untz 2005-03-31 19:29:56 UTC
Created attachment 39520 [details] [review]
Probable patch

Hi Albrecht,

If you have the possibility of recompiling the panel with this patch, it'd be
great to know if it fixes the problem. I'm having some hard time with my
locales here (only utf-8 right now).

Thanks
Comment 3 Vincent Untz 2005-03-31 19:33:46 UTC
Created attachment 39521 [details] [review]
Better patch

This one is a bit better :-)
Comment 4 albrecht.dress 2005-03-31 20:04:21 UTC
The 2nd patch (39521) fixes the problem. Thanks!
Comment 5 Vincent Untz 2005-04-01 05:56:04 UTC
It's committed. It should be in 2.10.1.