182229 - dead keys don't work with unicode locale

Status: RESOLVED EXPIRED

(Core :: Internationalization, defect)

Description

[Martin Küchler]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.2/mozilla-i686-pc-linux-gnu-1.2-sea.tar.gz

When I changed my locale setting (LANG, LC_CTYPE variables from de_DE@euro to 
de_DE.UTF-8, dead keys stopped working, both in the URL line and in html forms
(That is, they function as ordinary keys). This occurred in Mozilla/1.0.0 from 
Debian and in Phoenix 0.4. All other X-apps did not have this problem. Dead 
keys work as before in all KDE apps and in OpenOffice. I upgraded to Mozilla 
1.2 final but no change. Easy solution : export LANG and LC_CTYPE to de_DE in 
the Mozilla / Phoenix start script and everything works fine. So no big problem 
as to my opinion.

Reproducible: Always

Steps to Reproduce:
change LANG and LC_CTYPE to de_DE.UTF-8 before starting Mozilla
Actual Results:  
"´" + "e" = "´e"

Expected Results:  
"´" + "e" = "é"

Debian/woody

Comment 1

[Paulo Vilela]

I  have  the same problem. My locale was LANG=pt_PT.utf-8, and in the composer
or the "compose message", boyh TXT and HTM pressing an accent ( like tilde ~)
and a vowel would resul in two chararacters ( ~a ) instead of just one accented
character ( ã ) . I had to change the locale to LANG=pt_PT.

This just happens with mozilla, in the other KDE 3.1.1 or GNOME 2.0
applications, like OpenOffice , Evolution, Kate,  the deadkeys wwere working OK.

I have RedHat 8.0, and Mozilla 1.3 (Mozilla/5.0 (X11; U; Linux i686; en-US;
rv:1.3) Gecko/20030312)

Paulo Vilela

Comment 2

[Kathleen :Brade]

*** Bug 202969 has been marked as a duplicate of this bug. ***

Comment 3

[Kathleen :Brade]

*** Bug 192453 has been marked as a duplicate of this bug. ***

Comment 4

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.