[Libreoffice-ux-advise] [Bug 91192] AutoCorrect: Writer not recognizing a URL's trailing carat, hash mark, question mark, backslash, or pipe

[bugzilla-daemon at bugs.documentfoundation.org]

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

sdc.blanco at youmail.dk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |needsUXEval
                 CC|                            |libreoffice-ux-advise at lists
                   |                            |.freedesktop.org,
                   |                            |sdc.blanco at youmail.dk
             Blocks|                            |103341
            Summary|Writer not recognizing a    |AutoCorrect: Writer not
                   |URL's trailing carat, hash  |recognizing a URL's
                   |mark, question mark,        |trailing carat, hash mark,
                   |backslash, or pipe          |question mark, backslash,
                   |                            |or pipe

--- Comment #12 from sdc.blanco at youmail.dk ---
With AutoCorrect "URL Recognition" [T] and Tools > AutoCorrect > While Typing
enabled.

Can reproduce all examples shown in attachment 156589 using 7.2.0.0.alpha0+

Additional Information:

1. If additional text follows # or ?, then there is URL recognition

http://example.com/directory#testing  
http://example.com/directory?testing  

Both these examples are recognized as URLs.

2. For ^ | \

URL conversion stops with these characters, even if additional text is appended
to them. 

e.g.,  http://example.com/directory^testing  (URL stops at 'y' in directory)


Asking for UXEval:  Two questions.

1.  Is it a considered a "bug" a potential URL that ends with #  (or ?) does
not include the # (or ?) in the URL recognition?

(but, as noted, no problem if text follows # or ? )

2.  Is it a problem that the three characters:  ^ | \ are not recognized as
part of a URL (and URL recognition stops with these characters)?

Relevant to note that these three characters are considered "unsafe" and should
have percent-encoding ( https://www.ietf.org/rfc/rfc1738.txt )

Could consider an enhancement request to character encode  ^ | \ as part of URL
Recognition.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103341
[Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
-- 
You are receiving this mail because:
You are on the CC list for the bug.