From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: Jochem Huhmann <joh@gmx.net>
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: <38F6E77C.66C4280E@cybercable.tm.fr> (raw)
In-Reply-To: <m31z49937a.fsf@nova.revier.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Jochem Huhmann wrote:
>
> * Eric Bischoff <ebisch@cybercable.tm.fr> wrote:
> > The stylesheets solution could perfectly work if there was a
> > way to easily detect which extension(s) do exist for this
> > file from DSSSL.
>
> Could this be done by looking at this from the converting
> (shell-)backend that builds the command-line for jade? It knows the
> output format and could pass a variable to jade via "-V variable=value",
> which is available in the stylesheet then (or isn't it?). Just a fuzzy
> idea...
You idea is good, but this would mean that you should pass
*for each screenshot* its file type while calling jade. If
your doc includes, say, 120 screenshots, you can imagine the
number of parameters to Jade... Well, a shell script could
do the job, yes, but would jade stand so much variables ?
--
Ãric Bischoff - mailto:ebisch@cybercable.tm.fr
__________________________________________________
\^o~_.
.~. ______ /( __ )
/V\ Toys story \__ \/ ( V
// \\ \__| (__=v
/( )\ |\___/ )
^^-^^ \_____( )
Tux Konqui \__=v
__________________________________________________
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 ` Diego Sevilla Ruiz (dsevilla@um.es)
2000-12-27 6:36 ` Eric Bischoff
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Sam Roberts
2000-12-27 6:36 ` Eric Bischoff
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 ` Jochem Huhmann
2000-12-27 6:36 ` Eric Bischoff [this message]
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 ` Eric Bischoff
2000-12-27 6:36 ` godoy
2000-12-27 6:36 ` Jochem Huhmann
2000-12-27 6:36 ` Jochem Huhmann
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=38F6E77C.66C4280E@cybercable.tm.fr \
--to=ebisch@cybercable.tm.fr \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=joh@gmx.net \
/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).