Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 22 Sep 2002 11:56:07 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g8M9u5VP031725 for ; Sun, 22 Sep 2002 11:56:05 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2621E.453D9580" 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 g8M9oqaL003174; Sun, 22 Sep 2002 11:50:52 +0200 (MET DST) 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 g8M400ZM012650; Sun, 22 Sep 2002 11:48:59 +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 5214 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 11:48:59 +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 g8M9mxWM013881 for ; Sun, 22 Sep 2002 11:48:59 +0200 Received: from wisbech.cl.cam.ac.uk (IDENT:Xg1HGHdSRtv93foxOkrKamZJc+oMYrrB@mta1.cl.cam.ac.uk [128.232.0.15]) by relay2.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8M9ooaL003158 for ; Sun, 22 Sep 2002 11:50:51 +0200 (MET DST) Received: from pallas.cl.cam.ac.uk ([128.232.8.88] helo=cl.cam.ac.uk ident=rf) by wisbech.cl.cam.ac.uk with esmtp (Exim 3.092 #1) id 17t3O7-0002Tt-00 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 10:50:51 +0100 In-Reply-To: Your message of "Sun, 22 Sep 2002 11:31:06 PDT." <001101c26266$36fde3b0$c69d70d5@gotia> Return-Path: X-OriginalArrivalTime: 22 Sep 2002 09:56:07.0304 (UTC) FILETIME=[456BF880:01C2621E] 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 10:50:51 +0100 Message-ID: A X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: proposal [graphics] Thread-Index: AcJiHkWE7D4yzWVKT9O2/3pQSPqelQ== From: "Robin Fairbairns" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4364 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2621E.453D9580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > 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. latex needs to know the dimensions of the graphic, only. the rest is down to the dvi->whatever converter (in the case of latex) or to pdftex itself (in the case of pdflatex). further reading: http://www.tex.ac.uk/faq, answers about \specials and the graphics section. ------_=_NextPart_001_01C2621E.453D9580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: proposal [graphics]

> 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.

latex needs to know the dimensions of the graphic, = only.  the rest is
down to the dvi->whatever converter (in the case = of latex) or to
pdftex itself (in the case of pdflatex).

further reading: http://www.tex.ac.uk/faq, answers = about \specials and
the graphics section.

------_=_NextPart_001_01C2621E.453D9580--