We do get occasional problems on the EN forum where a stray trailing non printing character causes unexpected problems with some formulae. I don't know how much of an issue it would be to add this, but if it is comparatively simple I'd support it; as I suspect would a few others who spend time on the forum.
This would be the time to add your $0.02 if you think this would be a good thing - either via the dev list or by vote on BZ.
Slackware 15 64 bit
Apache OpenOffice 4.1.16
LibreOffice 25.8.2.2; SlackBuild for 25.8.2 by Eric Hameleers
---------------------
Tech support noun: A person who does precision guesswork based on unreliable data provided by those of questionable knowledge.
The service can't connect to the DB right now (which, incidentally, is the same error message I have encountered the last 3-4 times I tried to follow a link to an Apache list display). Hopefully a temporary problem. I didn't send a message by the link provided. Wait and see a while...
Presenting a use case is not enough to justify implementing a feature.
The criteria for implementing a feature should be how many users will use it and how many volunteers are available to code it.
I believe a space can be detected with a formula or macro.
In a big spreadsheet visual inspection of non printing characters is fallible.
-1 from me.
That would be a -1 from me too. If you use autoinput, you should expect entries to be the same, whitespace included. As much as I dislike the feature in the first place, and the fact that it is enabled by default, I think that the suggested "fix" will only make it worse.
