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:47:53 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g8MHlpVP032500 for ; Sun, 22 Sep 2002 19:47:52 +0200 MIME-Version: 1.0 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.27]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8MHd1aL008382; Sun, 22 Sep 2002 19:39:01 +0200 (MET DST) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C26260.2CEE6A80" 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 g8M400dK012650; Sun, 22 Sep 2002 19:36:53 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5476 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 19:36:53 +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 g8MHarWM015925 for ; Sun, 22 Sep 2002 19:36:53 +0200 Received: from webmail.tiscali.de ([62.27.55.1]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8MHckaL008350 for ; Sun, 22 Sep 2002 19:38:46 +0200 (MET DST) Received: from linux.local (62.246.98.243) by webmail.tiscali.de (6.0.045) id 3C9A8918027B0394 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 19:23:25 +0200 Received: (from one@localhost) by linux.local (8.11.3/8.11.3/SuSE Linux 8.11.1-0.5) id g8MHlLc04235 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 19:47:21 +0200 In-Reply-To: References: <001101c26266$36fde3b0$c69d70d5@gotia> Return-Path: X-OriginalArrivalTime: 22 Sep 2002 17:47:53.0892 (UTC) FILETIME=[2D768640: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: Sun, 22 Sep 2002 18:47:21 +0100 Message-ID: A<20020922174721.GA4120@linux> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: proposal [graphics] Thread-Index: AcJiYC2c9YJt/9v9RqSp/rM59Lrm7A== From: "Heiko Oberdiek" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4365 This is a multi-part message in MIME format. ------_=_NextPart_001_01C26260.2CEE6A80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.2CEE6A80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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.2CEE6A80--