Closed
Bug 62345
Opened 25 years ago
Closed 24 years ago
Unambiguous Unicode hyphen rendering differs from that of hyphen-minuses
Categories
(Core :: Internationalization, defect, P3)
Tracking
()
VERIFIED
INVALID
People
(Reporter: decoy, Assigned: erik)
References
()
Details
In Unicode, we have two different hyphens: the normal ASCII one, with ambiguous
ASCII semantics and the unambiguous Unicode one (U+2022 or something). In
justified text, one does not get additional space on the sides of the ASCII
variant, but does when the Unicode one is substituted. The ASCII behavior should
extend to the Unicode unambiguous hyphen.
Comment 2•25 years ago
|
||
Verified
Platform: PC
OS: Windows 98
Mozilla Build: 2000121804 M18 Trunk Build
Marking as NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•24 years ago
|
||
Mark it as invalid. This is a typographic issue. The font use different glyph for
these two character. There are no reason they should appear as the same.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 4•24 years ago
|
||
True. Eventhough fonts should ideally deal with them as pretty much identical,
this is not Mozilla's concern.
But there are still differences which are not font related. For instance,
Mozilla does not seem to permit line-breaks after the Unicode hyphen, which is
funny considering why we have it in Unicode in the first place.
You need to log in
before you can comment on or make changes to this bug.
Description
•