Option to disable auto-space after punctuation and/or prediction
Add an option to disable automatic space after completing a word in flow. Instead add space after I have either chosen a suggestion is state typing a new word This way I could choose the proper suggestion much faster or need be correct my previous typing.
Sometimes when you're entering your email or a username that has a period in it you get an automatic space which sometimes results in a wrong username.
Would really like the option do disable/enable auto-space after punctuation (.,!), particularly period. Would make entering e.g. adresses and version number strings (which I do a lot) much less of a hassle.
And related, an option to do the same for prediction: Some languages, e.g. Swedish, uses composite words (combining word stems/lexemes into one word) extensively.
This issue is something we’ve thought about on many occasions, as it would definitely simplify some of the typing use cases.
One of the primary problems is that people often build words by selecting the root or prefix and then adding a suffix. For instance, if I want the word “predicting” I might select “predict”, then add the “ing”. In this case, if you add space before a prediction, there’s no way of knowing if the user intended to start the next word or add to the selected word.
In the absence of a space after a prediction, a user whose cursor was next to the end of a word would not know if the predictions/corrections that they saw related to the word they are currently “in”, or to the next word.
There may be a way to solve this problem via probabilistic modelling, but it’s definitely non-trivial. We’ll be thinking about it.
Kyuhwa Lee commented
I have waited for almost a year and all you say is thinking about it?
Please first add an option to disable this offending feature as soon as possible while "thinking".
This is a major problem for lots of people. Please listen to your customers!
Why do you need to be so stubborn? It's just like watching the old Swype.
Michael Merlin commented
sooooo annoying typing in . com. au domain names into dolphin browser address bar (just look at what it did above, I am typing on swiftkey) it should be .com.au
An ellipsis, or even just a dot, before "spaceless" suggestions would disambiguate them for users.
Siva Pratap commented
Please fix this...This makes typing super slow.
Basically, it would solve several issues/complaints that have already been requested by multiple other users.
1. It would make it easier to fix words after they are put in. This would help a lot with us Flow users, which when you swipe the next word, the previous almost always is completed before the next word is added in most of these cases.
2. The few requests to make it so you could just swipe your username and it doesn't add the extra space afterwards would be very easily fixed by this, which would also be of massive help to us Flow users.
3. Entering web addresses would be a lot easier to both code/maintain support for and also actually do if there is no automatic space after punctuation.
4. The double-hyphen "--" used often in place of an em-dash in many cases would be easier to use correctly without the added space after words. Normally, there isn't supposed to be a space on either side of the em-dash in standard English grammar (and probably many other languages as well, but I don't know for sure).
5. The ellipsis "..." isn't supposed to have a space on either side of it if it is in the middle of a sentence, which is the case in every language that uses it. That correction would make it a lot easier to correctly code the lack of a space after it. On the other hand, there shouldn't be a space subtracted if it already exists, which would mean if there isn't a space, don't make one and if there already is one, don't take it away. That would be the implementation of this.
These five issues/requests would all be fixed (except for possibly the last one in some specific cases) by this one thing being implemented into the keyboard.
And by the way, if current word prediction was displayed instead of the ridiculous next word suggestions which i never use our even look at, no one would need to build words the way Sarah mentions. One would simply flow "predict" and be able to choose predicts, prediction, predicted, predicting, predilection, and predicate from the list of suggestions. How is this not obvious to the developers?
The real problem here is that SwiftKey doesn't have the option to change the top row from next word prediction. This feature is practically useless. Apparently swiftkey thinks it is so smart that a user would never need to change the word just entered, and so it forces you to hit backspace to do this... And then only gives you three options to choose from. Stock android keyboard has a button to expand this list and this is desperately needed in swiftkey. I spend more time deleting words and typing them in one character at a time because they don't happen to be one of the three that SwiftKey wants to force on you- even after multiple attempts to flow them - that it negates any time saved from the flow feature. Typing in compound words that require a hyphen is also a nightmare.
I love Swiftkey but sadly uninstalling due to the "space after full stop" issue. It makes the Swiftkey experience less swift!!
How is this not fixed yet? It is a huge pain having the keyboard automatically remember email addresses but with spaces in the middle of them. This is not a problem with Google Keyboard or Swype.
After reading Sarah Reynolds response, the simple answer is warn the user and let them decide. When the user selects this option, a warning will pop up that says "with auto spacing disabled, SwiftKey will not be able to predict and complete suffixs".
At the very least, please remove auto spacing after punctuation till you figure the rest out.
Michael Peacock commented
It is crucial that auto space after punctuation be made optional. Not after predictions; that's understandable; but after punctuation for sure.
anonymous paid supporter commented
please give me an otion to disable spaces after period. It is so cumbersome I cant stand it.
Ian Beck commented
Add another vote to the massive pile. I'm currently demo-ing both SwiftKey and Swype vs. the default KitKat keyboard, and the only reason that SwiftKey isn't dominating my typing is because the "feature" of inserting a space after every blessed thing is driving me quickly insane. I may well end up back with the stock keyboard after my month is up simply because it offers the two features I really care about: no automatic spaces after insertions, and the ability to swipe through the keyboard to insert multiple words in one go.
Michael Coolidge commented
I'm removing SwiftKey because of its ridiculous word corrections. I typed photis which was supposed to be photos and it put in hobos! Really.? Can't believe you can't disable that. Shame.
Jelmer Feenstra commented
@Pandu Poluan thanks for mentioning the bilingual support in the new version of Swype. Installed it immediately and was blown away by a feature it has that is missing from SwiftKey: it only inserts the characters you actually hit on the keyboard, so tt doesn't add extra spaces after periods and commas and thus you don't end up with double spaces all over the place.
I know, amazing right?! It's nothing short of revolutionary!
Sonny Patterson commented
Sarah's Oct 8 comments have a simple remedy. You already have no-space prediction, where you offer predictions of two words when the user doesn't inset a space. If adding just make the first prediction space at the predicted breaking point. At any time the user can select the broken word then continue typing.
John Smith commented
Oh come on swiftkey team. It's just adding a toggle option (a boolean for developers), is it so hard to do? Even adding it in the swiftkey client app (not the keyboard) would be fine, there's already so many users asking you to fix this so please. Thanks
Dadoo René commented
Thank you Sarah,
It seems to me that we need a setting toggle that would disable adding spaces for some input. This toggle could be added to the "Swipe" menu, like a cap lock key. It seems that other toggles will be needed...
One (you) should merge similar issues : there are at least 3 threads on this topic.
Thank you for your inputs
René the Swiss
AwesomeBill FromDawsonville commented
incorporating the option to swipe from the chosen word, may be a solution for recognition that user intends for a suffix to be used.
Tim vd Westhuizen commented
I also re-install SwiftKey every few months to see if this has been added. I really like everything about it except this issue and it's a complete deal breaker. I will continue using Kii, but if this "feature" is added I'll most definitely use SwiftKey again.