Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 22 Sep 2002 19:51:14 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g8MHp5VP032507 for ; Sun, 22 Sep 2002 19:51:13 +0200 MIME-Version: 1.0 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8MHhkL0018872; Sun, 22 Sep 2002 19:43:47 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C26260.A4BC9500" Received: from listserv (listserv.uni-heidelberg.de [129.206.100.27]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g8M400dS012650; Sun, 22 Sep 2002 19:41:52 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5485 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 19:41:52 +0200 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g8MHfqWM015951 for ; Sun, 22 Sep 2002 19:41:52 +0200 Received: from mf2.bredband.net (pop02.lab.bredband.com [195.54.122.120]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8MHhiaL008757 for ; Sun, 22 Sep 2002 19:43:45 +0200 (MET DST) Received: from gotia ([213.112.157.198]) by mf2.bredband.net with SMTP id <20020922174529.UMQL8373.mf2@gotia> for ; Sun, 22 Sep 2002 19:45:29 +0200 References: <001101c26266$36fde3b0$c69d70d5@gotia> <20020922174721.GA4120@linux> Return-Path: X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft Exchange V6.5 X-OriginalArrivalTime: 22 Sep 2002 17:51:18.0282 (UTC) FILETIME=[A749F6A0:01C26260] X-Scanned-By: MIMEDefang 2.11 (www dot roaringpenguin dot com slash mimedefang) Content-class: urn:content-classes:message Subject: Re: proposal [graphics] Date: Mon, 23 Sep 2002 03:48:06 +0100 Message-ID: A<009101c262ab$a4f75f00$c69d70d5@gotia> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: proposal [graphics] Thread-Index: AcJiYKdlGhis+Z6/Suq3eNHZlRKhhQ== From: =?iso-8859-1?Q?Anders_Lind=E9n?= To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4371 This is a multi-part message in MIME format. ------_=_NextPart_001_01C26260.A4BC9500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable The idea is to get rid of the need of conversion programs. All I want to do is to \includegraphics{foo.jpg} or \includegraphics{foo.gif} or \includegraphics{foo.png} (The last is actually possible to do with pdflatex). I dont want to be dependent on a number of external conversion = utilities. /A ----- Original Message ----- From: "Heiko Oberdiek" To: Sent: Sunday, September 22, 2002 10:47 AM Subject: Re: proposal [graphics] > On Sun, Sep 22, 2002 at 10:50:51AM +0100, Robin Fairbairns wrote: > > > > I am still new to LaTeX, but I cant resist on giving a proposal = for a LaTeX > > > improvement. > > > > > > I think that any of the 20 most common graphics formats shall be > > > include:able using \includegraphics. > > > > > > Bitmap as well as vector. > > > Using latex as well as using pdflatex. > > > > the problem is, that to first order, this is nothing to do with = latex > > itself. > > At least it has to do with the interface to LaTeX's graphicx > package. > > > latex needs to know the dimensions of the graphic, only. > > There are a lot of "graphics" formats (eg. PDF, PS, ...) > that contain several "pages", so the graphicx package needs > to know the number of pages, too. > > > the rest is > > down to the dvi->whatever converter (in the case of latex) or to > > pdftex itself (in the case of pdflatex). > > * dvi->whatever, pdfTeX, VTeX, ... use its own methods. > pdfTeX, VTeX can provide bounding box informations back > to TeX, but this is not possible with dvi->whatever. > Perhaps a program by \immediate\write18 can help to > provide the information in this case. > * Some TeX implementations provide \immediate\write18, > so a conversion program could be called by the > graphicx package to get informations and the > understandable format of the graphics for the given driver. > * Plugin/Library method: > * Interface for inclusion in TeX, pdfTeX, ... for > extracting informations to LaTeX's graphicx package. > * Interface for inclusion in dvi->whatever, pdfTeX, ... > for reading the different graphics formats that are > then put into the output. > > Yours sincerely > Heiko ------_=_NextPart_001_01C26260.A4BC9500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: proposal [graphics]

The idea is to get rid of the need of conversion = programs.
All I want to do is to

\includegraphics{foo.jpg}

or

\includegraphics{foo.gif}

or

\includegraphics{foo.png}

(The last is actually possible to do with = pdflatex).

I dont want to be dependent on a number of external = conversion utilities.

/A


----- Original Message -----
From: "Heiko Oberdiek" = <oberdiek@UNI-FREIBURG.DE>
To: <LATEX-L@listserv.uni-heidelberg.de>
Sent: Sunday, September 22, 2002 10:47 AM
Subject: Re: proposal [graphics]


> On Sun, Sep 22, 2002 at 10:50:51AM +0100, Robin = Fairbairns wrote:
>
> > > I am still new to LaTeX, but I cant = resist on giving a proposal for a
LaTeX
> > > improvement.
> > >
> > > I think that any of the 20 most common = graphics formats shall be
> > > include:able using = \includegraphics.
> > >
> > > Bitmap as well as vector.
> > > Using latex as well as using = pdflatex.
> >
> > the problem is, that to first order, this = is nothing to do with latex
> > itself.
>
> At least it has to do with the interface to = LaTeX's graphicx
> package.
>
> > latex needs to know the dimensions of the = graphic, only.
>
> There are a lot of "graphics" formats = (eg. PDF, PS, ...)
> that contain several "pages", so the = graphicx package needs
> to know the number of pages, too.
>
> > the rest is
> > down to the dvi->whatever converter (in = the case of latex) or to
> > pdftex itself (in the case of = pdflatex).
>
> * dvi->whatever, pdfTeX, VTeX, ... use its = own methods.
>   pdfTeX, VTeX can provide bounding = box informations back
>   to TeX, but this is not possible = with dvi->whatever.
>   Perhaps a program by = \immediate\write18 can help to
>   provide the information in this = case.
> * Some TeX implementations provide = \immediate\write18,
>   so a conversion program could be = called by the
>   graphicx package to get informations = and the
>   understandable format of the = graphics for the given driver.
> * Plugin/Library method:
>   * Interface for inclusion in TeX, = pdfTeX, ... for
>     extracting informations = to LaTeX's graphicx package.
>   * Interface for inclusion in = dvi->whatever, pdfTeX, ...
>     for reading the = different graphics formats that are
>     then put into the = output.
>
> Yours sincerely
>   Heiko = <oberdiek@uni-freiburg.de>

------_=_NextPart_001_01C26260.A4BC9500--