From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/52224 Path: news.gmane.org!not-for-mail From: "Thomas A. Schmitz" Newsgroups: gmane.comp.tex.context Subject: Re: lpeg substitution Date: Wed, 12 Aug 2009 11:04:30 +0200 Message-ID: <61F11BB9-7B02-4907-B0E7-4BD4E2E67271@uni-bonn.de> References: <00765789-37D5-4318-9055-898AAA792135@uni-bonn.de> <4A814EF6.60101@wxs.nl> <4A816587.2060302@wxs.nl> <4A81EA35.6040108@wxs.nl> <4A826674.2020401@elvenkind.com> <4A827E1B.6050608@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v935.3) Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1250067920 11580 80.91.229.12 (12 Aug 2009 09:05:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 12 Aug 2009 09:05:20 +0000 (UTC) To: mailing list for ConTeXt users Original-X-From: ntg-context-bounces@ntg.nl Wed Aug 12 11:05:12 2009 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from balder.ntg.nl ([195.12.62.10]) by lo.gmane.org with esmtp (Exim 4.50) id 1Mb9lf-0003AN-N7 for gctc-ntg-context-518@m.gmane.org; Wed, 12 Aug 2009 11:05:11 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id DB69AC9AAA; Wed, 12 Aug 2009 11:05:07 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bGWrlzK9i+FX; Wed, 12 Aug 2009 11:04:54 +0200 (CEST) Original-Received: from balder.ntg.nl (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id B480FC9A81; Wed, 12 Aug 2009 11:04:54 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by balder.ntg.nl (Postfix) with ESMTP id D788CC9A81 for ; Wed, 12 Aug 2009 11:04:53 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at balder.ntg.nl Original-Received: from balder.ntg.nl ([127.0.0.1]) by localhost (balder.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6LCp-p4bmgwh for ; Wed, 12 Aug 2009 11:04:48 +0200 (CEST) Original-Received: from uni-bonn.de (mail.uni-bonn.de [131.220.15.113]) by balder.ntg.nl (Postfix) with ESMTP id 42E21C9A77 for ; Wed, 12 Aug 2009 11:04:46 +0200 (CEST) Original-Received: from [87.178.90.94] (account tschmit1@uni-bonn.de HELO [192.168.0.2]) by fe2.uni-bonn.de (CommuniGate Pro SMTP 5.2.12) with ESMTPA id 21779751 for ntg-context@ntg.nl; Wed, 12 Aug 2009 11:04:45 +0200 In-Reply-To: <4A827E1B.6050608@wxs.nl> X-Mailer: Apple Mail (2.935.3) X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.12 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl Xref: news.gmane.org gmane.comp.tex.context:52224 Archived-At: On Aug 12, 2009, at 10:32 AM, Hans Hagen wrote: >>> if there is more demand for that i can consider making a >>> substituter that operates on the node list in an early stage; that >>> way it is controlled by attributes and there is no interference >>> with macro definitions, reading modules and such >> Macro interaction may be an issue, but I believe it is still better >> for transliterations to work on the actual input strings or on >> tokens. >> For example, you may want to run macros (like \delimitedtext) on the >> converted output. > > my main concern with that is that one then needs to control > precisely where to apply such translations; for instance turning a< > into something else might also mess up math and adding all kind of > extra checking and housekeeping (for instance when loading modules > or whatever in the middle of such a conversion) > > of course when the to be converted fragments are tagged it's trivial > to use lpeg and avoid \cs's > > btw, i think that delimitedtext would work anyway as we only replace > "glyph a glyph<" by something else then > > anyway, it all depends on the task and hopefully unicode will solve > all our problems (and not introduce more) Well, in my case the fragments are already delimited, so it's relatively easy. However, I wonder whether there are many applications for this. I don't see too many, but maybe I'm wrong. From my POV, there is no need for this in the core, but maybe others see more usage. Thomas ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________