From: jbf via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: jbf <roma83537@gmail.com>
Subject: \setupparagraphs - can they run over two pages?
Date: Fri, 24 Feb 2023 16:41:49 +1100 [thread overview]
Message-ID: <24401ae8-eac9-ebac-a0e1-a4133701e216@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 777 bytes --]
I have the following setup for side-by-side paras.
\defineparagraphs[Two][n=2]
\setupparagraphs[Two][1][width=.1\textwidth,style=\bfx,align=tolerant]
\setupparagraphs[Two][2][width=.9\textwidth,style=normal,align=tolerant]
My difficulty is that while there is only ever just a couple of numbers
in the left-hand 'column', the right-hand 'column' may have several
lengthy paragraphs. If I have one relatively short \startTwo followed by
one that is much longer, it will be forced to start on the next page,
leaving too much empty space on the previous page.
It is probable that getting this environment to split across pages is
not possible. I can try very different approaches (columns, tables) to
solve my problem, but I thought I would at least ask first.
Julian
[-- Attachment #1.2: Type: text/html, Size: 1348 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
___________________________________________________________________________________
next reply other threads:[~2023-02-24 5:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 5:41 jbf via ntg-context [this message]
2023-02-27 12:16 ` Denis Maier via ntg-context
2023-02-27 12:26 ` mf via ntg-context
2023-02-27 20:28 ` jbf via ntg-context
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=24401ae8-eac9-ebac-a0e1-a4133701e216@gmail.com \
--to=ntg-context@ntg.nl \
--cc=roma83537@gmail.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).