Broken filenames in gtk+-2.8.19 [SOLVED]

selig · Last edited by selig on Wed Sep 20, 2006 7:56 am; edited 1 time in total

I have just run "emerge -u world" and GNOME got updated amongst other things too. One of its dependancies is gtk+, which got upgraded to version 2.8.19. The problem is, that I have a non-UTF-8 locale (cs_CZ.iso8859-2) and the filenames containing accented characters are displayed with a "?" in them (in gtk+ apps). When running gqview, it suggests to set the environment variable G_BROKEN_FILENAMES to 1 - but it is already set at that and this does not help a bit. Unsetting it makes no difference. Also when I save a file (e.g. in the GIMP) when there is a space in the filename it gets translated to "%20" in the "Name:" field and I have to replace the "%20" for a space again - very frustrating.
I really do not want to switch to UTF-8. Has anyone experienced similar problems? Is there any way to make it work again? Thanks.

Q-collective · Advocate Joined: 22 Mar 2004 Posts: 2071

Does this issue also exist in 2.8.20-r1?

selig · Posted: Mon Jul 31, 2006 11:18 am Post subject:

The gtk+-2.8.20-r1 ebuild is not marked stable yet, but I am going to try it now anyway and post the results.

selig · Posted: Mon Jul 31, 2006 11:52 am Post subject:

The behaviour is almost the same in gtk+-2.8.20-r1 - the only difference being that when I save a picture with the GIMP, it gives me "Unnamed" in the name field instead of the old image file name.

Blurpy · Posted: Fri Aug 18, 2006 5:47 pm Post subject:

No solution yet? It's just extremely annoying that all my gtk+ apps are broken because they can't use the filesystem reliably anymore.

selig · Posted: Sun Aug 20, 2006 1:09 pm Post subject:

No, unfortunately there still is no new version that would solve the problem. I will try posting a report into Gentoo's bugzilla, since I have not found the issue mentioned in any existing bugreport.

Blurpy · Posted: Mon Aug 21, 2006 5:31 pm Post subject:

https://bugs.gentoo.org/show_bug.cgi?id=144523 is yours, right? I added a comment there.

selig · Posted: Wed Aug 23, 2006 7:51 am Post subject:

Yes, that bugreport is mine, I am hoping they fix it soon. While I usually fix some small annoying things in programs myself, the gtk+-2 library is beyond me.

Blurpy · Posted: Wed Sep 13, 2006 7:00 pm Post subject:

Doesn't look like anything is happening

UncleTom · Posted: Thu Sep 14, 2006 6:56 am Post subject:

Have you tried to set the filename encoding in /etc/env.d/50glib2 or your own profile? You should use

Blurpy · Posted: Thu Sep 14, 2006 9:09 am Post subject:

Thanks a lot! Both suggestions fixed the issue, so I stayed with @locale.

UncleTom · Posted: Thu Sep 14, 2006 11:26 am Post subject:

Cool.

This probably means that the bugreport could be closed as well?
_________________
bug, n: A son of a glitch.

selig · Posted: Tue Sep 19, 2006 10:27 am Post subject:

I would say that the "@locale" setting should be default, so modifying the ebuild to set it as such would be wise. That would work well for the vast majority.

UncleTom · Posted: Tue Sep 19, 2006 1:53 pm Post subject:

I second that.
_________________
bug, n: A son of a glitch.

selig · Posted: Wed Sep 20, 2006 7:55 am Post subject:

I got a good explanation of the problem: https://bugs.gentoo.org/show_bug.cgi?id=144523 So I have closed it as WONTFIX. The behavior is apparently desirable for new systems and it still can be reconfigured for people like me who cannot afford to change the whole Gentoo to UTF-8 on every computer they connect to. (I have bad experience with UTF-8 terminals connecting to non-UTF-8 machines and vice versa... they are almost unusable for anything more than those 7-bit ASCII characters).

UncleTom · Posted: Wed Sep 20, 2006 8:53 am Post subject:

Thanks for the feedback.

Our experiences with mixing UTF-8 and non-UTF-8 machines/devices must obviously be similar and I still feel that I can avoid a lot of pain by keeping everything in the same encoding. But perhaps I'll give UTF-8 another try on one of my systems as soon as I have the time to do so.
_________________
bug, n: A son of a glitch.