Closed Bug 2481 Opened 26 years ago Closed 25 years ago

[PP] Numeric entities aren't rendering right under Windows 95/98

Categories

(Core :: Internationalization, defect, P2)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: rekle, Assigned: erik)

References

()

Details

Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
There's no platform information so there's not much to go on. It looks fine for me on Windows NT
Status: RESOLVED → REOPENED
The TM mark is rendering as what looks like a double quote. I've seen other characters (a bullet character) also render as this double quote character. I'm running Windows 98, AMD K6-300, 64MB ram I can provide a screen shot if you like... :)
Assignee: troy → michaelp
Status: REOPENED → NEW
Component: Layout → Rendering
OS: other → Windows 98
Michael, I really don't know what the problem is. Works for me under NT, the problem is reported on Win98
Status: NEW → ASSIGNED
I know what the cause of this bug is now. If you enter a numeric character entity (i.e. '™'), it appears that the '#' symbol is lost from the entity, causing the character to be rendered wrong. To test this try this trivial bit of HTML: ™ View this with IE and NS and it shows a "TM" character as it is supposed to. View this with Mozilla and it appears as a double quote character. Then if you view the source for this little bit of HTML, all you see is '&153;'. The '#' symbol is gone. This losing of the '#' symbol appears to happen on all other numeric entities as well.
Setting all current Open/Normal to M4.
Severity: normal → major
Hardware: Other → PC
Summary: TM mark isn't rendering properly. → Numeric entities aren't rendering right under Windows 95/98
This problem appears to be a problem with Unicode. I have verified that this bug does NOT occur under Windows NT, but it DOES occur under Windows 98 (and I imagine Windows 95). The Unicode value 153 is the unicode character for the TM symbol. In this web page you have an entity listed as ™ The number 153 is apparently being assumed to be Unicode and the appropriate character is being displayed in NT. The problem is, that Unicode doesn't exist in Windows 95/98, so the wrong character is being displayed. There appears to also be a second bug at work here. My last comment wasn't very clear, so I'll try to explain it better now. It says that the '#' character is being lost and that's why it doesn't get rendered right. The '#' character is getting lost, but I don't think this is why it is rendering wrong. The '#' character IS getting lost when you view the source, but it IS there in the actual HTML passed into Mozilla. i.e., you feed Mozilla a "& #153;" and when you view the source, you see "&153;" I haven't tested the latest builds to see if the '#' is still getting lost, but as of the build from 2 nights ago (2/1/99), the rendering problem is still there.
Assignee: michaelp → ftang
Status: ASSIGNED → NEW
currently, there is no true unicode support in nglayout. our internaltional group is aware of this and is working on getting support in.
*** Bug 2955 has been marked as a duplicate of this bug. ***
1. TM is not encoded as dec 153 (dec 153 == 0x99) in Unicode . TM is encoded as U+2122 in Unicode (see http://charts.unicode.org/Unicode.charts/normal/U0080.html and http://charts.unicode.org/Unicode.charts/normal/U2100.html ) The reason people using ™ is because it is the TM in CP 1252. RickG use the hacky nsString.ToUCS2 to solve similar issue when we convert ISO-8895-1 into UCS2. We probably should apply the same thing after we import the NCR. 2. It is true we do not have full unicode support yet. We won't have FULL (such as klingon, tibiten, afracian scripts when we ship 5.0, or even year 2010). Howerver, it does not mean we do not support a reasonably subrange of unicode yet. In this particular case, both Window and Mac should see it without problem if we enforce the nsString.ToUCS2 in the Numeric Entity code. Reassign this back to RickG. RickG, could you reassign this to someone familiar with entity code to add the ToUCS2 there ? Thanks. Note: This is not a rendering issue on Mac and Window. Teruko, please remember to to include entity test in your test cases. Thanks.
Resolution: WORKSFORME → ---
Summary: Numeric entities aren't rendering right under Windows 95/98 → [PP] Numeric entities aren't rendering right under Windows 95/98
I wrote up bug #2955 which then was marked as a duplicate of this bug. The #2955 bug has to do with a special character not being recognized on some platforms. Current resolution of this bug is WORKSFORME. If #2955 truly is a duplicate of this one, then bug still exists and I am reopening this bug (added cnet.com to URL section). Also, I am marking this as a parity bug. I can't see the bug in the www.sweepstakesonline.com URL - could someone clarify this one for me? Thanks.
Taking myself off this cc list.
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
Resolution: --- → FIXED
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I created a small test case for the Trademark entity. Open the URL below: http://slip/projects/marvin/bugs/2481.html Tested with the 3/19 build on Win 95, Win 98, Win NT, Mac8.5 and Linux. The page displays the entity correctly on all platforms EXCEPT Linux. On Linux, the page displays quotation marks instead of the 'Trademark' entity.
Assignee: rickg → ramiro
Status: REOPENED → NEW
Ramiro -- I'm giving you this as a placeholder. I think the real problem now (with entities) is font support under gtk. Are you ok with this?
m7
Assignee: ramiro → erik
OS: Windows 98 → Linux
Target Milestone: M7 → M10
marking m10. erik: can i reassign this to you ? I have no clue and it sounds like a font issue. If not, then throw it back over. thanks.
Status: NEW → RESOLVED
Closed: 26 years ago25 years ago
OS: Linux → Windows 95
Resolution: --- → FIXED
Target Milestone: M10 → M6
I really hate it when people start bug reports on one platform and then somehow change it to another platform when they find that the bug exists there too. For low-level graphics rendering problems, these bugs should be specific to a certain platform. In this case, the bug report started out as a Windows 9X bug, and then became a Linux bug. Since the TM character is rendering correctly on Win9X and NT now, I'm going to close this bug report. We already have a bug report for Linux for the CP1252 characters: http://bugzilla.mozilla.org/show_bug.cgi?id=454
Target Milestone: M6 → M7
Status: RESOLVED → VERIFIED
I verified this in 6-17-08 Win32 build under Windows 98, Windows 95, and Winnt4.0.
You need to log in before you can comment on or make changes to this bug.