I've noticed that calling the dialog "Spell check" (F7) on the first document for writer will populate this dialog with the errors from the first document. I've left the dialog open and I've opened a second document for editing and called again the dialog (F7) but this was containing the errors from the first document instead of those from the second document. If I go further and work with the dialog on the second document unexpected effects will happen. Parts of text from the second document will be replaced with suggestions related to the first document. I've used for my Test OO 3.2.1 (OOO320m18, Build 9502). I've checked this also with OO 3.3 RC3 and the problem is still present. I've reported this problem also on openoffice.org. http://openoffice.org/bugzilla/show_bug.cgi?id=115488
Created attachment 45567 [details] bug spellcheck
The dialog "Spell checking" is context independent in Microsoft Office 2003.
[Reproducible] with "LibreOffice 3.4.2 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:203)]". For the check you should have installed German (Germany) and EN (US) dictionaries Steps to reproduce: 0. Download, unzip test kit, open both documents 1. Switch to "sourceEn.odt", <f7> for spell check Spell check dialotg appears Some misspelled word, for example "Karota", will be indicated 2. Switch with <alt+tab> to "source.de", <f7> for spell check As expected spell check dialog appears, but unexpectedly it does not check the German text of this document, but continues spell check for "sourceEn.odt" (you see English text in text view pane in the dialog). I see "Jatt" as misspelled, what also will be the next indicated word in "sourceEn.odt", if you switch back to that document and click button "ignore once" Might be inherited from OOo, I also see the problem in Oo 3.3
Created attachment 50193 [details] Test kit, see Comment 3 Corresponding OOo issue: "74574 - interactive spell checking in two Writer documents" <http://openoffice.org/bugzilla/show_bug.cgi?id=74574>
Since all new unconfirmed bugs start in state UNCONFIRMED now and old unconfirmed bugs were moved to NEEDINFO with a explanatory comment, all bugs promoted above those bug states to NEW and later are automatically confirmed making the CONFIRMED whiteboard status redundant. Thus it will be removed.
for me not reproducible with LO 4.2.1.1 (Win 8.1) Can anybody still confirm this bug? Otherwise, I would propose to close this issue as Resolved.
Bugs do not fix themselves and this is still perfectly reproducible.
@Urmas: Thank you very much for your very fast reexamination of my check. Could I am doing something different, because I tried it once more and it seems to work OK (or there is maybe a misunderstanding from my side)? Please find below all the steps I had done. Please correct if you had done something different. Steps I had done: 1. Open both files from the Test kit (sourceDe.odt and sourceEn.odt) directly from the Windows Explorer 2. Swtich to sourceDe in WRITER to start 3. Press F7 -> Result: German spell checks opens and shows "Paschtu" as error (or missing word) 4. Close the German spell check by pressing the CLOSE button 5. Press Alt + Tab keys to switch to sourceEn 6. Press F7 -> Result: English (USA) spell checks opens and shows "Karota" as error (or missing word)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.4.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-05-02
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear liviucoman, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear liviucoman, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I can still see interaction between two writer documents being spellchecked at the same time in: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
*** Bug 139375 has been marked as a duplicate of this bug. ***
A workaround was suggested by sasha.libreoffice@gmail.com 2012-02-15 04:26:08 UTC in Bug 43789: https://bugs.documentfoundation.org/show_bug.cgi?id=43789 Try resetting or fully disabling spellcheck in the LO document/application of your choice as follows: To disable spellcheck per document: 1. Press F11, appears Stylist pane 2. Select there "Default" style 3. Right click it, choose Modify 4. Select tab "Font" 5. Change language to [None] Now spellcheck is disabled for document To disable spellcheck in an application for a newly created document: 1. Create new template with disabled language 2. Set it as default template File->Templates->Organize and right click on selected template, choose "Set as default template" Sasha recommends never changing existing templates, only creating new ones. Let us know if this issue persists, SPinz