From: John Culleton <john@wexfordpress.com>
Subject: Sidebars and versals Oh my!
Date: Fri, 24 Dec 2004 11:15:57 -0500 [thread overview]
Message-ID: <200412241115.57398.john@wexfordpress.com> (raw)
Been working my way through the examples in the Columns Manual, the Details
Manual etc. and had some thoughts on additional features.
Versals come in many different flavors, of which the conventional dropped cap
is just one. Even that facility could use a tweak. Conventionally, to provide
a transition from the dropped cap to the normal text, the rest of the first
word, or the next two or three words, or sometimes the entire first line is
put in a small caps typeface. I cobbled up my own macro for this for a
particular book I typeset:
\def\drop#1#2{%
\noindent
{\head #1}
\vskip -20pt
\noindent
\hangindent=1.7em
\hangafter=-2
{\sc #2}
}
But this is not the only type of versal. Sometimes a large capital letter
(perhaps in italics) is centered on the top of the textblock thus:
\def\drop#1#2{\noindent\hglue .4\hsize{\tfd#1}{\sc#2}}
Now there are other variations seen in fine books, such as a dropped initial
cap partly or completely protruding into the left margin, often colored gray.
The first macro above could be modified for a specific case. A general macro
is more challenging.
A matter of continuing interest is the sidebar, which can be placed in the
outer margin, or flush left or right in a paragraph, or partly protruding
into the outer margin. Usually these sidebars will have a gray background and
often have a border. It appears that creating the sidebar separately as a pdf
graphic and then importing and placing it would be the easiest way home.
Context already has mechanisms for flowing or wrapping text around a graphic.
How well the wraparound feature works when more than one short paragraph is
involved I have not tested yet.
In any case I will continue to explore these layout features, and if anything
interesting shows up I will share.
--
John Culleton
Short list of publishing/marketing books:
http://wexfordpress.com/tex/shortlist.pdf
next reply other threads:[~2004-12-24 16:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 16:15 John Culleton [this message]
2004-12-26 20:33 ` h h extern
2004-12-27 11:33 ` Adam Lindsay
2004-12-27 15:10 ` John Culleton
2004-12-27 17:08 ` Adam Lindsay
2004-12-27 17:42 ` John Culleton
2004-12-27 19:15 ` if I only had a frame (was: Re: Sidebars and versals Oh my!) Adam Lindsay
2004-12-27 19:24 ` if I only had a frame Hans Hagen
2004-12-27 19:40 ` Adam Lindsay
2004-12-27 19:46 ` Hans Hagen
2004-12-27 19:25 ` Hans Hagen
2004-12-27 19:29 ` Sidebars and versals Oh my! Hans Hagen
2004-12-27 20:29 ` John Culleton
2004-12-27 20:56 ` Adam Lindsay
2004-12-27 21:19 ` Hans Hagen
2004-12-27 21:31 ` Adam Lindsay
2004-12-29 22:05 ` Tobias Hilbricht
2004-12-30 9:32 ` Hans Hagen
2005-01-03 9:22 ` Tobias Hilbricht
2005-01-03 10:06 ` Hans Hagen
2005-01-03 10:39 ` Tobias Hilbricht
2005-01-03 12:32 ` Hans Hagen
2005-01-03 13:54 ` Tobias Hilbricht
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=200412241115.57398.john@wexfordpress.com \
--to=john@wexfordpress.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).