From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startmode and \ignorespaces
Date: Fri, 14 Oct 2011 11:26:10 +0200 [thread overview]
Message-ID: <201C6347-13D4-47B3-961B-F272A1C5BD75@googlemail.com> (raw)
In-Reply-To: <BC3B3964-18E1-408D-AADB-B18046B82EC0@uva.nl>
Am 14.10.2011 um 10:38 schrieb Meer, H. van der:
> I made an example of the effect of this on \doifmode and \startmode. The example shows that the appearance of extra space in \doifmode follows a regular pattern. The startmode case differs in that respect because \startmode[condition-true] has the extra space but \startmode[condition-false] has not. In my view that is an unwanted anomaly. A little redefinition remedies that as can be seen in the example.
I wrote you already a few times that you can use the annotation module for this. The module serves also as replacement for the fixme module where it is necessary to take care that no extra spaces are added when the text is hidden.
\usemodule[annotation]
\defineannotation[fulltext] [alternative=text]
\defineannotation[shorttext][alternative=none]
\defineannotation[modetext] [alternative=command,command=\ModeText]
\define[2]\ModeText
{\doifelse{\placeannotationtitle}{off}{\removeunwantedspaces}{#2}}
\starttext
abc \fulltext {pqr} xyz
abc \shorttext{pqr} xyz
abc \fulltext [alternative=none]{pqr} xyz
abc \shorttext[alternative=text]{pqr} xyz
\blank
abc \startfulltext pqr \stopfulltext xyz
abc \startshorttext pqr \stopshorttext xyz
abc \startfulltext [alternative=none] pqr \stopfulltext xyz
abc \startshorttext[alternative=text] pqr \stopshorttext xyz
\blank
abc \modetext {pqr} xyz
abc \modetext {on}{pqr} xyz
abc \modetext{off}{pqr} xyz
\blank
abc \startmodetext pqr \stopmodetext xyz
abc \startmodetext{on} pqr \stopmodetext xyz
abc \startmodetext{off} pqr \stopmodetext xyz
\stoptext
Wolfgang
___________________________________________________________________________________
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:[~2011-10-14 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 15:43 Hans van der Meer
2011-10-14 8:38 ` Meer, H. van der
2011-10-14 9:26 ` Wolfgang Schuster [this message]
2011-10-14 10:09 ` Meer, H. van der
2011-10-14 13:21 ` 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=201C6347-13D4-47B3-961B-F272A1C5BD75@googlemail.com \
--to=schuster.wolfgang@googlemail.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).