From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Bug in \defineenumeration
Date: Fri, 02 Apr 1999 13:58:13 +0200 [thread overview]
Message-ID: <3704B0D5.66F1E45B@wxs.nl> (raw)
In-Reply-To: <14084.43257.962632.878200@localhost>
Taco Hoekwater wrote:
> Sorry, but it is not OK.
> \doornummeren[definition][tekst=Definition]
> \steldoornummerenin[definition] % some more here
> [plaats=aanelkaar,kopletter=kap,
> paragraafnummer=ja,wijze=perdeel]
>
> \startdefinition
> ....
> \stopdefinition
>
> This tries to evaluate the counter \@@ddDEFINITION@@ddnummer when
> typesetting (as well as \@@ddDEFINITIONlinks etc. etc.).
Indeed. The \uppercase in \kap is the troublemaker. There is no easy way
around this, which is (see source) why \def\kap##1{##1} was there inside
this macro. I forgot to adapt that one to an update. I now simply
disable the kap option, because the proper solution (there are
workarounds possible, but they should work at all levels and thereby
increase the code a lot) is to let eetex provide something \nocase{},
which, when issued inside \uppercase or \lowercase, disables the
conversion.
Suggestion: say [...,tekst=DEFINITION,letter=\tx,...] instead and you
will get what you want: an uppercase label is a smaller typeface.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-04-02 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 13:25 \definehead with some extra's Gilbert van den Dobbelsteen
1999-04-01 14:49 ` Hans Hagen
1999-04-01 16:10 ` Bug in \defineenumeration Taco Hoekwater
1999-04-01 15:41 ` Hans Hagen
1999-04-01 17:46 ` Taco Hoekwater
1999-04-01 16:36 ` Hans Hagen
1999-04-02 11:24 ` Taco Hoekwater
1999-04-02 11:58 ` Hans Hagen [this message]
1999-04-02 12:00 ` Hans Hagen
1999-04-02 13:14 ` 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=3704B0D5.66F1E45B@wxs.nl \
--to=pragma@wxs.nl \
--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).