On Thu, Aug 28, 2014 at 2:18 AM, Stéphane Gourichon <
[email protected]> wrote:

> Both Docbook toolchains solve these issues. You have source documentation
> and get a reproducible final document ready to ship, no manual operations,
> no mistake possible.


I agree that nothing beats a proper toolchain. I consider print to PDF in
the browser for one-off, informal needs.

Having said that, I will say that most of those problems are already solved
or solvable. For instance, the manual workflow is solved by using a
headless browser from a script (that's what wkhtmltopdf and Phantom JS
provide). Headless browsers like Phantom JS also offer vector output, so
you don't have to rasterize graphics. I'm not claiming it's easy to setup.
Once you start tweaking those tools, you have to consider the trade-offs
because its an engineering effort.

What Asciidoctor aims to provide is support for pipelines both old (read
as: mature) and new (read as: bleeding edge and experimental). Asciidoctor
doesn't yet provide LaTeX output, but we do have a converter API that let's
you convert to any format you want...so it's just a matter of someone
implementing it...and someone will.

One of my long term goals for Asciidoctor is to encourage a *new*
implementation of AsciiDoc in Python 3. AsciiDoc Python 2 has brought us a
loooooong way in the last decade. However, having spent a lot of time
reviewing the code, I can say that it's time to break new ground. If we can
agree on a standard for AsciiDoc / UniDoc, it should be very reasonable to
implement. Obviously, that's a very long-term goal, but there is a future
and we need to prepare for it.

-Dan

-- 
Dan Allen | http://google.com/profiles/dan.j.allen

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.

Reply via email to