unable to type <, > and | while using Finnish layout on a 101-key keyboard

Bug #181595 reported by Toni Ruottu
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xkeyboard-config
Fix Released
Medium
xkeyboard-config (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xkeyboard-config

This may affect also other layouts that were originally designed for a 102-key keyboard.
Inability to type <, > and | is very irritating while trying to use traditional UNIX applications.

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi toni-ruottu,

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with the latest development release of Ubuntu? (ISOs are available from cdimage.ubuntu.com)

If it remains an issue, could you also attach a new /var/log/Xorg.0.log?
Thanks in advance.

The output of lspci -vvnn would also be worth having.

Changed in xkeyboard-config:
status: New → Incomplete
Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Is this some sort of a trick question? My bug report is about a problem in the keymap. It has nothing to do with pci bus or Xorg failures.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

It's the default copy-paste to X-related bug reports which have no attachments.

The problem might be in the X / GNOME keyboard settings. As of 8.10, no xorg.conf is needed anymore, and the default auto-detection should theoretically work. The keyboard settings come now from /etc/default/console-setup (see https://wiki.ubuntu.com/IntrepidReleaseNotes/fi#X.Org-sy%C3%B6telaitteet).

So the system has been quite revamped for 8.10 release, which might be enough to resolve the problem (if just willing to upgrade to 8.10).

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

It is not a detection problem. The 101-key keyboards don't have the button which is mapped to <, > and |. So in order to fix this, the Finnish keymaps need to be extended with a secondary way of typing <, >, |. When the preferred key is missing.

Bryce Harrington (bryce)
Changed in xkeyboard-config:
status: Incomplete → Confirmed
importance: Undecided → High
Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Tony, what's your proposal? We could try putting these keys on 3rd level, if you like. But if we do it in Finnish layout, it will also affect people with larger kbds.

Another question - if you chose US layout, do you have normal access to these characters? Why not add US as a second layout - and use, for example, group:rctrl_switch option?

PS Honestly, never realized there are still 101-keys around;)

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

What does "3rd level" refer to? I think the change should affect users with larger kbds as well, because this would make it easier to learn about these alternative ways of writing those characters.

Rctrl_switching is a good duct tape fix, but Ubuntu ought to have something that worked without tweaking.

I wonder, if any other layout suffers from the same problem.

Bryce Harrington (bryce)
Changed in xkeyboard-config:
status: Confirmed → Triaged
Revision history for this message
In , Bryce Harrington (bryce) wrote :

Forwarding this bug from a Ubuntu reporter:
https://bugs.edge.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/181595

[Fwiw, I searched through launchpad for other clear dupes of this bug, and there are several with issues relating to <>|\, but it was uncertain if they were dupes or other bugs that just had similar symptoms.]

[Problem]
The Finnish 101-key keyboards don't have the button which is mapped to <, > and |. So in order to fix this, the Finnish keymaps need to be extended with a secondary way of typing <, >, | when the preferred key is missing.

[Original Report]
This may affect also other layouts that were originally designed for a 102-key keyboard.
Inability to type <, > and | is very irritating while trying to use traditional UNIX applications.

I think the change should affect users with larger kbds as well, because this would make it easier to learn about these alternative ways of writing those characters.

Rctrl_switching is a good duct tape fix, but Ubuntu ought to have something that worked without tweaking.

I wonder, if any other layout suffers from the same problem.

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

answered there.

Revision history for this message
Bryce Harrington (bryce) wrote :

Forwarded this up to the xkeyboard-config bug tracker in case it's more convenient for svu to track it there. Toni, please subscribe to this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=20300

Changed in xkeyboard-config:
status: Unknown → Confirmed
Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

"3rd shift level" is usually accessed by presing RAlt (2nd level is accessed with any Shift). If you think that putting extra mappings to 3rd level is ok (people won't complain), we can do that.

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

I used to map
AltGr+z to <,
AltGr+x to >, and
AltGr+§ to |
(§ refers to the key above tabulator, one step left from key "1", below Esc)

This mapping worked ok for me while I was using a "Happy Hacking" keyboard (a stripped down 101-key kbd).
Yet, there are some things to consider:

- AltGr+z and AltGr+x are currently in use. They map to ʒ and ×. I just trashed those because I didn't need them that often. Maybe someone needs them? Could they be moved?
- in any case < and > are needed quite often, so mapping them in some really awkward place is not a good idea either
- it would be good for this redundant mapping to be in place even when it is not needed. This helps the users find it and try it out while they are lucky enough to not need it.
- It would further help users to find the feature, if the functions from the potentially missing key would be mapped in a similar manner between different layouts. Are AltGr+z and AltGr+x equally available for this use on all 102-key layouts?
- Is the key that produces § available on most obscure keyboards. I doubt anyone would want to add separate fixes
  for yet another obscure keyboard, so this fix might as well map it to something that is very likely to be around.
- My choice of key § is completely arbitrary. Is there a combination for | that would be easier to guess? Maybe AltGr+L (with a lowercase L) would be good? Would that be available for this use on all 102-key kbd layouts?
- Is the problem only about people not being able to produce characters that get mapped to the missing key? Maybe someone needs support for actually producing the key code for that button (this might ofcourse be another bug)

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Of course, technically everything can be moved. But in reality it would lead to some number of irritated users. I would do everything to avoid that. Could you please use some available AltGr combinations? Actually, in the default variant fi(kotoistus) there are very few empty spaces (NoSymbol), almost all of them on level 4 (AltGr-Shift):

AltGr-1, AltGr-Shift-~, AltGr-Shift-7, AltGr-Shift-8, AltGr-Shift-9, AltGr-Shift-e, AltGr-Shift-i, AltGr-Shift-s, AltGr-Shift-k, AltGr-Shift-l.

Feel free to choose. All other symbols, as I understand, are specified in kotoistus, so we cannot move them without breaking compatibility.

Yes, your changes will be available to 102-key configurations.

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

In that case I'd go for:

AltGr-Shift-8 to <,
AltGr-Shift-9 to >, and
AltGr-Shift-i to |

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Just noticed the missing key has ¦ as well. So let's go for:

AltGr-Shift-8 to <
AltGr-Shift-9 to >
AltGr-Shift-i to |
AltGr-Shift-l to ¦

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

key 8 has currently characters ( and [
key 9 has currently characters ) and ]
so, if you think of < and > as they are used in xml tags they have a similar opening (<) and closing (>) association.

with | and ¦ it would be a good to choose a key that has something similar in it. Key 1 is too far away to be reached conveniently. We also need two combinations as they are two different characters. so let's use l and i.

One may wonder why I chose l for ¦ and i for |. Indeed l looks more like | and i looks more ¦. And that is my reason. You want to be able to tell the characters apart. l and | look too much in common. It can cause errors. Also | is needed more often and you'd normally press i with a stronger finger than l.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

The current layout is from Research Institute for the Languages of Finland, approved last year by Finnish Standards Association SFS and is available at http://www.kotoistus.fi/nappaimisto.htm. More Linux-specific information at http://kotoistus.tksoft.com/linux/index-en.html. Indeed any mapping specified there should not be changed. 8, 9, l and i look like currently being available (1 is mapped to ¡).

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

Copy from launchpad. Solution which is going to be implemented:

AltGr-Shift-8 to <
AltGr-Shift-9 to >
AltGr-Shift-i to |
AltGr-Shift-l to ¦

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

Committed, please check in git

Revision history for this message
In , Troy (tjk-tksoft) wrote :

<> and | (007C, bar) are on the missing key, and have a clear need.

I would not add the broken bar (00A6) to the layout, though. When we drafted the Finnish standard, we tried to avoid adding extraneous characters with no common use. We specifically excluded math, typography etc. symbols. Having extra characters available, with similar appearance to other characters (bar vs. broken bar), will confuse users and will inevitably lead to typos. The broken bar character is not commonly used, except in specialized applications.

More importantly, there are only a limited number of positions on the keyboard. By defining a use for every position, future additions become impossible. The fact that we left as many positions as possible unused, is the reason this fix is now possible.

As an aside, I think this is a welcome addition to the layout. I recently noticed that at least the EeePC has combined the <>| key and zZ keys into one key, with a meta(a green) key used to activate the <>| functionality. The solution works, but it's clearly better to have a universal solution for all keyboards which are missing the key.

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

Which positions do you prefer? There is not much of a choice...

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

Sorry, I've asked wrong question. What's wrong with adding broken bar? Or do you have better candidates?

Revision history for this message
In , Toni Ruottu (toni-ruottu) wrote :

Troy: You do realize that broken bar is normally produced with AltGr+Shift+the102thkey? Atleast my Ubuntu does that. Isn't that part of the official Kotoistus-keymap then?

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

I think this is acceptable.

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

Fixed upstream

Revision history for this message
In , Troy (tjk-tksoft) wrote :

I recommend adding the bar (007C) to Shift+AltGr+L (level 4).

I see no reason for adding the broken bar. Just because it is on some other keyboard is not a valid reason. There are several characters and symbols which would be much more useful, and which are not added. Users should use the combinations specified in the compose file if they need those rare characters, or some application specific solution (e.g. layout programs, math programs have their own solutions for specific symbols).

Here are my recommendations:

Add < to level 4 of AE08 (8).
Add > to level 4 of AE09 (9).
Add | (007C, vertical bar) to level 4 of AC09 (L).

I.e.
key <AE08> { [ 8, parenleft, bracketleft, less ] };
key <AE09> { [ 9, parenright, bracketright, greater ] };
key <AC09> { [ l, L, dead_stroke, bar ] };

Revision history for this message
In , Troy (tjk-tksoft) wrote :

The broken bar is not part of the standard. You can see the current positions on my pages at

http://kotoistus.tksoft.com/linux/symbols_fi.txt

I will post these changes there shortly too. The data there now is all according to the standard, with no additions. This will be the first addition. It will not affect standards conformace, as additions are allowed. Replacements and omissions are not allowed.

Revision history for this message
In , Troy (tjk-tksoft) wrote :

The right windows key is specified as the compose key in this layout. Using the compose key we have a semi-universal (X11 only) solution for entering a large number of characters.

FYI: There is some work being done to address this issue of entering random characters (ones not in the national layout). The CEN/MEEK (csc.fi/meek) workgroup is discussing the issue, and there is also work being done at ISO (revising 9995-3). As part of the MEEK workgroup, I have also proposed a "global IM" solution which would address this issue. You can find it on the MEEK site.

Revision history for this message
In , Toni Ruottu (toni-ruottu) wrote :

Why L for bar? I looks more like a bar and is easier to access. The bar is needed rather frequently by people using command lines, and I'd really respect being able to press I instead of L.

Also, using I would cause all 102thkey features to appear in a compact triangle shaped area on most keyboards due to the physical layout of 8, 9 and I

Revision history for this message
In , Troy (tjk-tksoft) wrote :

You're right. 'i' on the keyboard looks like a bar. I see no reason why it wouldn't be a good spot for it. I.e.

key <AD08> { [ i, I, idotless, bar ] };

L unchanged, i.e.
key <AC09> { [ l, L, dead_stroke, NoSymbol ] };

Revision history for this message
In , Toni Ruottu (toni-ruottu) wrote :

Could someone please GIT the final result and mark this as fixed again?

Revision history for this message
In , Toni Ruottu (toni-ruottu) wrote :

Where is the GIT repository anyway? And where is the map file inside it?

Revision history for this message
In , Troy (tjk-tksoft) wrote :

The URL is
http://cgit.freedesktop.org/xkeyboard-config/tree/symbols/fi
Let's wait for Sergey to do the actual change.

Revision history for this message
In , Sergey V. Udaltsov (svu) wrote :

Done! Thanks lads for settling it so fast.

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Discussions in Freedesktop.org bug thread resulted in a decision to leave redundant mapping for broken bar out, as it is unclear, if broken bar should indeed have a direct mapping at all. It might be that broken bar will in future be supported only through character composing features involving the right side "Windows key".

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Now that we got it fixed upstream.
How long will it take for the fix to get into Ubuntu?
Is it going to be in Jaunty? Karmic? Next LTS maybe?

Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Oh, and the new map can be found at
http://cgit.freedesktop.org/xkeyboard-config/tree/symbols/fi

(just in case I wasn't the only one looking for it)

Changed in xkeyboard-config:
status: Confirmed → Fix Released
Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

I think this is how the process goes:

 1 Changes go into freedesktop.org git repository (that already happened)
 2 A release happens at http://cgit.freedesktop.org/xkeyboard-config
 3 Debian packages the new release
 4 The new Debian package gets pulled into Ubuntu

I guess there is no way all this could happen before Jaunty gets released,
but I hope it can be done in time for Karmic. Are xkeyboard-config releases
synchronized with xorg releases, or are they free to happen at any time?

Revision history for this message
Sergey V. Udaltsov (sergey-udaltsov) wrote :

xk-c is released on 4-monthly basis. Next release is in May

Revision history for this message
Bryce Harrington (bryce) wrote :

> I guess there is no way all this could happen before Jaunty gets released,

Ha, like ninjas in the night we are, picking the cherries...

Thanks, patch queued up for jaunty.

Changed in xkeyboard-config (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xkeyboard-config - 1.5-2ubuntu8

---------------
xkeyboard-config (1.5-2ubuntu8) jaunty; urgency=low

  * Update 106_ru_fix_shift.patch: Remove extraneous parts to only
    change the minus/underscore issue. Upstream.
    (LP: #309844)
  * Add 109_de_low_quotemarks.patch: Add keys for typing low quotation
    marks. Upstream.
    (LP: #59572)
  * Add 110_fi_brokenbar.patch: Add keys for bar and broken bar symbols in
    the finnish keymap. Upstream.
    (LP: #181595)
  * Add 111_si_rm_unnecessary_diagraph_layouts.patch
    and 112_si_rm_unnecessary_diagraph_layouts_basexmlin.patch:
    Remove unnecessary diagraph layouts. Upstream.
    (LP: #162462)
  * Add 113_kg_fix_kyrgyz_layouts.patch: Update to official Kyrgyz
    Republic layouts. Upstream.
    (LP: #198655)

 -- Bryce Harrington <email address hidden> Wed, 18 Mar 2009 22:02:42 -0700

Changed in xkeyboard-config:
status: Fix Committed → Fix Released
Revision history for this message
Toni Ruottu (toni-ruottu) wrote :

Thank you. I'm very happy about getting the mapping for Jaunty.

I took a look on the mapping file. It seems that Jaunty will have the broken bar mapping (AltGr+Shift+l). This mapping was decided to be removed in a further update to the xorg key map file, but I guess that won't be a problem. Iirc broken bar did not exist at all in the original Kotoistus mapping and is not needed that often, so reserving another key combination for it would have been waste. Thus AltGr+Shift+l is unmapped in the current edition. This will only be a problem, if some users start to use the combination before moving Karmic which will obviously have the later version which removes this feature. I think that is not too likely to happen.

Changed in xkeyboard-config:
importance: Unknown → Medium
Changed in xkeyboard-config:
importance: Medium → Unknown
Changed in xkeyboard-config:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.