Closed Bug 104531 Opened 23 years ago Closed 23 years ago

Heart symbol using <font face="Symbol"> is displaed as a Japanese Hankaku character

Categories

(Core :: Internationalization, defect)

Product:
Core
Component:
Internationalization
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 33127

People

(Reporter: momoi, Assigned: shanjian)

References

(
URL
)

Details

** Observed with 20011012 Win32 trunk & branch build **

This is probably similar to Bug 33258. 

The above page is encoded in Shift_JIS Japanese. 
The following type of font face definitions is used
to display a heart symbol using Symbol font.

<font face="Symbol">0xA9</font>

I put in 0xA9 above but it is actually a raw code point
in the above document.

This document has a DOCTYPE which shows that it is in 
non-standard mode.

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

Thus, the font face should be honored and the heart symbol
should be displayed but instead Mozilla shows Japanese Hankaku
"u" character which would be what corresponds to "0xA9"
in Shift_JIS.
I guess we are currently converting to Unicode based on
the document encoding without paying attention to the font face 
tag.

As coparison, both IE 5.5 and Comm 4.7x display the heart symbol.
shanjian - We need to have a better story about "Symbol" font. Please work on this.
Assignee: ftang → shanjian
ftang, may I ask what is the "better story" you have in mind?
See the recent comments in bug 33127.

Mark this one as dup of 33127. I don't think it is appropriate to honor the 
encoding suggested by symbol font tag. 

*** This bug has been marked as a duplicate of 33127 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
QA Contact: andreasb → ylong
pierre re-opened Bug 33127 for re-consideration.
For backward compatibility, it is probably a good 
idea to do this for Windows only in quirks mode. 
Too many similar bugs have been filed on this topic
and I agree with that assessment. We are only hurting
ourselves if we don't provide compatibility with
older Netscape clients and other browsers.

ylong, please make sure that you're copied on Bug 33127 and
check on its progress for the problem reported here.

You can verify this as a duplicate now as long
as you monitor the other bug.
You need to log in before you can comment on or make changes to this bug.