From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: emergency stretch not taken in account in some cases
Date: Wed, 20 Jul 2016 22:46:23 +0200 [thread overview]
Message-ID: <578FE31F.4050505@gmail.com> (raw)
In-Reply-To: <0bd1b6d687ce472788e10bad6e631694@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]
> josephcanedo@gmail.com <mailto:josephcanedo@gmail.com>
> 20. Juli 2016 um 20:48
> I think I could figure out the reason of this problem. Actually
> emergency stretch is broken in all cases it seems. In luatex source
> code I see:
>
> source/texk/web2c/luatexdir/tex/commands.w:
> primitive_tex("emergencystretch",
> assign_dimen_cmd, *dimen_base *+ emergency_stretch_code, dimen_base);
>
> source/texk/web2c/luatexdir/tex/equivalents.h:#define
> emergency_stretch_par
> *glue_par*(emergency_stretch_code)
>
> source/texk/web2c/luatexdir/tex/equivalents.h:# define glue_par(A)
> equiv(*glue_base*+(A))
>
> I could be wrong but to me it seems we assign some value to emergency
> stretch “variable” setting using “emergencystretch” command and we use
> another via emergency_stretch_par.
>
> Unfortunately I am not able to build luatex locally on Windows
> Platform, only sync code from SVN repository.
This produces three different paragraphs.
\setupwhitespace[line]
\starttext
\input tufte
\startalignment[stretch]
\input tufte
\stopalignment
\startalignment[extremestretch]
\input tufte
\stopalignment
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 3374 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-07-20 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 21:21 josephcanedo
2016-07-18 22:10 ` Wolfgang Schuster
2016-07-19 6:59 ` josephcanedo
2016-07-20 18:48 ` josephcanedo
2016-07-20 20:46 ` Wolfgang Schuster [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=578FE31F.4050505@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).