From: JT Moree <moreejt@xperienceinc.com>
To: docbook-tools-discuss@sourceware.org
Subject: Re: docbook 2 html with images
Date: Fri, 03 Feb 2006 18:18:00 -0000 [thread overview]
Message-ID: <43E39ED8.1000004@xperienceinc.com> (raw)
In-Reply-To: <200602031445.11703.ebischoff@nerim.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>Alas none of the images were copied into the subdirectory which left me
>>with only part of what I needed.
> It's an old issue. The difficulty is to guess which images should be copied
> where from and where to. I can imagine how you can write a script that works
> for you, but not how you can write a script that would work for everyone. If
> you have a generic solution of course it is more than welcome.
I used the SRC tag in the resulting html files. In fact, two checks
would make the process more efficient.
for each SRC tag found in resulting html files
if srcfile does not exist
if srcfile does exist in original files
copy srcfile
This is done easily in shell with unix utilities. I dont know if it
could be integrated into a makefile. are makefiles just shell commands?
- --
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
iD8DBQFD457YucZ4lMT2d5IRAtH8AKCNb/fbcgSQQIpnVkpybxj2z+KD+ACfYbUV
0KUFnv3uXxs+Kke8rkoWi8s=
=cJIr
-----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 prev parent reply other threads:[~2006-02-03 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 14:27 JT Moree
2006-02-03 13:44 ` Éric Bischoff
2006-02-03 18:18 ` JT Moree [this message]
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=43E39ED8.1000004@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).