Closed Bug 151726 Opened 22 years ago Closed 21 years ago

"-splash" prevents use of accented characters

Categories

(Core :: Internationalization, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 118478

People

(Reporter: p.fessel, Assigned: shanjian)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020605
BuildID:    1.0.0

Whenever I start mozilla with -splash option, no accented characters are shown
on composer. That is, I can't type text in accented brazilian portuguese. The
problem goes away if I don't use the option. 

Reproducible: Always
Steps to Reproduce:
1. Start mozilla from command line with "mozilla -splash". Or, modify the
startup script of mozilla to include the "-splash" parameter on it.
2. Fire up composer.
3. Try to type accented characters with dead keys.

Actual Results:  There will be no accented letters on the screen. The dead keys
work as should but no accented characters are shown.

Expected Results:  Show correctly-accented characters.

Mandrake 8.2 with packages compiled from mozilla-1.0-1.2mdk.src.rpm.
XFree 4.2 with NVidia GeFORCE 2 MX400 card.
KDE 3.0.1 configured for US-International keyboard.
Linux 2.4.18-xfs-1.1
-->akk for triage
Assignee: syd → akkana
I'm a novice with dead keys, so I may need some help to reproduce this.

Here's what I tried on Redhat 7.3 (I told it to enable dead keys when I
installed, but I'm using keyboard layout "us" in XF86Config-4):

cd /usr/share/xmodmap
xmodmap xmodmap.fr

Then, in a composer window, I hit the '[' key twice (which is one of the dead
keys in xmodmap.fr), and got a circumflex.

Then I exited mozilla, ran it again with -splash, and brought up a composer
window.  I hit the [ key twice, and I got a circumflex, as before.

Mandrake 8.1 had some very nonstandard key mapping (they mapped the alt key to
meta, which caused problems in lots of apps) and my first inclination is to say
this is probably something weird that Mandrake 8.2 is doing.  But if it's
different depending on whether mozilla shows its splash screen, there's a
mozilla issue here too.  Please give me more details on what keymap I should
use, the command line to start mozilla, and exactly what I should type in the
composer window.  And do I need any particular locale environment variables set?

It's definitely the splash screen, not the profile manager, right?  We have
known issues with some key events not working right if you go through the
profile manager when starting up, but none of them should apply to the splash
screen.
Hello Akkana, here is the keyboard section of my XF86Config:

Section "InputDevice"

    Identifier "Keyboard1"
    Driver      "Keyboard"
    Option "AutoRepeat"  "250 30"

    Option "XkbRules" "xfree86"
    Option "XkbModel" "pc102"
    Option "XkbLayout" "us_intl"

EndSection

As you can see, I'm using "us_intl" for the keyboard layout, that is the XFree86
equivalent of Windows' "US International" (US keyboard with dead keys). I'm not
using KDE's keyboard layouts as they interfere with Kylix and God knows what
other applications.

The command line to reproduce is just mozilla -splash; after this, try to
compose an e-mail message. I've just gave it a try and the bug is still here.
For example, in portuguese we use frequently the sequence of characters "усo" ou
"ушes"; the "у" is obtained typing "'" and "c" immediately thereafter; the "с"
and "ш" are obtained by typing "~" immediately before typing "a" or "o",
respectively. When we use "-splash", the dead keys work - that is, nothing is
shown when you type "~", "'", "^" and """ (the umlaut) but when you type the
desired letter they appear without accents. In the examples I gave, you should
get "cao" ou "coes".

I've not tried profile manager, so I assume that the bug is really composer-related.
I just tried it on Debian with this keyboard section in XF86Config-4:

        Identifier      "Generic Keyboard"
        Driver          "keyboard"
        Option          "CoreKeyboard"
        Option          "XkbRules"      "xfree86"
        Option          "XkbModel"      "pc104"
        Option          "XkbLayout"     "us-intl"

Neither ~ nor ' act as dead keys: they just insert those two characters
respectively, in Mozilla Composer (with or without -splash), mozilla text
controls (like this textarea), and xterm.  So there's still something I'm
missing compared to your set.  I'll keep trying ...
Hello again, Akkana.

Have you checked locale settings? Mine are as follows:

SYSFONT=lat1u-16
LC_CTYPE=en_US
LC_MONETARY=en_US
LANGUAGE=en_US:en
LC_TIME=en_US
LC_NUMERIC=en_US
LC_COLLATE=en_US
LC_MESSAGES=en_US
LANG=en_US
SYSFONTACM=iso8859-1

There's also /etc/sysconfig/keyboard in Mandrake:

KBCHARSET=C
DISABLE_WINDOWS_KEY=no
BACKSPACE=Delete
KEYTABLE=us-latin1

Finally, try to load the console keymap; in Mandrake it is us-latin1.

HTH
I18n folk: do you have any idea what might be going on here, or how to reproduce
it?  I've been unable to reproduce it on Redhat, Debian, or SuSE but it might
take a machine that's really set up to do international input.
Assignee: akkana → yokoyama
Component: Editor: Composer → Internationalization
QA Contact: sujay → ruixu
cc simon and bstell
Assignee: yokoyama → shanjian
QA Contact: ruixu → ylong
Paulo, could you try a recent mozilla nightly build (anything after March 3
2003) and see if this behavior is still present? I suspect bug 118478 may have
resolved this issue. Apparently, the GTK library, including its locale support,
was being initialized differently with and without -splash.

If you find the problem is resolved, please resolve this bug as FIXED or as a
dupe of bug 118478.
No response from the reporter. I'm going to go ahead and resolve this as a dupe.
Paulo, if you think this is still a problem with current versions of mozilla,
please feel free to reopen the report.

*** This bug has been marked as a duplicate of 118478 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Mark as verified as fixed in bug 118478.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.