Received: from mail.proteosys.com ([213.139.130.197]) by nummer-3.proteosys with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Mar 2009 13:13:07 +0100 Received: by mail.proteosys.com (8.14.3/8.14.3) with ESMTP id n2OCD6hM018373 for ; Tue, 24 Mar 2009 13:13:07 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n2OC9EtG011660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Mar 2009 13:09:14 +0100 Received: from listserv.uni-heidelberg.de (localhost.localdomain [127.0.0.1]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n2O8wjaa001396; Tue, 24 Mar 2009 13:09:12 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 15.5) with spool id 218332 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Tue, 24 Mar 2009 13:09:12 +0100 Received: from relay2.uni-heidelberg.de (relay2.uni-heidelberg.de [129.206.210.211]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id n2OC9CLu004050 for ; Tue, 24 Mar 2009 13:09:12 +0100 Received: from coliposte.enst-bretagne.fr (coliposte.enst-bretagne.fr [192.108.115.12]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id n2OC94NV011535 for ; Tue, 24 Mar 2009 13:09:07 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with ESMTP id n2OC96f3005348 for ; Tue, 24 Mar 2009 13:09:06 +0100 Received: from courrier.enst-bretagne.fr (vss-mail-02.priv.enst-bretagne.fr [10.29.90.4]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2008.01.11) with ESMTP id n2OC92HF005312 for ; Tue, 24 Mar 2009 13:09:05 +0100 Received: from [192.168.1.36] (passerelle-interne.enst-bretagne.fr [192.108.117.210]) (user=eroux mech=PLAIN bits=0) by courrier.enst-bretagne.fr (8.13.8/8.13.8/2006.06.07) with ESMTP id n2OC8vtb022836 for ; Tue, 24 Mar 2009 13:08:57 +0100 User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 References: <11ECEE9E-C040-44DF-9D1F-97281D9128ED@gmail.com> <49C8B459.5050201@telecom-bretagne.eu> <49C8C80B.3020504@elzevir.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at enst-bretagne.fr Message-ID: <49C8CD5A.4070105@telecom-bretagne.eu> Date: Tue, 24 Mar 2009 13:08:58 +0100 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Elie Roux Subject: Re: inputenc for XeTeX and LuaTeX To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE In-Reply-To: <49C8C80B.3020504@elzevir.fr> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-ProteoSys-SPAM-Score: -4 () RCVD_IN_DNSWL_MED X-Scanned-By: MIMEDefang 2.65 on 213.139.130.197 Return-Path: owner-latex-l@LISTSERV.UNI-HEIDELBERG.DE X-OriginalArrivalTime: 24 Mar 2009 12:13:07.0304 (UTC) FILETIME=[E400AE80:01C9AC79] Status: R X-Status: X-Keywords: X-UID: 5729 Manuel Pégourié-Gonnard a écrit : > I'm sorry but I disagree on this point. I don't think it is urgent to > adjust the > real inputenc. LuaTeX is still in early beta, so it should be used only by > somehow experienced users, or at least users aware of what they are doing. Such > users should be able to understand that they should either encode their source > in utf-8 (and don't load any inputenc) or load luainputenc. > With the new solution, people have to load luainputenc, it's not optional anymore. > By the way, people using XeTeX just encode their sources in utf-8 and skip > loading inputenc, and seem to be happy with it. > I think LuaTeX does not target the same users. With luainputenc and fontenc working, LuaTeX can start targetting the average user, as the old LaTeX documents will be working with LuaLaTeX (if inputenc loads luainputenc). XeTeX will never allow old documents to be compiled with it, as most input encoding problems have no solution. > Ok, so this is the point. You expect LuaTeX to become the default engine some > day, and for this to happen, backwards compatibility will indeed be very > important. But this will not happen before (at least) 2012 (announced date for > the first stable version). So I see no harm in waiting a bit before implementing > backward compatibility solutions. > And I see no harm in proposing a working LuaLaTeX... Of course, as LuaTeX is not stable, LuaLaTeX won't be stable... but remember that people call LuaLaTeX with the command "lualatex", so they know what they are doing. > Moreover, luainputenc, as far as I understand it, is currently not able to > compile correctly 100% of the old documents written for LaTeX over 8-bit TeX, > mainly due to the generated files problem. So IMO it is best to keep it as a > separate package while the issues are not solved. It also needs some (more) > real-life testing before being integrated in inputenc, IMO. > LuaTeX can only write UTF-8, so people needing to write in files in 8-bit without LICR (meaning not a lot of people) will have problems if they do it in home-made package (I solved the problem for all files generated by packages in TeXLive), so the problem concerns noone except very advanced TeX users... I know you're one of them, but for the average user it will be 99.9999% backward compatible. It doesn't mean that it's 100% stable though, as LuaTeX will continue to evolve. > A important point is, people need to know the difference between what is stable > and what isn't. They expect core packages maintained by the LaTeX team to be > stable and work in a 100% compatible way. This expectation should be satisfied. > Well, I'm not sure pdfTeX and TeX82 were 100% compatible neither... > By the way, while we're at suggesting things concerning inputenc and Unicode TeX > engines, my suggestion would be to detect those engines and issue a meaningfull > error message (not just a warning) like "You're running LuaTeX. inputenc can't > currently work on Unicode variants of TeX such as LuaTeX. Please consult > http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lualatex for how to use LaTeX > with LuaTeX." and refusing to load. > Or even better: a warning and the loading of luainputenc. I don't think this warning is necessary, but I don't have a strong opinion about it, I think it will just be boring for the average user... -- Elie