Closed
Bug 90049
Opened 23 years ago
Closed 21 years ago
x-user-defined encoding: copyright symbol displayed incorrectly
Categories
(Core :: Internationalization, defect)
Tracking
()
VERIFIED
WORKSFORME
Future
People
(Reporter: diego, Assigned: ftang)
References
()
Details
(Keywords: intl, testcase)
Attachments
(2 files)
This is a spinoff from bug 85059. Mozilla used to crash, now it still renders the copyright symbol as (c) in this simple testcase: <html> <head> <meta http-equiv=Content-Type content="text/html; charset=x-user-defined"> </head> <body> © </body> </html> Netscape 4.77 has no problems.
Reporter | ||
Comment 1•23 years ago
|
||
Reporter | ||
Updated•23 years ago
|
Reporter | ||
Comment 2•23 years ago
|
||
adding keywords
Comment 3•23 years ago
|
||
Would you kindly descibe the cases where x-user-defined is required?
Status: NEW → ASSIGNED
Summary: copyright symbol displayed incorrectly → x-user-defined encoding: copyright symbol displayed incorrectly
Target Milestone: --- → Future
Comment 4•23 years ago
|
||
oh, by-the-way: thanks for the testcase, it does help
Reporter | ||
Comment 5•23 years ago
|
||
To be perfectly honest, I am lightyears away from being a HTML expert and I do not have the slightest idea what x-user-defined is or where it is required. www.theinquirer.net uses it, Netscape 4.77 renders it correctly. That's reason enough to file a bug in my eyes.
Updated•23 years ago
|
URL: www.theinquirer.net
Reporter | ||
Comment 6•23 years ago
|
||
Bertilo Wennergren just posted this comment to bug 85059. The problem appears to be related and seems to expand the issue, maybe this is not that harmless after all: I just saw something related to this bug in Mozilla news. I tried to reply to a news posting that used the encoding "x-user-defined". When I typed a non-ASCII character the computer froze for a while (I thought it had crashed), and started a lot of disc activity (a lot!). When I got control back, the character I had typed materialized in the form of a surrogate ASCII sequence: a c with a circumflex had become "c^" (two characters). From then on, in that reply window, all such characters - that I normally type without a problem in Mozilla - became such surrogate ASCII combinations. If I change the encoding for such a message _before I hit "reply"_, this weird behaviour does not happen. But changing the encoding when the reply window is already open does not help. So this is not about the copyright symbol, but about a lot of characters that are in this (undocumented?) table of ASCII surrogates (I've seen it used sometimes when copying from Mozilla into non-Unicode-aware applications).
Comment 8•23 years ago
|
||
I should add to my report that I saw this on Mozilla build 2001100308 on Linux RedHat 7.1 with KDE 2.1.1.
Comment 9•23 years ago
|
||
Some comments: 1. We should separate the mail related problem from the browser one. Please file a separate bug and assign it to nhotta@netscape.com 2. This problem occurs only on Unix. And also only when the document charset is set to 'x-user-defined'. So if you override the encoding with a legitimate encoding name, the copyright symbol will show correctly. 3. The purpose for having "User-defined" category is so that if someone wants to experiment with a private font without an official Unicode mapping chart, Mozilla will in essence pass through the codepoints as they are. For this category, all HTML entities seem to use transliteration on Linux builds. On Windows and Mac, you get proper display of these entities. 4. There might be a font-related reason why you cannot have entities displayed on Linux only under user-defined encoding. By the way, if you have a public web page, you should not be using "x-user-defined" as your encoding. The results will be totally unpredictable and depends on what font the user has set to that category. In this sense, I think this is a minor bug.
Updated•23 years ago
|
Assignee: bstell → ftang
Status: ASSIGNED → NEW
Comment 10•23 years ago
|
||
--> ftang
Comment 12•21 years ago
|
||
Comment 13•21 years ago
|
||
Comment on attachment 118633 [details] Copyright symbol (©) doesn't always render; appears as a question mark. ><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><HTML xmlns="http://www.w3.org/1999/xhtml"><HEAD> > <META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> > <META name="GENERATOR" content="BreezeBrowser, www.breezesys.com"/><TITLE>October 11, 2002 - Testing the 70-200/2.8 IS L</TITLE> > > <LINK rel="stylesheet" type="text/css" href="http://www.mainefocus.com/styles/mainefocus.css"/></HEAD> > > > <BODY> > <CENTER> > <TABLE summary="block format"> > <TBODY><TR> > <TD align="right"> > <TABLE border="3" summary="photo format"> > <TBODY><TR> > <TD> > <FONT color="black"><IMG src="img_4267_std.jpg" width="600" height="400" alt="photo"/></FONT> > </TD> > </TR> > </TBODY></TABLE> > <SPAN class="i">Copyright © 2002 - Maine Focus Enterprises</SPAN> > </TD> > </TR> > </TBODY></TABLE> > <P> > > </P> > <BR/> > <BR/> > </CENTER> > </BODY></HTML>
Attachment #118633 -
Attachment description: Copyright symbol (©) doesn't render; appears as a question mark. Same page does show copyright symbol on other browsers → Copyright symbol (©) doesn't always render; appears as a question mark.
Reporter | ||
Comment 14•21 years ago
|
||
The testcase now displays a copyright symbol in my week-old Linux CVS build. Resolving as WORKSFORME.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Comment 15•21 years ago
|
||
Verified worksforme with 1.4 branch linux on RH8.0.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•