AnySoftKeyboard / LanguagePack

[deprecated]
Apache License 2.0
117 stars 186 forks source link

Polish characters like ąęł on second positions in popup despite heavy use #246

Open mkf opened 5 years ago

mkf commented 5 years ago

Polish characters like ąęł on second positions in popup despite heavy use

Joppla commented 5 years ago

Indeed, should be more logical, where to change it?

mkf commented 5 years ago

ęóąśłżźćń

photo_2019-03-03_17-47-30

mkf commented 5 years ago

also btw #245 could be dealt with by adding and « to n and and » to m

mgoral commented 5 years ago

Hi, as Polish LP author I think I can explain my choices. They're not random and I actually spent some time tweaking it.

  1. For numbers it's no-brainer. All numbers are first so there's no exception for "3ę" and "9ó".
  2. I think that in today's world people will more often use "@" than "ą".
  3. ")" is first for a symmetry with "(". It'd be strange if one could open parentheses with long press and wouldn't be able to close it with the same motion. I think that the result would be many mistakes with "ł" written instead of ")" in such cases. Same with "< ń".
  4. Others ("$ vs ś", "/ vs żź" etc) are like that for consistency reasons. I had a legitimate reason (in my opinion) for placing over half of Polish characters as a second choice, so it'd be strange if suddenly some of the others acted differently.
  5. Also important fact is that AOSP keyboard does the same thing for the layout: Polish characters are less important than punctuation. I assumed that AOSP Keyboard authors were more experienced than me and as it basically goes along with my previous thoughts, I decided to leave it this way.

Hope this clears my design choices a little bit.

menny commented 5 years ago

@mgoral thanks for the explanation. @mikrfe makes sense?

mkf commented 5 years ago

I use the "alternative numeric keys" common top row, so i would want to get rid of numbers. But yeah, i understand some don't want it... I have no answer to this, it just feels wrong — but this one compromise is present everywhere and is acceptable.

I dislike this paradigm of punctuation over keys consistently with English layout... Polish heavy use of diacritics for avoiding tremendous ambiguity was already obstructed by Polish Programmer's layout — although in it's case it might have seemed convenient and not too problematic. Hiding Polish diacritics as secondary options might seem fine with aggressive perfect autocorrect (and choosing the right options whenever there is ambiguity, hoping dictionary isn't lacking — feels almost like typing with some T9 sometimes), but without it...

ofc i understand now that what i am opposing here might just be the general paradigm of ASK... so i guess i will just proceed to finding myself something else for now, and, hopefully, maybe writing what i want myself once i will have the means to do so.

mgoral commented 5 years ago

It's obvious that there's no single layout that'll fit all and I totally understand why you would want Polish diacritics before interpunction or numbers. I guess the way to go is creating one or two alternative layouts. It shouldn't be too hard - it's just editing 2 or 3 XMLs.

I'd like to migrate Polish language pack to mono repo first though because that will simplify contributions and release process.

Dnia 23 lipca 2019 18:45:36 CEST, "Michał Krzysztof Feiler" notifications@github.com napisał(a):

I use the "alternative numeric keys" common top row, so i would want to get rid of numbers. But yeah, i understand some don't want it... I have no answer to this, it just feels wrong — but this one compromise is present everywhere and is acceptable.>

I dislike this paradigm of punctuation over keys consistently with English layout... Polish heavy use of diacritics for avoiding tremendous ambiguity was already obstructed by Polish Programmer's layout — although in it's case it might have seemed convenient and not too problematic. Hiding Polish diacritics as secondary options might seem fine with aggressive perfect autocorrect (and choosing the right options whenever there is ambiguity, hoping dictionary isn't lacking — feels almost like typing with some T9 sometimes), but without it...>

ofc i understand now that what i am opposing here might just be the general paradigm of ASK... so i guess i will just proceed to finding myself something else for now, and, hopefully, maybe writing what i want myself once i will have the means to do so.>

-- > You are receiving this because you were mentioned.> Reply to this email directly or view it on GitHub:> https://github.com/AnySoftKeyboard/LanguagePack/issues/246#issuecomment-514291347

-- Wysłane za pomocą K-9 Mail.