Tiny Core Extensions > TCE Bugs

GTK2 and GTK3 cannot handle Unicode characters in file names

<< < (5/6) > >>

curaga:
That reminded me, my LFS box has this in bashrc:

--- Quote ---export G_FILENAME_ENCODING=@locale

--- End quote ---

However glib docs claim it defaults to utf-8, which is weird in your case.

GNUser:
If I don't specify a value for the variable, I find that it's set to iso8859-1:


--- Code: ---bruno@box:~$ echo $G_FILENAME_ENCODING
iso8859-1

--- End code ---

Maybe glib does default to utf-8--I found this in /etc/profile:


--- Code: ---# Screen display for X and encoding for GTK+ apps.
#
G_FILENAME_ENCODING=iso8859-1
--- End code ---

Boy, did it cause me a world of hurt. Maybe something similar to what LFS does would be a better way to go than hardcoding a default encoding?

curaga:
I think that's for best compatibility with fat32 etc. Trying to create utf-8 names on fat32 would either fail or be incompatible with Windows IIRC. By default, TC does not have locales installed, it's the "C" default which is ASCII, which would prevent the @locale from being useful.

GNUser:
If I don't specify an encoding in ~/.profile and comment-out the relevant line in /etc/profile (and backup the changes), the variable doesn't have a value after a reboot:


--- Code: ---bruno@box:~$ echo $G_FILENAME_ENCODING

bruno@box:~$
--- End code ---

Everything works as expected in this scenario, so glib must indeed be defaulting to utf-8.

GNUser:
Perhaps getlocale.tcz could give the user a hint about this environmental variable potentially being a pitfall? It could prevent some pain.

Navigation

[0] Message Index

[#] Next page

[*] Previous page