Received: from mail.proteosys.com ([62.225.9.49]) by nummer-3.proteosys with Microsoft SMTPSVC(5.0.2195.5329); Sun, 22 Sep 2002 21:16:38 +0200 Received: by mail.proteosys.com (8.12.2/8.12.2) with ESMTP id g8MJGaVP032738 for ; Sun, 22 Sep 2002 21:16:37 +0200 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 g8MJBraL015862; Sun, 22 Sep 2002 21:11:53 +0200 (MET DST) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2626C.92E0EF00" 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 g8M400f2012650; Sun, 22 Sep 2002 21:09:51 +0200 Received: from LISTSERV.UNI-HEIDELBERG.DE by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8d) with spool id 5590 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 21:09:51 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.12.2/8.12.2/SuSE Linux 0.6) with ESMTP id g8MJ9pWM016428 for ; Sun, 22 Sep 2002 21:09:51 +0200 Received: from gwyn.kn-bremen.de (root@gwyn.kn-bremen.de [212.63.36.242]) by relay.uni-heidelberg.de (8.12.4/8.12.4) with ESMTP id g8MJBhL0026648 for ; Sun, 22 Sep 2002 21:11:44 +0200 (MET DST) Received: from gwyn.kn-bremen.de (uucp@gwyn [127.0.0.1]) by gwyn.kn-bremen.de (8.12.3/8.12.3/Debian -4) with ESMTP id g8MJBheV011997 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Sun, 22 Sep 2002 21:11:43 +0200 Received: (from uucp@localhost) by gwyn.kn-bremen.de (8.12.3/8.12.3/Debian -4) with UUCP id g8MJBh3c011995 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 21:11:43 +0200 Received: (from ms@localhost) by lucien.oneiros.kn-bremen.de (8.9.3/8.9.3) id VAA23718 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Sun, 22 Sep 2002 21:09:52 +0200 In-Reply-To: ; from apostolo@OBELIX.EE.DUTH.GR on Sun, Sep 22, 2002 at 09:10:04PM +0300 References: <009101c262ab$a4f75f00$c69d70d5@gotia> Return-Path: X-OriginalArrivalTime: 22 Sep 2002 19:16:38.0593 (UTC) FILETIME=[933B6B10:01C2626C] mail-followup-to: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE User-Agent: Mutt/1.2.5.1i 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 20:09:51 +0100 Message-ID: A<20020922210951.A22378@lucien.kn-bremen.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: proposal [graphics] Thread-Index: AcJibJNXwUV5Fl40R/KBnP92j+2dSg== From: "Martin Schroeder" To: Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4368 This is a multi-part message in MIME format. ------_=_NextPart_001_01C2626C.92E0EF00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On 2002-09-22 21:10:04 +0300, Apostolos Syropoulos wrote: > On Sun, 22 Sep 2002, [iso-8859-1] Anders Lind=E9n wrote: > > \includegraphics{foo.png} That should always be \includegraphics{foo} so the driver can sort out which format it can read best. > Actually both of these are possible with pdfTeX. As far it regards gif > files, I think they are actually useless... AFAIK the relevant patents expire sometime next year, so maybe it could be added to the drivers. OTOH as long as on-the-fly conversion to a supported format is needed, I don't see any sense in bloating the drivers by adding support for another format. Best regards Martin -- http://www.tm.oneiros.de ------_=_NextPart_001_01C2626C.92E0EF00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: proposal [graphics]

On 2002-09-22 21:10:04 +0300, Apostolos Syropoulos = wrote:
> On Sun, 22 Sep 2002, [iso-8859-1] Anders = Lind=E9n wrote:
> > \includegraphics{foo.png}

That should always be
    \includegraphics{foo}
so the driver can sort out which format it can read = best.

> Actually both of these are possible with pdfTeX. = As far it regards gif
> files, I think they are actually = useless...

AFAIK the relevant patents expire sometime next year, = so maybe it
could be added to the drivers. OTOH as long as = on-the-fly
conversion to a supported format is needed, I don't = see any sense
in bloating the drivers by adding support for another = format.

Best regards
    Martin
--
          &nbs= p;         http://www.tm.oneiros.de

------_=_NextPart_001_01C2626C.92E0EF00--