Closed
Bug 32420
Opened 25 years ago
Closed 25 years ago
(c) != © ?
Categories
(Core :: Networking, defect, P4)
Core
Networking
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: BenB, Assigned: BenB)
References
()
Details
Attachments
(5 files)
1.01 KB,
patch
|
Details | Diff | Splinter Review | |
10.47 KB,
patch
|
Details | Diff | Splinter Review | |
423 bytes,
patch
|
Details | Diff | Splinter Review | |
14.41 KB,
patch
|
Details | Diff | Splinter Review | |
419 bytes,
patch
|
Details | Diff | Splinter Review |
© = copyright sign
-- Additional Comments From davidr8@home.com 2000-03-18 20:48 in bug #32412 --
> Are you sure it's ok to replace (c) with © ?
> http://www.templetons.com/brad/copymyths.html says © is legally
> recognized but (c) is not. You don't want a sender to think everyone's going
> to see a © when most will see a (c).
Cool! :-(
My standpoint would be, that "(c)" is a representation of ©, where this
glyph is not available, just like GFX renders "tm", if ™ (the trademark
sign) is not available, like on Linux.
An alternative standpoint :-) would be, that "(c)" is an abbreviation of
"Copyright".
Comment 1•25 years ago
|
||
Wait. Ben, I think the autoconversion of ;-) etc into glyphs is a neat thing,
but thousands of mathematicians, physicists, etc. will wring their hands when
they write things like "Let f be a function so that f(c) = 0" and get ©!
I know, there's going to be a pref, etc., but still. Lots of cases where (c) is
not intended as ©, as in: "(a) ..., (b) ...., and (c) ..."
Assignee | ||
Comment 2•25 years ago
|
||
Richard Zach,
Yes, you're right, this are cases, I didn't think of. Propably the best to
disable them.
BTW: If you want to look over the spec, see
<http://www.bucksch.org/1/projects/mozilla/16507>.
mscott,
can you please review/check in? tnx.
Status: NEW → ASSIGNED
Whiteboard: Patch waiting
Target Milestone: M15
Assignee | ||
Comment 3•25 years ago
|
||
Assignee | ||
Updated•25 years ago
|
Target Milestone: M15 → M16
Assignee | ||
Updated•25 years ago
|
Priority: P3 → P4
Assignee | ||
Comment 5•25 years ago
|
||
Assignee | ||
Comment 6•25 years ago
|
||
Assignee | ||
Comment 7•25 years ago
|
||
mscott, can you review and checkin for M16 please? The patches are just |cvs
diff -u [mozTXTToHTMLConv|html.css]| in the respective dirs.
Wait, I forgot a change for bug 31906. I'll submit a new patch for
mozTXTToHTMLConv soon.
Whiteboard: Fixed. Waiting for review and checkin.
Assignee | ||
Comment 8•25 years ago
|
||
Assignee | ||
Comment 9•25 years ago
|
||
Assignee | ||
Comment 10•25 years ago
|
||
OK, I hope, that's it.
Assignee | ||
Comment 11•25 years ago
|
||
reviewed and checked in by mscott. Thanks!
Whiteboard: Fixed. Waiting for review and checkin.
Assignee | ||
Comment 12•25 years ago
|
||
ops
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 13•24 years ago
|
||
qa to me.
Don't know why this is networking, but it's Tom's, so I'm working on it.
Created test document (see URL field).
QA Contact: tever → benc
Assignee | ||
Comment 15•24 years ago
|
||
> Don't know why this is networking
Because that's where the code lives.
Comment 16•24 years ago
|
||
Wow, learn a new thing every day....
You need to log in
before you can comment on or make changes to this bug.
Description
•