From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Critical editions with ConTeXt
Date: Wed, 22 Jul 2015 22:19:34 +0200 [thread overview]
Message-ID: <55AFFAD6.30704@gmx.es> (raw)
In-Reply-To: <loom.20150722T210228-179@post.gmane.org>
On 07/22/2015 09:26 PM, Talal wrote:
> [...]
> I would like to be able to automate (through macros) the making of a
> critical apparatus' note. This is for two reasons. First, the body text
> and the lemma in the note below should be identical: as such, they
> ideally not have to be typed twice, as it introduces the possibility of
> error. Furthermore, if one manually writes out \linenote{Lemma ]
> Comment} in the body of the text, you forego the separation of content
> and style, since the separator ] has been hardcoded in.
Hi Talal,
I wonder whether creating a new thread should be the right thing to do.
The original thread is three years old.
Anyway, this may help you (it isn’t my original code):
\unexpanded\def\doVariant#1#2#3%
{\startlinenote[#1]{#2] #3}#2\stoplinenote[#1]}
\newcounter\countvariants
\unexpanded\def\variant
{\doglobal\increment\countvariants
\normalexpanded{\doVariant{Varia:\countvariants}}}
\starttext
\startlinenumbering
\dorecurse{20}{\variant{donald e knuth}{herman zapf} }
\stoplinenumbering
\stoptext
BTW, it has a “minor issue”: hyphenation doesn’t work in the body text
It works fine in the notes. I reported this, but I’m afraid it hasn’t
been solved.
Just in case it helps,
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-07-22 20:19 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 [this message]
2015-07-22 21:33 ` talazem
2015-07-23 18:09 ` Pablo Rodriguez
2015-07-24 10:10 ` Hans Hagen
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=55AFFAD6.30704@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).