From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Footnotes lost in description terms
Date: Mon, 08 May 2006 01:28:59 +0200 [thread overview]
Message-ID: <445E82BB.6020206@wxs.nl> (raw)
In-Reply-To: <ops8601oil9niby6@localhost>
nico wrote:
> On Sun, 07 May 2006 19:52:23 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>>> Thanks, it works fine.
>>>
>>> But as a side effect (not introduced by the patch) it seems that
>>> putting
>>> footnotes in a term sets a fixed width to this term: in the example the
>>> term wraps, even if I set width=broad in the description definition. If
>>> the term does not contain a footnote, it is not wrapped.
>>>
>> send me a test file showing both
>
> Here it is. The first and third description terms containing footnotes
> are wrapped. The second term does not contain footnote and is not
> wrapped (it's the file committed in contexttest).
it took me quitea while to find out that it's in the the description
preroll which meant that the calculated width was too small and
therefore the real thing wrapped
\long\def\nododonote#1#2%
{\doifnot{#1}{-}
{\ifconditional\pagewisenotes
\doifreferencefoundelse{\s!fnt:t:\internalfootreference}
{\ifnum\currentrealreference>\lastnotepage\relax
\globallet\lastnotepage\currentrealreference
\resetnumber[\currentnote]%
\fi}
{}%
\fi
\incrementnumber[\currentnote]%
\makesectionnumber[\currentnote]%
\let\lastnotenumber\composedsectionnumber
\dolastnotesymbol
\decrementnumber[\currentnote]}}
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-05-07 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 20:48 nico
2006-05-06 7:51 ` Hans Hagen
2006-05-06 22:37 ` nico
2006-05-07 17:52 ` Hans Hagen
2006-05-07 18:16 ` nico
2006-05-07 23:28 ` Hans Hagen [this message]
2006-05-08 10:52 ` nico
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=445E82BB.6020206@wxs.nl \
--to=pragma@wxs.nl \
--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).