From: "Thomas Floeren" <thomas.floeren@boschung.com>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: mkIV framedcontent not working
Date: Tue, 1 Sep 2009 07:48:02 +0200 [thread overview]
Message-ID: <001e01ca2ac7$c53eb4c0$8614a8c0@boschung.local> (raw)
In-Reply-To: <fe8d59da0908311423q13fc0c3em4dc40e486fbfae@mail.gmail.com>
luigi scarso <mailto:luigi.scarso@gmail.com> wrote on Monday, August 31, 2009 11:24 PM:
> On Mon, Aug 31, 2009 at 11:36 AM, Thomas
> Floeren<thomas.floeren@boschung.com> wrote:
>>
>> Hi,
>>
>> \stopframedcontent gives an undefined control sequence in mkIV. mkII
>> is ok.
>>
>> Any ideas?
>>
> Can you give a short example ?
\defineframedcontent[FrCT]
[offset=.5em]
\starttext
\startframedcontent[FrCT]
Am I framed?
\stopframedcontent
\stoptext
I know that \framed*text* would work in this minimal example, but it does not return the same results as \framedcontent in mkII; and it does not work well with more complicated group content (at least in mkII).
Thomas
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-09-01 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-31 9:36 Thomas Floeren
2009-08-31 21:23 ` luigi scarso
2009-09-01 5:48 ` Thomas Floeren [this message]
2009-09-09 20:38 ` Hans Hagen
2009-09-10 16:47 ` Wolfgang Schuster
2009-09-10 21:29 ` 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='001e01ca2ac7$c53eb4c0$8614a8c0@boschung.local' \
--to=thomas.floeren@boschung.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).