Closed
Bug 160803
Opened 23 years ago
Closed 15 years ago
Frame not displaying proper Unicode character 02bb
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: keola, Assigned: jag+mozilla)
References
()
Details
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.13; Mac_PowerPC)
BuildID: 20020508
Attempting to use Unicode character 02bb (modifier letter turned comma) in webpage,
but get question mark displayed. Correct character also resides at 0091.
Reproducible: Always
Steps to Reproduce:
Simply view linked URL with Nav 6.2 on other Mac OS 9 or OS X.
Actual Results: Saw question marks whereever this character appeared.
Expected Results: Displayed a left single quote where question marks are.
WorksForMe using FizzillaCFM/2002080203. Keola, Bugzilla is intended for Mozilla
bugs only. Netscape bugs should be reported at
[http://home.netscape.com/browsers/6/feedback/]. Can you reproduce this problem
using a Mozilla build? Are you certain you have a font installed that contains
that character?
Comment 2•23 years ago
|
||
*** Bug 160802 has been marked as a duplicate of this bug. ***
Comment 3•23 years ago
|
||
WFM Mozilla 2002-07-22-03 Mac OS X, but metrics are messed up as usual. Go ATSUI
at once. Don't wait. This is ridiculous.
Reporter | ||
Comment 4•23 years ago
|
||
No Unicode font I've tried has the correct character at 02bb, though an
identical character resides at 0x91. I suggested that 02bb be mapped to
display 0x91. Was instructed by ftang@netscape.com to enter in Bugzilla,
fix needs to be implemented in both. Fix is needed for proper display of
Hawaiian and other Polynesian languages in Unicode.
Keola, in quick testing, I found the free fonts Arial Unicode MS, TITUS Cyberbit
Basic, and Code2000 all contain a glyph at x02bb. All three fonts can be freely
downloaded from the web.
Reporter | ||
Comment 6•23 years ago
|
||
> Keola, in quick testing, I found the free fonts Arial Unicode MS,
> TITUS Cyberbit Basic, and Code2000 all contain a glyph at x02bb.
> All three fonts can be freely downloaded from the web.
My apologies, Greg. I was deeply engrossed in one technical issue for Hawaiian while
typing my reply to you.
Aloha Greg. This is a Mac OS 9 and OS X issue, and I meant to say Mac fonts, not
Unicode. We donÿt want to require people to download a font (as we used to with our
custom fonts) in order to display a single character when all of our other Hawaiian
characters are present and displayable in OS 9 and OS X. I corresponded extensively
with ftang@netscape.com before posting the bug at his request, he already has a fix in
mind for this and other display issues for Hawaiian and other Polynesian languages.
Keola
That's fine, Keola. Generally, I advise against such custom methods, but whether
or not to handle special cases this way isn't my call, ultimately.
I think it's much easier for users to install a font than to maintain a lot of
extra special-case code in the application. It tends to rot fast and cause other
problems.
Updated•23 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 8•23 years ago
|
||
we might add code to map 2bb to other unicode (not U+0091, that is cp1252 0x91,
not unicode 0x91) if 2bb is not available on the system.
Updated•23 years ago
|
Target Milestone: --- → mozilla1.2beta
Updated•23 years ago
|
Target Milestone: mozilla1.2beta → mozilla1.2alpha
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
Comment 9•20 years ago
|
||
-> to default owner
Assignee: ftang → jag
Status: ASSIGNED → NEW
QA Contact: pawyskoczka
Updated•17 years ago
|
Target Milestone: mozilla1.2alpha → ---
![]() |
||
Comment 10•16 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.
If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.
Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
![]() |
||
Comment 11•15 years ago
|
||
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.
Because of this, we're resolving the bug as EXPIRED.
If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.
Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•