ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: next space (problematic example!)
Date: Sat, 4 Dec 2010 17:16:20 +0100	[thread overview]
Message-ID: <F5079469-6B62-4FB7-8122-CDA28DCB62E1@st.estfiles.de> (raw)
In-Reply-To: <9D7B286B-ABDC-43C1-9C33-2F67CB655DAB@gmail.com>


Am 04.12.2010 um 15:56 schrieb Wolfgang Schuster:

> 
> Am 03.12.2010 um 17:21 schrieb Steffen Wolfrum:
> 
>> But how about this (see below)?
>> Is there a chance to get a space after footnote even before an italic?
> 
> No, \autoinsertnextspace fails when the next token in the input is a command
> which is no criterion to insert a space and you have to help tex in this case
> with a {} or \ after \stopfootnote.


Ok. I'll use {} . Again :o)

(this looks quite save .... hopefully there is no unforeseen side-effect)


Steffen
___________________________________________________________________________________
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-12-04 16:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29  9:29 next space Steffen Wolfrum
2010-11-29 13:39 ` Wolfgang Schuster
2010-12-03 16:21   ` next space (problematic example!) Steffen Wolfrum
2010-12-04 14:12     ` Steffen Wolfrum
2010-12-04 14:56     ` Wolfgang Schuster
2010-12-04 16:16       ` Steffen Wolfrum [this message]

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=F5079469-6B62-4FB7-8122-CDA28DCB62E1@st.estfiles.de \
    --to=context@st.estfiles.de \
    --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).