<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - AutoCorrect: Writer not recognizing a URL's trailing carat, hash mark, question mark, backslash, or pipe" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91192#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - AutoCorrect: Writer not recognizing a URL's trailing carat, hash mark, question mark, backslash, or pipe" href="https://bugs.documentfoundation.org/show_bug.cgi?id=91192">bug 91192</a> from <a class="email" href="mailto:guilhem@fripost.org" title="Guilhem Moulin <guilhem@fripost.org>"> Guilhem Moulin</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=91192#c13">comment #13</a>) > With the pipe breaking the hyperlink it is clearly a bug to me. I tend to disagree, any compliant URL-parser would stop there as well. > Not sure if all the other characters are proper URLs, but why should LibreOffice guard the web? Would take everything until the next white space (all kind of spaces, tab, cr) into the URL. How about URLs enclosed in parentheses, square/angle brackets, or even pipes? Formatted URLs shouldn't include the markers. How about punctuation following a URL? Makes sense to greedily parse URLs following RFC3986/3987 and stick to this IMHO.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>