Closed Bug 5928 Opened 26 years ago Closed 26 years ago

Keyboard entries: Alt -0128, -0134, -0153, -0159 not displayed

Categories

(Core :: DOM: Editor, defect, P3)

x86
Windows NT
defect

Tracking

()

VERIFIED DUPLICATE of bug 4819

People

(Reporter: bobj, Assigned: buster)

Details

In both the mail compose and the editor window I tried to enter: Alt-0128 (Euro), Alt-0134 (dagger), Alt-0153 (TM), Alt-0159 (Y-diaresis) No characters are displayed. However when I send the composed email, the characters are actually sent and can be displayed correctly by Messenger. I suspect this is the case for all 32 values: Alt-0128 through Alt-0159 which correspond to MS-Latin1 values 0xA0 - 0xAF. I tried Alt-0161 (upside-down !), Alt-0162 (cent), Alt-0163 (sterling pound), Alt-0169 (copyright), Alt-0191 (upside-down ?). These work.
Oh, I should have said in previous comment: Build 1999-05-04-08 running on US NT4.
See Bug 5930 for another problem related to handling 0x80 - 0x9F range characters for Mail Subject field for Latin 1 mail.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
The reason Ender doesn't display the characters is that it is never seeing them in the first place. In the widget code characters are being translated to ASCII. *** This bug has been marked as a duplicate of 4819 ***
I don't think this is the problem. Some non-ASCII are displayed. Only the MS-Latin1 0xA0-0xAF (at least some -- I did not verify for all) are not being displayed. Characters greater than 0xAF (at least some, as I noted in my first comment -- I did not verify for all) are being displayed.
Status: RESOLVED → VERIFIED
its a dup...marking verified...
Reassigning all bugs Assigned To kostello to buster
All these bugs were marked "New" when Jan transfered ownership of them to me. They were all resolved and need to be marked "Verified" again.
Status: NEW → RESOLVED
Closed: 26 years ago26 years ago
This was Verified on 05/05/99...resetting back to Verified...Bugzilla wacked out.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.