ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re: Bug in Enumerations
Date: Wed, 28 May 2003 19:02:00 +0200	[thread overview]
Message-ID: <16820812827.20030528190200@iol.it> (raw)
In-Reply-To: <20030528134800.GA2497@prioris.mini.pw.edu.pl>

Wednesday, May 28, 2003 Slawek Zak wrote:

SZ> There is a bug in enumerations' implementation. The following example
SZ> is nearly literally taken from english ConTeXt manual 
SZ> (cont-eni.pdf, p. 224)

SZ> See this example:

SZ>   \defineenumeration[step]  
SZ> [location=left,text={},width=2em]
SZ>   \setupenumerations[step]   [headstyle=bold]
SZ>   \setupenumerations[substep][headstyle=slanted]

SZ>   \starttext
SZ>           \step    One \par
SZ>           \substep Two \par
SZ>   \stoptext

SZ> The headstyle for substep is bold, just like for step, and not slanted
SZ> as stated in the manual.

As a temporary patch, put the following in your cont-loc and
tell me how it works out. If you don't have a cont-loc, put it
in your cont-new.

===============================================================================
\def\special@@definitiewoord#1#2#3#4[#5]#6#7%
  {\strut
   \doifelsevalue{\??dd#1\c!nummer}\v!nee
     \!!doneafalse
     {\doifelse{#5}{-}
        \!!doneafalse
        \!!doneatrue}%
   \chardef\definitiekoppeling\zerocount
   \iflocation
     \doifvaluesomething{\??dd#1\c!koppeling}
       {\processaction % genereert > of <
          [\getvalue{\??dd#1\c!koppelwijze}]
          [ \v!lokaal=>\chardef\definitiekoppeling1, % old: default
           \v!globaal=>\chardef\definitiekoppeling2]}% new: global crosslinking
   \fi
   \stelnummerin % the number is called indirectly
     [\getvalue{\??dd#1\??dd\c!nummer}]
     [\c!sectienummer=\getvalue{\??dd#1\c!sectienummer}]%
   \if!!donea
     \getvalue{\e!volgende#2#1}%
     \iflocation
       \bgroup
       \letvalue{\??dd#1\c!sectienummer}\v!ja
       \protectconversion
       \maakvoorafgaandenummer[\getvalue{\??dd#1\??dd\c!nummer}]%
       \preparethenumber{\??dd#1}\voorafgaandenummer\preparednumber
       \ifcase\definitiekoppeling \or
         \xdef\internaldoornummer{#3{#1}}%
         \rawreference\s!num{#1:\internaldoornummer}{}%
       \or
         \xdef\internaldoornummer{\countervalue{\??dd\c!koppeling#1}}%
         \rawreference\s!num{#1:\internaldoornummer}{}%
       \fi
       \egroup
     \fi
     \maakvoorafgaandenummer[\getvalue{\??dd#1\??dd\c!nummer}]%
     \preparethenumber{\??dd#1}\voorafgaandenummer\preparednumber
     \hbox
       {\let\normalkap\relax % sorry, uppercase causes troubles
        \doattributes        % \nocase primitive needed
          {\??dd#2#1}\c!kopletter\c!kopkleur
          {\getvalue{\??dd#1\c!commando}% hook for taco 
             {\showdntext{#2#1}%
              \domakednnummer{#1}{#2}{#3}}}%
        \iflocation\ifcase\definitiekoppeling \else
          \edef\localconnection{\getvalue{\??dd#1\c!koppeling}:\internaldoornummer}%
          \doifreferencefoundelse\localconnection
            {\in[\localconnection]}{}% genereert > of <
        \fi\fi}%
     \doifnot{#5}{-}{\rawreference\s!num{#5}{#3{#1}}}%
   \else % Why was this strange expansion needed? 
     \hbox
       {\edef\!!stringa{\showdnpuretext{#2#1}}% nog eens testen binnen \expanded
        \expanded{\doattributes{\??dd#1}\noexpand\c!kopletter\noexpand\c!kopkleur
          {\noexpand\getvalue{\??dd#1\c!commando}{\!!stringa}}}%
        \doifnot{#5}{-}{\rawreference\s!num{#5}{}}}%
   \fi}
===============================================================================
FOR HANS: I added a #2 in the \doattributes for kopletter and
kopkleur.

-- 
Giuseppe "Oblomov" Bilotta

  reply	other threads:[~2003-05-28 17:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 13:48 Slawek Zak
2003-05-28 17:02 ` Giuseppe Bilotta [this message]
2003-05-29  8:42   ` Hans Hagen
2003-05-29  9:05   ` Slawek Zak
2003-05-29  9:39     ` Hans Hagen
2003-05-30 17:17       ` Slawek Zak
  -- strict thread matches above, loose matches on Subject: below --
2000-03-03 17:28 Bug in enumerations Zeljko Vrba
2000-03-03 17:44 ` 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=16820812827.20030528190200@iol.it \
    --to=gip.bilotta@iol.it \
    --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).