|
Bugzilla – Full Text Bug Listing |
| Summary: | font aliases like 10x20 should expand to iso10646-1 instead of expanding to iso8859-1 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Mike Fabian <mfabian> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Enhancement | ||
| Priority: | P1 - Urgent | CC: | eich |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | fontaliases-unicode.diff | ||
|
Description
Mike Fabian
2003-09-18 20:39:42 UTC
Currently /usr/X11R6/lib/X11/fonts/misc/fonts.alias contains:
10x20 -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso8859-1
in future it would be better to change that to
10x20 -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
in all cases where a Unicode version of the same font is available.
This doesn't loose any functionality for iso8859-1 as the first page
of a iso10646-1 is identical to a iso8859-1 font, but it helps in
non-ISO-8859-1 locales.
*But*, xterm currently cannot detect whether the alias expands to a iso10646-1
font or not, i.e. xterm will not use the UTF-8 mode when such an alias is specified.
This is a bit tricky to fix in xterm, therefore it is not possible to solve
this for SuSE Linux 9.0 (I have entered this bug for SuSE Linux 9.1-pre just as
a reminder).
Ok. Then we need in Michael's xterm patch first. Enhancement for 9.1. Michael, any news on this one? Nope. No time for this at the moment. *** Bug 52765 has been marked as a duplicate of this bug. *** Michael, do you think you'll find the time to add this feature to xterm for 10.2 so we can finally switch to aliases for unicode fonts? I'll try... Thanks! Egbert, JFYI. Since Matthias or me is in Cc of this bugreport or the reported itself, it might be interesting for you as well. JFYI, Matthias. This is a bugreport, which is assigned to Egbert/me or with Egbert/me in CC or reported by Egbert/me. Ok. Nothing happened here in the last 4 1/2 years. ==> WONTFIX Yes, sorry. Too much other stuff with higher priority on my list... Michael, are you still running in a Latin9 locale 4 years after our default is UTF-8? I suggest to consider disabling your patch (configure --disable-mini-luit) and let the fonts.alias entries point to iso10646-1 fonts. Why would you want to disable the patch? It has nothing to do with the entries in fonts.alias. Obviously it has. See comment #1. Looks like you forget all the details already, which is not really surprising after more than 4 years ... What has comment #1 to do with the mini-luit patch? mini-luit is just saving the spawn of a real luit process for some locales, where the mapping is trivial. Mike? Mike and me talked about this issue again and agreed on simply doing this now. It's unlikey that it will break anything. .. together with Michael Schröder of course. I couldn't find a iso10646 replacement for these 8x16 -sony-fixed-medium-r-normal--16-120-100-100-c-80-iso8859-1 12x24 -sony-fixed-medium-r-normal--24-170-100-100-c-120-iso8859-1 Apart from these for all iso8859-1 aliases a iso10646 font is available. I'll attach a patch. Created attachment 210655 [details]
fontaliases-unicode.diff
fixed for STABLE/Factory and openSUSE 11.0 Beta2. |