Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add bépo layout as a host keyboard layout #1303

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

nicos68
Copy link

@nicos68 nicos68 commented Aug 23, 2023

This PR offers a solution to #1069. See my comment here. The idea is to add the bépo layout among the selectable layouts in the Layout editor section of the User Interface preferences:
image
As said in my comment the result is not perfect (so don’t hesitate to make suggestions) but it is a dramatic improvement for bépo users:
image
I only have a Fedora machine so I couldn’t test this on anything else, so don’t hesitate to make more tests.

@obra
Copy link
Member

obra commented Aug 23, 2023

So the other custom layouts assume a "traditional" host keymap. (Dvorak and Colemak both assume your host's layout is set to QWERTY.) Among other things, that allows the keyboard to work correctly when used on an "unconfigured" keyboard.

Would it make sense to have the Bépo layout assume an AZERTY configured computer instead?

@nicos68
Copy link
Author

nicos68 commented Aug 23, 2023

So the other custom layouts assume a "traditional" host keymap. (Dvorak and Colemak both assume your host's layout is set to QWERTY.) Among other things, that allows the keyboard to work correctly when used on an "unconfigured" keyboard.

Would it make sense to have the Bépo layout assume an AZERTY configured computer instead?

Hi,
on my machine the host os keyboard layout is set to bépo.
image
I made this xml file making the assumption that the user has set their host os keyboard layout to bépo, which is natively available on linux.
In my case it doesn’t make sense, and I’d say for a Linux user it doesn’t either, because as bépo is easy to configure, there’s no point complicating thing with transcoding like that.
For Windows it’s feasible but a bit more difficult, and I can’t speak for macos users.

And bépo has been normalized by a french authority (AFNOR), so I wouldn’t call it a custom layout.

@obra
Copy link
Member

obra commented Aug 23, 2023

I understand that for your particular setup, a native Bépo configuration is absolutely the right thing, but need to think about the more general case of a default configuration for users who want Bépo to "just work" for their keyboard. The right answer might be to offer both configurations.

@nicos68
Copy link
Author

nicos68 commented Aug 24, 2023

Maybe there could be a "French bépo (native)" and a "French bépo (emulated)" entry with tooltips to explain what each is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants