From: Wolfgang Schuster via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Subject: Re: issue with framed texts
Date: Sun, 24 Apr 2022 21:13:04 +0200 [thread overview]
Message-ID: <e38512f7-36b4-4d88-889f-e57289f263f0@gmail.com> (raw)
In-Reply-To: <e18a9529-e29e-0b52-e67b-521431525a1f@gmx.es>
Pablo Rodriguez via ntg-context schrieb am 24.04.2022 um 20:56:
> Dear list,
>
> I have the following sample:
>
> \defineframedtext[backcover]
> \setupframedtext[backcover]
> [frame=off,
> offset=overlay,
> width=\textwidth]
> \starttext
> \startframedtext[backcover]
> \input zapf
> \stopframedtext
> \stoptext
>
> Using current LMTX (2022.04.20 19:18), I’m afraid no format from
> \setupframedtext is applied to the backcover framed text.
>
> Can anyone confirm the issue or explain what I’m doing wrong?
You have to use
\startbackcover
...
\stopbackcover
in your document.
While you can pass a instance to \starframed (e.g.
\startframed[backcover]) the same isn't possible with \startframedtext.
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-04-24 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 18:56 Pablo Rodriguez via ntg-context
2022-04-24 19:13 ` Wolfgang Schuster via ntg-context [this message]
2022-04-25 16:17 ` Pablo Rodriguez via ntg-context
2022-04-25 20:00 ` Wolfgang Schuster via ntg-context
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=e38512f7-36b4-4d88-889f-e57289f263f0@gmail.com \
--to=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).