From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: indent lost after \placefigure
Date: Thu, 11 Feb 2010 12:55:01 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1002111238280.20130@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <201002111441.22561.alan.braslau@cea.fr>
On Thu, 11 Feb 2010, Alan BRASLAU wrote:
> PS: Your opinion is not so humble, and I do not really see the rational
> why indentnext=no is the default for most things* rather than indentnext=auto.
Below is my understanding of ConTeXt's design principle (Hans or Taco should
correct me if I am wrong). Content should be separate from presentation. This
means that indentation should be a function of semantics, and not of how you
format your source. So
some text ...
\startitemize
\item
\item
\stopitemize
some more text
and
some text
\startitemize
\item
\item
\stopitemize
some more text ...
should give the same result. If you want an item group that does not start a
paragraph, and an item group that starts a new paragraph, then they are two
different objects and you should define two different environments for them.
\defineitemgroup[spitemize] %single para
[indentnext=no,
before=\blank,
after=\blank]
\defineitemgroup[mpitemize] %multi para
[indentnext=yes,
before={\blank[big]},
after={\blank[big]}]
Then you can use \startspitemize or \startmpitemize dependening on what you
want. The way you format the source does not matter.
Aditya
___________________________________________________________________________________
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:[~2010-02-11 17:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 1:14 Tom
2010-02-11 4:07 ` Wolfgang Schuster
2010-02-11 7:57 ` Alan BRASLAU
2010-02-11 8:00 ` Taco Hoekwater
2010-02-11 12:13 ` Alan BRASLAU
2010-02-11 12:23 ` Peter Münster
2010-02-11 8:07 ` automatic lettrine Alan BRASLAU
2010-02-11 13:41 ` indent lost after \placefigure Alan BRASLAU
2010-02-11 17:55 ` Aditya Mahajan [this message]
2010-02-11 19:01 ` Alan BRASLAU
2010-02-11 19:17 ` Aditya Mahajan
2010-02-11 19:50 ` Tom
2010-02-11 19:59 ` chapter headers (was: indent lost after \placefigure) Wolfgang Schuster
2010-02-11 21:41 ` Tom
2010-02-11 22:09 ` chapter headers Wolfgang Schuster
2010-02-12 0:13 ` Tom
2010-02-11 5:20 indent lost after \placefigure Tom Benjey
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=alpine.LNX.2.01.1002111238280.20130@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).