1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
|
%%%%%%%%%%%%%%%%%% minitoc.bug #40 2004/12/20
There is a list of problems and frequently asked questions about
minitoc.sty. If your version is < 40, please upgrade.
(1) How to avoid a page break near the rules before and after
the minitoc?
> This problem seemed solved since version #8,
> but version #12 adds better fixes.
(2) How about implementing others layouts for the minitoc?
> Suggestions are welcome.
(3) \\ in a contents line makes an error.
> Use \protect\linebreak
(4) If you reorder chapters, havoc follows... minitocs going in wrong
chapters.
> the best way seems to make one run with the mtcoff
> package in place of the minitoc package, then restore
> the minitoc package and re-execute LaTeX three times
> (yes, it is time consuming...). The mtcoff package
> cleans the auxiliary files from spurious commands
> added by minitoc.
> A more radical solution is to delete the files .aux,
> .lof and .lot relative to the document, then re-execute
> LaTeX three times.
(5) Extensions for the names of auxiliary files
> If you have an operating system which tolerates only
> short file name extensions (of 3 characters, like MS-DOS),
> No modification is needed: all is automatic!
> From version #28, the extensions are auto-configured.
> If you insist to use 3 characters extensions, even on
> operating systems allowing more, just use the package
> option `shortext'. Then you will get first the
> auto-configuration messages, then a message saying that
> you will use short extensions.
(6) Playing with the chapter number.
> Do not cheat with the ``chapter'' counter, i.e. do not write
> uglt write things like
> \setcounter{chapter}{6}.
> The mechanism would break. It is better to add \chapter commands,
> to create empty (but numbered in a legal way) chapters.
> Since version #10, minitoc.sty works with appendices.
> Version #19 allows to begin with a chapter other that
> number 1. And look at the section ``Special Entries for
> TOC, LOF, LOT, Bibliography and Index''.
(7) Supported document classes.
> The minitoc package is restricted to document classes which
> define chapters in the standard way, like `book' and `report',
> or sections in the standard way, like `article'.
> There are ``parttocs'' if the document class defines
> the \part command.
(8) Compatibility with LaTeX versions.
> Some users have failed to make minitoc to work. They got
> a message like:
> Undefined command ... \@inputcheck ...
> or:
> Undefined command ... \reset@font ...
> The \reset@font command has been added to latex.tex
> on 29 September 1991 and the \@inputcheck command
> on 18 March 1992 and this version of latex.tex has been
> released on 25 March 1992. If you have this message, you
> have an old version of latex.tex. Get a recent one from
> the archives and regenerate a latex format via initex.
(9) Other mini tables
> Some demanding users want to have minilof, minilot and
> minibbl. First, minibbl is an other problem, strongly
> related to the BibTeX's dealing with .aux files. Look
> at the chapterbib, bibunits, multibib, and bibtopic packages
> (and others, perhaps).
> To make `minilof' (minilot is the same problem), we could apply
> the same method as for minitoc, but we need to add marks
> in the .lof (or .lot) file. It should be possible to do from
> minitoc.sty, but long to test. Version #13 implements basic
> minilofs and minilots. Minibbls are not the aim of this package
> file.
(10) Why so many auxiliary files?
> This package creates a lot of auxiliary files and some users
> have argued that it is too many. A deep redesign would be
> necessary to avoid that. Using only one big auxiliary file
> (or one for all minitocs, one for all minilofs, ...)
> would make the reading of such file very slow, and it must
> be read for each \minixxx macro!
> Moreover, this would make the checkfiles option impractical
> to implement.
> Note that the many files *.mtc*, etc., may be
> deleted after the LaTeX run. They are rebuilt by the
> \dominitoc command (and siblings).
> Moreover, since version #35, empty minitocs (and co.) can
> be automatically detected and skipped. It would not be
> easy to do with one big auxiliary file.
> But, since version #38, minitoc is able to detect and
> skip empty minitoc files (and co.) to avoid ugly titles
> with just two thin rules.
(11) How to do minitocs (minilofs and minilots) at levels other
than chapter?
> Here also, some redesign was needed. From version #15,
> here are parttocs, partlofs and partlots for the part
> level in book-like documents.
(12) Compatibily with LaTeX2.09.
> The more recent version of latex-2e adds a \protect
> command before \contentsline in the .toc, .lof and .lof
> files. Minitoc version #17 attempts to be compatible
> with latex-2e and latex-2.09. This will be the LAST
> version usable with latex-2.09. Versions #18 and later are
> latex-2e specific, and no more compatible with LaTeX2.09,
> which is obsolete.
(13) Documents resetting the chapter number at each part.
> From version #23, works with document classes resetting
> chapter (or section) number at each part.
(14) The minitocs have too much spaced lines.
> From version #29, you can have tight minitocs with the
> tight option.
(15) The secttocs are wrong.
> Secttocs did not work: corrected (#38).
(16) How to remove lines of dots between section titles and page numbers?
> The lines of dots are removed by the undotted option (#29).
(17) How to use the hyperref package with minitoc?
> Since version #31, works with the hyperref package,
> thanks to Heiko Oberdiek (oberdiek@ruf.uni-freiburg.de).
> If one add the loading of the hyperref package to a document
> yet using minitoc, you will get error message about spurious
> closing braces. Just let finish the LaTeX run, then re-LaTeX
> the document. There will be no problem if you remove the
> loading of hyperref and add it again: the problem occurs
> only when upgrading from minitoc #30 to minitoc #31
> (or higher) with a document already processed and adding
> hyperref at the same time! It seems better to process the
> document with minitoc #31 (or higher) without hyperref, then
> with hyperref, because some internal commands written
> into the auxiliary files have been modified. If used, the
> hyperref package must be loaded BEFORE minitoc. Note that
> minitoc.tex shows an example of the use of the hyperref
> package with minitoc.
(18) {Problem while upgrading minitoc.
> If upgrading from version #30 or lower to version #31 or higher,
> you should delete the .aux, .toc, .lof, .lot of the document,
> else the first LaTeX run with version #31 or higher will
> produce a lot of errors (the next run should be ok).
(19) A local table of contents for the set of appendices.
> Some users need a table of contents for the appendices,
> but without putting the entries of it into the main table of
> contents. The solution is to put the appendices in
> a \part subdivision of the document and ask for a table
> of contents at the \part level:
>
> \doparttoc % after \begin{document}
> . . .
> \appendix
> \part{Appendices} % create a part level subdivision
> \parttoc % create a local table of contents
> To suppress the appendix part in the main toc
> \addtocontents{toc}{\protect\setcounter{tocdepth}{-1}}
> \chapter{First appendix}
> . . .
> Add this at the end of appendices if there is something
> after the appendices (like an index or a bibliography)
> to put a bound to the contents of \parttoc:
> \addtocontents{toc}{\protect\partbegin}
(20) Use with the appendix package.
> If you use the appendix package (by Peter R.~Wilson,
> peter.r.wilson@boeing.com), you will observe a serious
> problem with minitocs in the appendices environment (and
> after it): they do not match with their appendix. In fact,
> the environnement opening \begin{appendices} hides a
> \addcontentsline command for a chapter or a section, putting
> trouble in the numbering of minitocs or secttocs. Two solutions
> are available. The first one is to add a \adjustmtc or
> \adjuststc command (depending if the appendices are at the
> chapter or section level) after EACH \begin{appendices} command.
> The other is to add the following commands in the
> preamble after the loading of the appendix package:
> \usepackage[...]{appendix} command:
> \let\oldappendices\appendices
> \def\appendices{\oldappendices\adjustmtc}
> if appendices are at the chapter level, OR:
> \let\oldappendices\appendices
> \def\appendices{\oldappendices\adjuststc}
> if appendices are at the section level.
(21) Use with the tocloft package.
> The tocloft and minitoc packages have an unfortunate interaction,
> discovered by Lyndon Dudding (lyndon.dudding@totalise.co.uk)
> which fortunately can be fixed. In the normal course of events,
> minitoc is used in a chaptered document it will typeset section
> entries in the minitocs in bold font. If tocloft is used in
> conjunction with minitoc, then the minitoc section entries are
> typeset in the normal font, except for the page numbers which are
> in bold font, while the ToC section entries are all in normal font.
>
> One cure, if you want the minitoc section entries to be all in
> normal font is to put:
> \renewcommand{\mtcSfont}{\small\normalfont}
> in the preamble.
>
> Otherwise, the cure is the following incantation:
> \renewcommand{\cftsecfont}{\bfseries}
> \renewcommand{\cftsecleader}{\bfseries\cftdotfill{\cftdotsep}}
> \renewcommand{\cftsecpagefont}{\bfseries}
> To have the section entries in both the ToC and the minitocs
> in bold then put the incantation in the preamble. To have only the
> minitoc section entries in bold while the ToC entries are in the
> normal font, put the incantation between the \tableofcontents
> command and the first \chapter command.
(22) Use with the memoir class.
> The memoir offers the functionnalities of the tocbibind and tocloft
> packages, hence it has the same problems; see upper the available
> solutions.
|
