From: lynx--- via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: lynx@polarcom.com
Subject: Re: [NTG-context] Two columns of footnotes
Date: Tue, 16 May 2023 12:50:05 -0700 [thread overview]
Message-ID: <ed49697daf607e1eca944e5c37c22dfa@polarcom.com> (raw)
In-Reply-To: <87f83e181746483babde266b30e0563e@unibe.ch>
[-- Attachment #1.1: Type: text/plain, Size: 1820 bytes --]
Denis:
Thanks, that is very helpful starting point which proves that it is
possible!
I have tried the suggestions there, but, so far:
* I cannot adjust the gap ("distance" or "gutter") between the columns
* It seems impossible to turn-on a column-separating ruled line
* It would be useful to have a method for controlling orphan / widow
behaviour (such that a footnote in the left column doesn't spill-over as
just a single line into the 2nd column).
Any comments or ideas?
MG
On 2023-05-16 00:46, Denis Maier via ntg-context wrote:
> Technically it should be possible:
>
> https://wiki.contextgarden.net/Footnotes
>
> (see under footnote formatting).
>
> However, the example is not particularly pretty and the explanatory text states there is a bug.
>
> Don't know if that is the current behavior or if this bug has been fixed.
>
> Best,
>
> Denis
>
> VON: ntg-context <ntg-context-bounces@ntg.nl> IM AUFTRAG VON lynx--- via ntg-context
> GESENDET: Dienstag, 16. Mai 2023 08:37
> AN: ntg-context@ntg.nl
> CC: lynx@polarcom.com
> BETREFF: [NTG-context] Two columns of footnotes
>
> I own a commercially published book that has makes effective use of footnotes that are arranged in two columns on each page. Does anybody know how this can be set up within ConTeXt?
>
> MG
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 4407 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2023-05-16 19:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 6:36 lynx--- via ntg-context
2023-05-16 7:46 ` Denis Maier via ntg-context
2023-05-16 19:43 ` lynx--- via ntg-context
2023-05-16 19:50 ` lynx--- via ntg-context [this message]
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=ed49697daf607e1eca944e5c37c22dfa@polarcom.com \
--to=ntg-context@ntg.nl \
--cc=lynx@polarcom.com \
/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).