From: Eric Bischoff <ebisch@cybercable.tm.fr>
To: 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: <38F68140.E84FEB31@cybercable.tm.fr> (raw)
In-Reply-To: <38F60D4B.FB8D16E7@ditec.um.es>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1872 bytes --]
"Diego Sevilla Ruiz (dsevilla@um.es)" wrote:
>
> Hi, Eric:
>
> Sorry for my ignorance, but I am new to docbook ;-)
>
> What you use (&gif-eps;) is standard? I mean, can I use directly? Or
> does it depend on some "macro" defined before? Sorry again, but I don't
> know how to define "macros" in SGML :-( .
It's a kind of "macro" that is called an "entity". You can
define it
in an external file and then "include" it. Here is an
example:
In "document.docbook":
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
<!ENTITY % magic-entities SYSTEM "magic.ent">
%magic-entities; <!-- This is where we include it -->
]>
<book lang="en">
...
<graphic fileref="flower.&jpeg-eps;"></graphic>
\x03 <!-- and here is where we use it -->
\x03...
<graphic fileref="cactus.&gif-eps;"></graphic>
...
</book>
and in "magic.ent":
<!-- here we define it -->
<!ENTITY % html "IGNORE">
<![%html; [
<!ENTITY % print "IGNORE">
<!ENTITY gif-eps "gif">
<!ENTITY jpg-eps "jpg">
<!ENTITY jpeg-eps "jpeg">
]]>
<!ENTITY % print "INCLUDE">
<![%print; [
<!ENTITY gif-eps "eps">
<!ENTITY jpg-eps "eps">
<!ENTITY jpeg-eps "eps">
]]>
You need to pass "-i html" or "-i print" to jade so the
right extension is chosen at processing time. The
docbook-tools wrapper scripts do this.
It is quite rough, but it works.
--
Ã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 [this message]
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 ` 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 ` 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 ` Sam Roberts
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` David C. Mason
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=38F68140.E84FEB31@cybercable.tm.fr \
--to=ebisch@cybercable.tm.fr \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/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).