Bug 141567 - Compose key not working with danish characters with en_US.UTF-8
Summary: Compose key not working with danish characters with en_US.UTF-8
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X.Org (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-05 12:22 UTC by Jens Axboe
Modified: 2006-01-05 14:21 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Axboe 2006-01-05 12:22:57 UTC 
I always use us keyboards with my computers, and I recently got a new laptop where  I chose to use the compose key in X to type the danish characters. However, with the default setup, only 'æ' (ae) worked. 'å' (aring) and 'ø' (oslash) didn't work. If I switch to en_US.iso8859-1 instead it works as expected.
Comment 1 Stefan Dirsch 2006-01-05 13:43:56 UTC 
/usr/X11R6/lib/X11/locale/en_US.UTF-8/Compose:
[...]
<Multi_key> <o> <a>     : "å" U00E5 # LATIN SMALL LETTER A WITH RING ABOVE
[...]
<Multi_key> <slash> <o> : "ø" U00F8 # LATIN SMALL LETTER O WITH STROKE

Works for me. Maybe you did use it in the different order ("... <a> <o>" and "... <o> <slash>") which is not specified in the UTF-8 compose file and only in the Latin1 Compose file?
Comment 2 Jens Axboe 2006-01-05 13:48:41 UTC 
Could be, I'll retry that when I'm one my notebook.

But isn't it then a bug that the compose sequences aren't the same? Why would it be compose a + a in iso8859-1 and compose o + a in utf (and similar for oslash)?
Comment 3 Stefan Dirsch 2006-01-05 14:12:15 UTC 
You can call it a bug. I prefer to call it a change. :-)

The en_US.UTF-8 Compose file is a (nice) try to merge all the Compose files for the legacy encodings, which is/was not easy because of many conflicts. :-( Therefore I recommend to most people, which use the Compose mechanism, to use a user Compose file instead and adjust it to your needs.

--> $HOME/.XCompose

Most users begin with an empty Compose file, which makes starting of X programs even faster. :-) Is this something you can live with?
Comment 4 Jens Axboe 2006-01-05 14:16:22 UTC 
Yes. ~/.XCompose would be perfect, I wasn't aware that this option existed! I trust I just fill mirror what the locale/xxx/Compose file contains, eg add my 3 characters to what I want?

I'll resolve this bug as WONTFIX then.
Comment 5 Stefan Dirsch 2006-01-05 14:20:06 UTC 
> Yes. ~/.XCompose would be perfect, I wasn't aware that this option existed!

Sure. Nearly nobody knows it.

> I trust I just fill mirror what the locale/xxx/Compose file contains, eg add > my 3 characters to what I want?

Exactly. :-)
Comment 6 Jens Axboe 2006-01-05 14:21:30 UTC 
Great thanks Stefan, that even allows me to define much better compose sequences for these three (often used in dk mails) characters.