215032 - Composer or mail composer editor can't produce a c cedilla using correct key sequence

Status: RESOLVED WORKSFORME

(Core :: XUL, defect)

Description

[Paulo Licio de Geus]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

When composing a message or a page, using character coding iso-8859-1 (or -15),
a c cedilla should be produced by typing "'" (acute accent), followed by "c".
This used to work till 1.2.1 that I previously used. 1.4 gives, as I type, a "c"
with an acute accent. If a send the msg back to me through my postfix mailer
(BTW, mozilla complains that I'm using characters that can't be produced with
the current coding scheme), what a see on screen is a "'", followed by a "c".

This happens with capital C cedilla and has nothing to do with my X environment
(all other applications are still producing c cedilla correctly).


Reproducible: Always

Steps to Reproduce:
1. select one of iso-8859-1, iso-8859-15 or UTF-8 coding schemes
2. open editor to compose a message or a page
3. type "'" (acute accent) followed by "c".

Actual Results:  
The editor produces an acute-accented "c" (not part of 8859-1).

Expected Results:  
The editor should produce a "c cedilla".

Using modern theme (don't think this is relevant...)

Comment 1

[Kathleen :Brade]

-->blizzard
Blizzard--wasn't there some changes between 1.2 and 1.4 that might have affected
this?

Comment 2

[Christopher Blizzard (:blizzard)]

Was this a gtk2 or gtk 1.2 build?

Comment 3

[Paulo Licio de Geus]

Well, turns out this is a configuration and/or compilation error introduced by
the Redhat compilation (1.4 for Rawhide). The standard mozilla 1.4 distribution
works OK, though I wanted the Redhat compilation due to the choice of
configuration parameters, such as xft enabled, unavailable in the mozilla
distro. I ended up doing my own configuration/compilation, which doesn't present
the problem.

Comment 4

[Christopher Blizzard (:blizzard)]

What did you use for your configuration parameters?

Comment 5

[Paulo Licio de Geus]

That's my .mozconfig:

# sh
# Build configuration script
#
# See http://www.mozilla.org/build/unix.html for build instructions.
#

# Options for client.mk.
mk_add_options MOZ_OBJDIR=/usr/src/redhat/SOURCES/mozilla-build

# Options for 'configure' (same as command-line options).
ac_add_options --enable-default-toolkit=gtk
ac_add_options --enable-calendar
ac_add_options --enable-xft
ac_add_options --enable-crypto
ac_add_options --disable-installer
ac_add_options --disable-debug
ac_add_options --enable-optimize=-O4
ac_add_options --with-default-mozilla-five-home=/usr/local/mozilla

Comment 6

[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 7

[Paulo Licio de Geus]

Well, I forgot I had submitted this bug, but I have since learned that this is a clash of   
possible alternatives in gtk, and not a mozilla fault (discussions about this can still be 
found on the Web). 
 
People using the pt_BR.UTF-8 locale and a us_intl keyboard layout must, to this day, 
change a few lines in /usr/lib/X11/locale/pt_BR.UTF-8/Compose to change from the 
default "accute c" to "cedilla c". 
 
As far as Mozilla's concerned, you can consider this as history... 

Comment 8

[Christopher Blizzard (:blizzard)]

I just tried this in a Firefox 3 Beta 1 build and was able to use my compose key to compose that character.  Marking as WORKSFORME.  (Also, this is gtk2, not gtk 1.x.  We don't support 1.x anymore.)