From: Jano Kula <jano.kula@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: expansion of xml userdata
Date: Sun, 17 Jan 2021 21:22:16 +0100 [thread overview]
Message-ID: <CAPefzZ1t+4mNRreMMvqrY8yegGEFzUnnwY5a7zDD9f+DKv3BnA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
Hello to everybody!
\setuphead[section][expansion=yes] expands xml reference to the actual
content in TUC file:
\xmlatt {xml:name::4}{title} → First section
for titles & bookmarks. The same is not true for userdata (mkiv & mkxl). Do
you know how to force expansion of userdata?
MWE attached.
Thank you,
Jano
\startbuffer[doc]
<?xml version "1.0"?>
<document>
<section title="First section">
text
</section>
<section title="Second section">
text
</section>
</document>
\stopbuffer
\setuphead[section][expansion=yes]
\setuplist[section][alternative=command,
command=\SectionListCommand]
\define[3]\SectionListCommand{%
{\bf#1\par
title: #2\par
usertitle: \structurelistuservariable{usertitle}}\par
\blank
\endgraf}
\startxmlsetups xml:name
\xmlsetsetup{\xmldocument}{document|section}{xml:name:*}
\stopxmlsetups
\xmlregistersetup{xml:name}
\startxmlsetups xml:name:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:name:section
\startsection[title=\xmlatt{#1}{title}]
[usertitle=\xmlatt{#1}{title}]
\stopsection
\stopxmlsetups
\starttext
\placelist[section]
\xmlprocessbuffer{xml:name}{doc}{}
\stoptext
[-- Attachment #1.2: Type: text/html, Size: 1809 bytes --]
[-- Attachment #2: xml-one-file-head-toc.tex --]
[-- Type: application/octet-stream, Size: 949 bytes --]
\startbuffer[doc]
<?xml version "1.0"?>
<document>
<section title="First section">
text
</section>
<section title="Second section">
text
</section>
</document>
\stopbuffer
\setuphead[section][expansion=yes]
\setuplist[section][alternative=command,
command=\SectionListCommand]
\define[3]\SectionListCommand{%
{\bf#1\par
title: #2\par
usertitle: \structurelistuservariable{usertitle}}\par
\blank
\endgraf}
\startxmlsetups xml:name
\xmlsetsetup{\xmldocument}{document|section}{xml:name:*}
\stopxmlsetups
\xmlregistersetup{xml:name}
\startxmlsetups xml:name:document
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:name:section
\startsection[title=\xmlatt{#1}{title}]
[usertitle=\xmlatt{#1}{title}]
\stopsection
\stopxmlsetups
\starttext
\placelist[section]
\xmlprocessbuffer{xml:name}{doc}{}
\stoptext
[-- Attachment #3: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2021-01-17 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 20:22 Jano Kula [this message]
2021-01-17 20:27 ` Wolfgang Schuster
2021-01-17 21:08 ` Jano Kula
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=CAPefzZ1t+4mNRreMMvqrY8yegGEFzUnnwY5a7zDD9f+DKv3BnA@mail.gmail.com \
--to=jano.kula@gmail.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).