ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: subfootnote
Date: Tue, 5 Oct 2010 15:32:27 +0200	[thread overview]
Message-ID: <CAB291D2-CC04-4346-9185-44452A98E61C@gmail.com> (raw)
In-Reply-To: <201010051441.06873.alan.braslau@cea.fr>


Am 05.10.2010 um 14:41 schrieb Alan BRASLAU:

> On Thursday 30 September 2010 18:53:43 Steffen Wolfrum wrote:
>> 
>> ------- test file:
>> 
>> \starttext
>>  test \footnote{xxxx}
>>  text
>>  test \startfootnote note \stopfootnote
>>  test \startsubfootnote subnote \stopsubfootnote
>>  text
>> \stoptext
> 
> On Thursday 30 September 2010 20:42:39 Wolfgang Schuster wrote:
>> 
>> \definestructureseparatorset [footnote][][]
>> \definestructureconversionset[footnote][number,characters][numbers]
>> \setupenumerations[footnote][numberconversionset=footnote,numberseparatorset=footnote]
> 
> Nice to discover subfootnotes!
> 
> The above example illustrates a *spacing problem* after
> \startfootnote \stopfootnote
> (the spacing after the footnote enumerator differs from \footnote{xxxx})

The \stopfootnote gobbles the next space, to prevent this you can say in mkii \setupnote[footnote][next=\autoinsertnextspace] but the ”next” key is missing in mkiv.

Wolfgang

___________________________________________________________________________________
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:[~2010-10-05 13:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 12:03 subfootnote Steffen Wolfrum
2010-09-30 16:05 ` subfootnote Aditya Mahajan
2010-09-30 16:28 ` subfootnote Wolfgang Schuster
2010-09-30 16:53   ` subfootnote Steffen Wolfrum
2010-09-30 18:06     ` subfootnote Wolfgang Schuster
2010-09-30 18:31       ` subfootnote Steffen Wolfrum
2010-09-30 18:42         ` subfootnote Wolfgang Schuster
2010-09-30 18:57           ` subfootnote Steffen Wolfrum
2010-09-30 20:07             ` subfootnote Hans Hagen
2010-09-30 20:06           ` subfootnote Hans Hagen
2010-10-05 12:41     ` subfootnote Alan BRASLAU
2010-10-05 13:32       ` Wolfgang Schuster [this message]
2010-10-05 14:01         ` subfootnote Steffen Wolfrum
2010-10-07  8:36           ` subfootnote Hans Hagen
2011-02-15 10:24             ` subfootnote Steffen Wolfrum
2010-10-12  9:48         ` \setupnote (was subfootnote) Alan BRASLAU
2010-10-12  9:54           ` Steffen Wolfrum
2010-10-12 10:27             ` Alan BRASLAU
2010-10-12 10:39               ` luigi scarso
2010-10-12 11:09                 ` Yury G. Kudryashov
2010-10-12 11:32                   ` luigi scarso
2010-10-12 14:46                     ` Aditya Mahajan
2010-10-14  9:03                   ` luigi scarso
2010-10-12 11:35           ` Wolfgang Schuster
2010-10-12 14:51             ` Aditya Mahajan
2010-10-12 15:06             ` Alan BRASLAU
2010-10-12 15:18               ` 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=CAB291D2-CC04-4346-9185-44452A98E61C@gmail.com \
    --to=schuster.wolfgang@googlemail.com \
    --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).