ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: (again) bug?: \about disables \setupnote[split=strict]
Date: Thu, 13 Mar 2014 18:12:23 +0100	[thread overview]
Message-ID: <5321E6F7.8060006@gmx.es> (raw)

Dear list,

I have the following sample:

\setuppapersize[A6]
\setupnote[footnote][split=strict]
\starttext
\section[bspaces]{Blank spaces}
\section[paragraph]{Paragraphs}

\dorecurse{11}{This is a sentence.\par}

This is already explained in sections
\about[bspaces] y \about[paragraph].
%~ \namedstructurevariable{section}{title} and
\namedstructurevariable{section}{title}.
\dorecurse{2}{This is a sentence. }.\footnote{\dorecurse{5}
{this is a footnote sentence. }}

This is another sentence.
\stoptext

If I use the lines with \about, footnote reference in body and footnote
are placed in different pages.

If I use \namedstructurevariable, footnote reference in body and
footnote are placed in the same page.

I have two questions:

Could anyone confirm this is a bug in \about?

Is there any way to use \namedstructurevariable for sections other than
the current? (So I would be able to avoid using \about.)

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-03-13 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 17:12 Pablo Rodriguez [this message]
2014-03-16 18:51 ` 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=5321E6F7.8060006@gmx.es \
    --to=oinos@gmx.es \
    --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).