From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: framedtext is (still) broken in LMTX
Date: Mon, 30 Nov 2020 21:05:29 +0100 [thread overview]
Message-ID: <fe5f2be8-88d0-e905-2521-bb8efe6cafc4@gmail.com> (raw)
In-Reply-To: <639fc8d9-2a54-d326-f8de-22e08badd978@rik.users.panix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1219 bytes --]
Rik Kabel schrieb am 30.11.2020 um 18:15:
> On 11/29/2020 17:15, Hans Hagen wrote:
>> On 11/29/2020 10:33 PM, Rik Kabel wrote:
>>> With ConTeXt ver: 2020.11.28 13:18 LMTX fmt: 2020.11.29 the
>>> *\framedtext* output is consistently *0.8\textwidth*. MkiV gives the
>>> expected result.
>>>
>>> \starttext
>>> \framedtext{Fail}\par
>>> \framedtext[width=fit]{Fail}\par
>>> \framedtext[width=3cm]{Fail}\par
>>> \framedtext[width=0.8\textwidth]{Fine by accident}\par
>>> \framedtext[width=\textwidth]{Fail}\par
>>> \framed{Fine}\par
>>> \framed[width=fit]{Fine}\par
>>> \framed[width=3cm]{Fine}\par
>>> \framed[width=0.8\textwidth]{Fine}\par
>>> \framed[width=\textwidth]{Fine}\par
>>> \stoptext
>> fixed in next upload (tomorrow)
>>
>>
>
> Sadly, *\framedtext* still appears to have a problem with the default
> width, although with today's update one can now explicitly set the
> width. (Nothing I can find in the docs suggests that *\framedtext* has
> a different default width than *\framed*. Perhaps I missed it.)
>
There is nothing wrong with framedtext, the command always used a fixed
width as default setting.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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:[~2020-11-30 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 21:33 Rik Kabel
2020-11-29 22:15 ` Hans Hagen
2020-11-30 17:15 ` Rik Kabel
2020-11-30 20:05 ` Wolfgang Schuster [this message]
2020-11-30 21:10 ` Rik Kabel
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=fe5f2be8-88d0-e905-2521-bb8efe6cafc4@gmail.com \
--to=wolfgang.schuster.lists@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).