ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>, ebohoyod <ebohoyod@disroot.org>
Subject: Re: lmtx update
Date: Wed, 16 Sep 2020 18:23:28 +0200	[thread overview]
Message-ID: <1aba28da-d437-60c3-ad1d-20ed312015e4@gmail.com> (raw)
In-Reply-To: <5979915d-274e-2e57-3129-da1255898ff8@disroot.org>

ebohoyod schrieb am 16.09.2020 um 17:52:
> Hi,
> 
> It seems that the Lettrine module is one of those affected:
> 
> https://tex.stackexchange.com/questions/562534/does-context-fail-in-the-lmtx-environment-with-the-lettrine-module?noredirect=1#comment1418902_562534 
> 
> 
> But, honestly, first, I don't know what means "/Of course it might have 
> other side effects once in lmtx we everywhere expect freezing to be 
> enabled./"
> I suppose that, in order not to be a nuisance (and not to digress into 
> this real subject of interest), a short answer would be enough to put me 
> on track to investigate it.
> 
> On the other hand, I suppose the best practice, from what I have just 
> read, would be not to use \forgetparagraphfreezing globaly, but 
> \forgetparagraphfreezing  and \setparagraphfreezing at the beginning and 
> end of the first paragraph respectively of each chapter.  Would this be 
> the least harmful way? That is, wrapping it up to avoid this provisional 
> failure of the Lettrine with LMTX module, but at the same time to avoid 
> affecting that default freezing proposal in the rest of the document, 
> right?
> 
> By the way, and just out of curiosity, how does the recommended 
> provisional command work? Would it be something like this in the preamble?:
> 
> \definingparagraphs
>      firstparagraph][n=1]
>      \setupparagraphs [firstparagraph][1][align={hanging}]
> 
> And then this arrangement in the \input files?:
> 
> \startfirstparagraph
> \lettrine{B}{lah} blah, blah, blah...
> \stopfirstparagraph
> \blank [overlay] \strut
> 
> I know it's a dirty, inelegant solution, but I can't think of a better 
> one at the moment.

Below is a minimal example which doesn't rely on the module,
the problem is caused by the order of the \noindent and \parshape
command.

When a paragraph starts before the \parshape values are set
the arguments are ignored because the values are already frozen
at this moment, when you set the values before the paragraphs
starts ConTeXt applies them.

\starttext

\hsize 10cm

% lettrine module, \noindent before \parshape

\noindent
\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\input weisman

\blank

% working order, \parshape before \noindent

\parshape 3 1cm 9cm 1.5cm 8.5cm 0cm 10cm
\noindent
\input weisman

\stoptext

Wolfgang
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-09-16 16:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16 15:52 ebohoyod
2020-09-16 16:23 ` Wolfgang Schuster [this message]
     [not found]   ` <6f2953c3-4b09-e824-da78-46347ef5f4af@disroot.org>
2020-09-17  8:14     ` Eduardo Bohoyo
2020-09-17 10:35       ` Wolfgang Schuster
2020-09-17 10:50         ` Eduardo Bohoyo
2020-09-17 11:11           ` Eduardo Bohoyo
  -- strict thread matches above, loose matches on Subject: below --
2023-02-06 17:21 Hans Hagen via ntg-context
     [not found] <mailman.0.1629453601.23792.ntg-context@ntg.nl>
2021-08-22 22:55 ` Benjamin Buchmuller via ntg-context
2021-08-23  6:21   ` Hans Hagen via ntg-context
2021-08-19 17:57 Hans Hagen via ntg-context
2021-08-19 20:07 ` Aditya Mahajan via ntg-context
2021-08-20  5:52   ` Hans Hagen via ntg-context
2020-07-31  8:32 Hans Hagen
2020-07-31  8:40 ` Taco Hoekwater
2020-07-31 10:18   ` Hans Hagen
2020-08-01 13:20 ` Otared Kavian
2020-08-01 14:17   ` Hans Hagen
2020-08-01 16:20     ` Otared Kavian
2020-08-01 16:41   ` Henning Hraban Ramm
2020-08-01 16:57     ` Otared Kavian
2020-08-02  3:30 ` Aditya Mahajan
2020-08-03 17:37 ` Pablo Rodriguez

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=1aba28da-d437-60c3-ad1d-20ed312015e4@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=ebohoyod@disroot.org \
    --cc=ntg-context@ntg.nl \
    --cc=taco@elvenkind.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).