ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henri Menke <henrimenke@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Bug: \adjustspacing=1 does not disable expansion
Date: Thu, 5 Dec 2019 10:04:19 +1300	[thread overview]
Message-ID: <a42ef879-0836-de84-b71b-f45457f649b5@gmail.com> (raw)

Dear devs,

The \adjustspacing register is described in the LuaTeX manual as
follows:

     When \adjustspacing has value 2, hz optimization will be applied to glyphs and kerns. When
     the value is 3, only glyphs will be treated. A value smaller than 2 disables this feature.

However, setting \adjustspacing=1 will only disable shrink but not
stretch.  Please find a minimal example example, where I have used
exaggerated values for shrink and stretch to emphasize the issue.  It
can be reproduced with both mtxrun --script plain and luatex with
luaotfload.sty.

I have already checked linebreak.c but add_to_widths looks innocuous and
properly checks the adjust_spacing parameter.

Cheers, Henri

---

%\input luaotfload.sty
\directlua{
   fonts.expansions.setups.default.stretch = 2000
   fonts.expansions.setups.default.shrink = 2000
}
\adjustspacing=1
\font\1="file:lmroman10-regular.otf:expansion=default"
\hsize=5em
\1 \input lorem
\bye
___________________________________________________________________________________
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:[~2019-12-04 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-04 21:04 Henri Menke [this message]
2019-12-05  0:34 ` Henri Menke
2019-12-05  0:39   ` Henri Menke
2019-12-05  8:33     ` Hans Hagen

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=a42ef879-0836-de84-b71b-f45457f649b5@gmail.com \
    --to=henrimenke@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).