After some experiments I am now fairly convinced that the entities are
substituted BEFORE the typesettting actually starts. And thus changing the
entity on the fly will have no effect. Is there a flag that can be set in order
to delay the substitution until the actual moment of typesetting that
I tried
\directlua{lxml.registerentity("DATE","NEWDATE")}
and
\directlua{lxml.registerentity("DATE","NEWDATE")}
but neither does effect a change in the entity.
Why is that entry not set in the Lua-table entities? (file xml-ent.lua) has as
that function:
function xml.registerentity(key,value)
> Use \xmltexentity
Already tried this. But doesn't work. I guess it has more to do with the
definition of the entity in the stsrem.
met vriendelijke groet,
dr. Hans van der Meer
Burgemeester Rijnderslaan 244
1185 MC Amstelveen
tel. 020 6452701 / 06 53743629
> On 17 Apr 2023, at 13:00, Thomas
Use \xmltexentity
Thomas
> On 17. Apr 2023, at 12:32, Hans van der Meer via ntg-context
> wrote:
>
> I would like to change an entity 'on the fly'. Example
___
If your question is of interest to others as well,
I would like to change an entity 'on the fly'. Example
\def\DATE{THEDATE}\expanded{\xmlsetentity{DATE}{\DATE}}
\startxmlsetups typ:event
\def\DATE{NEWDATE}\expanded{\xmlsetentity{DATE}{\DATE}}
Using within the .
\stopxmlsetups
However, using inside an always results in THEDATE and
