| Summary: | Problem with cyrillic encoding in xscreensaver lock screen | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kirill Anikin <anikinkirill94> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | loginov_alex, mtasaka, nicolas.salguero, rverschelde |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | xscreensaver-5.21-1.mga3 | CVE: | |
| Status comment: | |||
| Attachments: |
Patch add support for cyrillic UTF-8 to xscreensaver
Screen with problem Updated patch that adds support for cyrillic and japanese UTF-8 to xscreensaver |
||
|
Description
Kirill Anikin
2013-11-23 16:13:42 CET
As this is a software issue, rather than a packaging issue, your best bet is to report it upstream. There are instructions for doing that here: http://www.jwz.org/xscreensaver/bugs.html If a fix is developed for this, let us know and perhaps we can include it.
Alex Loginov
2014-10-29 18:33:46 CET
CC:
(none) =>
loginov_alex Created attachment 5552 [details]
Patch add support for cyrillic UTF-8 to xscreensaver
Hi,
This patch also works with latest version of xscreensaver (5.30).
Regards.
Nico.
Alex Loginov
2014-11-02 08:20:45 CET
URL:
http://img.by/i/UtDvR.png =>
(none) Created attachment 5553 [details]
Screen with problem
Fixed in xscreensaver-5.29-4.mga5 for Cauldron. Patch was sent to upstream. This bug is for mga3, but 2014-11-19 is EOL for mga3. I was asked from jwz about this patch, and I answered that this does not seem to work on ja_JP.utf8 . CC:
(none) =>
mtasaka Mamoru, hello, Feel free to write patch better. Created attachment 5572 [details]
Updated patch that adds support for cyrillic and japanese UTF-8 to xscreensaver
Hi,
This new version of the patch also works with ja_JP.UTF-8 locale but is a bit uglier because there is no restriction at all on font selection.
Regards.
Nico.
Attachment 5552 is obsolete:
0 =>
1 Well, * Fonts are currently very difficult for me, and I cannot verify your patch in detail, howeverl I don't think allowing all fonts is proper approach. And I have no idea what is the correct approach... Would you explain (also to Jamie) why allowing all fonts is "safe"? Hi, The problem is to find a subset of fonts which covers the maximum of languages and encodings (fonts that support ISO10646-1 do not necessarily provide support for cyrillic or japanese characters, for example "*-helvetica-*" font family cannot render UTF-8 cyrillic in my tests). I have not been able to find such a subset and it seems rather common, from the searches I made on the web, to allow X11 server to pick the first font that can render the text correctly (in my tests, it seems to often choose "*-fixed-*" font family, which covers many languages and encodings). I do not think there can be a performance issue because there is a limited number of available fonts (only fonts listed by xlsfonts, and no TTF font for example). Regards. Nico. Hi, thanks for reporting this bug. We are sorry, but we no longer maintains this version of Mageia. Please upgrade to the latest version and reopen this bug against that version if this bug exists there. As a result we are setting this bug to CLOSED:WONTFIX This bug is for mga3, but 2014-11-19 is EOL for mga3. Resolution:
(none) =>
WONTFIX For the sake of consistency, this bug has been fixed for Mageia 5 using Nicolas' patch. Hardware:
i586 =>
All |