From: JT Moree <moreejt@xperienceinc.com>
To: docbook-tools-discuss@sourceware.org
Subject: docbook 2 html with images
Date: Thu, 02 Feb 2006 14:27:00 -0000 [thread overview]
Message-ID: <43E2174E.3090103@xperienceinc.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I recently tried out docbook2html (which of course is just jw with
some default options). I and the documentation for blender (which led
me to this in the first place) used the -o option to output to a
subdirectory.
Alas none of the images were copied into the subdirectory which left me
with only part of what I needed.
I wrote a script to copy the images for me but I thought perhaps the
latest version of the utils might have already dealt with this issue.
I am on debian sarge for amd64 and the utils version is 0.6.14. jw
version 1.1.
Can anyone tell me if this issue has been addressed? Shall I clean up
my script and post it somewhere for the maintainer of docbook-utils to
possibly include?
- --
JT Morée
PC Xperience, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFD4hdOucZ4lMT2d5IRAgAYAJ9tLtC6qbeq+pNmRDmmkcSFaWTwPwCgkGkm
5/PaT7TJerEE9sxfujCKeAE=
=tgvA
-----END PGP SIGNATURE-----
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
next reply other threads:[~2006-02-02 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 14:27 JT Moree [this message]
2006-02-03 13:44 ` Éric Bischoff
2006-02-03 18:18 ` JT Moree
2006-02-03 18:29 ` JT Moree
2006-02-03 20:36 ` Éric Bischoff
2006-02-04 13:42 ` JT Moree
2006-02-04 15:05 ` Éric Bischoff
2006-02-04 22:05 ` JT Moree
2006-02-05 8:47 ` Éric Bischoff
2006-02-06 1:50 ` JT Moree
2006-02-06 6:31 ` Éric Bischoff
2006-02-03 20:39 ` Éric Bischoff
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=43E2174E.3090103@xperienceinc.com \
--to=moreejt@xperienceinc.com \
--cc=docbook-tools-discuss@sourceware.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 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).