Closed Bug 32412 Opened 26 years ago Closed 26 years ago

© not displayed

Categories

(Core :: Layout, defect, P3)

x86
All
defect

Tracking

()

VERIFIED DUPLICATE of bug 30840

People

(Reporter: BenB, Assigned: mscott)

References

Details

(Keywords: platform-parity)

Reproduce: Send with any mailer a plain text mail containing the following string: foo(c), bar Actual result: Simone reported, she saw foo, bar on Win98. She tried fixed and variable width fonts (change that in "Mail & Newsgroups" pref panel) and used commercial M14 build #31711. Expected result: You'll see fooO, bar where "0" is the copyright sign (HTML 4.0 entity "©"). Additional Comments: The problem might also appear for foo(r), bar where (r) is replayed with the regitrated trademark sign ("®"). It works fine for me on Linux (both trunk and M14). Mac not tested.
Blocks: 17962
Keywords: pp
I should add, that the fact, that the expected result is the copyright sign, not "(c)", is due to a recognition feature of the TXT->HTML converter <http://www.bucksch.org/1/projects/mozilla/16507>.
Looks like a font issue
Assignee: troy → erik
&copy; (copyright) itself works on Win98, so this is probably a problem with the TXT->HTML converter. Reassigning to Phil. Please forward to the right person. It would be a good idea to try "foo(c), bar" and "foo(c) bar" to see if the comma has anything to do with it.
Assignee: erik → phil
Component: Layout → Back End
Product: Browser → MailNews
Are you sure it's ok to replace (c) with &copy; ? http://www.templetons.com/brad/copymyths.html says &copy; is legally recognized but (c) is not. You don't want a sender to think everyone's going to see a &copy; when most will see a (c).
> so this is probably a problem with the TXT->HTML converter. Reassigning to > Phil. Please forward to the right person. I wrote the converter. It puts out "&copy;" in both cases; define "DEBUG_BenB" and recompile mozilla/netwerk/streamconv/converters, if you don't believe me. REASSIGN back to erik. I'll download a M14 Windows build, reboot into Windows :-( and test more. > &copy; is legally recognized but (c) is not. Aaaaaarrrrrrggggggg!!!!!!!!!!! I hate this legal crap. I'll file a new bug on it.
Temporarly reassign to me, so phil doesn't have to care.
Assignee: phil → mozilla
Legal stuff about (c) != &copy; -> Bug 32420 (thanks, mozilla@bucksch.org)
OK, I can second Simone's report. I'm using build 2000-03-10-05 on Win95 and I don't see &copy; in Mail, even if a space is before and after it. I do see it in the browser, however. REASSIGN to erik (this time for real). Erik, the browser mostly uses Western for me, Mailnews Unicode. Could that be the reason?
Assignee: mozilla → erik
Component: Back End → Layout
Product: MailNews → Browser
> I'm using build 2000-03-10-05 on Win95 If I'm not completely confused, this is <ftp://ftp.mozilla.org/pub/mozilla/nightly/2000-03-19-06-M15-nb1b/mozill-win32-installer.exe> Anyway, I downloaded build 2000-03-19-06-M15-nb1b for Linux and see the same bug! I do not see it with M14-crypto Linux build 2000-03-03-16 or my M15 Linux build from 2000-03-07-08. So, it looks like a XP regression on the Netscape Beta1 branch.
OS: Windows 98 → All
cc rhp
I think erik is right. I set a break point at nsScanner::Append (mozilla/htmlparser/src/nsScanner.cpp) I saw a space instead of a "&copy;" in the place the "(c)".
Re-assign to mozilla@bucksch.org based on ftang's comment.
Assignee: erik → mozilla
Yes, with my last comment, this makes sense. But I don't have a nb1b tree, so over to mscott, who made the last changes in mozTXTToHTMLConv, for investigation.
Assignee: mozilla → mscott
forget about my earily comment. My build do not have mscott's lateset check in in the nsTXTToHTMLConv.cpp After I update nsTXTToHTMLConv.cpp, it show the copy sign to me. Is this a dup of 30840
tnx, ftang. *** This bug has been marked as a duplicate of 30840 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Marking verified dup of 30840.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.