[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#95147: tetex-extra: Minor error in slidesec style package.



From: brian@debian.org (Brian Mays)
Subject: Bug#95147: tetex-extra: Minor error in slidesec style package. 
Date: Mon, 29 Oct 2001 11:40:43 -0500

> By default, this is not a problem, which is probably why this bug has
> not been noticed before now.  The reason that the \makeslideheading
> and \makeslidesubheading macros are used is to allow the user to
> redefine them and thereby provide a different style for his slides.
> That is, if I redefine \makeslidesubheading to another macro, my new
> definition should be used by the \slide@subheading macro.  Currently,
> it is not, which is why the change is needed.

I see.  Sound reasonable.

But I found seminar package provided seminar.bg2 file which 
would fix the problem you mentioned;

\def\slide@subheading[#1]#2{%
% Modification D.G. begin - Oct. 15, 1997
%  \stepcounter{slidesection}%
  \refstepcounter{slidesubsection}%
% Modification D.G. end
  \addtocontents{los}{\protect\l@subslide
    {\the\c@slidesubsection}{\ignorespaces#1}{\@SCTR}}%
% Modification D.G. begin - May 30, 1997
%  \gdef\theslidesubheading{#1}%
% Modification D.G. end
  \def\@tempa{#2}%
  \ifx\@tempa\@empty\else
    {\edef\@currentlabel{\csname p@slidesubsection\endcsname
% Modification D.G. begin - Jul. 18, 1995
%      \theslidesubsection}\makeslideheading{#2}}%
      \theslidesubsection}\makeslidesubheading{#2}}%
% Modification D.G. end
  \fi
% Modification D.G. begin - May 30, 1997
  \gdef\theslidesubheading{#1}%
% Modification D.G. end
}

It looks like seminar package adds corrections to seminar.bg2
so a user needs to include seminar.bg2.

If this is a policy of seminar package, the problem might be 
said to be fixed already, although I did not know so much
about seminar package.

Best regards,			2001.10.30

-- 
 Debian Developer & Debian JP Developer - much more I18N of Debian
 Atsuhito Kohda <kohda@debian.org>
 Department of Math., Tokushima Univ.



Reply to: