|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 somerefinement 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 amongother things.
I can see the benefit if users can use the same CSS across the
HTML output of different plugins. Let's hope that we have the
necessary expertise and the time to specify also the HTML. Finding
a minimal and semantic correct HTML representation can be a
challenge (and a source for endless discussions). If we manage to
solve that in the language spec, it is one thing less the single
implmentation has to solve.
From my personal experience I can say that the Asciidoctor HTML
served me well as long as I used it with its original CSS. When I
was mixing it with other HTML I used more lightweight HTML from
the great html5s-backend (https://github.com/jirutka/asciidoctor-html5s).
So there is a real-life need to have (next to a standard HTML
outout) also plugable alternative HTML outputs.
-- Alexander Schwartz (alexander.schwartz@xxxxxxx) https://www.ahus1.de
Back to the top