robtimus opened a new issue, #1029:
URL: https://github.com/apache/maven-doxia/issues/1029

   ### Affected version
   
   3.21.0
   
   ### Bug description
   
   I am using Markdown files to generate my site. When these files include 
anchors to relative URLs these get encoded. That currently prevents me from 
including links to methods in my own API docs unless I make them absolute.
   
   I have found apache/maven-site-plugin#731 and apache/maven-site-plugin#748, 
as well as https://github.com/apache/maven-doxia/issues/391, but the 
suggestions in these don't solve my issue.
   
   I have tried the following:
   * Escape both ( and ) using \. These get encoded to .28 and .29 respectively.
   * Use %28 and %29 instead of ( and ). These get encoded to .2528 and .2529 
respectively.
   * Use Markdown links as well as <a> elements. Both show the same issue.
   * Use ## instead of a single #, as suggested in the Doxia issue. That gets 
converted into #a.23, and my ( and ) still get encoded.
   * Use %23 instead of #. That %23 and the %28 and %29 now remain, but the URL 
then leads to a 404, because the "anchor" now becomes part of the URL, and the 
file no longer ends with .html but with the anchor.
   
   For reasons I am unable to switch to xhtml or Velocity. However, because I'm 
not using any templating at all, I expect  links in my Markdown files to remain 
as-is.
   
   Apart from using absolute links, what can I do to make my anchors remain 
intact?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to