ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: linguafalsa--- via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: linguafalsa@gmail.com
Subject: Re: [NTG-context] Protect the lettrine
Date: Wed, 14 Jun 2023 13:43:51 -0400	[thread overview]
Message-ID: <nd6wxoruyo7jqvqt6kntkygxlf2nqjg5esctelu5wpm3jkrt7y@jkncda2een3g> (raw)
In-Reply-To: <CAANrE7pTbtiBo77BuvHW1LrLv6tPXf4NVv_UowvWnyXx7iyNMw@mail.gmail.com>

On Tue, Jun 13, 2023 at 08:46:59PM -0700, Thangalin via ntg-context wrote:
> Thank you for taking the time to reply, linguafalsa, I appreciate it.
> 
> The source document is written in Markdown using KeenWrite, my Markdown
> editor. Inserting typesetting instructions into the document would defeat
> the software's architecture, hence being untenable. After the Markdown is
> transformed into XHTML, a specific theme instructs ConTeXt how to typeset
> the XHTML.

Never heard of it (keenwrite), but your request is indeed, valid all along.

I haven't checked the code that lmtx uses but by just looking at the bare
macros, it seems as if `\forgetplaceinitial` is limited in what it can
and can't do. I think it's reasonable the way it was implemented but
nevertheless this is something that ought to be looked at rather than
ignore it or put aside  for later

I didn't see the video, it's distracting, but as I said, is a valid
request on your part 

Perhaps `\setuphead` can have such of a feature in the future — that
of different settings for different chapters, and if one exists now,
I'm just simply unaware of, but either way,  you're dealing mainly
here with a table and tabskips and whatnot. It seems that there's one
feature for subsubsections, written in lua, but this is entirely different

Even with something as the following I just wouldn't know how to specify
it to apply it concurrently for each particular chapter thereafter and
dissuade it from subsequently applying it to where not otherwise. I just
don't know. 


\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


> 
> Here's a video showing how theme selection works:
> 
> https://youtu.be/3QpX70O5S30?list=PLB-WIt1cZYLm1MMx2FBG9KWzPIoWZMKu_&t=14
> 
> I hope this explains the situation more clearly about why changing the code
> between \starttext and \stoptext isn't an option, as you've done with
> introducing and using a macro.
> 
> Greets!

take care Tangalin 

Carlos

> 
> On Tue, Jun 13, 2023 at 7:33 PM linguafalsa--- via ntg-context <
> ntg-context@ntg.nl> wrote:
> 
> > On Tue, Jun 13, 2023 at 02:01:14PM -0700, Thangalin via ntg-context wrote:
> > > Thanks Otared,
> > >
> > > Unfortunately, that's adding content between \starttext and \stoptext,
> > > which isn't tenable in my situation. The user is writing in Markdown,
> > which
> > > is automatically converted to XHTML then passed to ConTeXt, and so the
> > > setups need to account for this scenario without modifying the source
> > > document.
> > >
> >
> > Yeah yeah yeah, tenable. A lot of things aren't tenable. Anyhow,
> > What source document are you talking about here?
> >
> > You're already sourcing the lines after chapter one. As a matter of
> > fact, if you weren't sourcing, then you'd have zilch, nada, zero, empty,
> > null, void, an space, a separation, an abstract
> >
> > Just define Kermit Muffins and it should be good to go
> >
> >
> > \setupinitial[n=2]
> >
> > \def\KermitMuffins{\vbox{Kermit Muffins\par\hskip 1.3cm \tfd Meet me at
> > the second line}}
> >
> > \setuphead[chapter][
> >   after={\placeinitial},
> >   page=no,
> > ]
> >
> > \starttext
> > \chapter{one}
> > \KermitMuffins
> >
> > \chapter{two}
> > \input knuth
> >
> > Meet me at the second line.
> > \stoptext
> >
> >
> >
> > > Cheers!
> > >
> > > On Tue, Jun 13, 2023 at 1:30 AM Otared Kavian via ntg-context <
> > > ntg-context@ntg.nl> wrote:
> > >
> > > > Hi,
> > > >
> > > > Adding \hfill\break to the short line solves the issue, but probably
> > there
> > > > is a better way to achieve the correct result.
> > > >
> > > > \setupinitial[n=2]
> > > >
> > > > \setuphead[chapter][
> > > >   after={\placeinitial},
> > > >   page=no,
> > > > ]
> > > >
> > > > \starttext
> > > > \chapter{one}
> > > > Kermit Ruffins \hfill\break % <---
> > > >
> > > > Meet me at the second line.
> > > >
> > > > \chapter{two}
> > > > \input knuth
> > > >
> > > > Meet me at the second line.
> > > > \stoptext
> > > >
> >
> >
> >
> >
> > > >
> > > > Best regards: Otared
> > > >
> > > > On 13 Jun 2023, at 04:43, Thangalin via ntg-context <
> > ntg-context@ntg.nl>
> > > > wrote:
> > > >
> > > > I'm using KeenWrite Themes (specifically, Boschet) to typeset a chapter
> > > > wherein the first letter is a lettrine. When the first paragraph is too
> > > > short, the second paragraph overlaps the lettrine.
> > > >
> > > > % SOT
> > > > \setupinitial[n=2]
> > > >
> > > > \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
> > > >
> > > > Produces: https://i.stack.imgur.com/kNDqw.png
> > > >
> > > > How would you instruct ConTeXt to "protect" the lettrine such that
> > > > regardless of whether the first paragraph spans multiple lines, a short
> > > > first paragraph will still prevent the second paragraph from
> > overlapping
> > > > the lettrine?
> > > >
> > > > That is, the setups should work in both cases, without any knowledge
> > about
> > > > the first paragraph length being added between \starttext and
> > \stoptext.
> > > >
> > > > ConTeXt LMTX version: 2023.06.04 18:58
> > > >
> > > > Thank you!
> > > >
> > > >
> > ___________________________________________________________________________________
> > > > 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
> > > >
> > > >
> > ___________________________________________________________________________________
> > > >
> > > >
> > > > Otared Kavian
> > > > e-mail: otared@gmail.com <otared@gmail.com>
> > > > Phone: +33 6 88 26 70 95
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > ___________________________________________________________________________________
> > > > 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
> > > >
> > > >
> > ___________________________________________________________________________________
> > > >
> >
> > >
> > ___________________________________________________________________________________
> > > 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
> > >
> > ___________________________________________________________________________________
> >
> >
> > --
> > ... an anecdote from IBM's Yorktown Heights Research Center.  When a
> > programmer used his new computer terminal, all was fine when he was sitting
> > down, but he couldn't log in to the system when he was standing up.  That
> > behavior was 100 percent repeatable: he could always log in when sitting
> > and
> > never when standing.
> >
> > Most of us just sit back and marvel at such a story; how could that
> > terminal
> > know whether the poor guy was sitting or standing?  Good debuggers, though,
> > know that there has to be a reason.  Electrical theories are the easiest to
> > hypothesize: was there a loose wire under the carpet, or problems with
> > static
> > electricity?  But electrical problems are rarely consistently reproducible.
> > An alert IBMer finally noticed that the problem was in the terminal's
> > keyboard: the tops of two keys were switched.  When the programmer was
> > seated
> > he was a touch typist and the problem went unnoticed, but when he stood he
> > was
> > led astray by hunting and pecking.
> >                 -- "Programming Pearls" column, by Jon Bentley in CACM
> > February 1985
> >
> >
> > ___________________________________________________________________________________
> > 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
> >
> > ___________________________________________________________________________________
> >

> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________


-- 
If graphics hackers are so smart, why can't they get the bugs out of
fresh paint?

___________________________________________________________________________________
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 17:44 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 [this message]
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

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=nd6wxoruyo7jqvqt6kntkygxlf2nqjg5esctelu5wpm3jkrt7y@jkncda2een3g \
    --to=ntg-context@ntg.nl \
    --cc=linguafalsa@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).