Problem description: New entries not saved. Steps to reproduce: 1. enter text into document highlight 2. open auto correct options enter text to be replaced 3. click new then ok 4. repeat once or twice Current behavior: will place either a blank or the text that should be replaced into the replace with column. Expected behavior: text to replace with should not change automatically only if manually changed and saved. Operating System: Mac OS X Version: 4.2.3.3 release
hi robert. I can save autocorrect entries with LibO 4.2.3.3 under Win7x64 bit sorry but your description is not fully clear to me... let see it together step-by-step > Steps to reproduce: > 1. enter text into document highlight do you mean "select" a spelling error with left mouse double-click? > 2. open auto correct options enter text to be replaced ok, that is "Tools/Autocorrect options" > 3. click new then ok > 4. repeat once or twice > > Current behavior: will place either a blank or the text that should be > replaced into the replace with column. are you maybe complaining about the fact that the "selected" text is automatically entered in the "with" column rather than the "replace" column? if it is that, I can confirm it and I think that the selected text should instead go under the "replace" column. actually you have to cut and paste that text from "with" column to "replace" column and manually type the needed autocorrect text in the "replace column". > Expected behavior: text to replace with should not change automatically only > if manually changed and saved. this sentence is not clear to me. try to explain again. > > Operating System: Mac OS X > Version: 4.2.3.3 release I set status to NEEDINFO please answer my questions then revert status to UNCONFIRMED
I created Bug 78217 - Autocorrect replacement table: selected text is copied in "With" field rather than "Replace" field if the problem is the same mark this report's status as RESOLVED DUPLICATE of 78217 which has clearer description, test file and screenshot if you think you are describing a different problem please give additional informations as requested.
Dear Bug Submitter, 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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO 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! Warm Regards, QA Team Message generated on: 10/01/2015
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 FDO Message generated on: 2015-02-11