From: Gregory Leblanc <gleblanc@cu-portland.edu>
To: Alan "W. Irwin" <irwin@beluga.phys.uvic.ca>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Where, what and how - The future of DocBook
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <9a19b6001cedac1a9e964e4343c44b43@NO-ID-FOUND.mhonarc.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0012052201100.2919-100000@localhost>
> That said, you have been a good advocate for emacs/psgml (and so was my
> partner in the project) so I will probably try it next time, but I don't
> regret for a moment doing my first DocBook project this simple and
> straightforward way. I seem to learn the best if I solve problems with
> low-end tools to start, and then move on up to more sophisticated tools
> later on. YMMV, of course.
I dove into psgml when I first started writing, and it was a really nice
learning tool, especially combined with the templates that the GNOME Doc
Project has. I've since become one of the most knowledgeable docbook
people actively involved in that project.
> This has been an interesting discussion about methods and perhaps even
> valuable as well, but I sure wish I could get as quick a response on this
> list to the practical problem of Cygnus pdfjadetex not working in the
> latest release.
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
WARNING: multiple messages have this Message-ID
From: Gregory Leblanc <gleblanc@cu-portland.edu>
To: Alan "W. Irwin" <irwin@beluga.phys.uvic.ca>
Cc: docbook-tools-discuss@sources.redhat.com
Subject: Re: Where, what and how - The future of DocBook
Date: Wed, 06 Dec 2000 09:39:00 -0000 [thread overview]
Message-ID: <9a19b6001cedac1a9e964e4343c44b43@NO-ID-FOUND.mhonarc.org> (raw)
Message-ID: <20001206093900.1EFkjA83MVEt80I2_Sbb6ZKqxbGTe0X-pfnwEHg85RA@z> (raw)
In-Reply-To: <Pine.LNX.4.21.0012052201100.2919-100000@localhost>
> That said, you have been a good advocate for emacs/psgml (and so was my
> partner in the project) so I will probably try it next time, but I don't
> regret for a moment doing my first DocBook project this simple and
> straightforward way. I seem to learn the best if I solve problems with
> low-end tools to start, and then move on up to more sophisticated tools
> later on. YMMV, of course.
I dove into psgml when I first started writing, and it was a really nice
learning tool, especially combined with the templates that the GNOME Doc
Project has. I've since become one of the most knowledgeable docbook
people actively involved in that project.
> This has been an interesting discussion about methods and perhaps even
> valuable as well, but I sure wish I could get as quick a response on this
> list to the practical problem of Cygnus pdfjadetex not working in the
> latest release.
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
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` 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 ` 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 ` 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 [this message]
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
[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
[not found] <200012061723.KAA06519@gw.estinc.com>
2000-12-27 6:36 ` Craig Boone
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
2000-12-27 6:36 Pfaffner, Peter
2000-12-05 7:18 ` Pfaffner, Peter
2000-12-27 6:36 Peter Ring
2000-12-05 7:45 ` Peter Ring
2000-12-27 6:36 Peter Ring
2000-12-07 3:45 ` Peter Ring
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=9a19b6001cedac1a9e964e4343c44b43@NO-ID-FOUND.mhonarc.org \
--to=gleblanc@cu-portland.edu \
--cc=docbook-tools-discuss@sources.redhat.com \
--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).