Closed Bug 12662 Opened 22 years ago Closed 19 years ago

Compatible characters not displayed


(Core :: Internationalization, defect, P3)






(Reporter: karl, Assigned: ftang)




(Keywords: intl)


(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

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.
Summary: Compatible characters characters not displayed → Compatible characters not displayed
Target Milestone: M17
>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 ?
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.).
The new draft <URL:> from Unicode
have more information on which characters should (and shouldn't) be substituted
using compatibility equivalents.
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.
I've created a document with more information at
<URL:>. 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: ftang → erik
Target Milestone: M17 → M20
Window rendering FER . reassign to erik as M20
Target Milestone: M20 → M16
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.
OS: Windows 98 → All
Hardware: PC → All
This issue is not limited to Windows. Changing platform and OS fields.
Moving all M16s to M17. Please make comments if you disagree.
Target Milestone: M16 → M17
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 file. Can some one 
add more stuff to that file ? Can someone think about how to use 
nsIEntityConverter for rendering fallback ?
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
Keywords: mozilla1.1
Is this still a issue ? Should we file 3 bugs for each platform so we can trace 
it easier ?
Target Milestone: M20 → Future
Yes, this is still an issue. See attached test case.
Keywords: intl
erik resign. reassign all his bug to ftang for now.
Assignee: erik → ftang
mark all future new as assigned after move from erik to ftang
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.
I think the problem go away these day
Closed: 19 years ago
Resolution: --- → WORKSFORME
Changed QA contact to
QA Contact: teruko → ylong
The page:
display fine with me on all platforms on latest builds.

Mark as verified as worksForMe.
You need to log in before you can comment on or make changes to this bug.