From: godoy@conectiva.com.br
To: Eric Bischoff <ebisch@cybercable.tm.fr>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: images in Docbook with Red Hat 6.2
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <m23doo1po6.fsf@nexus.conectiva> (raw)
In-Reply-To: <38F7B703.CA303809@cybercable.tm.fr>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
Eric Bischoff <ebisch@cybercable.tm.fr> writes:
> godoy@conectiva.com.br wrote:
> >
> > We work this way:
> >
> > All pictures are in TIFF format (better quality)
> >
> > When I choose "PS" backend, the script runs something similar to
> >
> > for i in `ls directory/images/tiff/*.tiff` ; do
> > convert directory/images/tiff/$i directory/images/eps/`basename $i .tiff`.eps
> > done
>
> Yes, this is a very good solution too. It only has two small
> drawback :
> - it can be slow to convert all the pictures each time you
> process the docbook
> document. But this can be avoided through a test or using
> the Makefile mechanism.
They are converted only if there's no converted file. Conversion can
be suppressed with "touch", for testing purposes...
> - it requires disciple from your authors ;-)
Well... Everything would require that, but all this process can be
mapped to Emacs and it can asks interactively by these
parameters. VI/pico/jed/etc users can run these by hand.
1. There's no perfect solution.
2. "Make a foul proof tool and only a foul would use it".
These two sayings are very useful guidelines when developing something
:-)
--
Godoy. <godoy@conectiva.com.br>
Departamento de Publicações
Publishing Department Conectiva S.A.
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` godoy
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` godoy [this message]
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` Diego Sevilla Ruiz (dsevilla@um.es)
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
-- strict thread matches above, loose matches on Subject: below --
2000-12-27 6:36 Peter Toft
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=m23doo1po6.fsf@nexus.conectiva \
--to=godoy@conectiva.com.br \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=ebisch@cybercable.tm.fr \
/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).