Closed
Bug 8594
Opened 26 years ago
Closed 26 years ago
[PP]Unix: add support for -iso10646-1 fonts
Categories
(Core :: Layout, defect, P3)
Tracking
()
VERIFIED
FIXED
M11
People
(Reporter: erik, Assigned: erik)
Details
There are several X fonts the end with "-iso10646-1", and we probably should
support them. They don't contain a fixed set of glyphs like the other X fonts
(such as -iso8859-1). The glyph set can be determined by looking at the per_char
array in XFontStruct. If that is not there, we should look for a font property
called _XFREE86_GLYPH_RANGES. This was invented by Mark Leisher and I.
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M9
Summary: Unix: add support for -iso10646-1 fonts → [PP]Unix: add support for -iso10646-1 fonts
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M9 → M11
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M11 → M14
| Assignee | ||
Comment 1•26 years ago
|
||
Basic -iso10646-1 support was added a while ago, but the _XFREE86_GLYPH_RANGES
support is still missing. Marking M14 (after beta).
| Assignee | ||
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 2•26 years ago
|
||
There was an email discussion with Markus Kuhn and Mark Leisher, and we
determined that _XFREE86_GLYPH_RANGES is not necessary, since the per_char
array is always there, except for abnormal fonts such as those that have 0
in the average width field of the XLFD font name. Mozilla already "filters"
those out (to support scalables). So this bug can now be closed, since we
already added the per_char array support a while ago.
| Assignee | ||
Updated•26 years ago
|
Target Milestone: M14 → M11
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 3•25 years ago
|
||
Based on erik's comments, marking verified fixed in the Nov 29th build.
You need to log in
before you can comment on or make changes to this bug.
Description
•