From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: no tif?
Date: Wed, 14 Feb 2001 09:31:03 +0100 [thread overview]
Message-ID: <3.0.6.32.20010214093103.01bee100@server-1> (raw)
In-Reply-To: <01021401372808.00556@bilbo>
At 01:37 AM 2/14/01 +0100, Uwe Koloska wrote:
>Hello,
>
>You wrote on Dienstag, 13. Februar 2001 18:13:
>>> [tif problems with context and pdftex]
>>
>>when pdftex is used, context does not use texutil.
>>
>>tif support in pdftex is not always compiled into the binary so i disabled
>>it in context, also because not all tif formats are supported [actually,
>>pdf does not support tiff, but some tiff compression schemes]. Png is a
>>better format.
>
>Ahh! So to make it clear I changed the table from the manual:
>
> eps pdf mps tif png jpg mov
>dvips + - + - - - +
>dvipsone + - + + - - +
>pdftex - + + - + -? +
>
>what about jpg and pdftex??
pdftex supports jpg
>And I don't have to use "texutil --figures" if I use pdftex, right?
right, context will parse eps/mps anyway, and when using pdftex, not parse
at all;
when you have 100 Gig figures and want to run on another machine, you can
generate a tuf file (texutil --fig) and move that to the other machine
(did you ever try: texexec --fig --pdf fig-*.* or alike?)
also, when needed context can run texutil itself (if enabled)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-02-14 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 14:54 Uwe Koloska
2001-02-13 17:00 ` Taco Hoekwater
2001-02-13 17:13 ` Hans Hagen
2001-02-14 0:37 ` Uwe Koloska
2001-02-14 8:31 ` Hans Hagen [this message]
2001-02-14 14:03 White, George
2001-02-14 14:41 ` Han The Thanh
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=3.0.6.32.20010214093103.01bee100@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).