Tiny Core Extensions > TCE Bugs

GTK2 and GTK3 cannot handle Unicode characters in file names

<< < (3/6) > >>

GNUser:
Thanks, Rich. Loading gtk2-locale.tcz made no difference to my gtk2 application (thunderbird).

To hopefully take advantage of en_CA in glib2-locale.tcz I deleted mylocale.tcz from tcedir/optional/ then loaded getlocale.tcz then generated a new mylocale.tcz containing en_CA.UTF-8. Rebooted with the new locale then loaded glib2-locale.tcz. No difference.

Quite the stubborn problem!

P.S. Truth of the matter is that I only rarely need to create filenames with fancy characters. Where I get hit with this bug the most (sometimes daily) is when I try to print a webpage to PDF from my browser (iridium-browser, which uses GTK3) and there is a dash (not an ASCII hyphen/minus) somewhere in the webpage's name. As an example, check out duckduckgo.com's homepage. The dash in the page name triggers this bug--if I try to print the page to a PDF file, three "invalid file name" dialogs appear. The dialogs must be closed (in the correct order UGH) before I can delete the dash and proceed with printing.

Juanito:
As I understand it, en_US is the default in linux, so no additional locale files are required.

curaga:
Indeed, the .mo files are translated messages, not tables/etc. They would let you get glib2 errors in German for example.

GNUser:
Thank you, juanito and curaga. So we can confidently eliminate glib2-locale as the missing piece here.

Rich:
Hi GNUser

--- Quote from: GNUser on December 12, 2019, 08:14:21 AM ---Thank you, juanito and curaga. So we can confidently eliminate glib2-locale as the missing piece here.
--- End quote ---
As well as any other  -locale  extension since they only translate pre canned messages (i.e "Invalid file name") compiled into
the library.

Navigation

[0] Message Index

[#] Next page

[*] Previous page