ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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: Wed, 14 Jun 2023 14:32:35 -0700	[thread overview]
Message-ID: <CAANrE7qgmMy3tDuSMWtyJZOCAkUVjSTATS21Ak4ieDm2APazBg@mail.gmail.com> (raw)
In-Reply-To: <nd6wxoruyo7jqvqt6kntkygxlf2nqjg5esctelu5wpm3jkrt7y@jkncda2een3g>


[-- Attachment #1.1: Type: text/plain, Size: 1092 bytes --]

It's a tough problem for sure.

I'm wondering if there's a general solution?

That is, a way to tell ConTeXt to "protect the lettrine" regardless of the
source document text? Nothing can be hard-coded because the setups (take a
look at keenwrite themes
https://github.com/DaveJarvis/keenwrite-themes/tree/main/boschet) don't
"know" anything about the source document text.

That's why I stated that nothing between \starttext and \stoptext may
change.

In effect, we don't know if the text is going to be "Kermit Ruffins" or
"Yankee Doodle Dandy" or "We believe these truths to be self-evident." All
we know is that we want the first letter to be a lettrine and the
subsequent paragraph not to overlap the lettrine.

Cheers!


> \setuphead[chapter][
>   after={\placeinitial\vbox to 1cm{\relax {K{\hskip 2pt \lower 5pt
> \hbox{ermit MUffins \vbox to -0.055cm {\hskip -2.8cm \raise 1pt \hbox{meet
> me at the second
> line}}}}}}},
>   page=no,
> %]
>
> \starttext
>
> \startchapter[1]
> \stopchapter
>
> \forgetinitial \par
>
> \startchapter[2]
> \input knuth
> \stopchapter
>
> \stoptext
>
>

[-- Attachment #1.2: Type: text/html, Size: 1652 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
___________________________________________________________________________________

  reply	other threads:[~2023-06-14 21:33 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 [this message]
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

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=CAANrE7qgmMy3tDuSMWtyJZOCAkUVjSTATS21Ak4ieDm2APazBg@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).