From: Joseph Canedo <josephcanedo@gmail.com>
To: Hans Hagen <j.hagen@xs4all.nl>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Issues with vertical spacing in simple case
Date: Wed, 18 Jul 2018 22:33:44 +0200 [thread overview]
Message-ID: <5b4fa427.1c69fb81.f14db.41eb@mx.google.com> (raw)
In-Reply-To: <33c6d509-cb3b-eb28-8173-69114558ec95@xs4all.nl>
[-- Attachment #1.1: Type: text/plain, Size: 2001 bytes --]
Thanks Hans.
Picked up today beta and some code I have relying on value of tex.prevgraf starts breaking. This is lettrine related code that sets hangafter for 1st paragraph and eventually subsequent if lettrine is larger than 1st par.
I see the function vspacing.synchronizepage() sets prevgraf value I guess to avoid bleeding also paragraph lines.
Is there any possibility to get original unchanged tex.prevgraf value, possibly using some callback or some other tex.<Something> ?
Thanks
Joseph
De : Hans Hagen
Envoyé le :mercredi 18 juillet 2018 11:11
À : mailing list for ConTeXt users; Joseph Canedo
Objet :Re: [NTG-context] Issues with vertical spacing in simple case
On 7/17/2018 11:35 PM, Joseph Canedo wrote:
> Dear list,
>
> Trying to build a MWE for a problem with unexpected page break (near a
> \blank[line, samepage]) I could not yet reproduce yet, I came up with
> strange output.
>
> With latest beta
>
> mtx-context | current version: 2018.07.17 17:25
>
> MWE :
>
> \starttext
>
> \dorecurse{5}{
>
> \input knuth
>
> \blank[line, samepage]Second.
>
> \input zapf
>
> \blank[line, samepage]Second maybe vertically wrong align?
>
> }
>
> \stoptext
>
> Please see in page 2, the line printing : Second maybe vertically wrong
> align? (topskip related?)
>
> Seems very close to next line for an unknown reason to me.
The next beta will have a fix. The problem is that tex's prevdepth
bleeds over into a next page so i try to deal with that ... it's
sometimes hard to take all into accoutn that needs to (esp when there is
interferences).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
[-- Attachment #1.2: Type: text/html, Size: 5162 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2018-07-18 20:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 21:35 Joseph Canedo
2018-07-17 22:03 ` Hans Hagen
2018-07-18 9:10 ` Hans Hagen
2018-07-18 20:33 ` Joseph Canedo [this message]
2018-07-18 22:00 ` Hans Hagen
2018-07-19 6:55 ` Joseph Canedo
2018-07-19 7:35 ` Hans Hagen
2018-07-19 20:26 ` Joseph Canedo
2018-07-19 20:52 ` Joseph Canedo
2018-07-20 8:51 ` Hans Hagen
2018-07-20 22:01 ` Joseph Canedo
2018-07-26 20:57 ` Joseph Canedo
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=5b4fa427.1c69fb81.f14db.41eb@mx.google.com \
--to=josephcanedo@gmail.com \
--cc=j.hagen@xs4all.nl \
--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).