User case: 1- Install dictionaries for Spanish and Italian. 2- Set the language for two different paragraphs: one in Italian, the other in Spanish. 3- In the Italian paragraph, type the word "raccomandare" 4- In the Spanish paragraph start typing the word "racimo" Result: When you type "rac" in the Spanish paragraph, autocorrect suggest "raccomandare" which is wrong because you are typing in the Spanish paragraph, not in the Italian paragraph. This is a problem for translators when the languages are akin. The problem is also present if you have two documents opened at the same time, one in each language.
Reproduced here on 3.3 build.
Autocomplete is not language dependent, you can write anything like "dsfghkldélgsfdjkk", it will be autocompleted.
It's a feature request not a bug.
(In reply to comment #2) > Autocomplete is not language dependent, you can write anything like > "dsfghkldélgsfdjkk", it will be autocompleted. That's not true: if the word is not recognized by spellchecker it will not be included on the autocompletion list. That makes it a bug because autocompletion suggest a word on another language which clearly is not on the dictionary used on the paragraph.
I think it is important to distinguish between "input" and "output". The "input" into the word list (word completion) is language dependent if AutoSpellcheck is enabled. The "output" of the word list into the document has never been language dependent (as far as I remember). So I would propose to modify the bug report as a request for enhancement.
(In reply to comment #5) > I think it is important to distinguish between "input" and "output". > The "input" into the word list (word completion) is language dependent if > AutoSpellcheck is enabled. > The "output" of the word list into the document has never been language > dependent (as far as I remember). > So I would propose to modify the bug report as a request for enhancement. I know that the "output" was never language dependant. The problem here (and the main reason because I filled it as "bug") is that the behaviour is completely unexpected, leading to problems and waste of user time. I.e., on its actual implementation autocorrect gives wrong results when editing multilingual documents. This report is not about adding a new feature, but about fixing an existing feature that gives wrong results.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
REOPENED as request for enhancement. It seems, that a steamroller has occupied Bugzilla... ;)
manj_k : It was necessary ( The problem: NOT 4 times....)
(In reply to comment #13) > manj_k : It was necessary ( The problem: NOT 4 times....) No. It was a stupid course of action, without any social intelligence.
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.