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


Yes, the plan is to eventually address other output formats such as PDF as well. There are just a lot of other things to solve first, so we'd be getting ahead of ourselves if we tried to start there.

Producing PDFs consistently and with full fidelity is always going to be a challenge since PDF is a such a constrained and esoteric format. I've come to accept more recently that the most direct and capable path to get there is to go through the browser engine (web to PDF). The reason is that the web provides a tremendously strongly layout engine which can then be readily distilled into the fixed, page-oriented medium of a PDF. We're currently experimenting with this approach in the Asciidoctor project.

Having said that, the main focus of the specification project, at least initially, is only the AsciiDoc language, not the output formats. The whole idea behind AsciiDoc is to give you the power and control to produce the publishable format you want to create. So while there will be some stipulations about what must be produced, we will never go so far as to dictate the style. That variation you talk about is one of the strengths, not weaknesses.

Best Regards,


On Tue, Jun 16, 2020 at 10:56 AM Graeme Smecher <gsmecher@xxxxxxxxxxxxxxxxxxx> wrote:
Hi all,

> 6. Conversion to PDF

I suspect this is deliberately last on the agenda because it's not time
yet. I'm taking the bait anyway...

Given the state of the AsciiDoc-to-PDF workflow (XML-FO, dblatex, CSS3
paged media, asciidoctor-pdf): is there a plan to address PDF generation
at a WG level, rather than on an implementation-by-implementation basis?

As an enthusiastic AsciiDoc user, I find the PDF flow to be the most
fragmented, least consistent, and most frustrating part of the ecosystem
right now. If each language stack follows a different technical path
towards PDF generation I think it will be a missed opportunity.

I have a conflicting meeting today but will be following the mailing
list eagerly.


On 2020-06-16 8:00 a.m., Alexander Schwartz wrote:
> Reminder:
> For those you want to join me on a Jitsi video conference call today: it
> starts in 2 hours from now.
> When: June 16th, 17:00 UTC - Convert to your time zone:
> Where:
> Best regards,
> Alexander
> On 10.06.2020 17:08, Alexander Schwartz wrote:
>> Hi AsciiDoc enthusiasts,
>> the AsciiDoc WG is an exciting effort to standardize the language and
>> to allow the ecosystem to grow on the basis of a common specification.
>> After talking to Dan Allen I volunteered to write a project proposal
>> for an AsciiDoc implementation for the Java/JVM ecosystem. As a
>> maintainer of the AsciiDoc plugin for IntelliJ I have experience in
>> parsing AsciiDoc and using AsciidoctorJ, but I also know he areas
>> where parsing and good tool support is difficult today.
>> What use cases do you see for an AsciiDoc JVM implementation? What
>> contributions do you want to make or see necessary?
>> Please collaborate with me on this draft:
>> To edit the document request access or discuss it on this mailing list.
>> Don't forget to add you and your company to the "Interested Parties"
>> section!
>> For those who want to have a synchronous communication, please join me
>> on a Jitsi video conference call next week:
>> When: June 16th, 17:00 UTC - Convert to your time zone:
>> Where:
>> Please get in contact before the call with all the questions you might
>> have.
>> Best regards,
>> Alexander
> --
> Alexander Schwartz (alexander.schwartz@xxxxxxx)
> _______________________________________________
> asciidoc-wg mailing list
> asciidoc-wg@xxxxxxxxxxx
> To unsubscribe from this list, visit
asciidoc-wg mailing list
To unsubscribe from this list, visit

Dan Allen, Vice President | OpenDevise Inc.
Pronouns: he, him, his
Content ∙ Strategy ∙ Community

Back to the top