From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: problem with interaction and TOC
Date: Sun, 22 Mar 2015 11:53:15 +0100 [thread overview]
Message-ID: <550E9F1B.2010202@gmx.es> (raw)
In-Reply-To: <550DFE5C.2030003@wxs.nl>
On 03/22/2015 12:27 AM, Hans Hagen wrote:
> On 3/21/2015 10:49 PM, Pablo Rodriguez wrote:
>> Dear list,
>>
>> I have the following sample:
>>
>> \setupinteraction[state=start]
>> \starttext
>> \placelist[chapter]
>> %~ \uppercasestring{context}\to\ascii
>> %~ \chapter{\getvalue{\ascii}}
>> \chapter{ConTeXt}
>> \stoptext
>>
>> ConTeXt complains about an error in the first line.
>>
>> What am I doing wrong? (Sorry, but I wanted to test the commented lines,
>> but I don’t know why the simplified example doesn’t work.)
>
> \uppercasestring{context}\to\ascii
> \chapter{\meaning\ascii} % \getvalue{\ascii}}
> \chapter{\WORD{ConTeXt}}
>
> so, \ascii is made undefined at some time
Many thanks for your reply, Hans.
I’m afraid that my ignorance prevents me for understanding your reply.
What I was trying to solve was this:
\startbuffer[demo]
<doc>
<h1><span label="context">ConTeXt</a></h1>
<span label="context">ConTeXt</a>
<span label="tex">TeX</a>
<span label="latex">LaTeX</a>
</doc>
\stopbuffer
\setupinteraction[state=start]
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{h1|span}{xml:*}
\xmlsetsetup{#1}{span[@label]}{xml:logo}
\xmlsetsetup{#1}{span[@label='context']}{xml:context}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:h1
\placecontent[criterium=all]
\chapter{\xmlflush{#1}}
\stopxmlsetups
\startxmlsetups xml:logo
\uppercasestring\xmlatt{#1}{label}\xmlatt{#1}{name}\to\ascii
\ifx\ascii\empty\else\getvalue{\ascii}\fi
\stopxmlsetups
\startxmlsetups xml:context
\ConTeXt
\stopxmlsetups
\starttext
\xmlprocessbuffer{main}{demo}{}
\stoptext
xml:logo doesn’t work when it has to be parsed in a heading.
Is there a fix for xml:logo or is xml:context the proper fix?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2015-03-22 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-21 21:49 Pablo Rodriguez
2015-03-21 23:27 ` Hans Hagen
2015-03-22 10:53 ` Pablo Rodriguez [this message]
2015-03-22 11:46 ` Wolfgang Schuster
2015-03-22 12:25 ` Pablo Rodriguez
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=550E9F1B.2010202@gmx.es \
--to=oinos@gmx.es \
--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).