Compose and FN Combo Requests for Arabic-derived alphabets #769
Comments
|
The glyphs have been made, @Julow ! Except there's a couple things to know about them: Firstly, I had to change the font for those, because Roboto had improper shapes and even missing shapes for some of them. I used Noto Naskh Arabic. Secondly, these glyphs feel cramped. How important is it that I keep the symbol within bounds? Would it be okay to scale down the half-circle to make more room for the diacritic? |
|
Here's the same table with less cramped versions of the glyphs, assuming that it's okay for the shapes to poke through the ceiling like this. When I was working on combining forms of the existing glyphs, I noticed that some of them poked through the ceiling a bit, so I thought that might be fine. If it is fine, let's try these:
|
|
Here's the same table once again, but this time I shrank the half-circle thing to make more room.
|
|
I added another symbol: the small-alef diacritic which goes below the letter rather than above.
|
|
The only problem is |
|
Wow, Jules! I'll keep toying with it, but my initial impression is just… Chef's kiss, my friend🤩! This is incredible. It's so powerful, without being cluttered |
|
As for Fn+space, I apologize for that oversight. It could just go on Fn+: in that case. Or alternatively, Fn+، which is just the arabic version of the comma. |
|
Ok I've toyed some and found a couple of things. So I didn't realize, but the persian numbers, ۷ and ۸, are different codepoints than the arabic counterparts, ٧ and ٨ even though they pretty much look identical. So for keyboard layouts that use the arabic versions of the numbers, let's add the following which are essentially duplicated from what we have already, but with the persian codepoint swapped for the arabic one:
Then, since arabic and persian have slightly different versions of the same letter— ي and ی, respectively — I tried to make sure each combination that used this letter was duplicated so that it would work with either version of the letter. With the following three, I didn't realize I neglected to do this, so let's also add:
And then, with the FN variants, I noticed this discrepancy in behaviour. The OP table had these:
whereas in this build it behaves rather like this:
|
|
Thanks for taking a look! I have done the fixes you listed, here's the new debug build: https://github.com/Julow/Unexpected-Keyboard/actions/runs/11990917674?pr=807
I went for |
There are hardly any compose combos or FN alternates yet set up for the
arabic-based letters, so I thought I'd put together some. I think this is a
strong start, but we'll probably want to add more to this list at some point.
But basically, I considered the alphabets for Arabic, Persian, Kurdish, and
Urdu, and the goal was to create combinations that would allow someone with just
one of those language's keyboards to type the letters which are present in the
other languages but absent in their own, and to type them without having to
enable an additional keyboard.
The text was updated successfully, but these errors were encountered: