From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: FOOTNOTES IN COLUMNS
Date: Fri, 31 May 2013 19:04:34 +0200 [thread overview]
Message-ID: <645B684C-0F36-453A-89BC-307EE0AFD4B9@gmail.com> (raw)
In-Reply-To: <CAPgWwFUc8tLNgMupf+jDc9bWVHZDw4uwpsG4rsoDbH_cgTv0ig@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
Am 31.05.2013 um 18:53 schrieb Manuel González Suárez <manuelteral@gmail.com>:
>
>
> 2013/5/31 Wolfgang Schuster <schuster.wolfgang@gmail.com>
>
> Am 31.05.2013 um 00:51 schrieb MANUEL GONZALEZ SUAREZ <gonzalezsmanuel@uniovi.es>:
>
>> hello
>> I do not know how I can make footnotes covering the entire bottom of the page and not grouped in the first column in a 3 column text. This is the code:
>> \ setupfootnotes [location = page]
>> \ starttext
>> \ startcolumns [n = 3, rule = on]
>> \ input knuth Manolo mine \ footnote {\ input knuth}
>> \ stopcolumns
>> \ stoptext
>> Can you help me? Is this the "normal" behavior?
>
> When I run your example I get three columns for the text but the footnotes
> are placed in a single column which uses the width of the textblock.
>
> Wolfgang
>
> Yes Wolfgang, but that's not the result I want. Footnotes should occupy the entire width of the page and not just the width of a column. I can achieve this??
The textblock is the width of all three columns including the space between the columns, see the attachment for the result I get.
Wolfgang
[-- Attachment #1.2.1: Type: text/html, Size: 3065 bytes --]
[-- Attachment #1.2.2: test.pdf --]
[-- Type: application/pdf, Size: 16984 bytes --]
[-- Attachment #1.2.3: Type: text/html, Size: 207 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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:[~2013-05-31 17:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 22:51 MANUEL GONZALEZ SUAREZ
2013-05-31 6:34 ` Wolfgang Schuster
2013-05-31 16:53 ` Manuel González Suárez
2013-05-31 17:04 ` Wolfgang Schuster [this message]
2013-05-31 17:35 ` Manuel González Suárez
2013-06-01 10:17 ` Pablo Rodríguez
-- strict thread matches above, loose matches on Subject: below --
2021-01-25 21:04 Footnotes in columns Clyde Johnston
2021-03-06 18:18 ` Jano Kula
2021-08-12 13:23 ` Henning Hraban Ramm via ntg-context
2021-08-12 20:01 ` Jano Kula via ntg-context
2021-08-12 22:03 ` Hans Hagen via ntg-context
2021-08-12 22:32 ` Henning Hraban Ramm via ntg-context
2021-08-13 6:43 ` Hans Hagen via ntg-context
2021-08-13 6:54 ` Henning Hraban Ramm via ntg-context
2021-08-13 7:21 ` Hans Hagen via ntg-context
2007-04-16 21:29 Aditya Mahajan
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=645B684C-0F36-453A-89BC-307EE0AFD4B9@gmail.com \
--to=schuster.wolfgang@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).