From: morgan.brassel@free.fr
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Need of a new global option for indenting?
Date: Wed, 30 Jan 2008 20:32:02 +0100 [thread overview]
Message-ID: <1201721522.47a0d0b20a7f4@imp.free.fr> (raw)
In-Reply-To: <47A0C7A8.70201@elvenkind.com>
Selon Taco Hoekwater <taco@elvenkind.com>:
> morgan.brassel@free.fr wrote:
> > Hi,
> >
> > Sorry to bother you with this question again, but I didn't get any
> definitive
> > answer in the previous discussion: wouldn't it be useful to have a new
> option in
> > \setupindenting that indents EVERY paragraph? I mean even after floats,
> > formulae, heads, etc.
> >
>
> This is a french typographical tradition thing, isn't it?
Yes, indeed. But it might be useful to non french people too, I think.
>
> > It would be easier than to set every 'indentnext' option to 'yes'. My first
> > thought was that it should be the role of the 'always' option. Is it silly?
>
> In fact there is a common entry point for indentnext already, and
> redefining that woudl do what you want, I believe:
>
> \def\checknextindentation[#1]% original
> {\processaction
> [#1]
> [yes=>\doindentation,
> no=>\noindentation,
> auto=>\autoindentation]}
>
> \def\checknextindentation[#1]{\doindentation} % redefined
Thank you for this trick!
>
> Hooking into \setupindenting may not be the best idea, because of
> backward compatibility. If Hans not feel like adding an extra
> inferface, my next proposal would be to add this redefined command
> to the t-french module on the garden
>
> http://modules.contextgarden.net/t-french
I understand the problem of backward compatibility, and in this regard, it seems
difficult to modify the 'always' option. But what about adding a completely new
option?
As this might be helpful to non french people too, modifying the t-french module
only would be a pity (according to me, of course).
>
> Best wishes,
> Taco
>
___________________________________________________________________________________
> 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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
>
___________________________________________________________________________________
>
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-30 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 18:31 morgan.brassel
2008-01-30 18:53 ` Taco Hoekwater
2008-01-30 19:14 ` Henning Hraban Ramm
2008-01-30 19:32 ` morgan.brassel [this message]
2008-01-30 21:53 ` Henning Hraban Ramm
2008-01-30 22:16 ` Idris Samawi Hamid
2008-01-30 19:14 Henning Hraban Ramm
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=1201721522.47a0d0b20a7f4@imp.free.fr \
--to=morgan.brassel@free.fr \
--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).