layouts/latn_bone.xml: improve #760
Conversation
quantenzitrone
changed the title
quantenzitrone
force-pushed
the
main
branch
from
4a06c5f
to
cadd6c4
Compare
quantenzitrone
changed the title
quantenzitrone
force-pushed
the
main
branch
from
cadd6c4
to
25f0c95
Compare
There was a problem hiding this comment.
Thanks!
switch_backward and switch_forward are extremely important keys as they allow between layouts.
The bottom row is similar to the default one except for some keys added in this PR. To avoid maintaining this in the future and missing new features, what do you think of removing the custom bottom row in this layout ? The cost is to move 0 elsewhere.
|
I've always been switching keyboard with |
|
Oh I realize its for switching the internal layout. |
new syntax: n/s/e/w/ne/nw/se/sw instead of key{1..8}
Some keys were missing keys according to the tests, this adds them in a
similar way to latn_neo2.
Only `switch_forward` didn't fit (because of the 0
at the bottom of the spacebar).
quantenzitrone
force-pushed
the
main
branch
from
7dd7c01
to
ee4c6d6
Compare
|
Ok now only I could put the |
|
I have an idea. |
|
Do we have these diacritical marks? |
That means having to maintain the layout more often and having inconsistent placement for important keys.
That's currently only possible by modifying the app to add this combinaison as a new diacritic.
We don't have Rough and Smooth breathing I believe but they could be added if necessary. |
- use number row to unclutter rest of keyboard - use modmap for special shift functions of bone layout - add missing loc characters - use standard bottom bar - add diacritics from the 3 dead key keys on bone - 2 small keys left and right of the number row (don't fit all 6 diacritics, so they leak onto the number keys) - row 1 is full too, so the dead keys from the left of that row leak onto the keys there as well open questions: - should bone rely on the math layer or use modmap? - possibility to combine diacritics?
quantenzitrone
force-pushed
the
main
branch
from
ee4c6d6
to
8d3a8a2
Compare
|
Nah I think rough and smooth breathing are not necessary. |
quantenzitrone
changed the title
|
Would you accept if I add neo specific modifiers (diacritics)? |
|
Adding neo specific diacritics and compose sequences to the app is fine! It's possible to add a new compose key that is either a pre-applied sequence or an entirely different set of sequences. |
|
If you want, you can merge this like this. |
There was a problem hiding this comment.
The layout is extremely busy and the extra row makes it hard to read. Are you sure you need all these symbols on the main layer ?
Many of these are already on the Fn layer or in compose sequences. For even more symbols, I'd suggest you to make a second custom layout dedicated to rarely used symbols.
| <shift a="4" b="»"/> | ||
| <shift a="5" b="«"/> |
There was a problem hiding this comment.
yeah the fn mapping conflicts with neo layouts,
i was considering removing it or completely mod-remapping it for some other purpose
| <shift a="8" b="„"/> | ||
| <shift a="9" b="“"/> | ||
| <shift a="0" b="”"/> |
There was a problem hiding this comment.
These are already Fn+", Fn+( and Fn+) respectively.
| <row> | ||
| <!--left side--> | ||
| <key width="0.5" key0="loc accent_circonflexe" nw="superscript"/> | ||
| <key key0="1" ne="¹" se="₁" nw="loc accent_caron" n="subscript"/> |
There was a problem hiding this comment.
₁, ₂, ₃ and ₀ are already accessible with subscript, which is also present on the layout.
Same for the superscripts.
There was a problem hiding this comment.
i think they were put there because ¹²³₁₂₂₀ are used more frequently that all the other numbers
| <key key0="4" ne="›" se="♀" nw="loc accent_hook_above" n="loc accent_horn"/> | ||
| <key key0="5" ne="‹" se="♂" nw="loc accent_dot_below"/> | ||
| <!--right side--> | ||
| <key key0="6" nw="¢" sw="⚥" ne="loc accent_macron"/> |
| <key key0="2" ne="²" se="₂" nw="↻"/> | ||
| <key key0="3" ne="³" se="₃" nw="loc accent_dot_above"/> | ||
| <key key0="4" ne="›" se="♀" nw="loc accent_hook_above" n="loc accent_horn"/> | ||
| <key key0="5" ne="‹" se="♂" nw="loc accent_dot_below"/> |
There was a problem hiding this comment.
‹ and › are already on the keyboard as Fn+{ and Fn+}
| <key key0="1" ne="¹" se="₁" nw="loc accent_caron" n="subscript"/> | ||
| <key key0="2" ne="²" se="₂" nw="↻"/> | ||
| <key key0="3" ne="³" se="₃" nw="loc accent_dot_above"/> | ||
| <key key0="4" ne="›" se="♀" nw="loc accent_hook_above" n="loc accent_horn"/> |
There was a problem hiding this comment.
Do you use symbols like ♀, ♂, ⚥ and ↻ so often that you need them on the main layout ? I'd suggest creating compose sequences for these.
There was a problem hiding this comment.
not really but i just wanted to make it more close to the original
i don't think it hurts to include them
Furthermore, neo layouts use ↻ in compose sequences for rotating characters. e.g. Compose ↻ r becomes ɹ
new syntax: n/s/e/w/ne/nw/se/sw instead of key{1..8}
Some keys were missing keys according to the tests, this adds them similarly to latn_neo2.
Only
switch_backwarddidn't fit (because of the 0 at the bottom of the spacebar).I also added a
\in front of the@, not sure if that is necessary, but it is part of the escape character documentation.