All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: more observations on the usermanual dir and docbook translation
Date: Sun, 22 Nov 2009 07:25:36 -0500 (EST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0911220719570.13278@localhost> (raw)


  since i've done a fair bit of docbook processing, i took a quick
look at the usermanual dir, and here's another observation from the
README, where it reads:

  For html and xhtml you need xsltproc installed.
  For the other you need docbook-utils installed.

at least under fedora, that's not all -- you'll need the
docbook-utils-pdf package as well:

$ rpm -ql docbook-utils-pdf
/usr/bin/db2dvi
/usr/bin/db2pdf
/usr/bin/db2ps
/usr/bin/docbook2dvi
/usr/bin/docbook2pdf
/usr/bin/docbook2ps
/usr/share/man/man1/db2pdf.1.gz
/usr/share/man/man1/docbook2dvi.1.gz
/usr/share/man/man1/docbook2pdf.1.gz
/usr/share/man/man1/docbook2ps.1.gz
$

  not sure what the situation is under other distros.  also, the last
time i looked, most output formats can now be generated with no
reference to SGML or DSSSL or jade, but i'd have to go back and verify
that.  (pdf output can be generated using fop.)

  if no one else wants to handle this, i can start putting together
patches to bring that directory up to date as long as i can do it in
bite-size pieces.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================



             reply	other threads:[~2009-11-22 12:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-22 12:25 Robert P. J. Day [this message]
2009-11-24 18:24 ` more observations on the usermanual dir and docbook translation Cliff Brake

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=alpine.LFD.2.00.0911220719570.13278@localhost \
    --to=rpjday@crashcourse.ca \
    --cc=openembedded-devel@lists.openembedded.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.