summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
blob: ba1e45e0f82f739779f490981d5a4f097d509a0c (plain)
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
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
<title>Class novel - 9 - Special Layouts</title>
<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
</head>

<body>
<div id="master">


<div id="toc">

<p>Document class "novel"</p>

<p><a href="#a9">9. Special Layouts</a></p>

<ul>
  <li><a href="#a9.1">9.1 Copyright Page</a>
    <ul>
      <li><a href="#a9.1.1">9.1.1 Useful Commands</a></li>
    </ul>
  </li><!-- end 9.1 -->
  <li><a href="#a9.2">9.2 Epigraph or Dedication</a>
    <ul>
      <li><a href="#a9.2.1">9.2.1 Available Methods</a></li>
      <li><a href="#a9.2.2">9.2.2 Example of Epigraph</a></li>
    </ul>
  </li><!-- end 9.2 -->
  <li><a href="#a9.3">9.3 Table of Contents</a>
    <ul>
      <li><a href="#a9.3.1">9.3.1 Environment: toc</a></li>
      <li><a href="#a9.3.2">9.3.2 \tocitem[]{}{}</a></li>
      <li><a href="#a9.3.3">9.3.3 Example Table of Contents</a></li>
    </ul>
  </li><!-- end 9.3 -->
  <li><a href="#a9.4">9.4 Foreword, Preface, etc.</a></li>
  <li><a href="#a9.5">9.5 New Chapters</a>
    <ul>
      <li><a href="#a9.5.1">9.5.1 Environment: ChapterDisplay</a></li>
      <li><a href="#a9.5.2">9.5.2 Commands for Chapter Titles</a></li>
      <li><a href="#a9.5.3">9.5.3 ChapterDisplay with Image</a></li>
      <li><a href="#a9.5.4">9.5.4 \QuickChapter[]{}</a></li>
    </ul>
  </li><!-- end 9.5 -->
  <li><a href="#a9.6">9.6 Scene Breaks</a>
    <ul>
      <li><a href="#a9.6.1">9.6.1 \scenebreak \sceneline \scenestars</a></li>
      <li><a href="#a9.6.2">9.6.2 \IndentAfterScenebreak</a></li>
    </ul>
  </li><!-- end 9.6 -->
  <li><a href="#a9.7">9.7 Footnotes</a>
    <ul>
      <li><a href="#a9.7.1">9.7.1 \SetMarkers[]{}</a></li>
      <li><a href="#a9.7.2">9.7.2 \realmarker \fakemarker</a></li>
      <li><a href="#a9.7.3">9.7.3 \footnote[]{}</a></li>
    </ul>
  </li><!-- end 9.7 -->
  <li><a href="#a9.8">9.8 Endnotes</a>
    <ul>
      <li><a href="#a9.8.1">9.8.1 \endnote</a></li>
      <li><a href="#a9.8.2">9.8.2 \endnotetext{}{}</a></li>
    </ul>
  </li><!-- end 9.8 -->
</ul>

<p>&nbsp;</p>
</div><!-- end toc -->



<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
<p>Documentation version: 1.0.7.</p>


<div class="pagetopage">
<p><b>User Guide</b></p>
<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br/>
<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
<p>9. Chapters, Display Pages</p>
</div>


<a id="a9"></a>
<h2 style="clear:none">9. Special Layouts</h2>

<p>In this part of the documentation, I will discusss a variety of special layout situations: Copyright Page, Dedication/Epigraph, Table of Contents, Chapter Displays (new chapters), Scenes, Footnotes, and Endnotes. What these have in common is that they are not continuous flowing text, and are not part of the overall layout dimensions.</p>

<p>In many cases, you will need to manually insert a page break using <code>\clearpage</code> or <code>\clearpage</code>. This is not built into the various commands that are used after a page break.</p>

<p>If you need a blank page, here is how:</p>

<p class="code"><code>\clearpage\thispagestyle{empty}\null\clearpage</code></p>

<p>TeX is smart enough to know that if you issue two consecutive <code>\clearpage</code> instructions, without at least a <code>\null</code> command to occupy the blank page, then you did not really intend to skip a page.</p>

<p>It is often the case that display pages provoke an "Underfull \vbox (badness 10000)" message in the log file, due to the break in continuous text flow. In most (probably all) cases, this message may be ignored.</p>

<p>In fiction, the book title page is often very stylish. A good one cannot be constructed by automatically placing information such as title and author. For that reason, <code>novel</code> has no commands such as <code>\maketitle</code>. You will probably want to use stylish fonts, and images, perhaps even using an image for the entire title page. The methods for using new fonts are described on <a href="noveldocs-05-fonts.html#a5.3.3">Page 5</a>. Techniques for images are described on <a href="noveldocs-08-images.html">Page 8</a>.</p>

<p>If your book is self-published, which is normally the case for print-on-demand, remember that <em>you</em> are the publisher, not the service that prints and distributes your book. You cannot use their name or logo in circumstances that might imply that they are the publisher.</p>



<a id="a9.1"></a>
<h3>9.1 Copyright Page</h3>

<p>The copyright page is always the verso of the full title page. In books that begin with a half-title, blank, full title, the copyright page will be lowercase roman numeral <code>iv</code>. If your book begins directly with its full title page (uncommon), then the copyright page will be <code>ii</code>. In al cases, use <code>\thispagestyle{empty}</code> so that no header or footer prints on the copyright page. Thus, the page number will not appear in print (but you can see it in a PDF reader).</p>

<p>In <code>novel</code> there are several commands that are well-suited to the copyright page. But before I discuss them: Since you are using Unicode, just paste the copyright symbol © from a character map. No TeX code required.</p>

<p>&bull; The copyright page should have a different look from pages of the story. This may involve slightly smaller font size, or different margins. It usually involves pushing the text downward so that the unused space is at the top, rather than at the bottom. Your text will usually not be justified, but may be ragged-left, centered, or (very rarely) ragged-right. Words will not be hyphenated. It is <em>not</em> customary to use a different font or font weight. Paragraphs will not usually be indented, but will be separated by blank lines. Small Caps may be used for occasional emphasis.</p>

<p>&bull; If your book has Cataloging-in-Publication data (used by libraries), it may be prepared for you by someone using a word processor. Where you see two hyphens, it is supposed to be an <em>em dash</em>, which is <em>three</em> hyphens in TeX, rather than the two of MS Word.</p>

<p>&bull; Under no circumstances should you use "copyleft" or anything other than full Copyright ©year Your Name, All Rights Reserved. That, plus utter damnation to anyone who violates the copyright. Reason: Why should anyone take the trouble to prepare and distribute your book, even if you are paying for it, when someone else can legally do it cheaper? The demonstration file that comes with this documentation does not have a full copyright, but that is only because it is <em>not a real book.</em></p>

<p>Now for some code:</p>



<a id="a9.1.1"></a>
<h4>9.1.1 Useful Commands for Copyright Page</h4>

<p>These commands are not specific to copyright. They address a number of common situations encountered on that page.</p>

<pre>&nbsp;
<b>\begin{adjustwidth}{<em>left</em>}{<em>right</em>} <em>...</em> \end{adjustwidth}</b></pre>

<p>From the <code>changepage</code> package (included with <code>novel</code>), the <code>adjustwidth</code> environment allows you to increase the left and/or right margins by the indicated lengths. Use units of <code>em</code> or <code>\parindent</code> or <code>\textwidth</code> rather than points or inches. The environment can span pages, although a copyright page is rarely as much as a full page.</p>

<p class="code"><code>\begin{adjustwidth}{0em}{0.2\textwidth}<br/>
Copyright ©2017 Dirk Hardcase. All Rights Reserved.<br/>
... % and many other lines<br/>
\end{adjustwidth}
</code></p>

<p>The above code places its text so that it remains at the usual left margin, but only occupies 80% of the normal textwidth. Remember that the copyright page is always verso (on the left side of the open book).</p>


<pre>&nbsp;
<b>\begin{legalese} <em>...</em> \end{legalese}</b></pre>

<p>Although the <code>legalese</code> environment can be used for any purpose, it is most suited to ... legalese language, such as on a copyright page.</p>

<p>The included text will be set ragged-right, without hyphenation.</p>


<pre>&nbsp;
<b>\begin{center} <em>...</em> \end{center} &nbsp; <em>and</em> &nbsp; {\centering <em>...</em> \par}</b></pre>

<p>When used with a reduced-width textblock (<code>adjustwidth</code>), a centered copyright page can be attractive. I often see it. Something like this, which centers its text at 60% of the textblock width:</p>

<p class="code"><code>
\begin{adjustwidth}{0.2\textwidth}{0.2\textwidth}<br/>
\begin{center}<br/>
Copyright ©2017 Dirk Hardcase. All Rights Reserved.<br/>
... % and many other lines<br/>
\end{center}<br/>
\end{adjustwidth}
</code></p>

<p>The <code>center</code> environment may be used on the copyright page, where deviations from the baseline grid are acceptable. But do not use <code>center</code> in your main text, as there will often be a noticeable disruption of vertical alignment. You may use the <code>{\centering ... \par}</code> command anywhere, but it can only include one paragraph at a time.</p>


<pre>&nbsp;
<b>\begin{parascale}[<em>scale</em>] <em>...</em> \end{parascale}</b></pre>

<p>The <code>parascale</code> environment is described in more detail on <a href="noveldocs-07-text-size-style.html#a7.1.3">Page 7</a>.</p>
<p>If your copyright and related data does not quite fit on one page at normal size, then use <code>parascale</code> to shrink it.</p>


<pre>&nbsp;
<b>\lnum{<em>numbers or other text</em>}</b></pre>

<p>If your main font uses OldStyle numbers (it probably does), you might prefer Lining numbers for the legalese and other data. The <code>\lnum</code> performs the change. Note that the command only affects the appearance of numbers. Letters are unchanged:</p>

<p class="code"><img class="floatright" src="html-resources/lnum.png" width="185" height="32" alt="lnum"/><code>367Ag\lnum{367Ag}367Ag</code></p>


<a id="a9.2"></a>
<h3>9.2 Epigraph or Dedication</h3>

<p>If you use a Dedication, it must go on the recto page immediately following the copyright page, regardless of whether or not your frontmatter has any other content. The only exception is when the book is a critical edition of someone else's work, where the original author's dedication is delayed to near the end of the frontmatter.</p>

<p>Dedications aren't what they used to be. Nowadays, you can use a web site to dedicate your book to some current flame. Then, when you break up, you edit the web site. You next flame doesn't have to see it in print. There is a certain kind of author who likes to make a silly dedication, but I assume anyone using LaTeX is too sophisticated for that.</p>

<p>On the other hand, if you are a combat veteran writing about your adventures, most folks would expect something such as "To Our Armed Forces" on a Dedication page. It's up to you.</p>

<p>If you do not use a Dedication (best bet), then the recto immediately following the copyright page should be a Table of Contents, if your book has one. This is discussed below. If you don't have a Table of Contents, then the recto immediately following the copyright page might be an Introduction or Preface or some other part of frontmatter (but it is unusual to have these if you don't have a T of C).

<p>It is a bad idea to go directly from copyright at verso to the opening of your story at recto, because the page spread is awkward: Legal notice on the left, fiction on the right. If you have nothing else to put between them, consider an Epigraph recto, followed by blank verso.</p>

<p>An Epigraph is a (usually) a short quotation from someone else's work, with brief attribution. A good Epigraph can be very effective. Unlike a dedication, an epigraph may be placed almost anywhere, recto or verso.</p>
<p>Since a quotation from someone else's work is likely to be copyrighted, you cannot just use it. The safest thing to do is to use a work that is definitely out of copyright, such as the Bible or Shakespeare, or another work from long ago. Keep in mind that a recent translation can be copyrighted, even if the original is not.</p>
<p>An Epigraph may be pretentious, or it may be fun. Look online for the purposes served by an Epigraph, and for many examples from famous and not-so-famous literature.</p>
<p>In some genres, the story will refer to some fictional other book, which contains magical spells or an ancient legend. You can put a (fictional) quote from that book as an Epigraph, whether or not the quotation is used in the story.</p>
<p>You can also place a few lines of your own story, as an Epigraph. Perhaps the most famous example in Twentieth-Century fiction is the poem regarding magic rings, used as an Epigraph for Tolkien's novels on the subject.</p>

<p>Dedications and Epigraphs use <code>\thispagestyle{empty}</code>.</p>


<a id="a9.2.1"></a>
<h4>9.2.1 Available Methods for Styling Dedications and Epigraphs</h4>

<p>Command <code>\vspace*{<em>length</em>}</code> (note the asterisk) places vertical space, so that the material is not at the top of the page. The best position is somewhere above the vertical middle, rather then at the exact middle. You may use the <code>parascale</code> environment (see Page <a href="noveldocs-07-text-size-style.html#a7.1.3">7</a>) to change the font size and line skip of included text.</p>

<p style="margin-top:10px"><b>One centered line:</b> Use <code>{\centering <em>...</em> \par}</code> to place a single line of horizontally centered text. If repeated, each line is independently centered.</p>

<p style="margin-top:10px"><b>Justified block text:</b> If your dedication or epigraph is justified text (rather than poetry) you can use the <code>adjustwidth</code> environment, described above. However, unless you have also reduced the font size using <code>parascale</code>, you may find that a small-width justified block does not look nice. It is hard for the layout engine to make good-looking line breaks when the width is narrow. It would be better to use the <code>Epigraph</code> environment, described below, and manually insert line breaks using <code>\\</code>.</p>

<p style="margin-top:10px"><b>Epigraph environment:</b> <code>novel</code> provides the <code>Epigraph</code> environment. Note the capital E:<p>

<p class="code"><code>\begin{Epigraph}[<em>alignment</em>] <em>text, with manual line breaks</em> \end{Epigraph}</code></p>

<p>The optional <em>alignment</em> may be one of <code>l</code>, <code>c</code>, or <code>r</code>, which stand for left, center, right. Default is <code>c</code>. This is the horizontal alignment of the epigraph block <em>as a block</em>, not the alignment of the lines within the epigraph.<p>
<p>Within the epigraph block, alignments <code>l</code> and <code>c</code> produce left-alignment of the lines, with ragged right ends. Alignment <code>r</code> produces right-alignment of the lines, with ragged left ends.</p>
<p>There is no particular width to the Epigraph block. If you write a line that is too long, it will not wrap, but will flow into the page margin. Use <code>\\</code> (not <code>\par</code>) to manually break lines.</p>
<p>Exception: The final line, typically an attribution, should <em>not</em> end in <code>\\</code>. It may be without a closure. But if the final line does not end in punctuation, it may be very slightly to the right of its correct position. In this case, ending the line with <code>\par</code> tweaks it.</p>
<p>In the unlikely event that you need to use the ampersand, be sure to write it as <code>\&amp;</code> rather than as mere <code>&amp;</code>.</p>
<p>There is no provision for horizontal lines, or other styling used by academics.</p>


<a id="a9.2.2"></a>
<h4>9.2.2 Example of Epigraph Environment</h4>

<p>This one will be horizontally centered on its page. For typical text size on 5.5"x8.5" Trim Size, the Epigraph will be slightly above the middle of the page, and occupy about 50% of the textblock width. Note that I subsequently added the black border during image editing; it is not part of the Epigraph.</p>

<p class="code"><code>
\vspace*{10\nbs}% for vertical position<br/>
<img class="floatright" src="html-resources/epigraph.png" width="356" height="120" alt="Epigraph example"/> \begin{Epigraph}[c]<br/>
When sacred swallows sound at dawn,\\<br/>
And eager eagles eye their prey,\\<br/>
Then shall Shan-Sun wreak revenge.\\<br/>
\hfill---Book of Bjorn\par<br/>
\end{Epigraph}
</code></p>

<p>An Epigraph like that tells you something about what to expect in the book. Actually, it tells you to expect about 350 pages of badly-written prose, interspersed with badly-written poetry.</p>
<p>You can do better than that.</p>


<a id="a9.3"></a>
<h3>9.3 Table of Contents</h3>

<p>Do not place a table of contents just because you can. A table of contents is more useful when the story consists of discrete episodes. Or, if the book is a collection of short stories, a table of contents is mandatory. When a story is an "action adventure," in which short chapters move along in rapid succession, a table of contents would be unusual. Chapter titles would likely occupy only a small amount of space, and might not even start new pages.</p>

<p>If you use a Dedication (which must be recto), then the Table of Contents will be on the following recto page. The intermediate verso may be blank, or have an Epigraph, or perhaps something such as a map or other illustration. Neither Dedication nor Epigraph is listed in the Table of Contents.</p>

<p>If you do not use a Dedication, then place the Table of Contents on the recto page immediately following the copyright page. An Epigraph, if any, may be placed later (it may also be on the verso page that faces the start of your story, if it is not intrusive).</p>

<p>The TeX academic document classes, and related packages, have means for automatic construction of a table of contents. They do not work, in the <code>novel</code> class! Don't even think about it. If you want a Table of Contents, you have to design it yourself. Its entries are not automatically generated by the structure of your book. There is a reason for this: In fiction, a table of contents is often stylish. There is no single method that is best for all, and certainly no academic standard that must be met.</p>

<p>But you have not been abandoned. In <code>novel</code>, there is an environment for constructing a Table of Contents, and commands that place the individual entries. These are designed with fiction in mind. You do not have to use them, if you have your own method of designing.</p>

<p>In any case, avoid using any of the table environments that come with TeX or its packages. These do not provide the most attractive presentation for fiction, without a lot of work on your part.</p>


<a id="a9.3.1"></a>
<h4>9.3.1 \begin{toc}[<em>extra entry separation</em>]{<em>extra margins</em>} <em>...</em> \end{toc}</h4>

<p>The <code>toc</code> is not indented, and text within it is not indented.</p>

<p>&bull; The optional argument is a number. It is the portion of normal baselineskip that will be added beneath each <code>\tocitem</code> entry (see next section). Default is <code>0</code>, meaning that there is no extra skip between items, and normal baselineskip is maintained. A value greater than <code>0</code> spreads the entries, which could be attractive if there are only a few chapters and you'd like to use more space on the page. For example, a value of <code>0.25</code> means that a gap of 0.25 normal baselineskip will be added beneath each entry. A small negative value will crowd the lines together, but there is a limit (approximately <code>-0.1</code>) before the lines cannot be squeezed any tighter.</p>

<p>Note that the optional argument only applies to <code>\tocitem</code> entries, not to any other text within the environment.</p>

<p>&bull; The required argument is a length, which will be the amount of extra margin added at left and right of the table (using <code>adjustwidth</code>). A value of <code>0pt</code> allows the table to occupy the full width of the textblock. A value of <code>2em</code> adds 2em to the margin on each side, so that the width of the table is 4em less than the width of the textblock.</p>
<p>Note that it is best to specify horizontal lengths, within the textblock, in units of <code>em</code> or the proportional <code>\parindent</code> or <code>\textwidth</code>.</p>

<p>Typically, the label for the <code>toc</code> will not be as bland as "Table of Contents" or even "Contents." One possibility is to use the book's title (and subtitle, if any). You can add a graphic element or a short remark, if you wish.</p>

<p>In most cases, the table's title should not be placed where the first line of text would normally appear. This is because a fictional table of contents rarely fills the page, so it is more attractive to allow some space at top. Another reason is that if you use the <code>\charscale</code> command to increase the size of the topmost text, it will infringe the top margin, unless you provide at least one line of space above it. The <code>\null</code> command is best for this purpose.</p>

<p>The Table of Contents page has no header, but may include its page number beneath the table. <code>\thispagestyle{footer}</code> or <code>\thispagestyle{dropfoliobeneath}</code> or <code>\thispagestyle{dropfolioinside}</code> are helpful.</p>


<a id="a9.3.2"></a>
<h4>9.3.2 \tocitem[<em>chapter number</em>]{<em>description</em>}{<em>page number</em>} and starred version</h4>

<p>The <code>\tocitem</code> command, and its starred version, are used for individual entries in the TOC environment. Do not use this command for general text that is not linked to a page number.</p>

<p>&bull; The optional argument is the chapter number, at most two digits. The number will be left-aligned, with a period automatically added. Following the period will be the amount of space needed to keep the following description aligned.</p>
<p>If the optional argument is omitted (or empty), then there is no space, and the following description will align to the left of the table.</p>
<p>If the optional argument is the tilde character <code>~</code> then no number or period is printed, but the space is occupied, so that the following description aligns as if you had entered a chapter number.</p>
<p>&bull; The description is usually the chapter title. If it cannot easily fit on one line, then use an additional <code>\tocitem</code>, because the text cannot be wrapped. The following example shows how this can be done.</p>
<p>&bull; Without the asterisk, <code>\tocitem</code> fills the area between the description and the page number with empty space. The starred <code>\tocitem*</code> command fills with a dotted line, and is very attractive.</p>
<p>You may use ordinary style commands, such as <code>\emph{}</code>, in the entries.</p>


<a id="a9.3.3"></a>
<h4>9.3.3 Example of toc</h4>
<p>The use of the <code>toc</code> environment, and the <code>\tocitem</code> commands, are easily understood by looking at an example. The border of the image is where the normal page margins would be (the actual page is larger). The little explanation at top happens to exactly fit the table width, because I tweaked the text and the width until it fit!</p>

<p class="code" style="text-indent:0px; font-size:small"><img class="floatright" style="padding-top:2em" src="html-resources/toc.png" width="316" height="559" alt="TOC example"/>
<code>
\thispagestyle{dropfolioinside}<br/>
\begin{toc}[0.25]{3em}<br/>
\null\null<br/>
{\centering\charscale{1.25}{The Withens Retaliation}\par}<br/>
\null<br/>
In which Lord Withens, fresh from a program in horticulture, unleashes secret desires on the garden.\par<br/>
\null\null<br/>
\tocitem*[1]{The Evil Weeds}{1}<br/>
\tocitem*[2]{A Plan of Attack}{14}<br/>
\tocitem*[3]{Lady Withens Objects}{35}<br/>
\tocitem*[4]{Back-Hoe to the Rescue}{48}<br/>
\tocitem[5]{Invasion of the Dandelions}{}<br/>
\tocitem*[~]{\emph{Interlude}}{63}<br/>
\tocitem*[6]{Army of the Gardeners}{94}<br/>
\tocitem*[7]{Too Much Rain}{113}<br/>
\tocitem*[8]{To Nuke, or Not to Nuke?}{145}<br/>
\tocitem*[9]{Revenge of the Zucchini}{162}<br/>
\tocitem*[10]{Lady Withens Sneezes}{180}<br/>
\tocitem*[11]{The Concrete Lawn}{206}<br/>
\end{toc}<br/>
\null\null<br/>
\BlockImage{gnome.png}<br/>
\clearpage 
</code>
</p>



<a id="a9.4"></a>
<h3>9.4 Foreword, Preface, Introduction, Acknowledgements, Prologue, etc.</h3>

<p>My casual review of online forums indicates that new authors like to tell their life story in a Preface, or perhaps go into a long narrative about what motivated them to write the book. Don't do it. That's what web sites are for. Tell your story there. It's easier to edit, too.</p>

<p>There is a genre of fiction, often seen, in which the story is supposed to be a "lost manuscript" recently discovered by the author, or perhaps unearthed by an archaeologist. Or, it may be an "ancient legend" that has been "translated" by a fictional professor. In such a case, it is customary to put remarks from the author, archaeologist, or professor in frontmatter&mdash;as if they were real&mdash;even though they are just as fictional as the rest of the story.</p>

<p>As a general rule, each section that is distinctively different should begin on a recto page. If your frontmatter has many components, then consider rewriting to avoid excessive blank verso pages. Or, violate the general rule.</p>

<p>Also, as a general rule, the first page of any of these components should have no page header. A footer (or dropfolio) is allowed. The page number will be in lowercase roman numerals.</p>

<p>If the Foreword (Preface, etc.) is extensive, and if the style of your document has headers, then do use headers on the continuing pages. Always use footers, if that is your document style. You will need to take advantage of the <code>novel</code> commands <code>\SetVersoHeadText</code> and <code>\SetRectoHeadText</code> to control what appears in page headers. For example, if your book has an extensive Foreword, it is <em>not</em> customary to write the author's name verso, or the books's title recto. That is because the person writing the Foreword is not necessarily the book's author, and the text of the Foreword is not part of the main story. You might do something like this, for the continuing pages of a Foreword:</p>

<p class="code"><code>
\SetVersoHeadText{\allsmcp{Foreword}}<br/>
\SetRectoHeadText{\allsmcp{Foreword}}
</code></p>

<p>If you do the above, remember to change the head texts after you leave the Foreword. The above commands are not merely local.</p>



<a id="a9.5"></a>
<h3>9.5 New Chapters</h3>

<p>If your novel consists of chapters that begin on their own page, or if your book is a collection of stories, then you should use the <code>ChapterDisplay</code> environment to enclose the block of text (and possibly image) that starts each new chapter.</p>
<p>You may place almost anything you like at the beginning of new chapters, but in reality there are only a limited number of useful things. The <code>novel</code> class has special commands for handling them, especially for the needs of fiction.</p>
<p>If your book is actually a quick succession of many short chapters, then it might be better to treat them as scenes. See the following scene commands.</p>
<p>Also see <a href="noveldocs-06-header-footer.html#a6.1.7">Page 6</a> for the <code>\SetChapterDisplay</code> command, which provides a means to globally set how headers and footers are used on <code>ChapterDisplay</code> pages.</p>


<a id="a9.5.1"></a>
<h4>9.5.1 \begin{<em>ChapterDisplay</em>}[<em>lines</em>] <em>...</em> \end{<em>ChapterDisplay</em>}</h4>

<p>The ChapterDisplay environment reserves a block of space at the top of the textblock. The same space is reserved, no matter how much or how little content you put there. The optional argument set the number of lines displaced by the block. Its default is 10, minimum 4.</p>

<p>If you put a lot of material inside ChapterDisplay, it will not push the story farther down the page. Instead, the material inside the ChapterDisplay will overflow the reserved area, and mingle with the text below. Normally this is very undesirable. However, it might be attractive if your ChapterDisplay contains an image that you wish to dangle underneath the following text.</p>

<p>ChapterDisplay should use one of the header-less <code>\thispagestyle</code> commands. If you choose <code>dropfolioinside</code>, then a blank line will be removed from the top of the display, so that everything on the page moves upward.</p>

<p>If you are using symbolic footnote markers, each <code>ChapterDisplay</code> re-sets the symbols.</p>

<p>You will need to use <code>\clearpage</code> prior to the display.</p>


<a id="a9.5.2"></a>
<h4 style="clear:none">9.5.2 Pre-Styled Chapter Title Commands</h4>

<p>These are intended for use in the <code>ChapterDisplay</code> environment. If you use them anywhere else, then the text line grid will be disturbed.</p>

<p><code>\ChapterTitle{}</code> sets its text using chapterfont. The default is the main font scaled 1.6, with lining numbers.</p>

<p><code>\ChapterSubtitle{}</code> sets its text using subchfont. The default is the main font scaled 1.2, with lining numbers.</p>

<p><code>\ChapterDeco[]{}</code> does not commit to its contents. Typically a decoration will be used, perhaps from decofont. The optional argument is a scale factor to be applied to the required argument. Many horizontal decorations need to be magnified.</p>

<p>Each of these commands may only be used for a single line of contents. If the contents cannot fit on a single line, then you must manually break and issue the command twice. The commands may be used in any order, may be used more than once, or not at all.</p>



<a id="a9.5.3"></a>
<h4>9.5.3 ChapterDisplay With Image</h4>


<p>You can use an image in chapter titles. If you place an image, be sure to use one of the image commands defined by <code>novel</code> on Page 8 of this documentation. Any other method is likely to push the following text off-grid.</p>

<p>Be sure that you are licensed to use the image. Many clipart catalogs "for personal use only," prohibit usage in commercial books. One possible source is <a href="http://openclipart.org" rel="external" target="new">openclipart.org</a> (note the <em>.org</em>).</p>


<p><b>Text Over Image</b></p>

<p><img class="floatright" src="html-resources/ctimg35.png" width="79" height="196" alt="example of chapter title image, text over"/> You may position text over an image. Be aware that overlapping text and graphics may be interpreted as a mistake, by human reviewers. It is best to use black text, or grayscale text that is much darker than the underlying image. Results are uncertain if you try to place light text over a dark image.</p>

<p>Example, where the command <code>\unifrac</code> calls for the font UnifrakturMaguntia.ttf. Note that the font command is <em>outside</em> <code>\charscale</code>:</p>

<p class="code"><code>\begin{ChapterDisplay}<br/>
\BlockImage{sword.png}% centered by default<br/>
{\unifrak\centering\charscale[3,0pt,4\nbs]{35}\par}<br/>
\end{ChapterDisplay}</code></p>


<p style="clear:none;"><b>Text as Part of Image</b></p>

<p>If the text is not ordinary black, or not much darker than the background image, then it is better to include the text as part of the raster image. The reason is that there is no "white ink." Although light text over a dark image will appear correctly in PDF, and print that way on most printers, there are exceptions. If in doubt, ask your print service. In this example, the number is built into the image itself:</p>

<p class="code"><img class="floatright" src="html-resources/smfingerprint8.png" width="86" height="70" alt="example of chapter title image, raster text"/><code>\begin{ChapterDisplay}<br/>
\BlockImage[l]{smfingerprint8.png}<br/>
\end{ChapterDisplay}</code></p>


<a id="a9.5.4"></a>
<h4>9.5.4 \QuickChapter[<em>linelength</em>]{<em>chapter title</em>}</h4>

<p>If your novel is the kind of story that consists of numerous short chapters in rapid succession, then you probably do not wish to begin each chapter on its own page, with a block of whitespace at the top. The <code>\QuickChapter</code> command provides an alternative to <code>ChapterDisplay</code>.</p>

<p>The <code>\QuickChapter</code> command inserts two blank lines. In the gap, the chapter title is left-justified using <code>subchfont</code> (not <code>chapterfont</code>). It is slightly raised from the normal baseline, because this looks better; but the text in the following chapter is on-grid. The start of the chapter will be un-indented.</p>

<p>If the optional <code>linelength</code> is provided, then a dash will be written after the title, at the position and thickness typical of the em dash in <code>subchfont</code>. If <code>linelength</code> is specified in units of length, then that will be the length of the line. But if <code>linelength</code> is an asterisk, then the line will fill to the right margin.</p>

<p>Note that this command is too obstrusive for mere scene changes within a chapter.</p>

<p>Example:</p>

<p class="code"><code>Then he looked at me with a sneer, and barked, ``You better haul your can over to Vinny's joint, before the Boss finds out.''\par<br/>
\QuickChapter[3em]{16. At Vinny's}<br/>
So I took his advice, and hauled my can over to Vinny's. It was everything I had expected, and worse.\par<br/>
The bouncer wasn't the biggest one I'd ever seen, but he was the ugliest. ...</code></p>

<p class="centerimg"><img src="html-resources/quickchapter.png" width="629" height="240" alt="quick chapter"/></p>


<a id="a9.6"></a>
<h3>9.6 Scene Breaks</h3>

<p>There are several commands dedicated to the purpose of scene breaks.</p>

<a id="a9.6.1"></a>
<h4>9.6.1 \scenebreak, \sceneline, \scenestars</h4>

<p>These commands insert a one-line skip. After the skip, the next line will not be indented.</p>
<p>The first command simply leaves the skip blank. The second places a short line centered in the skip. The third places three widely-spaced asterisks, centered in the skip. Like this:</p>
<p class="code" style="font-size:small"><img style="float:right; margin-left:16px;" src="html-resources/scenebreaks.png" width="424" height="222" alt="scene breaks" />
<code>
\noindent It was a dark and stormy night.\par<br/>
Lord Withens, the last of his line, hurried through the gloom.\par<br/>
\scenebreak<br/>
Well, maybe it was not very dark.\par<br/>
But to Lord Withens, it seemed dark enough.\par<br/>
\sceneline<br/>
Actually, it was not all that stormy, either.\par<br/>
But the Withens clan never tolerated drizzle, much less a storm.\par<br/>
\scenestars<br/>
Ah, such ill fortune haunted the Withens!\par<br/>
Novelists of that era had so little to write about, unfortunately.\par
</code></p>

<p style="clear:both">&bull; If you begin the new scene with something such as an enlarged scene number, or a larger than normal letter, then be sure to put the number or letter inside <code>\charscale</code>. This will prevent enlarged characters from spreading the lines apart. And, unless you have a particular style in mind, it is better to use lining numbers instead of old style numbers. Something like this:</p>

<p class="code"><code>\scenebreak<br/>
\charscale[1.2]{\lnum{3.}}— The night was still dark and stormy. ...</code></p>


<a id="a9.6.2"></a>
<h4>9.6.2 \IndentAfterScenebreak</h4>

<p>This global command may only be used in the Preamble.</p>
<p>Normally, text begins without a paragraph indent, at each new scene. This is standard in fiction. If you prefer that each new scene begins indented, use this command. It works with <code>\scenebreak</code>, <code>\sceneline</code>, and <code>\scenestars</code>.</p>




<a id="a9.7"></a>
<h3>9.7 Footnotes</h3>

<p>This document class has <em>limited</em> support for footnotes, because footnotes are hardly ever used in original fiction. Nevertheless, they do appear on occasion.</p>
<p>Footnotes appear at the bottom of the page where they are placed. There is no option to accumulate them to another location. Very long footnotes might straddle pages, but that situation is uncommon in fiction.</p>
<p>If you have a lot of footnotes, consider endnotes instead. Both may be used.</p>


<a id="a9.7.1"></a>
<h4>9.7.1 \SetMarkers[<em>real,fake</em>]{<em>asterisk, dagger, number</em>} </h4>

<p>This command is used only in the Preamble.</p>
<p>A "marker" is a superscript or subscript, however used. Thus, a footnote or endnote is indicated by a marker in the main text (but not in the footnote or endnote itself).</p>
<p>Most book-quality Open Type fonts have markers in style sets (sups, sinf, subs). In professional fonts, the marker glyph weights are adjusted for consisent appearance compared to ordinary glyphs. However, many free fonts do not adjust marker glyph weights, so the markers may appear too small, or too light.</p>
<p>The option <code>real</code> (default) attempts to use the Open Type feature <em>sups</em> for superscripts, and the feature <em>sinf</em> (preferred) or <em>subs</em> (alternate) for subscripts. If the requested feature is not available, then it will be faked, by scaling/raising/lowering ordinary characters from the basefont (lining numerals will be used).</p>
<p>Option <code>fake</code> ignores whether the Open Type features are available, and simply fakes them.</p>
<p>Thus, you may choose whether real or fake markers look better, depending on the font you are using. What looks better in one font may not look better in another.</p>
<p>The required argument applies only to markers created by the <code>\footnote</code> command. It does not apply to endnotes, or to manually placed superscripts and subscripts.</p>
<p><code>asterisk</code> (default) uses symbolic footnote markers. The symbols rotate in order * † ‡ § ** †† ‡‡ §§ until reset.</p>
<p><code>dagger</code> uses symbolic footnote markers, but without asterisks. The symbols rotate in order † ‡ § †† ‡‡ §§ until reset.</p>
<p><code>number</code> uses numerical markers. Due to possible conflict, the log file will have a "Big Bad Warning" if you use a numerical footnote marker in a document that also has endnotes, since endnotes alays have numerical markers.</p>


<a id="a9.7.2"></a>
<h4>9.7.2 \realmarker &nbsp; \fakemarker</h4>

<p>Within the body of the document, you may use <code>\realmarker</code> and <code>\fakemarker</code> to change your preference. The choice remains in effect until you change it again.</p>
<p>The option real/fake applies wherever superscripts or subscripts are used, not just for footnotes or endnotes.</p>


<a id="a9.7.3"></a>
<h4>9.7.3 \footnote[<em>option</em>]{<em>text</em>}</h4>
<p>The <code>\footnote{<em>text</em>}</code> command places a "marker" at the place where the command is written. The included text is written at the bottom of the page, beneath a short line that separates it from the main text. The footnote text is at smaller size and line skip, and has the same marker placed before it. All of this is automatic.</p>
<p>You may, if necessary, apply some style to the footnote text. For example, if you are referring to another work, its title might be in italics.</p>
<p>Normally, no option is used. If you use option <code>0</code> (zero) then no marker will appear in the main text, and the footnote text will appear without a marker. The count of markers is not incremented. This applies whether the markers are numbers or symbols.</p>
<p>&bull; Trick: If you are using footnote numbers, but wish to place a special footnote using a symbol, you can do it manually. For example:</p>
<p class="code"><code>He blinked.*\footnote[0]{* No, he didn't.}</code></p>
<p>&bull; Avoid use of underlining, as it is considered bad style, due to visual distraction.</p>



<a id="a9.8"></a>
<h3>9.8 Endnotes</h3>

<p>Endnotes are sometimes used in fiction, particularly for the kind of novel that pretends to be a lost manuscript, or the translation of an ancient text.  The endnotes, by the fictional discoverer or translator, pretend to be an academic discussion of items in the main story. Unlike footnotes, which show quick points that must be immediately known by the reader during the story, endnotes are often a disguised chapter in themselves.</p>

<p>You may use both footnotes and endnotes, if you wish. However, if endnotes are used, then footnotes must be marked by symbols, rather than by numbers, to avoid confusion. The counts for endnotes and footnotes are independent.</p>


<a id="a9.8.1"></a>
<h4>9.8.1 \endnote</h4>
<p>The <code>\endnote</code> command inserts a superior number in the text. A running count of the numbers is automatically updated.</p>
<p>The endnote numbers run continuously through the text, without reset. If you wish to reset the count (perhaps at new chapters), you have to do it manually, using <code>\ResetEndnote</code>.
<p>When you use <code>\endnote</code> there is no provision for the actual note. If you wish to write a reminder to yourself, about why you put an endnote marker there, use <code>\memo{}</code>. The argument of <code>\memo</code> will not be printed, and will not be remembered for later use.</p>


<a id="a9.8.2"></a>
<h4>9.8.2 \endnotetext{<em>number</em>}{<em>text</em>}</h4>

<p>The <code>\endnotetext</code> command is a simple way of styling endnotes. You do not have to use it, if you have your own method.</p>
<p>The first argument is usually the endnote number. A period and following space will automatically be added, so that the text of the note is block-indented. You may use <code>\emph{<em>number</em>}</code> if you prefer the number to be in italics.</p>
<p>The text must be one paragraph. Be sure to end with <code>\par</code> or equivalent.</p>
<p>If the note needs more than one paragraph, then continue like this, with an empty note number:</p>
<p class="code"><code>\endnotetext{}{\indent <em>text</em>}</code></p>
<p>&bull; In <code>novel</code>, you must create and style the page(s) with endnotes yourself! There is no provision for bibliography, and no provision for any other kind of automated styling. This is because the endnotes, being fictional, are more like the main text than any academic style. Think of the endnotes as just another chapter, but starting with something that identifies them as being endnotes.</p>
<p>&bull; Although <code>novel</code> provides several ways of partitioning backmatter, this is discouraged in fictional works. Normally, endnotes continue as mainmatter, with arabic page numbers.</p>


<p>Example:</p>

<p class="code">
<code>
\endnotetext{9}{Yang Sho-Nuff was the twelfth son of the elder god of the ancient Who-Zit Clan, with power over the forces of rust.\par}<br/>
\endnotetext{}{\indent However, since this was not yet the Iron Age, the terible might of Yang Sho-Nuff was largely unrecognized.\par}<br/>
\endnotetext{10}{As Professor Withens notes in his treatise, \emph{When Sho-Nuff Was Not Enough}, the ceremony of daily human sacrifice had a devastating effect on the tribal population.\par}
</code></p>

<p class="centerimg"><img src="html-resources/endnotetext.png" width="637" height="219" alt="using endnotetext"/></p>



















</div><!-- end main -->

<div id="finish"></div>

</div><!-- end master -->

</body>
</html>