Bug 9466 - French map: nobreakspace change request.
Summary: French map: nobreakspace change request.
Status: RESOLVED WONTFIX
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high enhancement
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-28 06:01 UTC by Bob Mauchin
Modified: 2007-01-02 12:01 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Mauchin 2006-12-28 06:01:26 UTC
Hi,

First, your new layout rocks ! I was a bit disappointed but now I've unset my
Compose key, and use the four-level definition.
I just want to ask if the following method is possible :

    key <SPCE>  { [            space,            space,               
nobreakspace,          nobreakspace ] }; // ␣ ␣ ⍽ ⍽ (espace insécable)

Because it's a bit boring to use nonbreakspace with three keys together, and its
use is common in french translation.

Thanks a lot.

Bob Mauchin
Comment 1 Sergey V. Udaltsov 2006-12-29 12:31:09 UTC
I really do not mind this change. Nicolas, what do you think?
Comment 2 Denis Barbier 2007-01-02 11:37:01 UTC
I dislike this change, for the same reason as is written into symbols/fi:
  // AltGr+<SPCE> is pressed accidentally too often after AltGr+<LSGT>,
  // hence AltGr+<SPCE> produces now space, not nobreakspace.
Anyway, users can try the new nbsp:level3 option for this purpose.
Comment 3 Sergey V. Udaltsov 2007-01-02 12:01:55 UTC
Actually, Denis, I think you are right. Since now we have all sorts of nbsp:*
options, let's leave it as it is. Users can have this functionality already...

PS Personally I usually do not care about 3rd and 4th levels because neither
Russian not American layouts have it...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.