From: Johannes Graumann <johannes_graumann@web.de>
Subject: Re: Synonyms and XML - HOWTO?
Date: Wed, 03 May 2006 16:02:36 -0700 [thread overview]
Message-ID: <e3bcsp$m84$1@sea.gmane.org> (raw)
In-Reply-To: <e36b4g$hb2$1@sea.gmane.org>
Rather than doing this dirtily and on the fly (as implied by the quoted
code, I'd like to use synonyms in a more cleaner fashion: separate calling
and definition.
I have come up with the following code, but have two problems:
1) '<abb key="key" opt="full"/>' just gives me '[key]' after
defining '<abbreviation key="key"><short>shortkey</short><full>slightly
longer key</full></abbreviation>'.
2) The '\XMLop{key}' should really be the result of that preceeded by a '\'
to make the short version callable as a command. How to do that?
Thanks for any help,
Joh
% setup 'synonymes' list called 'abbreviations'
\definesynonyms[abbreviation][abbreviations][\infull]
% give all out in the list
\setupsynonyms[abbreviation][criterium=all]
% <abbreviations/> calls the completelist as a 'chapter'
\defineXMLargument [abbreviations] {\completelistofabbreviations}
% abbreviations are defined as follows
\defineXMLenvironment
[abbreviation]
[key=]
{
\defineXMLsave[short]
\defineXMLsave[full]
}
{\expanded{\abbreviation[\XMLop{key}]{\XMLflush{short}}{\XMLflush{full}}}}
% abbreviations are recalled like this (short version is the default)
\defineXMLargument
[abb]
[key=,opt=short]
{
\doifelse{\XMLop{opt}}{full}
{\expanded{\infull{\XMLop{key}}}}
{\XMLop{key}}
}
Johannes Graumann wrote:
> \definesynonyms[abbreviation][abbreviations][\infull]
>
> \defineXMLargument
> [abbrev]
> [short=,full=]
> {\expanded{\abbreviation{\XMLop{short}}{\XMLop{full}}}}
>
> \defineXMLargument [abbreviations] {\completelistofabbreviations}
>
> \starttext
> \startXMLdata
> <abbreviations/>
> Blabla short<abbrev short="short" full="slightly longer short"/>.
> \stopXMLdata
> \stoptext
prev parent reply other threads:[~2006-05-03 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 1:02 Johannes Graumann
2006-05-03 17:27 ` Mojca Miklavec
2006-05-03 19:15 ` Johannes Graumann
2006-05-03 23:02 ` Johannes Graumann [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='e3bcsp$m84$1@sea.gmane.org' \
--to=johannes_graumann@web.de \
--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).