Use German Hunspell. Enter this NONSENSE sentence (including the leading and trailing quote characters): "Wenn ich diesen Fehler testen Huhnd würde, würde ich jetzt einen Satz schreiben Huhnd." 'Huhnd' is a misspelled form of 'Huhn' which means 'chicken'. Hit F7 for spell checking and click on "Correct all". The sentence is corrected to this: "Wenn ich diesen Fehler testen Huhn würde, würde ich jetzt einen Satz schreiben Huhn" While the sentence still does not make sense, note that the trailing dot after the second 'Huhn' is removed erroneously.
[Reproducible] with reporter's sample and "LibreOffice 3.4.1 - WIN7 Home Premium (64bit) German UI [OOO340m1 (Build:103)]", even without quotation marks. Also visible with Master "LibO-dev 3.4.5 – WIN7 Home Premium (64bit) English UI [(Build ID:d337f79-a24c961-2865670-9752b71-7f8fd43 2fdd60d-fd28b6a-fd7bf20-aa369cb-28da3fb 6a9633a-931d089-ecd263f-c9b55e9-b31b807 82ff335-599f7e9-bc6a545-1926fdf)]" and English text / english spell check. @andre: I can confirm the problem with dot deleting by "Correct All", but I also see that without quotation marks. Do I observe something different or has behavior changed between 3.3.0 and 3.4.1? Can you please attach a sample document? What's your OS?
I can reproduce it without quotation marks, too. I'm Ubuntu 11.04 with LibO 3.3.2 Testdoc follows.
Created attachment 49335 [details] Test doc to reproduce bug
@Caolán: Is this your area?
I guess nothing and everything is my area. This should fix it. http://cgit.freedesktop.org/libreoffice/core/commit/?id=ecf8ed8eed580cfbfa6b32a51dbdbed6cf556659 i.e. do the same on change all as on change. I'm a bit dubious about our code which splits up sentences into words, so that could do with a rework, especially for languages like Hebrew and Maltese which can have embedded " and other marks inside words, but this at least makes it consistent between change and change all for the current word splitter.
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.
*** Bug 41251 has been marked as a duplicate of this bug. ***
Please have a look in the new (slightly modified) example file. The problem still exists in the same paragraph! But it is fixed in the following paragraph. The reason, why it works for the original example file is, that there is a paragraph break in the sentence.
Created attachment 61923 [details] a new example, where the fix is not working in the same paragraph
don't reopen old fixed bugs, file new ones. It makes it impossible to untangle things if bugs that appear to be similar get reused. There's no harm in having extra bugs that can get marked as duplicates if they turn out to be the same thing