From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: stretched title text
Date: Fri, 13 Jan 2006 10:57:05 +0100 [thread overview]
Message-ID: <43C77971.7070907@elvenkind.com> (raw)
In-Reply-To: <32804.213.233.219.56.1137143242.squirrel@webmail.solcon.nl>
M.guravage wrote:
> Hi,
>
> Something has changed in the past couple months that causes my stretched
> title code to fail with the message:
>
> ! You can't use `\end' in internal vertical mode.
> <recently read> \normalend
>
> I've attatched a small example. Has anyone a suggestion how I can adapt my
> code accordingly?
This is due to a change in core-sec.tex, for 2005.11.24.
(the addition of \ifcase\headtimingmode to \doplaceheadtext).
Below is a patched version (see lines marked with %TH), but
I am not completely sure if that doesn't break that
\headtimingmode accidentally.
Cheers, Taco
\unprotect
\def\doplaceheadtext#1#2#3#4%
{\beginheadplacement{#1}%
\ifemptyhead % = needed
\setbox0=\ifvertical\vbox\else\hbox\fi to \zeropoint
{\headnumbercontentfalse
\resetsystemmode\v!sectionnumber
#2}%
\makestrutofbox0
\else % = needed
\setbox0=\ifvertical\vbox\else\hbox\fi % \vhbox
{\headnumbercontentfalse
\resetsystemmode\v!sectionnumber
% less interfering
\ifcase\headtimingmode\or#2\fi
% outerside font determines distance
\dosetfontattribute{\??ko#1}\c!style
% but we don't want color to influence user commands
% todo: get the if-else out of it
\getvalue{\??ko#1\c!command}
{} % no number
{\dostartattributes{\??ko#1}\c!style\c!color\empty
\dostartattributes{\??ko#1}\c!textstyle\c!textcolor\empty
\dontconvertfont
\ifdisplaysectionhead
\setupinterlinespace
\else
\setupspacing
\fi
% \ifcase\headtimingmode#2\fi % can introduce cr
\getvalue{\??ko#1\c!commandbefore}%
\placeheadmargintexts{#1}% binnen #3?
\ifdisplaysectionhead
%TH
%TH \getvalue{\??ko#1\c!textcommand}%
%TH {\setstrut\begstrut\ifcase\headtimingmode\hbox{#2}\fi#3\endstrut}%
\ifcase\headtimingmode\hbox{#2}\fi %TH
\getvalue{\??ko#1\c!textcommand}{\setstrut\begstrut#3\endstrut}%TH
%TH
\xdef\localheadheight {\the\strutht}%
\xdef\localheaddepth {\the\strutdp}%
\xdef\localheadlineheight{\the\lineheight}%
% == \globallet\localheaddepth\strutdepth
\else
\ifcase\headtimingmode#2\fi
\getvalue{\??ko#1\c!textcommand}{#3}%
\fi
\getvalue{\??ko#1\c!commandafter}%
\ifdisplaysectionhead\endgraf\fi
\dostopattributes
\dostopattributes}}%
\fi
\endheadplacement{#1}{#4}}
\protect
next prev parent reply other threads:[~2006-01-13 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 9:07 M.guravage
2006-01-13 9:57 ` Taco Hoekwater [this message]
2006-01-13 10:23 ` 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=43C77971.7070907@elvenkind.com \
--to=taco@elvenkind.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).