Closed
Bug 12662
Opened 25 years ago
Closed 22 years ago
Compatible characters not displayed
Categories
(Core :: Internationalization, defect, P3)
Core
Internationalization
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: karl, Assigned: ftang)
References
()
Details
(Keywords: intl)
Attachments
(2 files)
Unicode contains a number of characters which doesn't exist in many fonts. Some of these have one or more _compatible_ characters which can be used instead. These are marked as <compat> in <URL:ftp://ftp.unicode.org/Public/UNIDATA/UnicodeData-Latest.txt>. Currently, when a character doesn't exist in a font, Mozilla uses the same character from another font (usually Lucida Sana Unicode?) or doesn't render it at all. It would be better if the the compatible characters were being used; changing the font in the middle of a sentence doesn't look good.
Reporter | ||
Updated•25 years ago
|
Summary: Compatible characters characters not displayed → Compatible characters not displayed
Reporter | ||
Comment 1•25 years ago
|
||
Reporter | ||
Comment 2•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17
Assignee | ||
Comment 3•25 years ago
|
||
>It would be better if the the compatible characters were being used;
>changing the font in the middle of a sentence doesn't look good.
Is this more or less a subjective view ? Someone else will argue the other way
around if we change it, right ?
Reporter | ||
Comment 4•25 years ago
|
||
Of course it's a subjective view, though I don't think anybody will complain. E.g., I think most people who use a fi ligature would probably prefer to have this replaced with the letters f and i instead of an fi ligature from a different font (with different weight, heigt etc.).
Reporter | ||
Comment 5•25 years ago
|
||
The new draft <URL:http://www.unicode.org/unicode/reports/tr20/> from Unicode have more information on which characters should (and shouldn't) be substituted using compatibility equivalents.
Comment 6•25 years ago
|
||
huftis, can you point me to a graphical list of the characters? I have no idea, about which chars we're talking. Yout PNG doesn't display for me on eeyes and Mozilla.
Reporter | ||
Comment 7•25 years ago
|
||
I've created a document with more information at <URL:http://home.sol.no/~huftis/mozilla/compat.html>. There, you can find a table showing some of the characters, along with their compatibility characters (view it using Mozilla to see how the characters are currently being rendered).
Assignee | ||
Updated•25 years ago
|
Assignee: ftang → erik
Status: ASSIGNED → NEW
Target Milestone: M17 → M20
Assignee | ||
Comment 8•25 years ago
|
||
Window rendering FER . reassign to erik as M20
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M20 → M16
Comment 9•25 years ago
|
||
Is this really just a Windows rendering issue? The issue of not displaying these characters is, if anything, more pronounced on Unix platforms since the default font doesn't handle most of these characters.
Updated•25 years ago
|
OS: Windows 98 → All
Hardware: PC → All
Comment 10•25 years ago
|
||
This issue is not limited to Windows. Changing platform and OS fields.
Comment 11•25 years ago
|
||
Moving all M16s to M17. Please make comments if you disagree.
Target Milestone: M16 → M17
Assignee | ||
Comment 12•25 years ago
|
||
naoki is adding the support for transliteration into nsIEntityConverter now. see bug 9574 for details. The mapping table from Unicode (dec) to the transliteration will be placed into transliterate.properties file. Can some one add more stuff to that file ? Can someone think about how to use nsIEntityConverter for rendering fallback ?
Comment 13•25 years ago
|
||
The important issues, such as displaying *something* (instead of nothing), and mapping windows-1252 chars to appropriate glyphs on Unix, are logged as separate bugs. The rest of this bug is relatively unimportant. Marking M20.
Target Milestone: M17 → M20
Reporter | ||
Comment 14•24 years ago
|
||
New URL: http://home.no.net/huftis/mozilla/gammalt/compat.html
Reporter | ||
Updated•24 years ago
|
Keywords: mozilla1.1
Assignee | ||
Comment 15•24 years ago
|
||
Is this still a issue ? Should we file 3 bugs for each platform so we can trace it easier ?
Target Milestone: M20 → Future
Reporter | ||
Comment 16•24 years ago
|
||
Yes, this is still an issue. See attached test case.
Assignee | ||
Comment 17•23 years ago
|
||
erik resign. reassign all his bug to ftang for now.
Assignee: erik → ftang
Status: ASSIGNED → NEW
Assignee | ||
Comment 18•23 years ago
|
||
mark all future new as assigned after move from erik to ftang
Status: NEW → ASSIGNED
Reporter | ||
Updated•23 years ago
|
Reporter | ||
Comment 19•22 years ago
|
||
I believe this is still an issue, but can't check with the test case any longer, as I *have* fonts with the characters mentioned in the test case.
Assignee | ||
Comment 20•22 years ago
|
||
I think the problem go away these day
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Comment 22•22 years ago
|
||
The page: http://www.huftis.org/nynorsk-programvare/mozilla/gammalt/compat.html display fine with me on all platforms on latest builds. Mark as verified as worksForMe.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•