ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans van der Meer via ntg-context <ntg-context@ntg.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Cc: Hans van der Meer <havdmeer@ziggo.nl>
Subject: Re: [NTG-context] xmlsetentity on the fly?
Date: Wed, 19 Apr 2023 11:24:31 +0200	[thread overview]
Message-ID: <226F29FE-B8FD-4213-9819-A4209865E0B1@ziggo.nl> (raw)
In-Reply-To: <04018D6D-B399-4984-A83B-05BA93BD6DDD@ziggo.nl>


[-- Attachment #1.1: Type: text/plain, Size: 2027 bytes --]

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 part of the input? I examined files lxml-ent.lua and lxml-tex.lua but could not find how to this.

dr. Hans van der Meer

> On 17 Apr 2023, at 18:11, Hans van der Meer via ntg-context <ntg-context@ntg.nl> wrote:
> 
> I tried 
> \directlua{xml.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)
>     entities[key] = value
>     if trace_entities then
>         report_xml("registering entity %a as %a",key,value)
>     end
> end
> 
> 
>> On 17 Apr 2023, at 12:32, Hans van der Meer <havdmeer@ziggo.nl> wrote:
>> 
>> 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 &DATE; within the <event>.
>> 
>> \stopxmlsetups
>> 
>> However, using &DATE; inside an <event> always results in THEDATE and never in NEWDATE.
>> 
>> How can I change the value of the entity inside the xmlsetups?
>> 
> 
> dr. Hans van der Meer
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : https://contextgarden.net
> ___________________________________________________________________________________


[-- Attachment #1.2: Type: text/html, Size: 4582 bytes --]

[-- Attachment #2: Type: text/plain, Size: 496 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2023-04-19  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17 10:32 Hans van der Meer via ntg-context
2023-04-17 11:00 ` Thomas A. Schmitz via ntg-context
2023-04-17 11:28   ` Hans van der Meer via ntg-context
2023-04-17 16:11 ` Hans van der Meer via ntg-context
2023-04-19  9:24   ` Hans van der Meer via ntg-context [this message]

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=226F29FE-B8FD-4213-9819-A4209865E0B1@ziggo.nl \
    --to=ntg-context@ntg.nl \
    --cc=havdmeer@ziggo.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).