From: "Richard Gabriel" <rgabriel@kerio.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Problem with XML entities in titles [2]
Date: Fri, 05 Oct 2007 12:06:40 +0200 [thread overview]
Message-ID: <20071005100640.89e191be@mx1.kerio.com> (raw)
In-Reply-To: 47053046.6050506@wxs.nl
[-- Attachment #1.1: Type: text/plain, Size: 1854 bytes --]
Hans,
\xmlsetsetups throws "Undefined control sequence"...
(ConTeXt 2007.09.28)
?!
R.
_____
From: Hans Hagen [mailto:pragma@wxs.nl]
To: mailing list for ConTeXt users [mailto:ntg-context@ntg.nl]
Sent: Thu, 04 Oct 2007 20:26:14 +0200
Subject: Re: [NTG-context] Problem with XML entities in titles [2]
Richard Gabriel wrote:
> Hello once again,
>
> I've puzzled my brain for a while ;-)
> and then I came to the following solution:
>
> \def\ExChapter#1{
> \expanded{\chapter{#1}}
> }
>
> \defineXMLcommand[chapter]{
> \defineXMLargument[title]\ExChapter
> }
in mkiv ... this becomes:
(1) register handler in setup ssection
\xmlsetsetups {main} {chapter} {*}
(2) access child element using lpath
\startxmlsetups chapter
\expanded{\chapter{
\xmlfirst{#1}{title}
}}
\stopxmlsetups
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 2781 bytes --]
[-- Attachment #2: Type: text/plain, Size: 487 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2007-10-05 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 10:06 Richard Gabriel [this message]
2007-10-05 11:53 ` Hans Hagen
2007-10-05 12:03 ` Thomas A. Schmitz
2007-10-05 14:16 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2007-10-05 15:06 Richard Gabriel
2007-10-05 15:55 ` Hans Hagen
2007-10-05 12:47 Richard Gabriel
2007-10-04 14:36 Richard Gabriel
2007-10-04 18:26 ` Hans Hagen
2007-10-04 12:33 Richard Gabriel
2007-10-04 9:32 Richard Gabriel
2007-10-04 10:52 ` Mojca Miklavec
2007-10-04 11:47 ` Wolfgang Schuster
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=20071005100640.89e191be@mx1.kerio.com \
--to=rgabriel@kerio.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).