From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Miklos Vajna <vmiklos@frugalware.org>
Subject: Re: What's cooking in git.git (Dec 2008, #02; Sun, 14)
Date: Sun, 14 Dec 2008 03:17:05 -0800 (PST) [thread overview]
Message-ID: <m3ljujdn2k.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.0812141142300.2014@eeepc-johanness>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Sun, 14 Dec 2008, Junio C Hamano wrote:
>
> > * mv/um-pdf (Wed Dec 10 23:44:50 2008 +0100) 1 commit
> > - Add support for a pdf version of the user manual
> >
> > I do not have a new enough combination of dblatex and asciidoc myself
> > but this would help interested people.
>
> I haven't had a look at the patches, but isn't "pdflatex" supposed to be
> the common way to get .pdf files from LaTeX sources?
The problem is that AsciiDoc, from what I understand, by itself
generates only XML-ish formats, namely HTML, XHTML and DocBook, and
the rest of formats are generated in postprocessing step by extra
tools from DocBook format:
* manpages require xmlto
* info requires docbook2X and makeinfo
* PDF requires dblatex (db = DocBook), or FOP and xmlto
So the answer is that AsciiDoc does not generate LaTeX, so pdflatex
would be not enough.
By the way, from the AsciiDoc page:
NOTE: Owning to to other commitments, Benjamin is unable to maintain
this backend. I don't have the expertise or time to take this
on consequently the LaTeX backend has not been tested or
updated since AsciiDoc version 8.2.7 and is currently
unsupported.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-12-14 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 8:24 What's cooking in git.git (Dec 2008, #02; Sun, 14) Junio C Hamano
2008-12-14 10:44 ` Johannes Schindelin
2008-12-14 11:15 ` Jeff King
2008-12-14 11:24 ` Johannes Schindelin
2008-12-14 11:17 ` Jakub Narebski [this message]
2008-12-14 13:15 ` Miklos Vajna
2008-12-14 11:08 ` Jakub Narebski
2008-12-15 6:16 ` Junio C Hamano
2008-12-15 19:59 ` Daniel Barkalow
2008-12-16 1:35 ` Nguyen Thai Ngoc Duy
2008-12-16 1:42 ` Junio C Hamano
2008-12-16 3:36 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3ljujdn2k.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=vmiklos@frugalware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).