ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "White, George" <WhiteG@mar.dfo-mpo.gc.ca>
Subject: RE: no tif?
Date: Wed, 14 Feb 2001 10:03:26 -0400	[thread overview]
Message-ID: <25DB90CB4178D4118AB300D0B72E7D030FC03F@MSGMARBIO05> (raw)

It is relatively non-informative to say "pdftex supports format XXX".  About
all
you can say is that a specific image worked with pdftex on a specific
platform.
Also, what "works" for one person may be unnacceptable to another
(e.g., color shifts).

EPS, TIF(F), and PNG, are umbrellas that cover a vast range of 
actual contents.  To use a particular format with pdftex you have to
first make sure that the support was compiled in, and then that the 
library you used is compatible with the particular file you happen to have.
With EPS you may not see the problem until you render the PS file.
The free libraries for TIFF, PNG, and JPEG have had bugs (some
provided by the system libraries they use) and often support a fraction
of the possibilities for a given format.  One many systems, ImageMagick
and gimp will use the same libraries that pdftex employs, so it can be
helpful to
a) check that you can view a troublesome image with either of those
applications
before blaming pdftex and b) try converting to another format (although each
format does have advantages for specific situations).  

There is a sample pdftex file that uses plain TeX and embeds some images.
It would be useful to expand this document by adding a larger range
of test images that people could use to verify the functionality of their
basic
pdftex installation.    

> -----Original Message-----
> From:	Uwe Koloska [SMTP:uwe.koloska@mailbox.tu-dresden.de]
> Sent:	Tuesday, February 13, 2001 8:37 PM
> To:	ntg-context@ntg.nl
> Subject:	Re: no tif?
> 
> 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??
> 
> And I don't have to use "texutil --figures" if I use pdftex, right?
> 
> Uwe
> 
> -- 
> mailto:koloska@rcs.urz.tu-dresden.de
> http://rcswww.urz.tu-dresden.de/~koloska/
> --                                    --
> right now the web page is in german only
> but this will change as time goes by ;-)


             reply	other threads:[~2001-02-14 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 14:03 White, George [this message]
2001-02-14 14:41 ` Han The Thanh
  -- strict thread matches above, loose matches on Subject: below --
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

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=25DB90CB4178D4118AB300D0B72E7D030FC03F@MSGMARBIO05 \
    --to=whiteg@mar.dfo-mpo.gc.ca \
    /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).