On 22 August 2016 at 22:40, Kukulkan <[email protected]> wrote: > Thank you Lex, > > no I didn't try the Latex output yet. LaTex has not been on my radar at all. > Maybe I should have a look there. Will first check the AsciiDoc latex > backend, as the AsciiDoc syntax is definitely nice :-) Thanks!
Remember also to try using dblatex to convert asciidoc docbook, its supported by a2x, and even is the default for PDF IIRC. > > Kind Regards, > > Kukulkan > > > Am Montag, 22. August 2016 14:25:57 UTC+2 schrieb Lex Trotman: >> >> On 22 August 2016 at 21:44, Kukulkan <[email protected]> wrote: >> > Hi Lex, >> > >> > I fully understand that AsciiDoc is not a mature software with years of >> > development. I do not complain about free or open software. The point >> > is, >> > that I tried AsciiDoc because of no success with DocBook and Apache FOP. >> > They all have the same problem to produce good looking and well formated >> > PDF >> > documents. Apache FOP lacks full support of Keep-With-* and >> > Keep-Together-* >> > and therefore also having the same issues. The commercial XSL renderers >> > are >> > way too expensive. And now, maybe AsciiDoc is also the wrong solution >> > for me >> > :-( I really liked the AsciiDoc syntax... >> > >> > Any idea, what product may be better in rendering documents to PDF? I >> > also >> > tried the HTML5 to PDF renderers wkhtmltopdf and WeasyPrint, but they >> > also >> > have the same issues with keeping together paragraphs, images and >> > sections/chapters in an intelligent way. >> > >> > Any other suggestion for me? >> >> Well, the gold standard has to be latex, its encoded decades of >> experience and is supposed to follow the printing industry best >> practices for hanging content. But we all use Asciidoc because we >> don't like latex markup :) >> >> You said you tried the FOP backend, did you try using the dblatex >> backend, it converts docbook to latex and therefore (theoretically) >> can make use of that expertise. >> >> Also there is/was a direct latex backend in Asciidoc Python, but I >> don't know what its status is. >> >> Cheers >> Lex >> >> > >> > Thanks, >> > >> > Kukulkan >> > >> > >> > Am Montag, 22. August 2016 09:02:08 UTC+2 schrieb Lex Trotman: >> >> >> >> Asciidoctor PDF is still relatively new, it hasn't had the time to >> >> accumulate all possible use-cases and formatting rules. You could try >> >> generating docbook and using dblatex where the latex engine has been >> >> encoding such rules of decades. Or you could try FOP which doesn't >> >> have the same pedigree, but is still had much more time to mature than >> >> Asciidoctor PDF. >> >> >> >> Cheers >> >> Lex >> >> >> >> On 22 August 2016 at 16:38, Kukulkan <[email protected]> wrote: >> >> > Thanks Allen, will try this. But I really wonder why such important >> >> > functionality is still so less supported. I believe a lot of people >> >> > need >> >> > to >> >> > create PDF docs from their AsciiDoc documents and all of them will >> >> > have >> >> > the >> >> > same need, right? >> >> > >> >> > In my case, several manuals are concatenated from several individual >> >> > chapters. This way, I do not have to duplicate information/chapters >> >> > for >> >> > multiple PDF documents. The PDF build is automatically, but the PDF >> >> > need >> >> > to >> >> > look like professional manuals. And this is where such options come >> >> > in. >> >> > The >> >> > doc needs to be formatted like a human did some optimizing by taking >> >> > care >> >> > about page breaks and if images belong to a paragraph or not. >> >> > >> >> > Best, >> >> > >> >> > Kukulkan >> >> > >> >> > >> >> > Am Mittwoch, 17. August 2016 21:58:13 UTC+2 schrieb Dan Allen: >> >> >> >> >> >> This is typically done by using the unbreakable option on the block. >> >> >> However, the open block does not support this option. If it did, you >> >> >> could >> >> >> use: >> >> >> >> >> >> == second header >> >> >> [options=unbreakable] >> >> >> -- >> >> >> second chapter text >> >> >> >> >> >> some more second chapter text >> >> >> -- >> >> >> >> >> >> If a section has no content on the current page, the section title >> >> >> will >> >> >> follow the content to the next page. However, as I said, this is not >> >> >> implemented for open blocks. >> >> >> >> >> >> It does not appear that the a2x configuration supports the <?dbfo >> >> >> keep-together="always"?> for sections. >> >> >> >> >> >> The raw material is there, but your exact use case is not yet >> >> >> covered >> >> >> by >> >> >> the toolchain. >> >> >> >> >> >> -Dan >> >> >> >> >> >> On Wed, Aug 17, 2016 at 9:00 AM, Kukulkan <[email protected]> >> >> >> wrote: >> >> >>> >> >> >>> Hi, >> >> >>> >> >> >>> I'm a complete newbie to automatic docs and AsciiDoc in general. >> >> >>> Only >> >> >>> some experience with DocBook and Apache FOP. I like to create PDF >> >> >>> manual for >> >> >>> a product but I'm not happy with the page breaks. >> >> >>> >> >> >>> I do not like to do manual page breaks as it is not correct after >> >> >>> changing previous chapters. So I need some more intelligent page >> >> >>> breaks >> >> >>> during rendering. >> >> >>> >> >> >>> For example, if I have this: >> >> >>> >> >> >>> == first header >> >> >>> some text >> >> >>> >> >> >>> some more text >> >> >>> >> >> >>> some image >> >> >>> >> >> >>> some more text >> >> >>> >> >> >>> some image >> >> >>> >> >> >>> == second header >> >> >>> second chapter text >> >> >>> >> >> >>> some more second chapter text >> >> >>> >> >> >>> >> >> >>> It should move the second header to the next page if the second >> >> >>> chapter >> >> >>> text does not fit to the current page. But what I see is the second >> >> >>> header >> >> >>> and one or two lines on the first page and the rest follows on page >> >> >>> 2. >> >> >>> What >> >> >>> do I need to do to tell asciidoc-pdf to jump to the next page in >> >> >>> this >> >> >>> case? >> >> >>> >> >> >>> In DocBook I would use this attribute for the header definition: >> >> >>> >> >> >>> <xsl:attribute >> >> >>> name="keep-together.within-page">always</xsl:attribute> >> >> >>> >> >> >>> Is there something equivalent for AsciiDoc? Or how is such problem >> >> >>> solved >> >> >>> here? >> >> >>> >> >> >>> BTW, the same with image and paragraph. I like to move a block of >> >> >>> an >> >> >>> image and the next paragraph to the next page if it does not fit to >> >> >>> the >> >> >>> current page. Is there a way to define such a "wrapping" block? >> >> >>> >> >> >>> -- >> >> >>> 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 https://groups.google.com/group/asciidoc. >> >> >>> For more options, visit https://groups.google.com/d/optout. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Dan Allen | @mojavelinux | https://twitter.com/mojavelinux >> >> > >> >> > -- >> >> > 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 https://groups.google.com/group/asciidoc. >> >> > For more options, visit https://groups.google.com/d/optout. >> > >> > -- >> > 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 https://groups.google.com/group/asciidoc. >> > For more options, visit https://groups.google.com/d/optout. > > -- > 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 https://groups.google.com/group/asciidoc. > For more options, visit https://groups.google.com/d/optout. -- 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 https://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
