From: <josephcanedo@gmail.com>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: emergency stretch not taken in account in some cases
Date: Wed, 20 Jul 2016 18:48:48 +0000 [thread overview]
Message-ID: <0bd1b6d687ce472788e10bad6e631694@gmail.com> (raw)
In-Reply-To: <578D53BC.60807@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2522 bytes --]
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.
Thanks a lot,
Joseph Canedo
From: schuster.wolfgang@gmail.com
Sent: Tuesday, July 19, 2016 12:10 AM
To: ntg-context@ntg.nl
josephcanedo@gmail.com
18. Juli 2016 um 23:21
Dear all,
In some cases specifying \setupalign[stretch] does not seem to have any effect with latest betas (live, 2016.06.20 22:14 version are fine, but 2016.07.18 is not), and the output has now overfulls instead of (admitedly a bit large) underfulls.
Attached simple (albeit bit extreme) MWE. Sorry for the relatively large MWE but could not figure out how to make it shorter.
emergency_stretch.pdf produced with latest beta (updated with first-setup.bat today).
emergency_stretch_ok.pdf produced with 2016.06.20 22:14 version.
I can’t reproduce your problem but justified text isn’t the best option in narrow columns.
Below is a simplified version of your code which doesn’t use the parent setting from margindata and marginframed setups, there is also no need to set the alignment twice and marginframed has no method key (the source is wrong).
\definemargindata
[InOuter]
[method=first,
location=outer,
margin=margin,
width=\outermarginwidth,
style=\tf,
stack=continue,
align={normal,hanging,morehyphenation,hz,verytolerant,stretch}]
\definemargindata
[InInner]
[method=first,
location=inner,
margin=margin,
width=\innermarginwidth,
style=\tf,
align=outer]
\definemarginframed[InOuter]
\definemarginframed[InInner]
%\setuplayout[width=12cm,rightmargin=4cm]
\starttext
Foo \InOuter{\input knuth } Bar.
\stoptext
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 5735 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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-07-20 18:48 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 [this message]
2016-07-20 20:46 ` Wolfgang Schuster
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=0bd1b6d687ce472788e10bad6e631694@gmail.com \
--to=josephcanedo@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).