Closed
Bug 77430
Opened 23 years ago
Closed 22 years ago
High ASCII Title Bar Text display problem in CJK system
Categories
(CCK Graveyard :: CCK-General, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: blee, Assigned: shrutiv)
References
Details
To see this, Launch CCK under a CJK system (e.g. JA); Type Extended (High ASCII) char's in Title Bar Text field during customization process; bld installer and launch it. ==> The text is correctly displayed in installation (the very first) window, but not on Title bar. The extended char there seems treated as a leading byte of a DBCS, hence the the disappearance of the low ASCII char which follows it, and incorrect display of the original high ASCII char. Observed in CCK 6.0 under WinNT JA.
The same problem happens with the text (customization field) input in: Installer Background Text; Start Menu (Netscape by .....).
*** Bug 79531 has been marked as a duplicate of this bug. ***
Comment 4•23 years ago
|
||
Updating QA contact to me for half of the CCK bugs while bom-shik is gone.
QA Contact: blee → barrettl
Comment 5•23 years ago
|
||
->CCK-General. Other CCK Components going away.
Component: CCK-Shell → CCK-General
Assignee | ||
Comment 8•22 years ago
|
||
Marking fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 10•22 years ago
|
||
Re-opening as the display on the Browser Title Bar Text can't be verified until bug 110134 is fixed.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 11•22 years ago
|
||
I verified this fixed as it worked fine in JA 6.2.1 w/ JA text input. However, I couldn't verify this with high ASCII input when the underlying EN client (trunk bld) is customized because of bug 110134.
Assignee | ||
Comment 12•22 years ago
|
||
Marking fixed. Since bug 110134 has been fixed now, this bug can be verified in the next CCK build which contains browser trunk bits.
Status: REOPENED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•