From: Henning Hraban Ramm <hraban@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bugs in beta (footnotes)
Date: Tue, 12 May 2009 19:07:19 +0200 [thread overview]
Message-ID: <6CD8EB8A-D426-4189-A935-F2026AB82F5B@fiee.net> (raw)
In-Reply-To: <D44C4180-4140-4756-8D11-C4A78375F930@fiee.net>
Am 2009-05-10 um 18:44 schrieb Henning Hraban Ramm:
> But it doesn't work, it's always "bytext", i.e. numbering runs
> through from start to end.
> And the marks still don't show up in the text!
>
> (Latest minimals beta, 2009-05-10 18.30 MESZ)
I find this is fixed now (Beta 2009.05.12 17:37). Great, thanks!
Only footnotes in section titles don't work - should they?
\chapter{My chapter\footnote{Note: might be also a section or
subsection}}
Shows the note mark, but eats the footnote text.
I can work around that like so:
\footnotetext[chap]{blah}
\subsection{My chapter\note[chap]}
It works in a minimal example, but in my actual project I get this
error:
! Argument of \dostructurecomponent has an extra }.
<inserted text>
\par
<to be read again>
}
\dostructurecomponent ...ctureparameter \c!title }
}}\endgroup \fi \fi
\fi \g...
\doregisterstructurehead ... \c!command =, #2][#3]
\reportcurrentstructure
\dohandlestructurehead ...ructurehead {#1}{#2}{#3}
\let
\getstructureheadsync...
l.76 \subsection{The European Dream\note[dream]}
I couldn't construct a minimal failing example - any hints?
Greetlings from Lake Constance!
Hraban
---
http://www.fiee.net/texnique/
http://wiki.contextgarden.net
https://www.cacert.org (I'm an assurer)
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-05-12 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 19:58 bugs in beta Thomas A. Schmitz
2009-05-06 20:12 ` Wolfgang Schuster
2009-05-06 20:25 ` Thomas A. Schmitz
2009-05-06 20:33 ` Wolfgang Schuster
2009-05-07 8:31 ` Henning Hraban Ramm
2009-05-07 8:41 ` Thomas A. Schmitz
2009-05-07 10:47 ` Henning Hraban Ramm
2009-05-07 11:31 ` Hans Hagen
2009-05-07 12:44 ` Hans Hagen
2009-05-07 13:11 ` Henning Hraban Ramm
2009-05-07 13:27 ` Hans Hagen
2009-05-07 13:51 ` Alan BRASLAU
2009-05-07 13:56 ` Wolfgang Schuster
2009-05-07 14:21 ` Alan BRASLAU
2009-05-07 11:38 ` Wolfgang Schuster
2009-05-07 13:08 ` Henning Hraban Ramm
2009-05-07 13:28 ` Wolfgang Schuster
2009-05-07 14:32 ` Henning Hraban Ramm
2009-05-07 14:43 ` Wolfgang Schuster
2009-05-07 16:34 ` Hans Hagen
2009-05-07 17:21 ` Henning Hraban Ramm
2009-05-07 18:04 ` Hans Hagen
2009-05-07 20:01 ` Alan BRASLAU
2009-05-07 21:17 ` Hans Hagen
2009-05-07 23:06 ` Yanrui Li
2009-05-07 23:12 ` Yanrui Li
2009-05-08 7:22 ` Hans Hagen
2009-05-08 9:46 ` Yanrui Li
2009-05-08 19:36 ` Alan BRASLAU
2009-05-08 19:42 ` Hans Hagen
2009-05-10 16:44 ` bugs in beta (footnotes) Henning Hraban Ramm
2009-05-12 17:07 ` Henning Hraban Ramm [this message]
2009-05-13 16:00 ` Wolfgang Schuster
2009-05-14 14:08 ` 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=6CD8EB8A-D426-4189-A935-F2026AB82F5B@fiee.net \
--to=hraban@fiee.net \
--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).