Closed
Bug 212684
Opened 21 years ago
Closed 20 years ago
Some chars use Times New Roman MT 30 unnecessarily
Categories
(Core Graveyard :: GFX: OS/2, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mkaply, Assigned: mkaply)
Details
(Keywords: fixed1.4.1)
Attachments
(3 files, 1 obsolete file)
4.33 KB,
patch
|
jhpedemonte
:
review+
|
Details | Diff | Splinter Review |
1.13 KB,
patch
|
Details | Diff | Splinter Review | |
2.14 KB,
patch
|
jhpedemonte
:
review+
|
Details | Diff | Splinter Review |
This one is hard to explain. We do OS/2 unicode very strange where we convert to the native codepage. For common chars, we should try to use the default font instead of always using Unicode.
Assignee | ||
Comment 1•21 years ago
|
||
Special case a few characters (we already special cased euro) /* euro */ /* bull */ /* ldquo */ /* rdquo */ /* mdash */ I do NOT do hellipse (as was suggested) because in DBCS, ellipses are centered, and bad things happened.
Assignee | ||
Updated•21 years ago
|
Attachment #127757 -
Flags: review?(pedemont)
Updated•21 years ago
|
Attachment #127757 -
Flags: review?(pedemont) → review+
Assignee | ||
Comment 2•21 years ago
|
||
Fix checked in.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Keywords: fixed1.4.1
Assignee | ||
Comment 3•20 years ago
|
||
Add lsquo rsquo hellop and ndash to our algorithm
Recently, wrong display of DBCS character "MIDLINE HORIZONTAL ELLIPSIS" revives. This is side effect of Jan-8's fix for this bug, I think. OS2-2004010808: ok OS2-2004010908: ng Test URL: http://www.serina.org/~mozilla/warpzilla1.4/ History: http://groups.google.com/groups?selm=beuo3h%24e23%40ripley.netscape.com Mike, could you reopen this bug?
Assignee | ||
Comment 6•20 years ago
|
||
What is the behavior now? Is it no longer midline? none of those screenshots are of the current build. Thanks
Behavior is completely same as 1.4 milestone build. No midline. I added a snapshot of 1.6 milestone build to end of the test page.
Assignee | ||
Comment 8•20 years ago
|
||
Logically this doesn't make sense, but I will remove the ellipses code. I believe it is a bug in the OS/2 codepage converters which is mapping the unicode ellipses to the wrong ellipses.
Assignee | ||
Comment 9•20 years ago
|
||
OK, I think I was trying to hard on this one. My IS_SPECIAL code should only be used for 1252 stuff. The problem I was trying to solve here was a problem mainly on western pages. By limiting to the 1252 path, I get the effect I wanted, and Japanese pages work as they did before.
Assignee | ||
Comment 10•20 years ago
|
||
Removing everything from the second case is the wrong idea - then some chars don't display at all. I'm just going to except hellip from the non 1252 case. Works well.
Attachment #141061 -
Attachment is obsolete: true
Assignee | ||
Updated•20 years ago
|
Attachment #141073 -
Flags: review?(pedemont)
Comment 11•20 years ago
|
||
Comment on attachment 141073 [details] [diff] [review] Bestest patch For legibility, I would split IS_SPECIAL into two lines, so it looks like the other defined. Otherwise, r=pedemont
Attachment #141073 -
Flags: review?(pedemont) → review+
Assignee | ||
Comment 12•20 years ago
|
||
My new patch hasn't gone in yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 13•20 years ago
|
||
Fix checked in to trunk and 1.4
Status: REOPENED → RESOLVED
Closed: 21 years ago → 20 years ago
Resolution: --- → FIXED
Updated•15 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•