Compose and FN Requests for Greek
anaskaejdar opened this issue · 0 comments
Hi, this goes together with #762 #763 #764 #765
I just thought there are some combinations that would be good to have. Here they are!
COMPOSE:
- Greek has its own ampersand ϗ ... this is short for the word καὶ, so maybe it could be composed with κ+α
- There are musical syllables called pelastikon (𝂴) and gorthmikon (𝂵) which have their own symbols which aren't represented in the primary alphabet. It's worth noting that both of these symbols are also letters in the Armenian alphabet (Ղ and ն) and the armenian versions can already be typed in the armenian keyboard. But I thought the greek versions could be composed like this: Pelastikon would be ν+α and Gorthmikon would be ν+ε
- In a lot of texts, the letters ου are combined together to look like ꙋ. In unicode, though, this ligature is organized with the related cyrillic block rather than directly with greek or greek-extended. Still, it would be fun to compose ꙋ by typing ο+υ
- Another common ligature is to combine σ and τ into ϛ … careful not to confuse this with ς even though computer fonts often make them look the same: they're not the same and traditional fonts make that clearer.
FN:
Well, basically, greek-extended block has a funny situation with oxeia. The standard greek/coptic block has vowels with "tonos," and greek-extended has vowels with "oxeia," but this is redundant, because tonos and oxeia are the same accent mark. It just has the unfortunate effect that it's possible to encode the same text in different ways, because oxeia and tonos are different codepoints. Thus, doing a text-based search through a polytonic greek text is more of a problem than it needs to be. Well, I thought it'd be nice if all the tonos stuff could be swapped out for oxeia if the FN layer is active. It would be extra cool if it also worked the other way, so that oxeia stuff would get swapped out with tonos stuff. That way, the keyboard designer can decide whether tonos or oxeia are default, but that might be technically challenging, I don't know...
That'd obviously turn standalone-acute into standalone-oxeia. Combining-acute remains unaffected, but it'd change the precombined-tonos layer into a precombined-oxeia layer, which seems a bit more complicated. But I hope this helps:
ά ⇒ ά
έ ⇒ έ
ή ⇒ ή
ί ⇒ ί
ό ⇒ ό
ύ ⇒ ύ
ώ ⇒ ώ
Ά ⇒ Ά
Έ ⇒ Έ
Ή ⇒ Ή
Ί ⇒ Ί
Ύ ⇒ Ύ
Ό ⇒ Ό
Ώ ⇒ Ώ
´ ⇒ ´
There are also some more archaic letters that aren't currently made available via FN:
γ+χ (Compose)⇒ ϙ
γ+ψ (Compose)⇒ ϟ
ϙ (Fn)⇒ ϟ
ϟ (Fn)⇒ ϙ
ω (Fn)⇒ ϝ
ALSO, just generally and universally, for any language... when FN is pressed, it'd be good if the accent-layer buttons could be replaced by their combining-accent-character equivalents. But if it seems like FN shouldn't be used for this purpose, then it could perhaps be accomplished by typing backspace with the accent layer active.