Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [asciidoc-wg] AsciiDoc implementation for the Java/JVM ecosystem / project proposal

On Thu, Jun 11, 2020 at 3:56 PM Alexander Schwartz <alexander.schwartz@xxxxxxx> wrote:
Given a source document and mulitple implementations, I assume they will
create differently styled PDFs and differently styled HTMLs.

This is actually one thing I'm hoping we will be able to address as part of the WG actually.
I realize this probably isn't the point in time to discuss it, but the default HTML output could use some 
refinement as it relates to current understandings of semantic and accessibility best practices.
I think it would be an enormous value to take this opportunity to standardize that across the implementations,
and I know that will be a larger discussion as it relates to backwards-compatibility and language parsing among
other things.

As a user of AsciiDoc this allows you to pick the implementation that
best matches your output format or plugin needs. When your requirements
change, you can change the implementation, but can continue to use your
AsciiDoc sources.  If you written your own (implementation specific)
plugins, you might need to rewrite them when you change implementations.

I hope this answers your question. I didn't follow the discussion
regarding RustDoc; if you want to go into details, please provide a link
or some context.

Best regards,

Alexander Schwartz (alexander.schwartz@xxxxxxx)

asciidoc-wg mailing list
To unsubscribe from this list, visit


Luke Dary

He | Him | His

Principal Web Development Engineer

Red Hat

Back to the top