I have a problem with linking to documents on my NextCloud instance. Since I want to provide my players with some PDF material which I can't directly integrate in WorldAnvil, I created links to a share with the URL tag. Unfortunately the link looks like this:   https://link-to-my-cloud.org/s/garbage?path=%2Ffolderdocument%20name.pdf&openfile=12345   The parser replaces the & with &amp and the link becomes invalid. Is there any way to prevent this? I have no way to omit the openfile parameter. I understand that it might be necessary to mask any ampersand in normal text to correctly display it on the site but for links they're vital according to RFC 2396, chapter 3.4 as part of the query part of an URI.   Please exclude the url segment of the url bbcode from masking specific characters as it breaks valid urls.

Steps to Reproduce

1. Create an article 2. Insert an url-bbcode 3. Make it link to an example URL with ampersands in it (e.g. https://link-to-my-cloud.org/s/garbage?path=%2Ffolderdocument%20name.pdf&openfile=12345) 4. Save & view the article 5. Hover over the link 6. Discover that the last part (which should be separated by the & character) becomes "&ampopenfile=12345"

Operating System

Browser