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

Bug#421079: Koma-Script: komafont sectioning messed up (disposition)



Package: texlive-latex-recommended
Version: 2007-4
Severity: normal

\usekomafont{sectioning} produces the word »disposition« instead of the
proper font switch. This can be observed in the example below, but it is
also all over the place in scrguide.pdf, just look at the index.

##################################
\documentclass{scrartcl}

\begin{document}
Like an author in dictum: {\usekomafont{dictumauthor} Author}

Like sectioning in general: {\usekomafont{sectioning} Sectioning}
\end{document}
##################################

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages texlive-latex-recommended depends on:
ii  texlive-common                2007-4     TeX Live: Base component
ii  texlive-latex-base            2007-4     TeX Live: Basic LaTeX packages

Versions of packages texlive-latex-recommended recommends:
ii  latex-beamer             3.06.dfsg.1-0.1 LaTeX class to produce presentatio
ii  latex-xcolor             2.09-1          Easy driver-independent TeX class 
pn  prosper                  <none>          (no description available)

Versions of packages tex-common depends on:
ii  debconf                       1.5.13     Debian configuration management sy
ii  ucf                           2.0021     Update Configuration File: preserv

Versions of packages texlive-latex-recommended is related to:
pn  tetex-base                    <none>     (no description available)
pn  tetex-bin                     <none>     (no description available)
pn  tetex-extra                   <none>     (no description available)

-- debconf information:
  tex-common/check_texmf_wrong:
  tex-common/check_texmf_missing:
  tex-common/singleuser: false



Reply to: