TapType v2.0 is out
-
@pvagner I'm going to add more languages. The source code is not published and there is no translation frontend.
@fireborn Oh, yes, I haven't realized it's not open-source. Excuse me for assuming that. -
@fireborn Oh, yes, I haven't realized it's not open-source. Excuse me for assuming that.
@pvagner Adding other languages is possible, but latin-based languages are easier. Others are harder.
-
@pvagner Adding other languages is possible, but latin-based languages are easier. Others are harder.
@fireborn Central european slavic languages are all latin based but their wordlists are much larger than english so I'm not sure you can accept that. -
@fireborn Central european slavic languages are all latin based but their wordlists are much larger than english so I'm not sure you can accept that.
@pvagner larger word lists isn't really an issue
-
@fireborn The word prediction is really good, I like it a lot.
Ere are some issues that i found:
*Sometimes punctuation is spoken in English.
*Ñ doesn't appear in the layout, just next to L.
*When you write a vowel and you choose its accented variation with right, a space is introduced. I'm not sure how to deal with character variants without long presses. Introducing the "´" symbol next to P, like in Latin American Spanish qwerty distribution, would be a good workaround.@muchanchoasado I see what's happening with the accented fouls. They are in the dictionary as words, and shouldn't be. they are committing a space because they are being considered a completed word. If you start typing a word that contains an accented character, the word should be suggested even without typing the accent, so just don't.
-
@muchanchoasado Can you give examples of punctuation names that get spoken in english?
@fireborn the categories and symbols when you swipe right at the end of the list are spoken in Spanish, but the basic symbols with swipes up and down are spoken in english.
Regarding the Ñ bug, I was referring to the physical layout. The last letter on the right side of the screen is L like in English, but in Spanish L is followed by ñ.
You can't write or predict words like año (year) or mañana (morning) because Ñ doesn't appear in the keyboard. -
@fireborn the categories and symbols when you swipe right at the end of the list are spoken in Spanish, but the basic symbols with swipes up and down are spoken in english.
Regarding the Ñ bug, I was referring to the physical layout. The last letter on the right side of the screen is L like in English, but in Spanish L is followed by ñ.
You can't write or predict words like año (year) or mañana (morning) because Ñ doesn't appear in the keyboard.@muchanchoasado I'll make the keyboard just handle that, so you won't need to actually be able to find the letter. Easier for everyone. The punctuation being spoken in english is a talkback issue, it's reading out the character on insert. You can turn off the typing echo or turn off talkback to prove this.
-
@muchanchoasado I see what's happening with the accented fouls. They are in the dictionary as words, and shouldn't be. they are committing a space because they are being considered a completed word. If you start typing a word that contains an accented character, the word should be suggested even without typing the accent, so just don't.
@fireborn There are some situations where a word has a different meaning if it's written with an accent. Si (without accent) means if, while Sí (accented) means yes. El (without accent) is the article the, while él (accented) is the pronoun he. I'll see if these words appear in the dictionary.
-
@fireborn There are some situations where a word has a different meaning if it's written with an accent. Si (without accent) means if, while Sí (accented) means yes. El (without accent) is the article the, while él (accented) is the pronoun he. I'll see if these words appear in the dictionary.
@muchanchoasado they do
-
@pvagner larger word lists isn't really an issue
@fireborn If you would be fine looking at adding slovak language support this appears to be pretty good word list according to my searches: p.brm.sk/sk_wordlist/
Also the upper row of keys has diacritic characters without shift key held down so the layout would have to be tweaked for slovak.
-
@muchanchoasado I have a couple ideas for making this better. The accent path is currently handled though, if you type one of the unaccented words exactly then swipe down you should see that it does let you pick the accented variant
-
@muchanchoasado I have a couple ideas for making this better. The accent path is currently handled though, if you type one of the unaccented words exactly then swipe down you should see that it does let you pick the accented variant
@fireborn Thanks! Please add the "ü" variant as a second option for U, is the only vowel that uses the "¨" symbol in Spanish.
-
@fireborn Thanks! Please add the "ü" variant as a second option for U, is the only vowel that uses the "¨" symbol in Spanish.
@muchanchoasado that just isn't how this works. The keyboard characters aren't really meant to be entered this way. The idea is you tap where the characters would be if typing the word, and the keyboard resolves the word into a most likely word list. I don't think from your messages that's what you're doing
-
@muchanchoasado that just isn't how this works. The keyboard characters aren't really meant to be entered this way. The idea is you tap where the characters would be if typing the word, and the keyboard resolves the word into a most likely word list. I don't think from your messages that's what you're doing
@fireborn My bad! I was typing the entire words most of the time when the core is prediction. I was using it to test the dictionary. In that case, the whole accent situation wasn't really a problem, sorry.
-
@fireborn My bad! I was typing the entire words most of the time when the core is prediction. I was using it to test the dictionary. In that case, the whole accent situation wasn't really a problem, sorry.
@muchanchoasado no, don't be sorry. It's totally okay, it's a usecase I hadn't really considered, it it still resulted in me tracking down a dictionary issue, so thank you!
-
@fireborn My bad! I was typing the entire words most of the time when the core is prediction. I was using it to test the dictionary. In that case, the whole accent situation wasn't really a problem, sorry.
@muchanchoasado I fixed so if you type an exact match to a word, and the variant of the word with an accent is actually more common, that variant will be suggested first. Obviously this will change as the keyboard learns how you type, but there was an issue where the exact match was always being suggested higher than the variant even when the variant should be more common, so thanks for helping me track that one down!
-
@muchanchoasado I fixed so if you type an exact match to a word, and the variant of the word with an accent is actually more common, that variant will be suggested first. Obviously this will change as the keyboard learns how you type, but there was an issue where the exact match was always being suggested higher than the variant even when the variant should be more common, so thanks for helping me track that one down!
@fireborn I'm happy to help! I've never used prediction before because I find GBoard really cluttered and slow to use, specially if you compare it with braille keyboard. TapType's design feels more intuitive and fast.
-
@fireborn I'm happy to help! I've never used prediction before because I find GBoard really cluttered and slow to use, specially if you compare it with braille keyboard. TapType's design feels more intuitive and fast.
@muchanchoasado It was designed so that prediction is the primary input method, and the fallback only exists for those times when prediction is failing or you need to type a word that is not, in fact, a word, like obscure acronyms and such. As a result, it doesn't include a lot of characters on the keyboard face like gboard and others do, so for passwords etc just use another inputmethod.
-
@fireborn I'm happy to help! I've never used prediction before because I find GBoard really cluttered and slow to use, specially if you compare it with braille keyboard. TapType's design feels more intuitive and fast.
@fireborn Sometimes I need to disable talkback because single-finger gestures stop working, but I'm totally sure this is Talkback's fault. Same happens with Advanced Braille and other keyboards that require direct touch. Last year I've discovered Jieshuo Extension, I don't know why they called it like that if its an individual app, that makes GBoard extremely responsive with talkback, but it only works well for a few minutes.
If you manage to finish your screen reader and the payd features are unlocked through Google Play, I'll subscrive or buy it for sure. -
@fireborn Sometimes I need to disable talkback because single-finger gestures stop working, but I'm totally sure this is Talkback's fault. Same happens with Advanced Braille and other keyboards that require direct touch. Last year I've discovered Jieshuo Extension, I don't know why they called it like that if its an individual app, that makes GBoard extremely responsive with talkback, but it only works well for a few minutes.
If you manage to finish your screen reader and the payd features are unlocked through Google Play, I'll subscrive or buy it for sure.@muchanchoasado This is unfortunately a talkback issue. You turned on pass through in the settings? the trick is to tap once on the keyboard when you open the text field. it should say TapType keyboard. Then your gestures should work, so long as you swipe in the keyboard area. If you have trouble with this, making the keyboard full screen in settings might help.
