ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing ConTeXt users list for <ntg-context@ntg.nl>
Subject: typesetting xml targets
Date: Fri, 8 Oct 2010 14:46:32 +0200	[thread overview]
Message-ID: <2EBF0358-0D84-4872-9D7E-BD984FED3AB8@uni-bonn.de> (raw)

Hi all,

I'm currently experimenting with the TEI schema for critical editions. There's one thing that goes beyond my minimal understanding: for internal references, the guidelines strongly suggest defining them with the xml:id attribute. Let's take the example of a textual witness, which could be defined as

<witness xml:id="A">manuscript A</witness>

Whenever this witness is referenced, it will be done with a target:

<rdg wit="#A">Hello</rdg>

How can I catch such targets in my ConTeXt setup? Would it be possible to have the #A translated into a macro \WIT:A or something like that? Would it be possible to have ConTeXt read in the value of the <witness> tag to which the taget refers and typset that? There must be something easier than a huge set of nested \doifelse calls, but I can't quite find what would be the best way.

I hope this question isn't too confusing...

Thanks, and best

Thomas
___________________________________________________________________________________
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
___________________________________________________________________________________


             reply	other threads:[~2010-10-08 12:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-08 12:46 Thomas A. Schmitz [this message]
2010-10-08 14:44 ` Hans Hagen

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=2EBF0358-0D84-4872-9D7E-BD984FED3AB8@uni-bonn.de \
    --to=thomas.schmitz@uni-bonn.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).