I am using Writer and I find that when I type the work "sick" followed by a "." or a"," then the space bar, the word sick and following becomes underlined and I cannot turn it off. I repeated this several times.
I am using windows 7 home premium 64-bit with 5gb Ram, Nvidia 9400GT on an HP Pavilion.
I confirm this behavior. Is wrongly detected as hyperlink.
Regression. It works fine on 3.3.2
Confirmed on Windows 7.
Type "A slot machine" and it does it as well. Adding it as an annoying bug for the 3.4 release because this is an unacceptable bug to have in a release.
*** Bug 36640 has been marked as a duplicate of this bug. ***
I see it on Linux as well. It is quite annoying.
Cedric, would you have time to look at it?
Still presente in 3.4 Beta 3.
Just type repeatedly "seal" to reproduce.
Modified Status due to facts
Modified OS due to Comment 6
"Bug 36640 - Involuntary conversion of word to hyperlink" contains lots of examples
I can add that it happened for me also with Beta 2 already on Mac OS X (x86, not -64).
Same behaviour on Win 7 / 64bit with LO3.4 beat3 when I type
followed by a space (it's a Danish word). It becomes an smb:/// link
*** Bug 36941 has been marked as a duplicate of this bug. ***
I have changed the wrong and misdirecting "Incorrect words" in the summary to "Some words".
That bug doesn't depend on AutoSpellcheck (ASP) or any language. Words with language attribute "None" or with deactivated ASP are also affected.
Still not fixed in LibO 3.4 beta 4
(In reply to comment #13)
> Still not fixed in LibO 3.4 beta 4
Of course not, here is no comment concerning a fix and / or integration!
Confirmed in 3.4.beta 5 writing in spanish at least two words
as soon as the space after the two words is entered, an hyperlink format is associated:
smb:/// for the first combination of letters
slot: for the second.
It doesn´t happen if the words are at the beginning of the line.
Just my two cents....
*** Bug 37194 has been marked as a duplicate of this bug. ***
it also links german sind
(In reply to comment #17)
> it also links german sind
Apparently, it simply doesn't matter what the language is. As I had indicated in duplicated bug 36640, several random combinations of "s" + "i" or "e" trigger the conversion of the word into a hyperlink.
Examples: "seen", "seem", "seam", "sick", "sion", "sean", "seon", "seol", "siam", "seal","sial".
Because it happens in several languages, with both existing and non-existing words it doesn't seem to be related with spellcheck or AutoCorrect.
It is the same in RC1 (WIN XP 32bit SP3 German).
It is a nogo-version for German if the word "sind" (first and third person singular of the word "to be") will be hypermarked every time.
No normal user can kandle and accept such a behaviour.
deserves blocker severity - you cannot tell uses to constantly hit <ctrl>+z/undo when the wrong hyperlink-detection happens - also LO seems to freeze (100%CPU) or crash because of this (crash/freete not 100% reproducible, but by just stupididly type the same word over and over again, if it is turned into hyperlink, open a new paragraph, repeat, at some point it will crash instead of turning to hyperlink)
Fixed in 3-4 branch. Still waiting for 2 reviews before pushing in 3-4-0 branch.
pushed to 3.4.0 after triple review,
Tested with 'nightly' LibO 3.4 v2011-05-23 [on WinXP]
Not any longer conversion into hyperlink for:
seen, seem, seam, sick, sion, sean, seon, seol, siam, seal, sial, sind, slot, skal, [...] skol.
(In reply to comment #23)
> Tested with 'nightly' LibO 3.4 v2011-05-23 [on WinXP]
> Not any longer conversion into hyperlink for:
> seen, seem, seam, sick, sion, sean, seon, seol, siam, seal, sial, sind, slot,
> skal, [...] skol.
Confirm fix on WinXp. Many thanks to the developers!
Also German Windows-Version works. Problem fixed. Expression "sind" won't be converted to hyperlinks anymore. Thanks to all involved!
*** Bug 37777 has been marked as a duplicate of this bug. ***
(In reply to comment #26)
> *** Bug 37777 has been marked as a duplicate of this bug. ***
Using 3.4.0 000340m1 (Build 11)
(In reply to comment #27)
> Using 3.4.0 000340m1 (Build 11)
I think that is RC1. Please, try RC2.
Whoops, you are correct! Sorry to waste your time.