From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: StretchedBox broken in mkiv
Date: Mon, 26 Sep 2011 22:37:04 +0200 [thread overview]
Message-ID: <4E45A9C2-78E6-4782-94C3-10094FAA9E15@googlemail.com> (raw)
In-Reply-To: <CAL-A5LbNQ8Hj__i96Yw9N83SoKdaVm45ARKZPRbZxanZD=rsPg@mail.gmail.com>
Am 26.09.2011 um 19:56 schrieb Michael Guravage:
>
> Several years ago Hans cooked up a fix using \CapStretch that allowed me to stretch words. That early version of \stretchedbox appeared in later ConTeXt versions as \StretchedBox as described in strc-sec.mkii and strc-ren.mkiv. This feature worked in the ConTeXt version dated 2011.07.26, but does not work in my current ConTeXt version dated 2011.09.10. I have attached an example file that works with mkii and with earlier mkiv versions, but not with the current mkiv.
>
> I am curious to know what has changed to break this functionality. Initially, I thought it had to do with \setuphead's definition of 'deeptextcommand', but since there are no difference in the files strc-sec-mkii and strc-ren.mkiv between these two releases, the reason must lie elsewhere. If anyone can explain what has changed, an more importantly how to reinstate it, I would be most grateful.
Use \kerncharacters etc. instead of \stretchednormalcase.
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-09-26 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 17:56 Michael Guravage
2011-09-26 20:37 ` 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=4E45A9C2-78E6-4782-94C3-10094FAA9E15@googlemail.com \
--to=schuster.wolfgang@googlemail.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).