From: Pavneet Arora <pavneet_arora@waroc.com>
To: ConTeXt Mailing list <ntg-context@ntg.nl>
Subject: Orphans and widows for specific paragraph groups
Date: Thu, 9 Jun 2016 16:18:11 -0400 [thread overview]
Message-ID: <20160609201811.GM39769@lahore> (raw)
I have a couple of questions about preventing orphans for specific
document blocks.
These all relate to a web-based report card application I have written
for a study abroad school client of mine. The ConTeXt file is being
generated and processed out of a PHP Laravel framework app.
I have stripped away most of the details as well as the application
fonts, but the issue that I am facing is related to keeping the course
header (done as a paragraph environment), \hairline, and the teacher's
comment for that course together as a unit.
At a minimum, I would like the three elements as a grouped and pushed to
the following page. Ideally, and this is more for my own learning, I'd
like to be able to have finer control---say the header, \hairline, and a
set number of comment lines would be acceptable at the bottom of a page.
What would be the best practices for this?
advTHANKSance
>>>> MWE
\definefontfamily[mainface][rm][Latin Modern Roman]
\definefontfamily[mainface][ss][Latin Modern Sans]
\definefontfamily[mainface][tt][Latin Modern Typewriter]
\definefontfamily[mainface][mm][Latin Modern Math]
\setupbodyfont[mainface,9pt]
% Set up default paragraph indenting and spacing.
\setupindenting[yes,
medium,
next]
\setupwhitespace[small]
% Set up paragraph environment for subject header.
\defineparagraphs
[subjectpar][
n=2,
before={\blank[2*big]}]
\setupparagraphs
[subjectpar]
[1]
[width=.3\textwidth]
\starttext
\blank[8*big, force]
\dorecurse{10}{
\blank[2*big]
\noindentation
\startsubjectpar
{\ss\tfc ENG4U}
\subjectpar
%% Need to keep the following together as a unit.
{\ss\tfc English (Grade 12)}
\stopsubjectpar
\noindentation
\vskip-2em\hairline
\setupindenting[yes,
medium,
next]
\dorecurse{1}{
\input lorem.tex
}
}
\stoptext
<<<< MWE
--
Pavneet Arora m: +1 (647) 406-6843
Waroc Informatik t: +1 (416) 937-9276
___________________________________________________________________________________
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 reply other threads:[~2016-06-09 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 20:18 Pavneet Arora [this message]
2016-06-17 12:22 ` Pavneet Arora
2016-06-17 14:03 ` Wolfgang Schuster
2016-06-17 20:26 ` 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=20160609201811.GM39769@lahore \
--to=pavneet_arora@waroc.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).