Created attachment 8469
Window-shot illustrating the problem
I set the LANG environment variable is set to uk_UA.KOI8-U. The help is trying to show me the Ukrainian version, but messes things up -- most likely, because no one has ever tested it in any encoding other than UTF-8.
Attachment 8469, "Window-shot illustrating the problem":
Version: 4.12.1
Designs
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
That help dialog is from libxfce4ui, but before moving to that component, the text is also garbled for screenshooter's dialogs?
Out of curiosity, why use an encoding other than UTF-8?
the text is also garbled for screenshooter's dialogs?
No, the buttons and other GUI-elements are all fine...
Out of curiosity, why use an encoding other than UTF-8?
I, and all of my local users, only know three languages -- Ukrainian, Russian, and English. Character-sets of all three can be expressed in KOI8-U -- a single-byte encoding. Why do we need to use a multi-byte encoding?
Using the solution from Bug #15350 makes any difference?
Of course, not -- that's only applicable to names of the files on the filesystem...
This might be the same problem as in Bug #11317, however -- where the already-UTF8 text was, erroneously, passed through "g_locale_to_utf8" again. That was fixed in:
I'm running "LANG=uk_UA.koi8u xfce4-screenshooter" and that dialog looks just right.
What libxfce4ui version do you have installed?
Try to call this help dialog from other apps, such as Thunar, panel or xfdesktop (settings), what happens?
Why do we need to use a multi-byte encoding?
Because except for very specific use cases, saving some megabytes on a desktop might not be worth the trouble of breaking some apps. I know they are supposed to work with whatever encoding is out there, but UTF-8 is so much more easy for devs...
This might be the same problem as in Bug #11317, however -- where the
already-UTF8 text was, erroneously, passed through "g_locale_to_utf8" again.
That was fixed in:
I started using computers, when 64Kb of RAM was A LOT -- for a mainframe... Besides, it could be a lot more -- any text using Cyrillics doubles in size, when converted to UTF8.
might not be worth the trouble of breaking some apps
Sorry, but I think we won't be able to solve your problem (wrong audience). Please reach out to the freebsd xfce maintainers to fix the packaging mess.
None of your problems are reproducible with an up-to-date packaged version of Xfce 4.14.