Closed Bug 34940 Opened 24 years ago Closed 24 years ago

font is not showing all characters correctly

Categories

(Core :: CSS Parsing and Computation, defect, P3)

x86
Windows 2000
defect

Tracking

()

VERIFIED DUPLICATE of bug 33127

People

(Reporter: hobbit_mak, Assigned: erik)

References

()

Details

(Keywords: verifyme)

Attachments

(3 files)

Build ID: 2000022820

1. Download SIL IPA font from

ftp://ftp.sil.org/fonts/win/silipa93.exe

2. Install to Windows98

3. View  http://homepage1.nifty.com/html/ipa.html

4. font-family:   SILDoulos IPA93
  has not effect.
  This has effect for Netscape Navigator 4.7.
Takahashi-san, this is not a bug.  Your page is incorrect.
Font names containing white space must be in quotes.

you should correct the following...

.ipa    {font-family:   "SILDoulos IPA93";
         font-size:     25pt}

You should see http://richinstyle.com/guides/fonts2.html#fontfamily !!
I corrected to .ipa {font-family: "SILDoulos IPA93"; font-size: 25pt} But this is also no effect. I can see this font in IE.
This problem is reproduced on M15 also.
The page referenced looks fine: the elements in the table that have class=ipa 
all look correct (at least I think they are correct, they look like the 
description next to them says they should). 

Marking WORKSFORME. Please reopen and assign to attinasi@netscape.com if I am 
missing something here. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
This problem is reproduced in Build ID 2000061311.
Reopening.

Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reassigning to Marc as requested. If "SILDoulos IPA93" is a bitmap font, it could 
be a dup of bug 22031.
Assignee: pierre → attinasi
This has regressed. It was working correctly back on 05/05 when I marked it 
fixed, now it is broken. Also, I am getting some assertions now:

###!!! ASSERTION: data in U+0100-U+FFFF will be lost: '(*first < 256)', file s:\
mozilla\xpcom\ds\bufferRoutines.h, line 302

I'll ahve to look into what broke this - possibly waterson's recent string 
changes in style?
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
This is working again... I'll attach a JPG of the screen I just saw testing 
this... Please look at the image and confirm that it looks like it is suppossed 
to. Thanks very much.
I don't know why this stopped working then started working again - but it now 
WORKSFORME. Please advise if it breaks again (I'll add it to my regression-risk 
list too).
Status: ASSIGNED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → WORKSFORME
This problem is reproduced on Build 2000080712 of Windows 2000.
Working fine on NT4.0, in trunk build as well as PR2 (2000080712)
OS: Windows 98 → Windows 2000
Adding 'verifyme' keyword
Keywords: verifyme
This problem is reproduced in Build ID 2000100208
Reopening do to Reporters comment.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
It still looks OK to me.  CC'ing ftang, hoping he can try it too.
This problem is reproduced on M18(2000101212).
CSS font specification for "Lucida Sans Unicode" works ok, but "SILDoulos 
IPA93" did not work.
This page can be viewed by NN 4.7 correctly.
I attached a screenshot of the page from my copy of the 2000101212 build. It
looks OK to me, if it is not correct, or I am looking at the wrong portion of
the page, please let me know.
If you install SIL IPA font you can see almost same letter of MS font and SIL 
font.
Please read reproduce procedure and follow it.
If you use Netscape Navigator 4.7.
You can see SIL IPA fonts.
Correct image of the page is here.

http://homepage1.nifty.com/hobbit/ie.gif
My apologies, you are correct. I see the problem with the fonts now. I'll
investigate.
Status: REOPENED → ASSIGNED
I'm attaching a testcase showing the IPA font being applied to characters #FA -
#1F3 and I'm seeing a problem starting at character #19a. This is not a style
problem, rather, there appear to be problems getting those characters out of the
font. IE and Nav4 both show very different results, none of which appear correct.

I'll admit, that I am out of my area of expertiese here - I know very little
about font mapping or unicode. But, I'll attach my testcase anyway, since it
makes it pretty clear that the style rules used to map in the IPA font are being
applied correctly, but that there are problems with either the font or the way
we are trying to extract characters our of the font.
SILDoulos IPA font is not for unicode font. So there are few characters defined
after 256(#100).
Problem is that font specification is not valid for character 33(#21) to 255(#FF).

For character after 256(#100) Mozilla can not find font in SIL, so Mozilla use
default font. It is not problem.

SIL use character 250(#FA) for U+266. My table is intended to show this
correspondense.

http://homepage1.nifty.com/hobbit/english/html/ipa.html  
Updating summary and assigning to engineer who (hopefully) undestands fonts and
font mapping, as I clearly do not. Erik, if you are not the appropriate person,
maybe you knwo who is?

To reiterate, this does not appear to be a style problem: the font-face style
rules is applied correctly, as many characters are displayed correctly. Also,
dumping the style data from Viewer shows that the font-face is being applied
correctly.
Assignee: attinasi → erik
Status: ASSIGNED → NEW
Summary: font-family of stylesheet did not effect → font is not showing all characters correctly
erik, please take a look at it when you have time.
I downloaded the SIL fonts, and it turns out that SIL Doulos IPA93 is a "symbol"
font (not a Unicode font). Older browsers such as Nav4 allowed the use of these
symbol fonts with illegal document encodings, but Mozilla/Netscape6 do not allow
this. See bug 33127. Marking dup of 33127.

*** This bug has been marked as a duplicate of 33127 ***
Status: NEW → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → DUPLICATE
Netscape's standard compliance QA team reorganised itself once again, so taking 
remaining non-tables style bugs. Sorry about the spam. I tried to get this done 
directly at the database level, but apparently that is "not easy because of the 
shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
vrfy dupl
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: