public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Fleck <jfleck@inkstain.net>
To: Aaron Weber <aaron@ximian.com>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: "xmlto pdf" stylesheet issues
Date: Wed, 29 Jan 2003 03:46:00 -0000	[thread overview]
Message-ID: <1043811985.1130.5.camel@jelloiii> (raw)
In-Reply-To: <1043773438.16441.62.camel@gimlet.boston.ximian.com>

Aaron -

My solution's off-topic for this list, but I have had good success using
xsltproc to generate fo files, then fop to generate the pdf's.

Robert Stayton has written an excellent guide to the tool chain and its
installation and use:

http://www.sagehill.net/xml/docbookxsl/index.html

Cheers,
John

On Tue, 2003-01-28 at 10:03, Aaron Weber wrote:
> Heigh ho.
> 
> I've got a couple of quick questions.
> 
> First, background: I have a multi-file, valid, well-formed Docbook 4.1
> XML document.  (xmllint --noount --noent --valid tells me it's OK, at
> least). I have converted it into reasonable HTML using the default
> stylesheets, with a little customization done by stylesheet-knowers
> here at Ximian. All well and good.
> 
> My Task: I'm now being asked for a PDF. I have managed to build a
> sort-of-ugly PDF (some pages have all the text in a tiny column down
> one side, for example, there are no stylesheet images, and I'll
> definitely need to customize the variablelists because they give equal
> space to the term and its explanation, which is not what I want
> exactly in terms of output, etc. etc.).
> 
> My Problem:  I can't figure out what it was that I installed that made
> it work, so our stylesheet-knowing-person can't actually reproduce
> even that much.
> 
> I have xmlto 0.0.8-3 and the latest versions of tetex, tetex-dvips,
> passivetex, xmltex, and so forth.
> 
> My questions: 
> What packages are required for converting a Docbook XML file to a PDF
> file, since it works for me and not for anyone else?
> 
> Am I using the recommended procedure, or is there a tool other than
> xmlto that I should be using?
> 
> Why would a PDF appear so broken when the HTML didn't?  Just the page
> size? I can see how running out of space would make a <screen> entry
> look pretty broken.
> 
> a.
-- 
John Fleck
jfleck@inkstain.net (h) jfleck@abqjournal.com (w)
http://www.inkstain.net http://www.abqjournal.com

"Sometimes, a diner is all about the mac and cheese." 
  - Zippy the Pinhead

  reply	other threads:[~2003-01-29  3:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-28 17:07 Aaron Weber
2003-01-29  3:46 ` John Fleck [this message]
2003-01-29  9:16   ` Tim Waugh

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=1043811985.1130.5.camel@jelloiii \
    --to=jfleck@inkstain.net \
    --cc=aaron@ximian.com \
    --cc=docbook-tools-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).