From: grant.b.edwards@gmail.com (Grant Edwards)
To: linux-arm-kernel@lists.infradead.org
Subject: PDF documentation
Date: Thu, 18 Oct 2012 14:00:46 +0000 (UTC) [thread overview]
Message-ID: <k5p22e$7d1$1@ger.gmane.org> (raw)
In-Reply-To: E1TOqZc-0005Wc-Oj@jdl.com
On 2012-10-18, Jon Loeliger <jdl@jdl.com> wrote:
>>
>> I would prefer if the source for the (PDF-)documentation would be
>> available in some open, free and widely used meta-language, e.g. LaTeX
>> (or XML or txt2tags or ..., but I'm oldschool and prefer LaTeX ;) ). So
>> everyone could build it's copy in whatever format he prefers or needs.
>
> Perhaps DocBook? It is readily rendered as PDF or HTML.
Unfortunately DocBook can't be read/edited by a human. IMO, Docbook
is only suitable as a machine-generated intermediate format.
I'd recommend one of the lightweight markup languages like asciidoc or
reStructuredText. They're easy to read/write, perfectly usable in the
source form and can be rendered into PDF, HTML, ODT, DocBook, whatever.
--
Grant Edwards grant.b.edwards Yow! Don't SANFORIZE me!!
at
gmail.com
prev parent reply other threads:[~2012-10-18 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 13:22 PDF documentation Constantine Shulyupin
2012-10-16 13:57 ` [Celinux-dev] " Bill Traynor
2012-10-16 14:05 ` Peter Stuge
2012-10-17 13:24 ` Constantine Shulyupin
2012-10-17 16:51 ` Peter Stuge
2012-10-17 19:26 ` Constantine Shulyupin
2012-10-17 22:04 ` [Celinux-dev] " Tim Bird
2012-10-17 22:29 ` Constantine Shulyupin
2012-10-17 22:19 ` Russell King - ARM Linux
2012-10-17 22:25 ` Peter Stuge
2012-10-17 22:29 ` Russell King - ARM Linux
2012-10-17 22:40 ` Peter Stuge
2012-10-18 5:20 ` [Celinux-dev] " Geert Uytterhoeven
2012-10-16 14:35 ` Wolfgang Denk
2012-10-16 18:32 ` Tim Bird
2012-10-17 10:12 ` Wolfgang Denk
2012-10-17 13:36 ` shiraz hashim
2012-10-16 14:45 ` Mikael Pettersson
2012-10-18 13:27 ` Alexander Holler
2012-10-18 13:55 ` Jon Loeliger
2012-10-18 14:00 ` Grant Edwards [this message]
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='k5p22e$7d1$1@ger.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.