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 p71E1s7f014002 for ; Mon, 1 Aug 2011 16:01:55 +0200 Received: (qmail 8497 invoked by alias); 1 Aug 2011 14:01:49 -0000 Delivered-To: GMX delivery to rainer.schoepf@gmx.net Received: (qmail invoked by alias); 01 Aug 2011 14:01:49 -0000 Received: from relay2.uni-heidelberg.de (EHLO relay2.uni-heidelberg.de) [129.206.210.211] by mx0.gmx.net (mx079) with SMTP; 01 Aug 2011 16:01:49 +0200 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 p71DxJbS010335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 1 Aug 2011 15:59:21 +0200 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 p71DrpeX010519; Mon, 1 Aug 2011 15:59:19 +0200 Received: by LISTSERV.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 16.0) with spool id 1580339 for LATEX-L@LISTSERV.UNI-HEIDELBERG.DE; Mon, 1 Aug 2011 15:59:19 +0200 Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by listserv.uni-heidelberg.de (8.13.1/8.13.1) with ESMTP id p71DxJK9004577 for ; Mon, 1 Aug 2011 15:59:19 +0200 Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with SMTP id p71Dx9XW019875 for ; Mon, 1 Aug 2011 15:59:13 +0200 Received: (qmail invoked by alias); 01 Aug 2011 13:59:09 -0000 Received: from vpn136a.rzuser.uni-heidelberg.de (EHLO [129.206.196.136]) [129.206.196.136] by mail.gmx.net (mp071) with SMTP; 01 Aug 2011 15:59:09 +0200 X-Provags-ID: V01U2FsdGVkX1/FZD1RsHjFIAK4ufY1+wWUTLsLJQ+TVJb46tXB6U qiiLT6hGE7WYKn User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20110628 Thunderbird/5.0 MIME-Version: 1.0 References: <1295793648.2637194.1308604124163.JavaMail.fmail@mwmweb004> <04DDF439-D2E2-4335-89D0-C410EE65935A@frycomm.com> <82376E2C-57BF-42D3-B6E8-91FA98DABA45@frycomm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Message-ID: <4E36B12B.3040000@gmx.de> Date: Mon, 1 Aug 2011 15:59:07 +0200 Reply-To: Mailing list for the LaTeX3 project Sender: Mailing list for the LaTeX3 project From: Arno Trautmann Subject: Re: future To: LATEX-L@listserv.uni-heidelberg.de In-Reply-To: <82376E2C-57BF-42D3-B6E8-91FA98DABA45@frycomm.com> Precedence: list List-Help: , List-Unsubscribe: List-Subscribe: List-Owner: List-Archive: X-GMX-Antispam: 0 (BackTrace mail analyze); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnGL2vqOgpaBYL16oitsMrgDt/NQNpSCZFFjDOy 97xb7Zpf+wZnd5ZXNcvLDXR3Wg3wRjdQbwEMh8=V1; X-Resent-By: Forwarder X-Resent-For: rainer.schoepf@gmx.net X-Resent-To: rainer@rainer-schoepf.de Status: R X-Status: X-Keywords: X-UID: 6798 Hi William, William Adams wrote: > On Aug 1, 2011, at 8:01 AM, William Adams wrote: > >> So I guess this has two questions: >> >> 1 - what is the optimal way to get non-standard characters like that into a text stream? LuaTeX, I guess. The node manipulation in the post_linebreak_filter should easily do this and is most flexible. > There's an obvious corollary to this: > > 1b - Do we have a list of characters which are replaced by vector elements? If so, what should be done about them? In LuaTeX, traverse the node list, check for the char code, read out the width, replace the char node with a rule to the given width. > I believe that in any instance of the user issuing a command to output character(s) matching character(s) need to show up in the output. Depending on how many instances there are, this could lead to a huge number of output lines. I'd rather say, there should be a warning for each character at the beginning or at the end of the output. Maybe even the number of substitutet characters – which is no deal to do with a Lua approach. cheers Arno