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)

x86
Windows NT
defect
Not set
normal

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 .....).
reassigning to tao
Assignee: shrutiv → tao
Blocks: 96359
Blocks: 79531
*** Bug 79531 has been marked as a duplicate of this bug. ***
Updating QA contact to me for half of the CCK bugs while bom-shik is gone.
QA Contact: blee → barrettl
->CCK-General. Other CCK Components going away.
Component: CCK-Shell → CCK-General
qa to blee
QA Contact: barrettl → blee
Re-assigning to shrutiv
Assignee: tao → shrutiv
Marking fixed.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Verified fixed in 4/9 bld.
Status: RESOLVED → VERIFIED
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 → ---
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.
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 ago22 years ago
Resolution: --- → FIXED
Verified fixed in 4/16 bld.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.