[
https://issues.apache.org/jira/browse/LOG4J2-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17638786#comment-17638786
]
Philippe Cloutier commented on LOG4J2-3510:
-------------------------------------------
Thank you for the explanations Matt, that makes sense.
[https://stackoverflow.com/questions/5319754/cross-reference-named-anchor-in-markdown]
suggests there would be a cleaner way:
{code:java}
### <a name="tith"></a>This is the Heading{code}
That means fixing should be simple, but unfortunately, I don't have Velocity
and don't know how to setup an environment to verify.
> Broken titles/sections
> ----------------------
>
> Key: LOG4J2-3510
> URL: https://issues.apache.org/jira/browse/LOG4J2-3510
> Project: Log4j 2
> Issue Type: Bug
> Components: Documentation
> Reporter: Philippe Cloutier
> Assignee: Ralph Goers
> Priority: Major
> Fix For: 2.18.0
>
>
> Log4j's website contains several broken titles (section headers). This seems
> most prevalent in [the _Migrating from Log4j 1.x to 2.x_
> page|https://logging.apache.org/log4j/2.x/manual/migration.html], but can
> also be seen on the homepage. For example, the following, which is presumably
> supposed to generate a level 4 "API Compatibility" header, shows raw:
> {code:java}
> #### API Compatibility
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
