Skip to content
This repository has been archived by the owner on Feb 4, 2020. It is now read-only.

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

Open
mkf opened this issue Mar 2, 2019 · 7 comments
Open

Comments

@mkf
Copy link

mkf commented Mar 2, 2019

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

@Joppla
Copy link

Joppla commented Mar 2, 2019

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

@mkf
Copy link
Author

mkf commented Mar 3, 2019

ęóąśłżźćń

photo_2019-03-03_17-47-30

@mkf
Copy link
Author

mkf commented Mar 3, 2019

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

@mgoral
Copy link

mgoral commented Jun 25, 2019

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
Copy link
Member

menny commented Jun 25, 2019

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

@mkf
Copy link
Author

mkf commented Jul 23, 2019

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
Copy link

mgoral commented Jul 23, 2019 via email

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

No branches or pull requests

4 participants