[
https://issues.apache.org/jira/browse/LOG4J2-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17634554#comment-17634554
]
Philippe Cloutier commented on LOG4J2-3510:
-------------------------------------------
Thanks [~vy] but I unfortunately have never worked with the .md.vm format,
don't know what you mean by "PR" and have no commit access to the repository
(to my knowledge).
By deduction, I am guessing that the problem in [the _Migrating from Log4j 1.x
to 2.x_ page|https://logging.apache.org/log4j/2.x/manual/migration.html] was
fixed by [commit
4e593a41fcbc07f13965cd96b5cb13ec2573380e|https://github.com/apache/logging-log4j2/commit/4e593a41fcbc07f13965cd96b5cb13ec2573380e].
However, the only change to fix titles that I see is addition of apparently
empty lines between anchors and titles, which seems questionable. It may be
that the proper fix is more complicated than it seems.
> 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)
