Closed Bug 88342 Opened 23 years ago Closed 23 years ago

cannot type oacute character

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: martin.macok, Assigned: asa)

Details

Attachments

(1 file)

When I want to type "o with accent" (o') (composed by dead keys) it types "n
with accent" (n') instead. This is in URLbar, Form Fields, Composer and various
mozilla's dialogs (seems to be in ALL components of mozilla).

This does happen with NO other apps (GTK apps, KDE/QT apps, xterm ... WFM).

Reproducible with BOTH latest trunk and latest pre0.9.2-1 from
http://ftp.mozilla.org/pub/mozilla/nightly/latest-0.9.2/Red_Hat_7x_RPMS/

My system is Red Hat Linux release 20010619 (Rawhide).XFree86-4.1.0-0.5.9
gtk+-1.2.10-1
glibc-2.2.3-11

locales LC_ALL=cs_CZ

XF86Config-4:
...
Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "keyboard"
        Option      "XkbRules"    "xfree86"
        Option      "XkbModel"    "pc104"
        Option      "XkbLayout" "cz_qwerty"
EndSection
...
Martin, why has you given this bug report severity level "critical"?

According to the on-line help, this means
"Critical crashes, loss of data, severe memory leak".

Wouldn't "major" be more appropriate?
Yes, you're right. I meant to mark it MAJOR and I thought I marked it as.
I need to move my mouse more carefully and double recheck ...

-> Major
Severity: critical → major
I can confirm this on 0.9.1 GNU/Linux Debian (woody). Both combinations
'deadacute + o', 'deadacute + n' produces 'nacute'. And yes, this bug is
specific to mozilla. (maybe it should be in 'editor' section?)
After 3 hours of investigation I've found that this bug isn't Mozilla's. So I've
suspected the gtk+ and then I've finally found that this is a bug in the XFree86
server.
It is sending bad keysym (keysym of the nacute instead of oacute) in the
keypress event. But the other applications get the right value because the
lookup for the actual charcode returns fine the oacute character. Mozilla
however doesn't use the charcode but the keysym.

Someone should send the attached patch to XFree86 developers.
The bug is in the file 'nls/Compose/iso8859-2' in the XFree86 source tree. It
may be even fixed in XFree86 4.1.0, because I have only the XFree86 4.0.1,2,3
(all of which are buggy).
 
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Summary: cannot type some iso-8859-2 characters → cannot type oacute character
I've emailed the report and the patch to the i18n@xfree86.org mailing list, but
I don't know if it's the right place to report the bug.
Fixes should be sent to fixes@xfree86.org.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: