From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Probelm with \defineenumeration
Date: Fri, 19 Sep 2003 10:36:32 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030919103404.027b03a0@server-1> (raw)
In-Reply-To: <001801c37e10$8211ffa0$0100a8c0@vademecum>
At 20:13 18/09/2003 +0200, you wrote:
>I have defined an enumeration. After typesetting the enumerated list I get
>on the first line the enumeration text and lost and alone in front of the
>second line the enumeration number.
>
>Is this something I do in a wrong way or is there a bug?
hm, this is due to the fact that the [ ] are not taken into the width
calculations. This problem was introduced some time ago when i made a
slightly more advanced width multiline calculator. In your case it's also
triggered by text=\em which should be textstyle=\em (now an extra space is
added between the text and number)
The next alternative fixes the width calculation.
\def\@@dostartdefinitie#1[#2]#3%
{\getvalue{\??dd#1\c!voor}%
\begingroup
\doadaptleftskip{\getvalue{\??dd#1\c!marge}}%
\showcomposition
\!!widthb\getvalue{\??dd#1\c!afstand}\relax
\ifdim\!!widthb=\zeropoint\relax
\doifvalue{\??dd#1\c!breedte}\v!ruim{\!!widthb=1em}%
\fi
% temp hack, we need to avoid this kind of preprocessing
\setbox\@@definitiebox\hbox % preroll
{\forgetall
\trialtypesettingtrue
\mindermeldingen
\def\\{\crcr}%
\@@definitiewoord{#1}[#2]{#3}%
{\begstrut\getvalue{\??dd#1\c!tekst}\ignorespaces#3\endstrut}}%
% so far
\assignwidth
{\!!widtha}
{\getvalue{\??dd#1\c!breedte}}
{\doifelsevaluenothing{\??dd#1\c!monster}
{% preroll can move here (test first)
\ifhbox\@@definitiebox\unhcopy\else\copy\fi \@@definitiebox}
{\@@definitiewoord{#1}[#2]{#3}%
{\getvalue{\??dd#1\c!tekst}\getvalue{\??dd#1\c!monster}}}}
{\!!widthb}%
\setbox\@@definitiebox\hbox
{\forgetall
\mindermeldingen
\let\\\endgraf
\doifelsevalue{\??dd#1\c!plaats}\v!aanelkaar
{\@@definitiewoord{#1}[#2]{#3}%
{\begstrut\getvalue{\??dd#1\c!tekst}#3\endstrut}}
{\@@definitiewoord{#1}[#2]{#3}%
{\vtop{\hsize\!!widtha\advance\hsize-\!!widthb
\begstrut\getvalue{\??dd#1\c!tekst}\ignorespaces#3\endstrut}}}}%
\doifelsevalue{\??dd#1\c!titeluitlijnen}\v!nee
{\edef\@@leftdefinitieskip {\the\leftskip }%
\edef\@@rightdefinitieskip{\the\rightskip}}
{\ifcase\insidedefinition
\edef\@@leftdefinitieskip {\the\leftskip }%
\edef\@@rightdefinitieskip{\the\rightskip}%
\fi}%
\expanded{\inspringen[\getvalue{\??dd#1\c!inspringen}]}%
\ifcase\insidedefinition % better a system mode
\chardef\insidedefinition\plusone
\or
\chardef\insidedefinition\plustwo
\fi} % now happens elsewhere : \noindent\ignorespaces
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-09-19 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 18:13 Willi Egger
2003-09-19 6:43 ` K.H. Wesseling
2003-09-19 19:15 ` Willi Egger
2003-09-19 8:36 ` Hans Hagen [this message]
2003-09-19 9:43 ` Patrick Gundlach
2003-09-19 10:21 Charles Doherty
2003-09-19 10:43 ` 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=5.2.0.9.1.20030919103404.027b03a0@server-1 \
--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).