From: Radhelorn <radhelorn@mail.ru>
Subject: Re: Not possible to redefine inbetween in \definedescription
Date: Fri, 15 Jul 2005 09:13:03 +0400 [thread overview]
Message-ID: <42D745DF.70902@mail.ru> (raw)
In-Reply-To: <42D6A5B8.9030701@creutzig.de>
Christopher Creutzig wrote:
> Radhelorn wrote:
>
>> I mean parameter values. Then why not have ConTeXt add braces to every
>> parameter? Or there will be slowdown Taco mentioned?
>
>
> Exactly. ConTeXt would need to find out the parameters' boundaries
> first, and that is the place where things would become slow, since it is
> not possible to use TeX's built-in parser for that; it just can't handle
> two different types of balanced brackets at the same time. Besides,
> you'd still need to quote commas, since \setupitemize[stopper=,] is just
> as valid as \setupitemize[stopper={,}] is, just with a completely
> different meaning. And while it may be a bit strange, you could even
> set \setupitemize[stopper={, before=abc },after=\blank] – absolutely no
> way of guessing these quotes.
>
>
> regards,
> Christopher
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
Thanks Adam, Christopher, you helped me a lot! It's always hard to
explain TeXnical things to Word users.
--
Radhelorn <radhelorn@mail.ru>
next prev parent reply other threads:[~2005-07-15 5:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 11:43 Radhelorn
2005-07-14 12:45 ` Taco Hoekwater
2005-07-14 13:53 ` Radhelorn
2005-07-14 14:30 ` Taco Hoekwater
2005-07-14 15:08 ` Adam Lindsay
2005-07-14 17:25 ` Radhelorn
2005-07-14 17:27 ` Adam Lindsay
2005-07-14 17:49 ` Christopher Creutzig
2005-07-15 5:13 ` Radhelorn [this message]
2005-07-14 15:01 ` luigi.scarso
2005-07-20 19:58 ` 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=42D745DF.70902@mail.ru \
--to=radhelorn@mail.ru \
--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).