ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: morgan.brassel@free.fr
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Indenting (again!): a real problem in indentnext=yes
Date: Thu, 31 Jan 2008 13:48:04 +0100	[thread overview]
Message-ID: <1201783684.47a1c384f127e@imp.free.fr> (raw)
In-Reply-To: <47A1BB69.8090109@elvenkind.com>

Selon Taco Hoekwater <taco@elvenkind.com>:

> morgan.brassel@free.fr wrote:
> >
> > Ok, it's clearer to me now. Then I've got one last question on the subject:
> I
> > didn't manage to have paragraph indented inside an 'enumeration' block, is
> there
> > an option to do that? Thank you for your patience!
>
> It is indeed possible, but the how is not very intuitive:
>
>    \startitemize[command=\indent] % or \setupitemize[each][command...]
>    \item ....
>    \stopitemize
>
> the output looks dreadful to my eyes, and I really doubt this
> will ever become more easily supported.

Sorry, I wasn't precise enough: I would like to indent paragraphs inside a block
created with \defineenumeration (like theorems...), not inside an itemize block.
The output in this latter case is indeed quite awful.

>
> > I still think that it would be great to have one option to indent
> absolutely all
> > paragraphs...
>
> Is 'absolutely all' including the one above? What about float captions?
> And multi-line entries in tables? Or table of contents items? Or synonym
> entries? Footnotes?

By 'absolutely all', I mean just like when you use \setlength{\parindent}{1em}
in LaTeX (plus eventually the indentfirst package for indenting after heads).
Every paragraph (preceded by an empty line or \par) in the "text flow" will get
indented, independently of:
* what is above (formula, float, etc)
* what environment it belongs to (quote, theorem, abstract, etc.), as long as
this environment doesn't need alignment (like itemize, tabular, etc.)

Of course, "particular" objects like captions, tables, footnotes, won't be
concerned by indenting.

I hope my explanations were clear enough... If needed, I can write a small LaTeX
example and send it to the list.

Best regards,
Morgan
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-01-31 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 21:46 morgan.brassel
2008-01-30 22:17 ` Taco Hoekwater
2008-01-30 22:44   ` morgan.brassel
2008-01-30 23:05     ` Taco Hoekwater
2008-01-30 23:32       ` morgan.brassel
2008-01-31  7:55         ` Taco Hoekwater
2008-01-31 11:07           ` morgan.brassel
2008-01-31 12:13             ` Taco Hoekwater
2008-01-31 12:48               ` morgan.brassel [this message]
2008-02-01  8:26                 ` Taco Hoekwater
2008-02-01 13:04                   ` morgan.brassel

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=1201783684.47a1c384f127e@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).