Matt Sicker commented on LOG4J2-1802:

I think it still does. That would probably require manual formatting of the 

Also, one thing I've noticed about using AsciiDoc with our existing site 
template is that we're missing some styling features. Things still render 
cleanly, it's just that some CSS may be needed to complete the migration.

> Convert documentation into AsciiDoc
> -----------------------------------
>                 Key: LOG4J2-1802
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1802
>             Project: Log4j 2
>          Issue Type: Documentation
>          Components: Documentation
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
>            Priority: Major
> The xdoc system currently in place is difficult to use correctly (it expects 
> proper XHTML, no block level elements inside inline level elements, the usual 
> pedantry from an XHTML/XML validator) and is needlessly verbose for writing 
> documentation.
> After experimenting with Markdown as an alternative to xdoc, it has not been 
> powerful enough for our uses. AsciiDoc, however, does offer more features 
> useful here without extending the markdown processor itself. This will also 
> help unify documentation formats used in other Log4j projects.

This message was sent by Atlassian JIRA

Reply via email to