129205 - Fizzilla fails to properly map HTML4 entities to appropriate TTF font glyphs

Status: RESOLVED FIXED

(Core Graveyard :: GFX: Mac, defect, P4)

Description

[Greg K.]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.9+)
Gecko/20020305
BuildID:    2002030508

Mozilla fails to properly map HTML4 entities such as rdquo and lsquo to the
appropriate glyphs in Windows TrueType (.ttf) fonts installed under Mac OS X.

Reproducible: Always
Steps to Reproduce:
1. Download and install the free Exmouth font available from
[http://desktoppub.about.com/library/fonts/hs/uc_exmouth.htm]
2. Access the attached HTML testcase

Actual Results:  ldquo, rdquo, lsquo, and rsquo entities were mapped to accented
capital O glyphs. (See attached screen shot.)

Expected Results:  The aforementioned entities should have mapped to the correct
glyphs.

Comment 1

[Greg K.]

Attachment: HTML test case

Comment 2

[Greg K.]

Attachment: Screen shot of the HTML test case in FizzillaCFM/2002030508

Comment 3

[Greg K.]

Note also that the correct glyphs can be typed in Key Caps, but not in BBEdit
6.1.2, so this could be yet another TTF font bug in Carbon apps. (See also bug
119397 and bug 119572.)

Comment 4

[Boris Zbarsky [:bzbarsky]]

To intl

Comment 5

[Boris Zbarsky [:bzbarsky]]

intl for real

Comment 6

[Greg K.]

Boris, are you sure Internationalization is the right component for this?

Comment 7

[Frank Tang]

now sure about the quality of Exmouth font. 
P4 future

Comment 8

[Greg K.]

FYI, using an experimental FizzillaMach build with the ATSUI patches in bug
121540 seems to fix this bug.

Comment 9

[Greg K.]

Problem also occurs using the Bitstream Cyberbit font available from
[ftp://ftp.netscape.com/pub/communicator/extras/fonts/windows/].

Comment 10

[Greg K.]

Confirmed that Exmouth has the expected glyphs at the appropriate Unicode
position using FontChecker.

Comment 11

[Greg K.]

Still a problem using FizzillaCFM/2002083017, even after recent TEC/ATSUI
improvements.

Comment 12

[Greg K.]

If this is a Mac OS bug, it apparently isn't fixed in 10.2 according to
[news://news.mozilla.org:119/ydNe9.9427$[e-mail]].

Comment 13

[Greg K.]

Still a problem in FizzillaMach/2003020603 on Mac OS X 10.2.3.

Comment 14

[Asaf Romano (gone)]

Reporter: can you check if the bug is still there on latest builds?

Comment 15

[Greg K.]

Yes, this is still evident using Camino 0.8 on OS X 10.3.5.

Comment 16

[Asaf Romano (gone)]

(In reply to comment #15)
> Yes, this is still evident using Camino 0.8 on OS X 10.3.5.

I said latest build, not latest release!
(There were some changes to the fonts code)

Comment 17

[Greg K.]

Oh. Yes, still fails using Mozilla-Mac/2004-08-20-08-trunk.

Comment 18

[Greg K.]

Tests as fixed using Camino/2007010201 (1.2+), likely due to Cairo.