ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Critical editions with ConTeXt
Date: Fri, 24 Jul 2015 12:10:57 +0200	[thread overview]
Message-ID: <55B20F31.7080206@wxs.nl> (raw)
In-Reply-To: <E474D500-4C61-4E35-8587-70F19E5AAEB0@fastmail.fm>

On 7/22/2015 11:33 PM, talazem@fastmail.fm wrote:
> Dear Pablo,
>
> Thank you very much for what you proposed — it did work indeed. I tried to achieve the same at some length this afternoon. I think I understand what is going on in the first macro, but wouldn’t have been able to arrive at the  the second one for \variant, or the counter (and still don’t fully understand it). Thanks again.
>
> Hans, Idris, Thomas, and others interested in critical editions: I wonder whether this code — with the user-facing command \variant{#1}{#2} — might be something that could become part of an eventual CritTeXt package.

This is rather specific code and one then ends up with options for 
either or not the ] and so which then makes it more complex. Better is 
to collect such things into a module. If there is enough we can always 
see if some mechanisms are needed.

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2015-07-24 10:10 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18  8:10 MANUEL GONZALEZ SUAREZ
2012-07-18 10:09 ` Thomas A. Schmitz
2012-07-18 18:35   ` Pablo Rodríguez
2012-07-19 10:57     ` MANUEL GONZALEZ SUAREZ
2012-07-20 15:41       ` Thomas A. Schmitz
2012-07-20 16:45         ` Hans Hagen
2012-07-20 17:03           ` Thomas A. Schmitz
2012-07-20 17:33           ` Sietse Brouwer
2012-07-20 18:01             ` Wolfgang Schuster
2012-07-20 18:21               ` Thomas A. Schmitz
2012-07-20 20:41                 ` Hans Hagen
2012-07-22 15:54                   ` Pablo Rodríguez
2012-07-22 18:07                 ` Pablo Rodríguez
2012-07-23 13:42                   ` Thomas A. Schmitz
2015-07-22 19:26           ` Talal
2015-07-22 20:19             ` Pablo Rodriguez
2015-07-22 21:33               ` talazem
2015-07-23 18:09                 ` Pablo Rodriguez
2015-07-24 10:10                 ` Hans Hagen [this message]
2012-07-20 18:10         ` Pablo Rodríguez

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=55B20F31.7080206@wxs.nl \
    --to=pragma@wxs.nl \
    --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).