From: Vladimir Lomov <lomov.vl@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: footnote in TABLE
Date: Wed, 19 May 2010 18:21:13 +0900 [thread overview]
Message-ID: <20100519092113.GE11459@smoon2> (raw)
In-Reply-To: <4BF3A46B.4040405@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 1972 bytes --]
Thanks both Wolfgang and Vianney.
** Wolfgang Schuster [2010-05-19 10:42:19 +0200]:
> Am 19.05.10 10:11, schrieb Vladimir Lomov:
>>Hi.
>>Am I right that footnote don't work inside TABLE?
>>Example:
>><example file="footnote_in_TABLE.ctx">
>>\starttext
>>Interaction between footnote and TABLE.
>>\bTABLE
>>\bTR \bTD This is first column \eTD \bTD This is second column\footnote{More convenient way to index as $a_{12}$ --- row and column}\eTD \eTR
>>\bTR \bTD This is second row \eTD \bTD This is cell in second row and second column\eTD \eTR
>>\eTABLE
>>\stoptext
>></example>
>>In table there is a mark (i.e. superscripted 1) but there is no
>>text.
> Write in the table '\postponenotes\footnote{...}' or use
> \automigrateinserts in preamble
> but for floats use localfootnotes.
Both methods work fine (preamble is part of document before \starttext I
guess).
Do I understand it correctly that TABLE is NOT a float?
I played with \{start,stop}locafootnotes, \placelocafootnotes;
\postponenotes; \automigrateinserts and \footnotetext -- \note:
- \postponenotes: works as footnote in text;
(footnoteTABLE3)
- \automigrateinserts: works too but result looks like there are two
columns (word 'column' is hyphenated);
(footnoteTABLE4)
- \{start,stop}localfootnote: this gives a big gap between number and
text in note;
(footnoteTABLE2)
- \footnotetext -- \note: works as footnote in text.
(footnoteTABLE)
>>P.S. I use ctx extension for context (mkiv) files.
> Use *.tex for your files, the ctx-extension for preprocessing files,
> see http://pragma-ade.com/general/manuals/xmanipulate.pdf
OK, I'll change my files and templates.
---
WBW, Vladimir Lomov
--
People often find it easier to be a result of the past than a cause of the
future.
[-- Attachment #2: footnoteTABLE.ctx --]
[-- Type: chemical/x-ctx, Size: 612 bytes --]
[-- Attachment #3: footnoteTABLE2.ctx --]
[-- Type: chemical/x-ctx, Size: 652 bytes --]
[-- Attachment #4: footnoteTABLE3.ctx --]
[-- Type: chemical/x-ctx, Size: 602 bytes --]
[-- Attachment #5: footnoteTABLE4.ctx --]
[-- Type: chemical/x-ctx, Size: 609 bytes --]
[-- Attachment #6: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-05-19 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 8:11 Vladimir Lomov
2010-05-19 8:17 ` Vianney le Clément
2010-05-19 8:42 ` Wolfgang Schuster
2010-05-19 9:21 ` Vladimir Lomov [this message]
2010-05-19 9:31 ` Wolfgang Schuster
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=20100519092113.GE11459@smoon2 \
--to=lomov.vl@gmail.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).