ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: ConTeXt Mailing List <ntg-context@ntg.nl>
Subject: Re: Footnotes
Date: Mon, 21 Jul 2008 12:39:44 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.1.00.0807211229420.26483@nqv-yncgbc> (raw)
In-Reply-To: <000101c8eb00$a82d5650$f88802f0$@de>

On Mon, 21 Jul 2008, Ulrich Dirr wrote:

> O.k. I could look in the source too, but where did you read
> 'location=normal'?

That is just from knowing how the footnotes work. In ConTeXt footnotes 
consist of two this, a number and the note definition. The note definition 
is defined as a description, location=normal is an option for 
descriptions.

>  Also I don't know what other option are allowed, e.g., in
> \numbercommand or \split. Only the default values are here as I understand.

numbercommand can be any predefined (or one that you define on your 
own) ConTeXt macro. By default, it is \inleft, and hence you see the 
footnotes in the margin. I do not know what split does, but just by seeing 
that by default it is defined to be tolerant, the other options should be
verystrict, strict, tolerant, verytolerant, and they should control how 
the splitting of columns work.

This is the good thing about ConTeXt; key value options are extremently 
consistent, once you know what values a particular key takes for one 
environment, you can guess what it will do for others (well, I could be 
wrong in case of footnotes, but ...)

> Anyway. How can I get that footnotes just flows as a standard paragraph (no
> hanging indentation)?

\setupfootnotedefinition[location=serried, distance=0.5em]

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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2008-07-21 16:39 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-20  7:54 Footnotes Ulrich Dirr
2008-07-20 17:50 ` Footnotes Aditya Mahajan
2008-07-21  7:09   ` Footnotes Ulrich Dirr
2008-07-21 16:39     ` Aditya Mahajan [this message]
2008-07-21 17:25       ` Footnotes Ulrich Dirr
2008-07-21 20:58         ` Footnotes Aditya Mahajan
2008-07-21 11:28   ` How to read sources? (was:) Footnotes Joachim Kreimer-de Fries
2008-07-21 12:01     ` How to read sources? Jörg Hagmann
2008-07-21 12:03       ` Wolfgang Schuster
2008-07-21 12:09         ` Andrea Valle
2008-07-21 12:02     ` How to read sources? (was:) Footnotes Thomas A. Schmitz
2008-07-21 12:13     ` Andrea Valle
2008-07-21 16:59     ` Aditya Mahajan
  -- strict thread matches above, loose matches on Subject: below --
2012-04-24  8:56 footnotes Alan BRASLAU
2012-04-24 12:21 ` footnotes Wolfgang Schuster
2012-04-24 13:26   ` footnotes Alan BRASLAU
2012-04-01 21:03 footnotes Thomas A. Schmitz
2012-04-02 10:26 ` footnotes Steffen Fritzsche
2012-04-02 11:02   ` footnotes Thomas A. Schmitz
2012-04-02 20:40 ` footnotes Wolfgang Schuster
2012-03-12 16:50 Footnotes Willi Egger
2010-12-12 11:09 footnotes Achim Jander
2010-12-12 13:41 ` footnotes Achim Jander
     [not found] <mailman.1.1254823203.32637.ntg-context@ntg.nl>
2009-10-13 17:20 ` footnotes Wolfgang Werners-Lucchini
2009-10-13 17:44   ` footnotes Wolfgang Schuster
2009-10-05 14:53 footnotes Wolfgang Werners-Lucchini
2009-10-06  9:36 ` footnotes Taco Hoekwater
2006-01-29 13:48 footnotes Hans van der Meer
2006-01-30 10:49 ` footnotes Hans Hagen
2006-01-30 14:41   ` footnotes Hans van der Meer
2006-01-30 15:45     ` footnotes Hans Hagen
2003-10-06 15:25 Footnotes Steffen Wolfrum
2003-10-06  9:58 Czech patterns in TeXlive2003 David Antos
2003-10-06 13:40 ` Footnotes Albrecht Kauffmann
2003-10-04 19:02 Footnotes Steffen Wolfrum
2003-09-15 15:54 Footnotes Willi Egger
2003-09-15 16:15 ` Footnotes Pawel Jackowski na Onet
2003-09-15 18:00   ` Footnotes Willi Egger
2003-09-16  5:55     ` Footnotes Pawel Jackowski na Onet
2003-09-16 12:18       ` Footnotes Willi Egger
2003-09-16 19:33         ` Footnotes Pawel Jackowski na Onet
2003-09-19 21:04           ` Footnotes Willi Egger
2003-09-20  5:23             ` Footnotes Pawel Jackowski na Onet
2003-09-20  7:28               ` Footnotes Willi Egger
2003-09-23 17:50                 ` Footnotes Pawel Jackowski na Onet
2003-09-16 17:16     ` Footnotes Hans Hagen
2001-04-04 22:28 Footnotes P. van Kranenburg
2001-04-05  7:40 ` Footnotes Hans Hagen
2001-03-12 17:08 footnotes Hans Hagen
2001-03-17 18:14 ` footnotes Giuseppe Bilotta
2001-03-18 20:41   ` footnotes Hans Hagen
2000-05-09 10:09 footnotes Haseloff, Lutz
2000-04-18  8:41 footnotes Haseloff, Lutz
2000-04-19  1:16 ` footnotes Taco Hoekwater
2000-05-08 20:30 ` footnotes Hans Hagen
1999-11-30  8:10 Footnotes Haseloff, Lutz
1999-11-30 15:08 ` Footnotes 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=alpine.DEB.1.00.0807211229420.26483@nqv-yncgbc \
    --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).