Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100]) by h1439878.stratoserver.net (8.14.2/8.14.2/Debian-2build1) with SMTP id o1AJ0K2h012046 for ; Wed, 10 Feb 2010 20:00:21 +0100 Received: (qmail 6865 invoked by alias); 10 Feb 2010 19:00:15 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 10 Feb 2010 19:00:14 -0000 Received: from relay.uni-heidelberg.de (EHLO relay.uni-heidelberg.de) [129.206.100.212] by mx0.gmx.net (mx037) with SMTP; 10 Feb 2010 20:00:14 +0100 Received: from listserv.uni-heidelberg.de (listserv.uni-heidelberg.de [129.206.100.94]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id o1AIuhtP020605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Feb 2010 19:56:43 +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 o1A9akje013381; Wed, 10 Feb 2010 19:56:34 +0100 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 399943 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Feb 2010 19:56:34 +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 o1AIuYc9019667 for ; Wed, 10 Feb 2010 19:56:34 +0100 Received: from anchor-post-1.mail.demon.net (anchor-post-1.mail.demon.net [195.173.77.132]) by relay2.uni-heidelberg.de (8.13.8/8.13.8) with ESMTP id o1AIuNvt031703 for ; Wed, 10 Feb 2010 19:56:29 +0100 Received: from cremornelane.demon.co.uk ([80.177.25.195] helo=palladium.local) by anchor-post-1.mail.demon.net with esmtp (Exim 4.69) id 1NfHjb-000734-gq for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Wed, 10 Feb 2010 18:56:23 +0000 User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 References: <4B727378.8060704@morningstar2.co.uk>, <4B729944.5050308@residenset.net> , <4B72B36E.6010401@morningstar2.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <4B730157.5060605@morningstar2.co.uk> Date: Wed, 10 Feb 2010 18:56:23 +0000 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Joseph Wright Subject: Re: LaTeX3 8-bit only? To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (Mail was not recognized as spam); Detail=5D7Q89H36p4WX0t+AtsdW2ORvUlAfcdSIdQlIL3FTSFQDxQiodii41fjuqHQd8jelXgy3 MmJ3btkX5rSzFn9hFaFIkN3F60IXoQiiC2/fgzDMa2Sr9P5SXQm9Ht9JSeZtUVRZ8Ll4+eY8TRy+ si13Q==V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de X-Scanned-By: MIMEDefang 2.63 on 85.214.41.38 Status: R X-Status: X-Keywords: X-UID: 6239 Hello Chris, > Input is not the only place where character-like things appear in TeX; this is another way of saying what Lars said. Character repertoires are distinct from encodings of characters and these are different again from the encodings used in external files. > > So you need to know what character repertoires you are going to deal with internally in these various types of string, whether or not these are represeted by, for example, 7-bit LICRs. I was thinking of input encodings, where my point was (supposed to) be that something like the inputenc "utf8" approach would be an approach I hope we can avoid as there are better solutions (in the form of engines which deal with the issue). (Of course, that leaves UTF-16 issues, but I'd hope that engine developments can help out). (I'd point out that LaTeX3 code is intended for use in new documents, and the rest of the computer world is standardising on UTF-8 as far as I can see. So I'd hope very much that having an approach based on this concept is not too risky.) -- Joseph Wright