ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, H. van der" <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \startmode and \ignorespaces
Date: Fri, 14 Oct 2011 10:09:38 +0000	[thread overview]
Message-ID: <872E6023-F670-4C0E-86CB-1ED1BC0E3A7E@uva.nl> (raw)
In-Reply-To: <201C6347-13D4-47B3-961B-F272A1C5BD75@googlemail.com>


On 14 okt. 2011, at 11:26, Wolfgang Schuster wrote:

> 
> 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.


Wolfgang,

Thanks for your reply, but I find it takes a sidetrack and does not answer the question. Please let me explain.

It might well be that the annotation module does something of the sort, but that is not my point. The mode-mechanism is explicitely given as a means to do conditional typesetting. If I may cite from the wiki: "Very often, you want to generate multiple versions of the same document: one version for printing and one for viewing on the screen, one version for students and one version for the instructor, and so on. .. Or you could use modes - the ConTeXt way of doing conditional processing" 

Well, that is exactly what I want to do and I fail to see why another module (like annotation) should be necessary. Therefore, please do not keep pointing me to something that in my opinion is not needed in this case and is already fully provided for in ConTeXt.

When I am pointing out something that I think is an anomaly in the behaviour of ConTeXt or probably not intentional, it is not meant as criticizing. To the contrary, my intention is always to make a constructive contribution. Your reply however is not an answer to the question I brought forward. It might be that there are reasons for not changing ConTeXt in the manner I proposed on this issue. I can live with that, because I have no role in the development. But I think it is legitimate to ask why that decision is made. I am certain you will understand this.

Hans van der Meer


___________________________________________________________________________________
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:[~2011-10-14 10:09 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
2011-10-14 10:09     ` Meer, H. van der [this message]
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=872E6023-F670-4C0E-86CB-1ED1BC0E3A7E@uva.nl \
    --to=h.vandermeer@uva.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).