From: godoy@conectiva.com.br
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: <m2aeiw4ncn.fsf@nexus.conectiva> (raw)
In-Reply-To: <m3wvm04ptn.fsf@nova.revier.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
Jochem Huhmann <joh@gmx.net> writes:
> The actual problem (as so often with this stuff) is to make it easy to
> use from a documentation writers point of view. Actually we don't need
> any tools, we do need jade and stylesheets and DTD's and a Makefile.
> Period.
>
> Someone who just wants to write and convert docs needs simple, straight,
> well-documented tools with a man-page. With some commandline options or
> with a GUI and with simple configuration files, with reasonable defaults
> in /etc and his own in $HOME to override this. We should try to keep
> that in mind. Tell these people about entities and driver files and such
> and they won't use that at all.
We work this way:
1. Linux platform
2. DocBook and OpenJade or DocBook and other converter
3. All pictures are in TIFF format (better quality)
4. Emacs + PSGML as editor (choose whatever you want. This gave us the
easiness we needed to have plus an automation on validation of the
document --- and syntax highlighting)
5. NFS for stylesheet and some common scripts --- I'm changing this to
be a package now...
6. ImageMagick package (because of the graphical conversion tools)
7. teTeX
Our makefile is called by a script in a command line that looks like
this:
$ compiles document format [stylesheet -- optional] [converter -- optional]
document is the SGML document, format is one of the supported output
formats of Jade/OpenJade (mif, html, jadetex, ...) or a combination of
them (PS, DVI, ASCII, ...). Stylesheet is an optional stylesheet to be
used and converter is used to choose between Jade and OpenJade, being
OpenJade the default.
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
and then call the Makefile with the correct options (runs
collateindex, runs openjade, runs jadetex 3 times, runs dvips and
finally calls gv).
Authors use the <mediaobject> option to insert figures (as I've sent
before on this list).
We have no problems here (more than 20 people writing documents and books)...
PS:. We are in the process of changing some steps described, but this
works perfectly.
Regards,
--
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 ` 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 ` 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 ` 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 [this message]
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
-- 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=m2aeiw4ncn.fsf@nexus.conectiva \
--to=godoy@conectiva.com.br \
--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).