From: Thangalin via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Thangalin <thangalin@gmail.com>
Subject: Re: [NTG-context] Protect the lettrine
Date: Sun, 25 Jun 2023 18:52:21 -0700 [thread overview]
Message-ID: <CAANrE7pVemdaiUfwr-Vw-X66idea8dE2pv6BGWDvYohQyA=Vjw@mail.gmail.com> (raw)
In-Reply-To: <1d86aeb8-5009-e9e1-18e2-e5e1440b43d3@freedom.nl>
[-- Attachment #1.1: Type: text/plain, Size: 769 bytes --]
Thanks Hans.
I've updated the wiki. I'm wondering if there's a way to also control the
indenting? Max's solution removed any indenting, allowing the text for the
second paragraph to be flush. It looks a little strange to see text
indented next to a drop-cap. The test case is the same, but with the
addition of an indenting setup:
% SOT
\setupinitial[n=2, continue=yes]
\setupindenting[medium, yes]
\setuphead[chapter][
after={\placeinitial},
page=no,
]
\starttext
\chapter{one}
Kermit Ruffins
Meet me at the second line.
\chapter{two}
\input knuth
Meet me at the second line.
\stoptext
% EOT
This produces an unintended side-effect, as well, whereby the following
chapter heading is indented.
See https://i.ibb.co/n8cMkM9/unintended-indented.png
Cheers!
[-- Attachment #1.2: Type: text/html, Size: 1084 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-06-26 1:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 2:43 Thangalin via ntg-context
2023-06-13 8:29 ` Otared Kavian via ntg-context
2023-06-13 21:01 ` Thangalin via ntg-context
2023-06-13 21:11 ` Thangalin via ntg-context
2023-06-14 2:32 ` linguafalsa--- via ntg-context
2023-06-14 3:46 ` Thangalin via ntg-context
2023-06-14 17:43 ` linguafalsa--- via ntg-context
2023-06-14 21:32 ` Thangalin via ntg-context
2023-06-15 6:35 ` Max Chernoff via ntg-context
2023-06-16 18:25 ` Hans Hagen via ntg-context
2023-06-26 1:52 ` Thangalin 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='CAANrE7pVemdaiUfwr-Vw-X66idea8dE2pv6BGWDvYohQyA=Vjw@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=thangalin@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).