ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: lpeg substitution
Date: Wed, 12 Aug 2009 08:51:32 +0200	[thread overview]
Message-ID: <4A826674.2020401@elvenkind.com> (raw)
In-Reply-To: <4A81EA35.6040108@wxs.nl>

Hans Hagen wrote:
> Thomas A. Schmitz wrote:
>>
>> On Aug 11, 2009, at 2:35 PM, Hans Hagen wrote:
>>
>>> what exactly do you want to replace ?
>>>
>>> Hans
>>>
>>
>> I'm trying to use the lpegs you have written for mtx-babel.lua, but 
>> instead of rewriting the greek ASCII stuff to a new file, I want to 
>> convert it to proper utf Greek and feed that to mkiv. As I said, it's 
>> a stopgap, but better than nothing...
> 
> 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.

If I had to do this myself, I would probably work on token lists,
even though it is quite a bit less convenient than strings. I remember
we have talked about writing extended lpegs that work directly on
token- and nodelists, that would perhaps be the nicest solution in
the long run. Anyway, I am just thinking out loud.

Best wishes,
Taco
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-08-12  6:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  9:34 Thomas A. Schmitz
2009-08-11 10:59 ` Hans Hagen
2009-08-11 11:21   ` Thomas A. Schmitz
2009-08-11 12:35     ` Hans Hagen
2009-08-11 15:14       ` Thomas A. Schmitz
2009-08-11 22:01         ` Hans Hagen
2009-08-12  6:51           ` Taco Hoekwater [this message]
2009-08-12  8:32             ` Hans Hagen
2009-08-12  9:04               ` Thomas A. Schmitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A826674.2020401@elvenkind.com \
    --to=taco@elvenkind.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).