From: Jorge Godoy <godoy@conectiva.com.br>
To: DocBook Mailing List <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Figures (was figures' sizes in latex)
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <20000131101456.M13525@conectiva.com.br> (raw)
In-Reply-To: <389446BD.34B1D46F@hispalinux.es>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Sun, Jan 30, 2000 at 03:12:13PM +0100, Ismael Olea wrote:
>
> Hi:
>
> I'm usign figures as this
>
> <![ %PRINTONLY [<graphic width="5.5in" depth="3in" scalefit="1"
> fileref="./figs/figure.eps"></graphic>]]>
>
> but latex seems to ignore the sizes.
>
> I create the eps files from gifs converted with convert (ImageMagik).
>
Talking about figures, what's the correct way of using figures when
the desired output will be published on-line and in a book? I'll use
the TeX output for the printed version. Do I need to have pictures in
EPS (or PS) format and in another (e.g. JPEG) format? Isn't there a
way of using only one graphical format for all outputs? EPS pictures
are _really_ BIG.
Thanks,
--
Godoy. <godoy@conectiva.com.br> GPG Fingerprint
851B B620 626D 2AD0 E783
"Ser poeta não é minha ambição, E932 1330 BE6D A4A3 0625
é minha maneira de estar sozinho"
- Fernando Pessoa. Publicações @ Conectiva S.A.
Except where explicitly stated I speak on my own behalf.
Exceto onde explicitado as declarações aqui feitas são apenas minhas.
next prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 figures' sizes in latex Ismael Olea
2000-12-27 6:36 ` Jorge Godoy [this message]
2000-12-27 6:36 ` Figures (was figures' sizes in latex) Mark Galassi
2000-12-27 6:36 ` figures' sizes in latex Mark Galassi
2000-12-27 6:36 ` David C. Mason
2000-12-27 6:36 ` Ismael Olea
2000-12-27 6:36 ` Ismael Olea
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=20000131101456.M13525@conectiva.com.br \
--to=godoy@conectiva.com.br \
--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).