[
http://jira.codehaus.org/browse/DOXIA-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226532#action_226532
]
Lukas Theussl commented on DOXIA-397:
-------------------------------------
A link like
{noformat}
{{{../apidocs/groovyx/.....}}}
{noformat}
is not a Doxia id because it contains slashes.
bq. just complain (emit a warning message) but don't munge it.
It is assumed that site builders have control over both target ids and links
for internal and local links, ie if Doxia fixes an invalid id, the developer
should be forced to fix the link and avoid the warning. Unfortunately this is
not possible for auto-generated docs that produce invalid anchors/links, like
javadoc.
bq. But maybe some people are relying on behavior to turn {{{Some Section
Heading}blah}} into <a href='#Some_Section_Heading'>blah</a>
Yes, that's the origin of the problem, we would break a lot of existing links
if we changed that now.
> Cannot link to javadoc methods
> ------------------------------
>
> Key: DOXIA-397
> URL: http://jira.codehaus.org/browse/DOXIA-397
> Project: Maven Doxia
> Issue Type: Bug
> Components: Core, Module - Apt, Module - Xdoc
> Affects Versions: 1.1.3
> Reporter: Lukas Theussl
>
> Using a link to a javadoc method like
> {noformat}
> {{{../apidocs/groovyx/net/http/ParserRegistry.html#parseText(org.apache.http.HttpResponse)}ParserRegistry}}
> {noformat}
> the apt parser removes the brackets of the anchor. The same thing happens
> with xdocs and probably other formats. Note that non-ascii characters are not
> legal in anchor names, but they should be replaced by their hex values, see
> http://www.w3.org/TR/html401/appendix/notes.html#non-ascii-chars.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
