From: Craig Boone <craig@estinc.com>
To: Gregory Leblanc <gleblanc@cu-portland.edu>
Cc: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>,
docbook-tools-discuss@sources.redhat.com
Subject: Re: Where, what and how - The future of DocBook
Date: Wed, 06 Dec 2000 11:06:00 -0000 [thread overview]
Message-ID: <3A2E8FCB.51D92BD2@estinc.com> (raw)
Message-ID: <20001206110600.ybzYW33mFsYMW-G09QZf5D8i5vjLQ8BVk8_Cb1HW1yg@z> (raw)
In-Reply-To: <200012061723.KAA06519@gw.estinc.com>
Gregory Leblanc wrote:
> I've gotten around this the easy way, I don't use pdfjadetex. Instead,
> I use a tool called htmldoc, which convers from HTML to PS/PDF, and does
> a VERY nice job at it. The only thing that's missing is that it doesn't
> convert the external (href) hyperlinks to something useful along the
> way. I can do this with jade, but jade is slow.
>
> Greg
Is htmldoc something that you created, or is it something that's
available for download? I can't seem to get any of the pdf/ps
conversions to occur properly with the DocBook tools that I have. I'm
using the db2pdf and db2ps scripts and all they seem to do is explode
and spew latex errors everywhere. I can write picture-perfect sgml and
it makes lovely html conversions, but it doesn't do me much good if I
can't get it printed.
I've been monitoring this list and watching all of the "Future of
DocBook" threads and I gotta say it's a great project and I'd love to be
able to set it as a standard to create all of my documentation.
However, I just can't seem to get a dependable set of tools and solidly
implement them. Suggestions?
--
Craig A. Boone craig@estinc.com
Technical Writer Enhanced Software Technologies, Inc.
Ph: 602.470.1115 Fax: 602.470.1116
www.estinc.com
After the game, the king and pawn go into the same box. --Italian
Proverb
Loyalty to a petrified opinion never yet broke a chain or freed a human
soul.
--Mark Twain
next parent reply other threads:[~2000-12-06 11:06 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200012061723.KAA06519@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone [this message]
2000-12-06 11:06 ` Craig Boone
[not found] ` <200012061858.LAA06946@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone
2000-12-06 11:46 ` Craig Boone
2000-12-27 6:36 ` Gregory Leblanc
2000-12-06 11:12 ` Gregory Leblanc
[not found] <200012061914.UAA08546@mailserv.caiw.nl>
2000-12-27 6:36 ` Hugo.van.der.Kooij
2000-12-06 12:31 ` Hugo.van.der.Kooij
2000-12-27 6:36 Peter Toft
2000-12-03 9:23 ` Peter Toft
2000-12-27 6:36 ` Norman Walsh
2000-12-04 6:08 ` Norman Walsh
2000-12-27 6:36 ` Peter Toft
2000-12-05 14:12 ` Peter Toft
2000-12-27 6:36 ` Jorge Godoy
2000-12-05 16:58 ` Jorge Godoy
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:10 ` Eric Bischoff
2000-12-27 6:36 ` madhu
2000-12-15 9:22 ` madhu
2000-12-27 6:36 ` Michael Smith
2000-12-15 10:40 ` Michael Smith
2000-12-27 6:36 ` Michael Wiedmann
2000-12-06 5:36 ` Michael Wiedmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:53 ` Eric Bischoff
2000-12-27 6:36 ` Mark Johnson
2000-12-06 8:05 ` Mark Johnson
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 8:15 ` Eric Bischoff
2000-12-27 6:36 ` Alan W. Irwin
2000-12-05 15:53 ` Alan W. Irwin
2000-12-27 6:36 ` Michael Smith
2000-12-05 21:27 ` Michael Smith
2000-12-27 6:36 ` Alan W. Irwin
2000-12-05 22:50 ` Alan W. Irwin
2000-12-27 6:36 ` Gregory Leblanc
2000-12-06 9:39 ` Gregory Leblanc
2000-12-27 6:36 ` Michael Smith
2000-12-06 0:51 ` Michael Smith
2000-12-27 6:36 ` Eric Bischoff
2000-12-06 5:23 ` Eric Bischoff
2000-12-27 6:36 Peter Ring
2000-12-07 3:45 ` Peter Ring
2000-12-27 6:36 Peter Ring
2000-12-05 7:45 ` Peter Ring
2000-12-27 6:36 Pfaffner, Peter
2000-12-05 7:18 ` Pfaffner, Peter
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=3A2E8FCB.51D92BD2@estinc.com \
--to=craig@estinc.com \
--cc=docbook-tools-discuss@sources.redhat.com \
--cc=gleblanc@cu-portland.edu \
--cc=irwin@beluga.phys.uvic.ca \
/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).