From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [callbacks] proper registration, node subtypes
Date: Tue, 26 Jun 2012 13:13:19 +0200 [thread overview]
Message-ID: <4FE9994F.6060403@wxs.nl> (raw)
In-Reply-To: <20120625145031.GC31738@phlegethon>
On 25-6-2012 16:50, Philipp Gesang wrote:
> ···<date: 2012-06-25, Monday>···<from: Hans Hagen>···
>
>> On 25-6-2012 15:39, Philipp Gesang wrote:
>>
>>> - Does the difference wrt node subtype matter assuming I only
>>> (a) copy glyph nodes and (b) manipulate their .char field?
>>
>> not that much, it's just a state signal for font processing
>
> Good to know.
>
>>> Any insights on this matter would be greatly appreciated. Regards
>>> Philipp
>>
>> it all depends on what you want to do
>
> Traverse the node list of a paragraph before line break from head
> to tail in sequential order, recursing into sublists where they
> appear. The callback removes and inserts nodes: which ones
> depends on the nodes already processed (has a state).
>
> Using the previous example code,
>
> \startfoo
> a\hbox{b}c
> \stopfoo
>
> should result in the traversal <glyph a>, <hlist ...>, <glyph c>.
\starttext
\startluacode
local function processnestedlist(head,n)
local current, done = head, false
while current do
local id = current.id
if id == nodes.nodecodes.hlist or id == nodes.nodecodes.vlist then
local _, d = processnestedlist(current.list,n)
if d then
done = true
end
elseif id == nodes.nodecodes.hglue_code and current.leader then
local _, d = processnestedlist(current.leader,n)
if d then
done = true
end
elseif id == nodes.nodecodes.glyph then -- todo: dics nodes
n = n + 1
print(n,utf.char(current.char))
end
current = current.next
end
return head, done, n
end
thirddata = thirddata or {}
thirddata.test = thirddata.test or { }
thirddata.test.one = function(head)
local head, done, n = processnestedlist(head,0)
print("n of glyphs",n)
return head, done
end
nodes.tasks.appendaction ("processors","before","thirddata.test.one")
\stopluacode
\ruledhbox to 10cm {\strut hello \ruledhbox{brave new} world
\cleaders\hbox{!}\hfil}
\stoptext
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-06-26 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 13:39 Philipp Gesang
2012-06-25 14:21 ` Hans Hagen
2012-06-25 14:50 ` Philipp Gesang
2012-06-26 11:13 ` Hans Hagen [this message]
2012-06-26 12:08 ` Philipp Gesang
2012-06-26 12:50 ` Hans Hagen
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=4FE9994F.6060403@wxs.nl \
--to=pragma@wxs.nl \
--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).