AutoCorrect is very hard to use.
1. The word AutoCorrect is misleading in itself. There are two different things: AutoCorrect and AutoFormat. For some reason both of them are called AutoCorrect.
2. AutoCorrect have no sane logic within it. See the attached comparison table.
3. There is no way to disable all AutoCorrect options at once. The user is required to check/uncheck a lot of checkboxes across different UI sections and pray that he/she haven't overlooked or forgot some of them.
Yes, you can disable "While Typing" in Writer and you will be safe (more or less). But Calc doesn't have such option, and therefore you will be required check/uncheck manually as I told above.
Yes, office suite have some advanced features for power users, but it shouldn't srcew up the basic workflow.
4. I have not checked Calc a lot because I use it very rarely. It could be additional pitfalls with it.
Steps to Reproduce:
User Profile Reset: No
Created attachment 156663 [details]
comparison table (odt)
Created attachment 156664 [details]
comparison table (png)
please split your report to several
Advice to split is not correct, until we understand what's suggested here.
Please first change component, is it Writer. And see bug 95908.
(In reply to Timur from comment #4)
> Please first change component, is it Writer. And see bug 95908.
As far as I understand, one request is about the option to disable Autocorrect in Calc (like in writer) => component is not writer
This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.
For more information about our NEEDINFO policy please read the
wiki located here:
If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
Thank you for helping us make LibreOffice even better for everyone!
Please read this message in its entirety before proceeding.
Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):
a) Provide details of your system including your operating
system and the latest version of LibreOffice that you have
confirmed the bug to be present
b) Provide easy to reproduce steps – the simpler the better
c) Provide any test case(s) which will help us confirm the problem
d) Provide screenshots of the problem if you think it might help
e) Read all comments and provide any requested information
Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:
a) respond via email
b) update the version field in the bug or any of the other details
on the top section of our bug tracker