Semicolon and other less common punctuation
RespondidaI saw someone else half address this, but whenever I try to add a semicolon after using flow input I get a space been the last word and the punctuation. If I want to use a semicolon or make my own made-up-phrase, I either have to backspace the last letter of what I've swiped (flowed) so it knows to look at what comes next as individual characters, or use the arrow keys to back up after hitting that semicolon and backspace spaces. Same applies to hyphenated words or series of words, but there's no reason to have the semicolon/colon/hyphen or dash not but the end of the preceding word. Particularly with the semicolon. I tend to like my punctuation as a way to fragment what would be a run on sentence and other areas where it would be appropriate but SwiftKey wants there to be space on either side of the ";" character or when using hyphenations. It should always hug the word to the left like a comma would; this range is same idea applies to full-on commas as well: it wants to have a space on either side instead of jumping back to the end of the last word like typing a period would. Why not give some (slightly) more obscure punctuation and symbols the period and comma treatment where after flowing a word it auto-spaces, but if a period, comma, or second space is input next that keyboard will smartly insert the formatting and punctuation before the auto-space between words.
Another hiccup I have that's always a fight is, for example, I want to list a file extension, SwiftKey will fight me to the pain several times in a row to not have it try to reformat that section to a URL.
It's to the point that I will flow a word, [backspace], [backspace], retype last letter of word and then long-pressing the "n" key for my semicolon to be in the proper place.
Side note:if the keyboard has to autocorrect the second half of a hyphenated word or expression it will add a space between the hyphen and the word it fixed looking like "blahblib- blahblah", assuming it had to fix my 'blahblah' for me, when the goal was "blahblib-blahblah".
SwiftKey is still hands down the most robust, well-rounded keyboard and I want you guys to continue to dig in your heels, keep pushing the envelope, and retain that innovation and magic autocorrect advantage without it getting too bogged down and keep it first time user friendly!
Keep up the stellar work guys!
-Ty
Also if you wanted to add gravy it'd be nice to have a way to flow on a larger screen (5.5" on my Pixel XL) when I'm manipulating the phone entirely with one hand without totally scrunching up the keyboard with the one-handed layout.
I second the motion regarding semicolons. I don't know if SwiftKey 's practice is a holdover from another language or what, but in English the semicolon (and colon) follow immediately after the previous word, with a single space afterward. Please fix!
Yes this really should be fixed. I know of absolutely no case (in English at least) where a colon or semicolon is preceded by a space. This should be a pretty easy fix right?
Yes, what a pain in the ASS!! My only complaint! I don't mind a space after a hyphen so much... But, the colon, semi-colon, and backslash (/)... WTF!?
Apparently this is not a bug ;it's a feature to make it easier to type :) and ;)
No really, I am not making this up :see https://support.swiftkey.com/hc/en-us/community/posts/115001788945-Space-before-semicolon
How can they possibly think that is a more common use case than the two I've used in this actual comment without even trying to make a point?
I agree. A real annoyance in something I paid for before it was free. There should at least be an option not to use a space. Why has this ignored after so many requests going back years?
This behaviour with space before (semi)colons drives me up the wall!
What's the progress on this? Fixing it is a matter of a button in the app settings. This is totally frustrating. In Greek, the semicolon is used as the "?". So every time I try to ask something I have to delete a space.
Same... And they Need to Move the + That's Next to the ? to where It's Supposed to be
I can't freakin' believe that they haven't fixed this in five years! It would be so easy: just make it behave like a comma. Seriously, it's for the benefit of people who want to use the ASCII convention to enter emojis rather than using the perfectly lovely emoji keyboard? That's appallingly stupid.
Hi, sorry to hear you’re experiencing issues with SwiftKey. We will certainly pass your feedback to our teams for future improvement. Thank you for your support!