https://bugs.documentfoundation.org/show_bug.cgi?id=148958

David Melik <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #14 from David Melik <[email protected]> ---
It's clear this never was entirely link bug, mainly underline but as result.
        If I remembered anything else relevant how I created, I'd have said. 
Though, it is possible/probable I created it in 1993 MS Word, resaved in Open
Office (sxw,) resaved in LibreOffice.  It started as my resume (anonymized now)
and I was advised to take to university counsellor to evaluate/improve,
exported to .doc.  She added horizontal line in MS Word (don't know how) which
you maybe noticed is undeletable... if I could replicate that anew I'd destroy
& rewrite the resume (such lines being separate bug, which documentation seems
missing after maybe LibreOffice 3.5.)  I resaved .odt, deleted text after email
hyperlink (when used to be proper autocreated URI,) at end typed comma but
underlines kept appearing... I tested WWW links, same happened.
        I deleted everything after line and before email.  I tried to
replace/edit email to [email protected], don't recall which buttons I pressed...
that's about all I know.
        Of course, on later Windows, it was backdoor-accessible so became
cursed and must be destroyed immediately--sorry!
        I tried creating a new file, typed emails & URLs which auto-hyperlink
fine now, so don't really care about this particular bug unless can't delete
that line, so probably time to close this bug, get to next ones.
        I just hope older Word documents people still read (not mine but
original 'netbooks' made for free usage) and use, and might want to fork, won't
get problems like this, but that (MS Office conversion) is a separate
category...

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to