summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/lualatex/novel
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2017-03-22 21:56:20 +0000
committerKarl Berry <karl@freefriends.org>2017-03-22 21:56:20 +0000
commitae46a827762636210d21328b3c5a75b826924a1e (patch)
tree3ca985adeeb78ff035c139f928e8a442cbabb80b /Master/texmf-dist/doc/lualatex/novel
parent9be209067b3b2ae9f128567279fffa136f353e7a (diff)
novel (22mar17)
git-svn-id: svn://tug.org/texlive/trunk@43575 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/lualatex/novel')
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/html-resources/endnotetext.pngbin39894 -> 25955 bytes
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.pngbin0 -> 5063 bytes
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/novel-template.tex2
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html127
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html26
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html24
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html62
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html98
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html103
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html42
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html30
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html472
12 files changed, 512 insertions, 474 deletions
diff --git a/Master/texmf-dist/doc/lualatex/novel/html-resources/endnotetext.png b/Master/texmf-dist/doc/lualatex/novel/html-resources/endnotetext.png
index 58067bee816..48bdc2563e4 100644
--- a/Master/texmf-dist/doc/lualatex/novel/html-resources/endnotetext.png
+++ b/Master/texmf-dist/doc/lualatex/novel/html-resources/endnotetext.png
Binary files differ
diff --git a/Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.png b/Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.png
new file mode 100644
index 00000000000..23318c56c5d
--- /dev/null
+++ b/Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.png
Binary files differ
diff --git a/Master/texmf-dist/doc/lualatex/novel/novel-template.tex b/Master/texmf-dist/doc/lualatex/novel/novel-template.tex
index 6456dee3e16..2c232c41b65 100644
--- a/Master/texmf-dist/doc/lualatex/novel/novel-template.tex
+++ b/Master/texmf-dist/doc/lualatex/novel/novel-template.tex
@@ -1,6 +1,6 @@
% !TeX program = LuaLaTeX
% !TeX encoding = UTF-8
-\documentclass{novel} % v. 1.0.7 or later
+\documentclass{novel} % v. 1.0.9 or later
% You may put this wherever your installation keeps templates.
% Many packages are pre-loaded. Nearly all settings are pre-configured.
% Some popular user settings:
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
index 9b8eb5d5ea7..0a994b5678b 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 1 - Overview</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -22,12 +22,13 @@
<li><a href="#a1.1.1">1.1.1 Licensing</a></li>
<li><a href="#a1.1.2">1.1.2 Installation</a></li>
<li><a href="#a1.1.3">1.1.3 Credits</a></li>
+ <li><a href="#a1.1.4">1.1.4 Useful Tools</a></li>
</ul></li><!-- end 1.1 -->
<li><a href="#a1.2">1.2 Differences. Important!</a>
<ul>
- <li><a href="#a1.2.1">1.2.1 LuaLaTeX, fontspec,<br/><span style="visibility:hidden">1.2.1 </span>utf-8, Open Type</a></li>
+ <li><a href="#a1.2.1">1.2.1 LuaLaTeX, fontspec,<br><span style="visibility:hidden">1.2.1 </span>utf-8, Open Type</a></li>
<li><a href="#a1.2.2">1.2.2 $ = dollar, not math mode</a></li>
- <li><a href="#a1.2.3">1.2.3 TeX Size Commands<br/><span style="visibility:hidden">1.2.3 </span>Are Disabled</a></li>
+ <li><a href="#a1.2.3">1.2.3 TeX Size Commands<br><span style="visibility:hidden">1.2.3 </span>Are Disabled</a></li>
<li><a href="#a1.2.4">1.2.4 Raster Images Only</a></li>
<li><a href="#a1.2.5">1.2.5 Academic Structure Disabled</a></li>
<li><a href="#a1.2.6">1.2.6 Think for Yourself</a></li>
@@ -48,10 +49,10 @@
<li><a href="#a1.4.2">1.4.2 Main Matter</a></li>
<li><a href="#a1.4.3">1.4.3 Back Matter</a></li>
</ul></li><!-- end 1.4 -->
-<li><hr/></li>
+<li><hr></li>
<li><a href="#a1.5">1.5 Command Summary: Preamble</a>
<ul>
- <li><a href="#a1.5.1">1.5.1 Class Options</a><br/>
+ <li><a href="#a1.5.1">1.5.1 Class Options</a><br>
<ul>
<li>draft, graytext, shademargins, cropmarks, cropview, closecrop, xml</li>
</ul>
@@ -85,9 +86,9 @@
<li>\frontmatter, \mainmatter, \backmatter</li>
</ul>
</li>
- <li><a href="#a1.6.2">1.6.2 Display Pages</a>
+ <li><a href="#a1.6.2">1.6.2 Special Pages</a>
<ul>
- <li>\begin{legalese}, \begin{toc}, \tocitem, \begin{ChapterDisplay}, \ChapterTitle, \ChapterSubtitle, \ChapterDeco, \thispagestyle, \FirstLine, \clearpage</li>
+ <li>\begin{legalese}, \begin{toc}, \tocitem, \begin{ChapterStart}, \ChapterTitle, \ChapterSubtitle, \ChapterDeco, \thispagestyle, \FirstLine, \clearpage</li>
</ul>
</li>
<li><a href="#a1.6.3">1.6.3 Block-Level Breaks and Styling</a>
@@ -138,7 +139,7 @@
<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
<p><b>User Guide</b></p>
@@ -147,11 +148,11 @@
<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-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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -178,27 +179,39 @@
<p>If you are ready to typeset your great detective novel, or your collection of sci-fi short stories, then <code>novel</code> is for you.</p>
-
+<a id="a1.1.1"></a>
<h4>1.1.1 Licensing</h4>
<p>The <code>novel</code> document class, including software, examples, documentation and supporting images, is distributed under the terms of the LaTeX Project Publc License, either version 1.3c of this license or (at your option) any later version. The exception is the included font NovelDeco.otf, which is distributed under terms of the SIL Open Font License, v.1.1. Small portions of the software use code placed on the Internet under terms of Creative Commons 3.0-by-sa license; attributions are provided at the places where such code is used.</p>
<p>To ensure that your book may be sold commercially, be careful to use only fonts that allow commercial usage. That may exclude some of the fonts in the LaTeX font catalog.</p>
-
+<a id="a1.1.2"></a>
<h4>1.1.2 Installation</h4>
-<p>Unless and until <code>novel</code> becomes part of TeX distributions, it must be manually installed in a "local" or "home" TeX directory. If obtained as a single compressed archive, the internal folder tree is already in correct configuration.</p>
-<p>Fonts from the <code>libertinus</code> package are required. They may be obtained through your TeX distribution. Note that neither <code>\RequirePackage{libertinus}</code> nor <code>\usepackage{libertinus}</code> will be effective. You must obtain and install the fonts yourself, or manually through your distribution's package manager.</p>
-<p>Depending on how you obtain the files, you may need to update the file name database. In TeXlive, try command line <code>mktexlsr</code>. In MiKTeX, use the <code>Options &gt; Update FNDB</code> button.</p>
-<p>Since you will be using LuaTeX, the font cache will be updated to include the newly-installed fonts, the next time you run this software. However, I recommend that you force a full cache refresh, by locating the <code>luatex-cache</code> directory, and discard its contents. The cache may be anywhere (sadly), so you will have to hunt for it. If you have never used LuaTeX before, it may not exist. If there are any updates to the fonts, then a manual cache refresh is necessary.</p>
+<p>Your TeX installation must be based on TeXLive 2016 or later. This is the case if you have manually installed TeXLive directly from its site, or if you are using MiKTeX. However, if you are on Linux and your distro is not the latest and greatest, the distribution may be based on TeXLive 2015 or earlier. Then, you will not be able to use <code>novel</code>.
+<p>The TeX code will be placed in (texroot)/tex/lualatex/novel/, the custom font will be placed in (texroot)/fonts/opentype/novel/, and the documentation will be placed in (texroot)/doc/lualatex/novel/.</p>
+<p>The <code>novel</code> class can now be installed like any other TeX package, through your distribution's package manager. The installation will provide the code, documentation, and a custom font.</p>
+
+<p>Fonts from the <code>libertinus</code> package are required, and may be installed via your TeX package manager. Note that a <code>novel</code> document does not request the package! Instead, if you have not manually specified which fonts to use, it will automatically look for pre-installed libertinus fonts (or Linux Libertine O) as defaults.</p>
+
+<p>Since you will be using LuaTeX, the font cache will be updated to include the newly-installed fonts, the next time you run this software. However, I recommend that you force a full cache refresh, by locating the <code>luatex-cache</code> directory, and discard its contents. The cache may be anywhere (sadly), so you will have to hunt for it. If you have never used LuaTeX before, it may not exist. If there are any updates to the fonts, then a manual cache refresh is necessary.</p>
+
+<a id="a1.1.3"></a>
<h4>1.1.3 Credits</h4>
<p>My method of "programming" (note the scare quotes) largely involves looking for solutions on the Internet, then using or modifying code provided by others with allowable license terms. Thus, within the TeX code files, you will find places where small or large pieces of code are the work of someone else, released by them for LaTeX purposes. Names or organizations are credited where the code is used.</p>
<p>Various clipart graphics were obtained from openclipart.org. The NovelDeco.otf font is partly derived from [Linux] Libertine O, using FontForge.</p>
+<a id="a1.1.4"></a>
+<h4>1.1.4 Useful Tools</h4>
+
+<p>Before sending your PDF file anywhere, you should always open it in Adobe Reader, and inspect it. If you are on a system that does not have that software, then find a friend who has it. The reason is that some other PDF readers will not object to problem files, but Adobe Reader will complain.</p>
+
+<p>In commercial printing, it is not necessary that your file be "optimized for fast web view" or "linearized." Nevertheless, some services do a lot of work with e-books, and may request that printer files be optimized or linearized, out of force of habit. The free <code>qpdf</code> command-line tool, available for Linux and Windows, is your friend.</p>
+<p>Your PDF cannot be encrypted or password-protected for commercial printing. Only you and the printer are supposed to see it. So, it is always possible to extract the text, not as a TeX document, but as plain text. Adobe Reader probably will not do what you expect. Adobe Acrobat Pro does a good job, if you first "add tags" via its accessibility features. Otherwise, the free Okular PDF reader does a reasonable job, as does the <code>pdftotext</code> command-line program (part of <code>xpdf</code>. Be sure to request that layout be preserved. You may need to review the exported text for words that were broken by hyphenation, and re-assemble the words.</p>
@@ -207,11 +220,13 @@
<p>There are several ways that <code>novel</code> is very different from other TeX document classes. Before you wonder why your document doesn't work, you need to understand the differences. All of these are features, not bugs. They are done with the intent of making <code>novel</code> best for its intended purpose.</p>
+<p><b>About TeX editors:</b> If you usually use a TeX editor GUI, such as Lyx or TeXstudio, avoid using it with the <code>novel</code> class. Those editors are capable of inserting standard LaTeX code from menus. However, <code>novel</code> does not necessarily use that standard LaTeX code. The result may be unexpected. Instead, create your document in an ordinary ut-8 plain text editor, and compile with <code>lualatex</code> from the command line. Or, you can use the TeXWorks editor, as long as you turn off features such as automatic smart quotes.</p>
+
<a id="a1.2.1"></a>
<h4>1.2.1 LuaLaTeX, fontspec, utf-8, and Open Type fonts</h4>
-<p><img class="floatright" src="html-resources/doordie.png" width="279" height="300" alt="Thou Shalt"/> With <code>novel</code>, you will be using the LuaLaTeX engine, whether you like it or not. No pdfTeX, no XeTeX, no dvips. You do not have to understand Lua code, since the heavy lifting is already done for you.</p>
+<p><img class="floatright" src="html-resources/doordie.png" width="279" height="300" alt="Thou Shalt"> With <code>novel</code>, you will be using the LuaLaTeX engine, whether you like it or not. No pdfTeX, no XeTeX, no dvips. You do not have to understand Lua code, since the heavy lifting is already done for you.</p>
<p>Forget about <code>fontenc</code> and <code>OT1</code> and other TeX exotica that go so far back in time, most folks did not have a cell phone. The built-in <code>fontspec</code> package handles modern Open Type fonts, and is able to access their internal features. The syntax is easy to learn, and very powerful. And, you can directly include text with diacritical marks, Greek, Cyrillic, and most other utf-8 encoded characters in your document. All you need are the fonts. You will wonder why you never did this before. The method for loading fonts is described on Page 5.</p>
<p>You must use utf-8 (Unicode) encoding in all parts of your code and document. No choice. Only utf-8, without BOM. Instead of typing TeX codes such as <code>\`{e}</code> you can simply paste <code>&egrave;</code> from a Unicode character map. Other alphabets such as Greek and Cyrillic are directly supported, if your fonts support those character sets.</p>
<p>Be sure that your editor uses utf-8 encoding without BOM. If you are on Linux (and presumably OS/X) then this is the default for your system. If you are on Windows, do not use Notepad! The free Notepad++ program (also Portable version) does the job. Configure it as specified.</p>
@@ -220,7 +235,7 @@
<a id="a1.2.2"></a>
<h4 style="clear:both">1.2.2 A dollar is a dollar, not math mode</h4>
-<p><img class="floatright" src="html-resources/trdol.png" width="238" height="67" alt="a dollar is a dollar"/> When you type <code>$</code> in the document body, with or without a preceding backslash, <em>you do not enter or leave math mode</em>. What you get is the dollar symbol. This has no effect in the Preamble, where the dollar sign has its usual TeX special meaning.</p>
+<p><img class="floatright" src="html-resources/trdol.png" width="238" height="67" alt="a dollar is a dollar"> When you type <code>$</code> in the document body, with or without a preceding backslash, <em>you do not enter or leave math mode</em>. What you get is the dollar symbol. This has no effect in the Preamble, where the dollar sign has its usual TeX special meaning.</p>
<p>If you really need math mode, you can use <code>\(</code> ... <code>\)</code>. But, why? You are writing a novel, yes? You shouldn't need math mode.</p>
@@ -241,7 +256,7 @@
<a id="a1.2.5"></a>
<h4>1.2.5 Numerous academic-purpose commands are disabled</h4>
-<p><img class="floatright" src="html-resources/fpaper.png" width="134" height="215" alt="flunked math"/> Commands such as <code>\section</code>, <code>\chapter</code>, <code>\abstract</code>, <code>\index</code>, <code>\tableofcontents</code>, <code>\maketitle</code>, and many other structural commands will not work with <code>novel</code>. Those are for academic papers. The results they would produce (if enabled) would be inappropriate for fiction. If you attempt to use them, you will either get an error message, or they will simply be ignored.</p>
+<p><img class="floatright" src="html-resources/fpaper.png" width="134" height="215" alt="flunked math"> Commands such as <code>\section</code>, <code>\chapter</code>, <code>\abstract</code>, <code>\index</code>, <code>\tableofcontents</code>, <code>\maketitle</code>, and many other structural commands will not work with <code>novel</code>. Those are for academic papers. The results they would produce (if enabled) would be inappropriate for fiction. If you attempt to use them, you will either get an error message, or they will simply be ignored.</p>
<p>Novelists do not need many ways to distinguish chapters. With <code>novel</code> there are commands specifically created for the needs of fictional works. They are described on <a href="noveldocs-09-chapters-displays.html#a9.5">Page 9</a>.</p>
<p>Also, the <code>float</code> and <code>table</code> environments are ineffective.</p>
@@ -271,7 +286,7 @@
<p>A <b>sheet</b> of paper is a single, physical piece of paper, regardless of whether anything is printed on it, or where. Often, paper starts out as a large sheet that will subsequently be cut into smaller sheets. The size doesn't matter. A sheet of paper is, in ordinary understanding, a piece of paper.</p>
-<p><img class="floatright" src="html-resources/page-leaf.png" width="490" height="155" alt="page, leaf"/> In a finished book, a <b>page</b> is one side of a <b>leaf</b>. Thus, there are always exacttly twice as many pages are there are leaves. From the manufacturer's point of view, a 240-page (double-sided printing) book has 120 leaves, regardless of whether or not anything is printed on the pages, or how they are numbered.</p>
+<p><img class="floatright" src="html-resources/page-leaf.png" width="490" height="155" alt="page, leaf"> In a finished book, a <b>page</b> is one side of a <b>leaf</b>. Thus, there are always exacttly twice as many pages are there are leaves. From the manufacturer's point of view, a 240-page (double-sided printing) book has 120 leaves, regardless of whether or not anything is printed on the pages, or how they are numbered.</p>
<p>If you take a sheet of 8.5" x 11" paper, and fold it in half across its width, you create a <b>folio</b>, consisting of one sheet of paper (as before), two leaves (previously one), and four pages (previously two), sized 5.5" x 8.5". Now, think about how those four pages must be numbered. Page 1 and page 4 are printed on the same side of the sheet, with pages 2 and 3 on the opposite side of the sheet. This is not the order they would be printed, if you were merely shrinking the text so that twice as much fit on one side of the sheet. The process of re-arranging the pages, and placing them in the correct positions (often involving rotation) is called <b>imposition</b>. Your home printer can do it, for the simple example described. But in the case of commercial book preparation, the imposition process is much more involved, and uses advanced software.</p>
@@ -281,13 +296,13 @@
<a id="a1.3.2"></a>
<h4>1.3.2 Page Spread, Recto, Verso, Line Grid</h4>
-<p><img class="floatright" src="html-resources/linegrid.png" width="303" height="234" alt="line grid"/> When a book is opened somewhere in its middle, you see a <b>page spread</b>. At right is the <b>recto</b> odd-numbered page, and at left is the <b>verso</b> even-numbered page. With continuous text, the lines of text on the verso must be in the same vertical position as the lines of text on the recto, and each line must be equally spaced. This is the <b>line grid</b>. Maintaining a proper line grid is essential to the <code>novel</code> class, and is why some <code>novel</code> commands differ from how they are used in academic works with other document classes.</p>
+<p><img class="floatright" src="html-resources/linegrid.png" width="303" height="234" alt="line grid"> When a book is opened somewhere in its middle, you see a <b>page spread</b>. At right is the <b>recto</b> odd-numbered page, and at left is the <b>verso</b> even-numbered page. With continuous text, the lines of text on the verso must be in the same vertical position as the lines of text on the recto, and each line must be equally spaced. This is the <b>line grid</b>. Maintaining a proper line grid is essential to the <code>novel</code> class, and is why some <code>novel</code> commands differ from how they are used in academic works with other document classes.</p>
<a id="a1.3.3"></a>
<h4>1.3.3 Perfect Binding, Spine, Signature</h4>
-<p><img class="floatright" src="html-resources/perfectbinding.png" width="160" height="290" alt="perfect binding"/> Most modern softcover books (and some inexpensive hardcovers) are manufactured using a process named <b>Perfect Binding</b>. The finished book has individual foils, glued together at the <b>spine</b>. There are several stages to the process. First, the books is subdivided into a number of <b>signatures</b>, each of which is a group of folios (typically 6). The imposition software calculates which page goes at which position on each folio, and also tweaks the positions to allow for the slight displacement of each folio, due to paper thickness. In each signature, the folios are like nested V. The signatures are clamped together in a block. Then the folded area is removed by a machine, so that there are no longer any signatures or folios, just individual leaves. Finally they are glued together, possibly with a reinforcement, and the cover is attached.</p>
+<p><img class="floatright" src="html-resources/perfectbinding.png" width="160" height="290" alt="perfect binding"> Most modern softcover books (and some inexpensive hardcovers) are manufactured using a process named <b>Perfect Binding</b>. The finished book has individual foils, glued together at the <b>spine</b>. There are several stages to the process. First, the books is subdivided into a number of <b>signatures</b>, each of which is a group of folios (typically 6). The imposition software calculates which page goes at which position on each folio, and also tweaks the positions to allow for the slight displacement of each folio, due to paper thickness. In each signature, the folios are like nested V. The signatures are clamped together in a block. Then the folded area is removed by a machine, so that there are no longer any signatures or folios, just individual leaves. Finally they are glued together, possibly with a reinforcement, and the cover is attached.</p>
<p>If you order your book in hardcover, it is likely to use the same production method, but with harder covers. So, don't think that your hadcover book will be like the expensive reference books you see in the library. Those books use a different, and much more expensive, binding method.</p>
@@ -295,14 +310,14 @@
<a id="a1.3.4"></a>
<h4>1.3.4 Gutter</h4>
-<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="perfect binding"/> To allow for the fact that most binding cannot be opened flat, the spine edge of each page must have an allowance for the loss of visible area there. The word <b>gutter</b> is used in this context.</p>
+<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="perfect binding"> To allow for the fact that most binding cannot be opened flat, the spine edge of each page must have an allowance for the loss of visible area there. The word <b>gutter</b> is used in this context.</p>
<p>Alas, some folks use <em>gutter</em> to mean the extra allowance for each page; others use it to mean the combined allowance for a two-page spread; and others use it to mean the full spine-side margin from the text, which is a larger value. So if you read about the gutter from different sources, the numbers may not make sense, because the word is being used with different meanings. It could be any of A, B, C, or D in the accompanying diagram. I won't be using the term, except indirectly.</p>
<a id="a1.3.5"></a>
<h4>1.3.5 Trim Size</h4>
-<p><img class="floatright" src="html-resources/tbrectomar.png" width="144" height="223" alt="trim size recto"/> <b>Trim Size</b> is the finished size of your book, width and height (but not thickness). In the case of hardcover books, where the cover is larger than the contents, it is (usually) the cover size that is measured, with the internal trim size being slightly smaller than nominal</p>
+<p><img class="floatright" src="html-resources/tbrectomar.png" width="144" height="223" alt="trim size recto"> <b>Trim Size</b> is the finished size of your book, width and height (but not thickness). In the case of hardcover books, where the cover is larger than the contents, it is (usually) the cover size that is measured, with the internal trim size being slightly smaller than nominal</p>
<p>In the USA, 5.5" x 8.5" is often used for softcover fiction. This is the default setting in <code>novel</code>. It seems to be the case that nonfiction prefers the slightly larger 6" x 9" trim size. Both of these are known as "trade" sizes.</p>
@@ -314,7 +329,7 @@
<a id="a1.3.6"></a>
<h4>1.3.6 Media Size, TrimBox</h4>
-<p style="clear:both"><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size recto"/> In a few cases, the commercial printer will request that the PDF page size be something larger than the Trim Size of your book. In PDF terminology, the larger dimensions are the <b>Media Size</b>. Typically, the Media Size will be U.S. Letter, or A4, and the Trim Size must be floated in the center, horizontally and vertically. As an alternative, the Trim Size will be at the edge. Something of the sort happens when you print a copy of your PDF at home, where your printer's paper tray has letter or A4, not the Trim Size.</p>
+<p style="clear:both"><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size recto"> In a few cases, the commercial printer will request that the PDF page size be something larger than the Trim Size of your book. In PDF terminology, the larger dimensions are the <b>Media Size</b>. Typically, the Media Size will be U.S. Letter, or A4, and the Trim Size must be floated in the center, horizontally and vertically. As an alternative, the Trim Size will be at the edge. Something of the sort happens when you print a copy of your PDF at home, where your printer's paper tray has letter or A4, not the Trim Size.</p>
<p>Do not use a Media Size larger than the Trim Size, unless the commercial printer requests it.</p>
<p>Since your PDF is being prepared for commercial print production, it will have an invisible <code>TrimBox</code> automatically encoded. This information tell the printer where the Trim Size is located. If (as usual) the Trim Size and Media Size are identical, then the TrimBox is the full size of the PDF page. But when the Trim Size is smaller than the Media Size, the TrimBox defines where the paper will be trimmed. Although it is not normally marked on the PDF page and never appears in print, some PDF viewers allow you make the TrimBox visible.</p>
<p>In the accompanying diagram, the TrimBox is shown as a green line. The margins, shaded gray, are measured relative to the Trim Size, not relative to the Media Size. The excess area beyond the Trim Size is "wasted paper" that will not become part of the book.</p>
@@ -472,10 +487,10 @@
<p>Default: off (no compliance set)</p>
<p>PDF/X describes a set of industry standards for print-ready PDF files. Your print service will probably require you to use it.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetApplication{<em>software that created the source document</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetApplication{<em>software that created the source document</em>}</pre>
<p>Default: an identifying string, automatically inserted by TeX.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetProducer{<em>software that compiled the PDF</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetProducer{<em>software that compiled the PDF</em>}</pre>
<p>Default: an identifying string, automatically inserted by TeX.</p>
@@ -514,19 +529,19 @@
<p>Default: Calculated automatically from other layout settings.</p>
<p>Main text, not including header/footer. Note than baseline skip (leading) is always calculated, not set by user.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetMediaSize[alignment]{width}{height}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetMediaSize[alignment]{width}{height}</pre>
<p>Default: Identical to Trim Size.</p>
<p>When Trim Size is on larger Media Size.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetCropmarkGap{<em>size of gap</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetCropmarkGap{<em>size of gap</em>}</pre>
<p>Default: <code>0.125in</code> (only effective with cropmarks class option)</p>
<p>Sets gap between TrimBox and cropmarks, when cropmarks are used.</p>
-<pre class="noindentcmd">Advanced:<br/>\ReworkTrimSize{width}{height}</pre>
+<pre class="noindentcmd">Advanced:<br>\ReworkTrimSize{width}{height}</pre>
<p>For emergency use only.</p>
<p>Re-sizes an already-finished layout.</p>
-<pre class="noindentcmd">Advanced:<br/>\ReworkMargins{top}{outside}{bottom}{inside}</pre>
+<pre class="noindentcmd">Advanced:<br>\ReworkMargins{top}{outside}{bottom}{inside}</pre>
<p>For emergency use only.</p>
<p>Re-sizes an already-finished layout.</p>
@@ -558,21 +573,21 @@
<p>Default: <code>[Numbers=Lining, Scale=1.2]{*}</code></p>
<p>Used in <code>\ChapterSubtitle{}</code> command.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetDecoFont[features]{font}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetDecoFont[features]{font}</pre>
<p>Default: <code>NovelDeco</code> (any setting must used a derivative of NovelDeco)</p>
<p>Automatically applied as <code>{\decofont...}</code> by certain other commands.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetSansFont[features]{font family}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetSansFont[features]{font family}</pre>
<p>Default: <code>Libertinus Sans</code></p>
<p>Alternate: <code>Linux Biolinum O</code></p>
<p>Rarely used in fiction.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetMonoFont[features]{font family}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetMonoFont[features]{font family}</pre>
<p>Default: <code>Libertinus Mono</code></p>
<p>Alternate: <code>Linux Libertine Mono O</code></p>
<p>Rarely used in fiction.</p>
-<pre class="noindentcmd">Advanced:<br/>\NewFontFamily\<i>yourfontcommand</i>[features]{font family}</pre>
+<pre class="noindentcmd">Advanced:<br>\NewFontFamily\<i>yourfontcommand</i>[features]{font family}</pre>
<pre class="noindentcmd2">\NewFontFace\<i>yourfontcommand</i>[features]{font}</pre>
<p>These use <em>fontspec</em> to define your own font commands.</p>
@@ -590,15 +605,15 @@
<p>Default: Adjusted author, in small caps</p>
<p>The text appears in verso headers, if the page style has headers. This command may also be used from time to time in the document body.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetEmblems{<em>verso</em>}{<em>recto</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetEmblems{<em>verso</em>}{<em>recto</em>}</pre>
<p>Default: both empty</p>
<p>Applies a decoration (emblem) near the page number. Only for selected header/footer styles.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetPageNumberStyle{<em>code using \thepage</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetPageNumberStyle{<em>code using \thepage</em>}</pre>
<p>Default: <code>\thepage</code></p>
<p>Allows page number to be styled (such as italics).</p>
-<pre class="noindentcmd">Advanced:<br/>\SetLooseHead{number}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetLooseHead{number}</pre>
<p>Default: <code>50</code></p>
<p>Tweaks tracking of header text, 0 to 200.</p>
@@ -606,19 +621,19 @@
<p>Default: <code>footer</code> (no header, footer only if used)</p>
<p>Sets the default page style for the start of new chapters. May be locally changed.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetIndentAfterScenebreak</pre>
+<pre class="noindentcmd">Advanced:<br>\SetIndentAfterScenebreak</pre>
<p>Default: unset (new scenes do not begin with indent)</p>
<p>If set, new scenes start with paragraph indent.</p>
-<pre class="noindentcmd">Advanced:<br/>\SetMarkerStyle[real/fake]{asterisk/dagger/number}</pre>
+<pre class="noindentcmd">Advanced:<br>\SetMarkerStyle[real/fake]{asterisk/dagger/number}</pre>
<p>Default: <code>[real]{asterisk}</code>
<p>Used for superscripts, subscripts, footnote markers.</p>
-<pre class="noindentcmd">Advanced:<br/>\microtypesetup{<em>see microtype package docs</em>}</pre>
+<pre class="noindentcmd">Advanced:<br>\microtypesetup{<em>see microtype package docs</em>}</pre>
<p>Default: <code>config=novel-microtype,stretch=20,shrink=20,final,tracking</code></p>
<p>Defaults are set for moderate typography suited to fiction. Options <code>final,tracking</code> will always be in effect.</p>
-<pre class="noindentcmd">Advanced:<br/>\setmainlanguage{<em>language</em>} and related commands</pre>
+<pre class="noindentcmd">Advanced:<br>\setmainlanguage{<em>language</em>} and related commands</pre>
<p>Default: <code>english</code></p>
<p>Several commands from the <code>polyglossia</code> package may be used for language choices.</p>
@@ -646,9 +661,8 @@
<a id="a1.6.2"></a>
-<h4>1.6.2 Display Pages</h4>
+<h4>1.6.2 Special Pages</h4>
-<p>A <em>display page</em> is one that either stands by itself (such as the book's copyright page), or provides a distinctive opening to new content (such as a chapter title page). In other words, a display page is one that does not merely contain the continuation of flowing text.</p>
<pre class="noindentcmd">\begin{legalese} <em>...</em> \end{legalese}</pre>
<p>Changes text alignment to left (ragged right), and disables hyphenation. Useful for copyright page. See also <code>parascale</code> environment.</p>
@@ -659,7 +673,7 @@
<pre class="noindentcmd">\tocitem[<em>number</em>]{<em>title</em>}{<em>page</em>}</pre>
<p>Item, such as chapter, in the toc environment.</p>
-<pre class="noindentcmd">\begin{ChapterDisplay}[<em>line count</em>] <em>...</em> \end{ChapterDisplay}</pre>
+<pre class="noindentcmd">\begin{ChapterStart}[<em>line count</em>] <em>...</em> \end{ChapterStart}</pre>
<p>Creates an area of fixed height, into which items such as <code>\ChapterTitle</code> may be placed.</p>
<pre class="noindentcmd">\ChapterTitle{<em>text</em>}</pre>
@@ -711,14 +725,14 @@
<pre class="noindentcmd">\endnotetext{<em>number</em>}{<em>note text</em>}</pre>
<p>Write the endnote text.</p>
-<pre class="noindentcmd">\realmarker<br/>\fakemarker</pre>
+<pre class="noindentcmd">\realmarker<br>\fakemarker</pre>
<p>Changes whether marker style is real or fake.</p>
<a id="a1.6.5"></a>
<h4>1.6.5 Images</h4>
-<pre class="noindentcmd">\InlineImage[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}<br/>\InlineImage*[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}</pre>
+<pre class="noindentcmd">\InlineImage[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}<br>\InlineImage*[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}</pre>
<p>Places an image that may be mingled in-line with text.</p>
<pre class="noindentcmd">\BlockImage[<em>alignment,hoffset,voffset</em>]{<em>filename.ext</em>}[<em>accompanying text</em>]</pre>
@@ -737,7 +751,7 @@
<p>Applies the font defined as <code>\somefontcommand</code> to the included text.</p>
<p>Example: <code>{\headfont <em>text</em>}</code> is automatically used for headers/footers.</p>
-<pre class="noindentcmd">\forceindent<br/>\backindent</pre>
+<pre class="noindentcmd">\forceindent<br>\backindent</pre>
<p>May be used in situations where ordinary <code>\indent</code> or <code>\noindent</code> fail.</p>
<pre class="noindentcmd">\hangindent{<em>text</em>}</pre>
@@ -749,10 +763,10 @@
<pre class="noindentcmd">\decoglyph{}</pre>
<p>Selects a decorative glyph from the decofont. Glyphs are chosen from a code table.</p>
-<pre class="noindentcmd">\squeeze{<em>text</em>}<br/>\crush{<em>text</em>}</pre>
+<pre class="noindentcmd">\squeeze{<em>text</em>}<br>\crush{<em>text</em>}</pre>
<p>Horizontally shrinks text by 1% or 2%, respectively.</p>
-<pre class="noindentcmd">\color[<em>gray</em>]{<em>name or code</em>} <em>... until group ends</em><br/>\textcolor[<em>gray</em>]{<em>name or code</em>}{<em>text</em>}</pre>
+<pre class="noindentcmd">\color[<em>gray</em>]{<em>name or code</em>} <em>... until group ends</em><br>\textcolor[<em>gray</em>]{<em>name or code</em>}{<em>text</em>}</pre>
<p>These commands from package <code>xcolor</code> have been modified so that they will only accept grayscale, and only when the <code>graytext</code> class option is used. Otherwise, K black is produced. Images are unaffected.</p>
<pre class="noindentcmd">\memo{<em>text</em>}</pre>
@@ -761,7 +775,7 @@
<pre class="noindentcmd">$ (dollar symbol)</pre>
<p>In document body: <code>$</code> means dollar, not math mode.</p>
-<pre class="noindentcmd">\nfs<br/>\nbs</pre>
+<pre class="noindentcmd">\nfs<br>\nbs</pre>
<p>These are abbreviations for the lengths <em>normal font size</em> and <em>normal baseline skip</em>.</p>
@@ -770,6 +784,9 @@
<p>These commands are defined by LaTeX or by a package that is automatically loaded with <code>novel</code>, or are standard commands given an alias for convenience. There are many other LaTeX commands that may be used, but these are most likely to be useful. Most of these are not documented by <code>novel</code>, since their usage is well-known.</p>
+<pre class="noindentcmd">\textit{<em>text</em>}, \emph{<em>text</em>}, \itshape{<em>text</em>}</pre>
+<p>Various ways to implement italics.</p>
+
<pre class="noindentcmd">\textsc{<em>text</em>}, \smcp{<em>text</em>}</pre>
<p>Lowercase to small caps. Novel uses the <code>smcp</code> Open Type feature, and does not fake small caps.</p>
@@ -843,7 +860,7 @@
<pre class="noindentcmd">\maketitle</pre>
<p>Sorry, but you have to do it yourself.</p>
-<pre class="noindentcmd">bibliography, index, etc.<br/>part, chapter, section, etc.<br/>floats, captions, tables</pre>
+<pre class="noindentcmd">bibliography, index, etc.<br>part, chapter, section, etc.<br>floats, captions, tables</pre>
<p>This ain't no stinking thesis. LaTeX "academic layout" commands don't work.</p>
@@ -853,7 +870,7 @@
<p>These commands may be used, but are likely to interfere with other commands defined by <code>novel</code>, or are likely to disturb the constant baseline grid. Only use them when you are willing to carefully inspect the output at magnification. These are less likely to be problematic when used on a display-only page, such as the book's title page.</p>
<p>This is not a comprehensive list. It includes only popular commands.</p>
-<pre class="noindentcmd">\parbox<br/>\minipage</pre>
+<pre class="noindentcmd">\parbox<br>\minipage</pre>
<p>Perhaps the <code>adjustwidth</code> environment will sui your needs.</p>
<pre class="noindentcmd">center environment</pre>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html
index aba89722db6..48b68571351 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 2 - Class Options</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -37,7 +37,7 @@
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
@@ -47,11 +47,11 @@
<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-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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -78,7 +78,7 @@
<p>In draft mode, a little black bar will be placed at the right side of text that didn't quite fit on the line. These locations are reported in the log file as "overfull hbox" warnings. The black bar is called an "overflow rule".</p>
-<p class="centerimg"><img src="html-resources/overflowrule.png" width="525" height="115" title="draft mode, overflow rule" alt="overflow rule"/></p>
+<p class="centerimg"><img src="html-resources/overflowrule.png" width="525" height="115" title="draft mode, overflow rule" alt="overflow rule"></p>
<p>Some packages take note of whether or not the document is in draft mode, and change their behavior accordingly. However, the included <code>microtype</code> package will always be in final mode, and the included <code>hyperref</code> package will always be in draft mode.</p>
@@ -92,7 +92,7 @@
<p>The <code>graytext</code> option over-rides this restriction, and obeys grayscale color commands from the <code>xcolor</code> package, which is already loaded with the class. Non-grayscale colors will be converted to shades of gray. The color commands are discussed on <a href="noveldocs-07-text-size-style.html#a7.2.8">Page 7</a>.</p>
-<p class="centerimg"><img src="html-resources/graytext.png" width="512" height="54" title="graytext" alt="graytext"/></p>
+<p class="centerimg"><img src="html-resources/graytext.png" width="512" height="54" title="graytext" alt="graytext"></p>
<p>Your book will not be printed with "gray ink." Instead, anything other than pure black will be emulated by a pattern of black dots. This is known as "halftone." It causes a reduction in resolution, so your gray text will appear somewhat fuzzy. In addition, the halftone operation may extend to nearby text that is not gray. So: Unlike the example shown above, it is a bad idea to mingle gray with the ordinary flow of black text. The most appropriate use of gray text is for special items such as chapter titles.</p>
@@ -103,7 +103,7 @@
<h4>2.3 shademargins</h4>
<p>This option is ignored unless using draft mode. It is not necessary to use the <code>graytext</code> option.</p>
-<p><img class="floatright" style="margin-top:6px" src="html-resources/shademargins.png" width="132" height="205" title="shademargins" alt="shademargins"/> The <code>shademargins</code> option is simple: The margins will have a light gray background. Note that <em>margins</em> refers to the area between the live text area (including head/foot, if any) and the TrimBox, which is the finished size of your book. If you are using <code>\SetMediaSize</code> to request paper larger than your book's Trim Size, the excess area is <em>not</em> considered to be margins; it is discarded paper, so it is not gray.</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/shademargins.png" width="132" height="205" title="shademargins" alt="shademargins"> The <code>shademargins</code> option is simple: The margins will have a light gray background. Note that <em>margins</em> refers to the area between the live text area (including head/foot, if any) and the TrimBox, which is the finished size of your book. If you are using <code>\SetMediaSize</code> to request paper larger than your book's Trim Size, the excess area is <em>not</em> considered to be margins; it is discarded paper, so it is not gray.</p>
<p>Some commands (in particular, images) allow their content to overflow the textblock area. With <code>shademargins</code> you can see where such object intrude into the margins.</p>
<p>Sometimes it is hard to see whether a centered object is really centered, because the left-right margins are not the same width. With <code>shademargins</code> you can more easily see centering.</p>
<p>Note that headers and footers are not part of the margins.</p>
@@ -116,13 +116,13 @@
<a id="a2.4"></a>
<h4>2.4 cropmarks</h4>
-<p><img class="floatright" style="margin-top:6px" src="html-resources/cropmarks.png" width="205" height="265" title="cropmarks" alt="cropmarks"/> This option is ignored if the TrimSize is the same as the MediaSize (the usual situation). It works whether or not in draft mode.</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/cropmarks.png" width="205" height="265" title="cropmarks" alt="cropmarks"> This option is ignored if the TrimSize is the same as the MediaSize (the usual situation). It works whether or not in draft mode.</p>
<p>If the PDF Media Size is larger than its finished TrimSize, you can place crop marks (also known as trim marks) to indicate where the paper will be cut. The <code>cropmarks</code> option makes the marks visible. If this option is not used, then no marks are placed, regardless of any other commands.</p>
<p>Note that most print-on-demand book printers <em>do not want crop marks</em>. The process flow is automated, and trim data is read from within the PDF. Crop marks may actually interfere with proper layout, if your PDF is re-formatted to share a large sheet of paper along with other pages. So, do not use <code>cropmarks</code> unless you must. For this reason, the built-in capability for cropmarks is very basic.</p>
-<p><img class="floatright" style="margin-top:6px" src="html-resources/cropmarkgap.png" width="140" height="141" title="cropmark gap" alt="cropmark gap"/> There is only one configurable setting, which may be used in the Preamble:</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/cropmarkgap.png" width="140" height="141" title="cropmark gap" alt="cropmark gap"> There is only one configurable setting, which may be used in the Preamble:</p>
<p class="code"><code>\SetCropmarkGap{<em>length</em>}</code></p>
@@ -134,7 +134,7 @@
<a id="a2.5"></a>
<h4>2.5 cropview</h4>
-<p><img class="floatright" style="margin-top:6px" src="html-resources/cropview.png" width="132" height="203" title="cropview" alt="cropview"/> This option is ignored if the TrimSize is the same as the MediaSize (the usual situation), because it is unnecessary. Also, it is ignored unless using draft mode.</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/cropview.png" width="132" height="203" title="cropview" alt="cropview"> This option is ignored if the TrimSize is the same as the MediaSize (the usual situation), because it is unnecessary. Also, it is ignored unless using draft mode.</p>
<p>With <code>cropview</code>, there is an internal instruction to PDF viewers, requesting that only the Trim Size be displayed on the screen, rather than the whole Media Size. This is useful during the layout phase, because it is hard to visualize layout when you have a small finished size floating in a much larger paper size. Nothing else is changed.</p>
@@ -144,7 +144,7 @@
<a id="a2.6"></a>
<h4>2.6 closecrop</h4>
-<p><img class="floatright" style="margin-top:6px" src="html-resources/closecrop.png" width="110" height="186" title="closecrop" alt="closecrop"/> This option is only effective in draft mode. When used, the layout of your text is unchanged, but the surrounding margins are shrunk so that they just clear the live text area (which includes header and footer, if present). Also, the TrimSize is shrunk accordingly. Left and right margins are the same. The resulting PDF will be easier to read on a handheld device.</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/closecrop.png" width="110" height="186" title="closecrop" alt="closecrop"> This option is only effective in draft mode. When used, the layout of your text is unchanged, but the surrounding margins are shrunk so that they just clear the live text area (which includes header and footer, if present). Also, the TrimSize is shrunk accordingly. Left and right margins are the same. The resulting PDF will be easier to read on a handheld device.</p>
<p>This does <em>not</em> produce an E-book, since the file will be missing some things that an E-book ought to have. The sole purpose of this option is to create a conveniently-sized file that you can carry around while you are thinking about edits and revisions.</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html
index 81a494a90d9..274cf5d3c21 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 3 - Metadata, PDFX</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -35,7 +35,7 @@
<li><a href="#a3.3.1">3.3.1 \SetTitle{}</a></li>
<li><a href="#a3.3.2">3.3.2 \SetAuthor{}</a></li>
<li><a href="#a3.3.3">3.3.3 \SetSubtitle{}</a></li>
- <li><a href="#a3.3.4">3.3.4 \SetApplication{}<br/>
+ <li><a href="#a3.3.4">3.3.4 \SetApplication{}<br>
<span style="visibility:hidden">3.3.4 </span>\SetProducer{}</a></li>
</ul></li><!-- end 3.3 -->
<li><a href="#a3.4">3.4 \SetPDFX[]{}</a>
@@ -58,7 +58,7 @@
<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
@@ -68,11 +68,11 @@
<p>3. Metadata, PDF/X</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-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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -95,7 +95,7 @@
<a id="a3.1.1"></a>
<h4 style="clear:none">3.1.1 ISBN Metadata</h4>
-<p><img class="floatright" src="html-resources/bookmanglerdashboard.png" width="500" height="309" alt="online form for ISBN metadata"/> When you obtain the ISBN for your book, either directly through the issuing agency or via your chosen print service, you will enter <em>ISBN Metadata</em> in an online form. This metadata will go into a database, and identify your printed book in distribution and sales channels. It neither knows nor cares about PDF. (If you were marketing an e-book, instead of print, that would be a different story.)</p>
+<p><img class="floatright" src="html-resources/bookmanglerdashboard.png" width="500" height="309" alt="online form for ISBN metadata"> When you obtain the ISBN for your book, either directly through the issuing agency or via your chosen print service, you will enter <em>ISBN Metadata</em> in an online form. This metadata will go into a database, and identify your printed book in distribution and sales channels. It neither knows nor cares about PDF. (If you were marketing an e-book, instead of print, that would be a different story.)</p>
<p>ISBN Metadata includes title, author(s), subtitle if any, ISBN, other identifying information, and a description. The description is by way of advertising, and can usually be changed later; it need not appear anywhere in your book or PDF file, although some authors might use the description on the book's rear cover or cover flap.</p>
@@ -105,7 +105,7 @@
<a id="a3.1.2"></a>
<h4>3.1.2 Printed Metadata</h4>
-<p><img class="floatright" src="html-resources/megatitlepagesm.png" width="165" height="256" alt="printed metadata, cover page"/> <em>Printed Metadata</em> refers to the information that can be seen on paper, in expected places: the book cover, the title page, and the copyright page. Whether your book was printed from a PDF file, or by some other method, is not relevant.</p>
+<p><img class="floatright" src="html-resources/megatitlepagesm.png" width="165" height="256" alt="printed metadata, cover page"> <em>Printed Metadata</em> refers to the information that can be seen on paper, in expected places: the book cover, the title page, and the copyright page. Whether your book was printed from a PDF file, or by some other method, is not relevant.</p>
<p>Your print service will insist that the title, subtitle (if any), author, and ISBN in these places exactly match what appears in the ISBN database. Of course, you can (and usually will) use styling or images to make the Printed Metadata more attractive than the plain-text ISBN Metadata.</p>
@@ -115,7 +115,7 @@
<a id="a3.1.3"></a>
<h4>3.1.3 File Data (PDF Metadata)</h4>
-<p><img class="floatright" src="html-resources/megadocprops.png" width="298" height="215" alt="PDF metadata"/> When your PDF file is produced, internal metadata will be automatically created for the benefit of PDF reader software. <em>To avoid confusion, this documentation uses the term "File Data" to mean this internal PDF metadata.</em> You can see some of the File Data when you open the PDF in any reader, and go to File&gt;Properties. To see all of it, you need professional software (such as Adobe Acrobat Pro).</p>
+<p><img class="floatright" src="html-resources/megadocprops.png" width="298" height="215" alt="PDF metadata"> When your PDF file is produced, internal metadata will be automatically created for the benefit of PDF reader software. <em>To avoid confusion, this documentation uses the term "File Data" to mean this internal PDF metadata.</em> You can see some of the File Data when you open the PDF in any reader, and go to File&gt;Properties. To see all of it, you need professional software (such as Adobe Acrobat Pro).</p>
<p>Be sure to read the rules for File Data, below. Some of it is generic, and some is particular to TeX or to the <code>novel</code> class.</p>
@@ -269,8 +269,8 @@
<p>Although many *.icc files are freely available, they usually cannot be distributed within an open-source project. You might already have them in your system, wherever such files are stored. Note that TeX uses forward slash in file paths, not backslash, even if the platform is Windows:</p>
<p class="isolate">
-Windows: <code>C:/Windows/System32/spool/drivers/color/</code> &nbsp; [older Windows: system32 instead of System32]<br/>
-Linux: <code>/usr/share/color</code> or hidden <code>~/.local/share/icc/</code> or other places<br/>
+Windows: <code>C:/Windows/System32/spool/drivers/color/</code> &nbsp; [older Windows: system32 instead of System32]<br>
+Linux: <code>/usr/share/color</code> or hidden <code>~/.local/share/icc/</code> or other places<br>
OSX: <code>/Library/Colorsync/Profiles/</code> or hidden <code>(username)/Library/Colorsync/Profiles/</code>
</p>
<p>If you do not have the files, look on the Internet <a href="https://www.adobe.com/support/downloads/iccprofiles/icc_eula_win_end.html" target="new">here</a> and <a href="http://www.color.org/profiles.xalter" target="new">here</a>. These links also have many other profiles, beyond the basic three. In a few cases, your print service may provide the necessary file.</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html
index 2b276446e6c..41d258d37bf 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 4 - Book Size and Page Layout</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -38,7 +38,7 @@
<li><a href="#a4.2.3">4.2.3 \SetFontSize{}</a></li>
<li><a href="#a4.2.4">4.2.4 \SetLinesPerPage{}</a></li>
<li><a href="#a4.2.5">4.2.5 \SetHeadFootStyle{}</a></li>
- <li><a href="#a4.2.6">4.2.6 \SetHeadJump{}<br/><span style="visibility:hidden">4.2.6 </span>\SetFootJump{}</a></li>
+ <li><a href="#a4.2.6">4.2.6 \SetHeadJump{}<br><span style="visibility:hidden">4.2.6 </span>\SetFootJump{}</a></li>
<li><a href="#a4.2.7">4.2.7 \SetMediaSize[]{}{}</a></li>
<li><a href="#a4.2.8">4.2.8 \SetCropmarkGap{}</a></li>
</ul>
@@ -65,7 +65,7 @@
<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
@@ -75,11 +75,11 @@
<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
<p>4. Page Layout</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-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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -110,7 +110,7 @@
<p>A <b>sheet</b> of paper is a single, physical piece of paper, regardless of whether anything is printed on it, or where. Often, paper starts out as a large sheet that will subsequently be cut into smaller sheets. The size doesn't matter. A sheet of paper is, in ordinary understanding, a piece of paper.</p>
-<p><img class="floatright" src="html-resources/page-leaf.png" width="490" height="155" alt="page, leaf"/> In a finished book, a <b>page</b> is one side of a <b>leaf</b>. Thus, there are always exactly twice as many pages are there are leaves. From the manufacturer's point of view, a 240-page (double-sided printing) book has 120 leaves, regardless of whether or not anything is printed on the pages, or how they are numbered.</p>
+<p><img class="floatright" src="html-resources/page-leaf.png" width="490" height="155" alt="page, leaf"> In a finished book, a <b>page</b> is one side of a <b>leaf</b>. Thus, there are always exactly twice as many pages are there are leaves. From the manufacturer's point of view, a 240-page (double-sided printing) book has 120 leaves, regardless of whether or not anything is printed on the pages, or how they are numbered.</p>
<p>If you take a sheet of 8.5" x 11" paper, and fold it in half across its width, you create a <b>folio</b>, consisting of one sheet of paper (as before), two leaves (previously one), and four pages (previously two), sized 5.5" x 8.5". Now, think about how those four pages must be numbered. Page 1 and page 4 are printed on the same side of the sheet, with pages 2 and 3 on the opposite side of the sheet. This is not the order they would be printed, if you were merely shrinking the text so that twice as much fit on one side of the sheet. The process of re-arranging the pages, and placing them in the correct positions (often involving rotation) is called <b>imposition</b>. Your home printer can do it, for the simple example described. But in the case of commercial book preparation, the imposition process is much more involved, and uses advanced software.</p>
@@ -120,13 +120,13 @@
<a id="a4.1.2"></a>
<h4>4.1.2 Page Spread, Recto, Verso, Line Grid</h4>
-<p><img class="floatright" src="html-resources/linegrid.png" width="303" height="234" alt="line grid"/> When a book is opened somewhere in its middle, you see a <b>page spread</b>. At right is the <b>recto</b> odd-numbered page, and at left is the <b>verso</b> even-numbered page. With continuous text, the lines of text on the verso must be in the same vertical position as the lines of text on the recto, and each line must be equally spaced. This is the <b>line grid</b>. Maintaining a proper line grid is essential to the <code>novel</code> class, and is why some <code>novel</code> commands differ from how they are used in academic works with other document classes.</p>
+<p><img class="floatright" src="html-resources/linegrid.png" width="303" height="234" alt="line grid"> When a book is opened somewhere in its middle, you see a <b>page spread</b>. At right is the <b>recto</b> odd-numbered page, and at left is the <b>verso</b> even-numbered page. With continuous text, the lines of text on the verso must be in the same vertical position as the lines of text on the recto, and each line must be equally spaced. This is the <b>line grid</b>. Maintaining a proper line grid is essential to the <code>novel</code> class, and is why some <code>novel</code> commands differ from how they are used in academic works with other document classes.</p>
<a id="a4.1.3"></a>
<h4>4.1.3 Perfect Binding, Spine, Signature</h4>
-<p><img class="floatright" src="html-resources/perfectbinding.png" width="160" height="290" alt="perfect binding"/> Most modern softcover books (and some inexpensive hardcovers) are manufactured using a process named <b>Perfect Binding</b>. The finished book has individual foils, glued together at the <b>spine</b>. There are several stages to the process. First, the books is subdivided into a number of <b>signatures</b>, each of which is a group of folios (typically 1 or 6 folios per signature). The imposition software calculates which page goes at which position on each folio, and also tweaks the positions to allow for the slight displacement of each folio, due to paper thickness. In each signature, the folios are like nested V. The signatures are clamped together in a block. Then the folded area is removed by a machine, so that there are no longer any signatures or folios, just individual leaves. Finally they are glued together, possibly with a reinforcement, and the cover is attached.</p>
+<p><img class="floatright" src="html-resources/perfectbinding.png" width="160" height="290" alt="perfect binding"> Most modern softcover books (and some inexpensive hardcovers) are manufactured using a process named <b>Perfect Binding</b>. The finished book has individual foils, glued together at the <b>spine</b>. There are several stages to the process. First, the books is subdivided into a number of <b>signatures</b>, each of which is a group of folios (typically 1 or 6 folios per signature). The imposition software calculates which page goes at which position on each folio, and also tweaks the positions to allow for the slight displacement of each folio, due to paper thickness. In each signature, the folios are like nested V. The signatures are clamped together in a block. Then the folded area is removed by a machine, so that there are no longer any signatures or folios, just individual leaves. Finally they are glued together, possibly with a reinforcement, and the cover is attached.</p>
<p>If you order your book in hardcover, it is likely to use a similar production method, but with harder covers. So, don't think that your hadcover book will be like the expensive reference books you see in the library. Those books use a different, and much more expensive, binding method.</p>
@@ -134,14 +134,14 @@
<a id="a4.1.4"></a>
<h4>4.1.4 Gutter</h4>
-<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="Which gutter?"/> To allow for the fact that most binding cannot be opened flat, the spine edge of each page must have an allowance for the loss of visible area there. The word <b>gutter</b> is used in this context.</p>
+<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="Which gutter?"> To allow for the fact that most binding cannot be opened flat, the spine edge of each page must have an allowance for the loss of visible area there. The word <b>gutter</b> is used in this context.</p>
<p>Alas, some folks use <em>gutter</em> to mean the extra allowance for each page; others use it to mean the combined allowance for a two-page spread; and others use it to mean the full spine-side margin from the text, which is a larger value. So if you read about the gutter from different sources, the numbers may not make sense, because the word is being used with different meanings. It could be any of A, B, C, or D in the accompanying diagram. I won't be using the term, except indirectly.</p>
<a id="a4.1.5"></a>
<h4>4.1.5 Trim Size, Margins, Live Area</h4>
-<p><img class="floatright" src="html-resources/tbrectomar.png" width="144" height="223" alt="trim size recto"/> <b>Trim Size</b> is the finished size of your book, width and height (but not thickness). In the case of hardcover books, where the cover is larger than the contents, it is (usually) the cover size that is measured, with the internal trim size being slightly smaller than nominal</p>
+<p><img class="floatright" src="html-resources/tbrectomar.png" width="144" height="223" alt="trim size recto"> <b>Trim Size</b> is the finished size of your book, width and height (but not thickness). In the case of hardcover books, where the cover is larger than the contents, it is (usually) the cover size that is measured, with the internal trim size being slightly smaller than nominal</p>
<p>In the USA, 5.5" x 8.5" is often used for softcover fiction. This is the default setting in <code>novel</code>. It seems to be the case that nonfiction prefers the slightly larger 6" x 9" trim size. Both of these are known as "trade" sizes.</p>
@@ -158,7 +158,7 @@
<a id="a4.1.6"></a>
<h4>4.1.6 Media Size, TrimBox</h4>
-<p style="clear:both"><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size recto"/> In a few cases, the commercial printer will request that the PDF page size be something larger than the Trim Size of your book. In PDF terminology, the larger dimensions are the <b>Media Size</b>. Typically, the Media Size will be U.S. Letter, or A4, and the Trim Size must be floated in the center, horizontally and vertically. As an alternative, the Trim Size will be at the edge. Something of the sort happens when you print a copy of your PDF at home, where your printer's paper tray has letter or A4, not the Trim Size.</p>
+<p style="clear:both"><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size recto"> In a few cases, the commercial printer will request that the PDF page size be something larger than the Trim Size of your book. In PDF terminology, the larger dimensions are the <b>Media Size</b>. Typically, the Media Size will be U.S. Letter, or A4, and the Trim Size must be floated in the center, horizontally and vertically. As an alternative, the Trim Size will be at the edge. Something of the sort happens when you print a copy of your PDF at home, where your printer's paper tray has letter or A4, not the Trim Size.</p>
<p>Unless you explicitly set it to a different value, Media Size will automatically be set at Trim Size. Do not use a different Media Size, unless the commercial printer requests it.</p>
<p>Since your PDF is being prepared for commercial print production, it will have an invisible <code>TrimBox</code> automatically encoded. This information tells the printer where the Trim Size is located. If (as usual) the Trim Size and Media Size are identical, then the TrimBox is the full size of the PDF page. But when the Trim Size is smaller than the Media Size, the TrimBox defines where the paper will be trimmed. Although it is not normally marked on the PDF page and never appears in print, some PDF viewers allow you make the TrimBox visible.</p>
<p>In the accompanying diagram, the TrimBox is shown as a faint green line. The margins, shaded gray, are measured relative to the Trim Size, not relative to the Media Size. The excess area beyond the Trim Size is "wasted paper" that will not become part of the book.</p>
@@ -197,13 +197,13 @@
<a id="a4.2.2"></a>
<h4 style="clear:none">4.2.2 \SetMargins{<em>top</em>}{<em>outside</em>}{<em>bottom</em>}{<em>inside</em>}</h4>
-<p><img class="floatright" src="html-resources/margins.png" width="303" height="234" alt="margins"/> Mnemonic: "TOBI, or not TOBI, that is the question."</p>
+<p><img class="floatright" src="html-resources/margins.png" width="303" height="234" alt="margins"> Mnemonic: "TOBI, or not TOBI, that is the question."</p>
<p>When you choose your book's Trim Size, margins are pre-configured. In most cases, the top, outside, and bottom margins are 0.5", and the inside (spine) margin is 0.75" to allow 0.25" binding clearance. These values are acceptable to most American printers, unless your book is very thick. The largest Trim Sizes have slightly larger margins.</p>
<p>Command <code>\SetMargins</code> lets you choose your own margins. If you use it, all four must be written, using units such as <code>in</code> or <code>mm</code>.</p>
-<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="Which gutter?"/> If your book has headers and/or footers, they sit inside the rectangle bounded by the margins. That is, they do not sit inside the peripheral areas cleared by the margins.</p>
+<p><img class="floatright" src="html-resources/whichgutter.png" width="276" height="219" alt="Which gutter?"> If your book has headers and/or footers, they sit inside the rectangle bounded by the margins. That is, they do not sit inside the peripheral areas cleared by the margins.</p>
<p>Be aware that there is a lot of confusion regarding the word "gutter." In the accompanying diagram, it might mean any of A, B, C, or D, depending on who is doing the talking and which software is in use. The <code>novel</code> class uses <em>inside margin</em>, also known as <em>spine margin</em>, to mean C.</p>
@@ -230,7 +230,7 @@
<a id="a4.2.5"></a>
<h4>4.2.5 \SetHeadStyle{<em>number</em>}</h4>
-<p><img class="floatright" src="html-resources/headfoot.png" width="276" height="219" title="head foot style 1" alt="head foot style 1"/> The use of this command is described on <a href="noveldocs-06-header-footer.html#a6.1.2">Page 6</a>. It is mentioned here, because whether or not your book has headers and/or footers will affect the overall layout. The default is style 1, which has header but no footer (shown here).</p>
+<p><img class="floatright" src="html-resources/headfoot.png" width="276" height="219" title="head foot style 1" alt="head foot style 1"> The use of this command is described on <a href="noveldocs-06-header-footer.html#a6.1.2">Page 6</a>. It is mentioned here, because whether or not your book has headers and/or footers will affect the overall layout. The default is style 1, which has header but no footer (shown here).</p>
<p>The pre-defined styles are comprehensive, for use in fiction. It is hard to imagine a header/footer style that is not identical to, or a variation from, one of those styles. But if you do wish to create your own style, you must use <code>\SetHeadStyle</code> to choose the closest available style, then use <code>fancyhdr</code> commands for your custom style. The reason is that <code>\SetHeadStyle</code> tells the layout engine how much space it needs to reserve.</p>
@@ -240,7 +240,7 @@
<p>Puzzled by TeX terms such as <em>headsep</em> and <em>footskip</em>? Me too! That's why I rewrote the way that the positions of headers and footers are calculated. Now, you can use easy-to-understand commands that do what you think they ought to be doing.</p>
-<p class="floatright" style="text-indent:0px"><img src="html-resources/headjump1.png" width="158" height="125" alt="headjump 1"/><br/><img src="html-resources/footjump2.png" width="130" height="116" alt="footjump 2"/></p>
+<p class="floatright" style="text-indent:0px"><img src="html-resources/headjump1.png" width="158" height="125" alt="headjump 1"><br><img src="html-resources/footjump2.png" width="130" height="116" alt="footjump 2"></p>
<p>The head and/or foot "jump" is a multiple of the normal baseline skip. When the jumps are set to 1, the header (if used) will be where the textblock would be, if it had one more line on top. The footer will be where the textblock would be, if it had one more line at the bottom. Values of 2 would skip a line at top and bottom. In other words, integer jumps maintain the line grid.</p>
<p>Actually, the header and/or footer do not need to be on line grid. The defaults are 1.5 for each, which balances the need to separate the header/footer from the text, with the need to avoid wasting vertical space.</p>
@@ -265,11 +265,11 @@
<p>For PDF/X compliance, an invisible PDF TrimBox is automatically calculated and written into the PDF file.</p>
-<p><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size larger than trim size"/> The accompanying image shows how this works. Here is the code:</p>
+<p><img class="floatright" src="html-resources/mbcrectomar.png" width="202" height="264" alt="media size larger than trim size"> The accompanying image shows how this works. Here is the code:</p>
-<p class="code"><code>\documentclass[draft,shademargins]{novel}<br/>
-\SetTrimSize{5.5in}{8.5in}<br/>
-\SetMediaSize{8.5in}{11in}<br/>
+<p class="code"><code>\documentclass[draft,shademargins]{novel}<br>
+\SetTrimSize{5.5in}{8.5in}<br>
+\SetMediaSize{8.5in}{11in}<br>
\SetMargins{0.5in}{0.5in}{0.5in}{0.75in}</code></p>
<p>Trim Size 5.5"x8.5" is centered in Media Size 8.5"x11". The <code>shademargins</code> option was used, so that the page margins can be seen. Whether verso or recto, the Trim is centered in the Media. This image is a recto page, which has its slightly-larger inside margin at left of the text. For purposes of illustration, I have drawn the invisible TrimBox with a green line.</p>
@@ -278,13 +278,13 @@
<a id="a4.2.8"></a>
<h4>4.2.8 Advanced: \SetCropmarkGap{<em>length</em>}</h4>
-<p><img class="floatright" src="html-resources/cropmarkgap.png" width="140" height="141" alt="media size larger than trim size"/> This command is only effective if you use the <code>cropmarks</code> class option. Note that user-provided cropmarks are <em>very unusual</em> in the print-on demand market. Do not use them unless your print service specifically requests them. The built-in cropmark capability is very elementary, and cannot be easily enhanced by adding other LaTeX packages.</p>
+<p><img class="floatright" src="html-resources/cropmarkgap.png" width="140" height="141" alt="media size larger than trim size"> This command is only effective if you use the <code>cropmarks</code> class option. Note that user-provided cropmarks are <em>very unusual</em> in the print-on demand market. Do not use them unless your print service specifically requests them. The built-in cropmark capability is very elementary, and cannot be easily enhanced by adding other LaTeX packages.</p>
<p>In the accompanying image with cropmarks, a corner of the Trim Size is at lower right. The invisible TrimBox has been drawn with a green line. The cropmark gap is G.</p>
<a id="a4.3"></a>
-<h3>4.3 <img src="html-resources/amb.png" width="30" height="22" alt="emergency icon"/> Emergency Clinic: Rework</h3>
+<h3>4.3 <img src="html-resources/amb.png" width="30" height="22" alt="emergency icon"> Emergency Clinic: Rework</h3>
<div style="padding: 6px 0px 6px 0px; margin:0px 32px 6px 16px; background:#ffe7e7 none"><p class="noindent">Situation: Your book is designed for Trim Size 5.25x8, one of several widely-used American sizes. You have put many hours of work into getting just the right line breaks within paragraphs, and just the right pagination. It looks beautiful. But then you get an e-mail from a British distributor. Could you change to British size B novel format, essentially 5.06x7.81 Trim Size?</p>
<p>Sure, you say. Just needs a little math. Knock 0.095" off each margin. What could be easier? So you try that, but the printer rejects your file. It seems that your original margins were as narrow as they could be, per the printer's specifications. You cannot make them any narrower.</p>
@@ -316,20 +316,20 @@
<p>In the following example, the original font size is 11pt, and the baselineskip (calculated based on other factors) is 14.377pt. After rework, the font size is automatically re-calculated to 10.468pt, with lineskip 13.883pt.</p>
<p class="code">
-<code>\documentclass{novel}<br/>
-\SetTrimSize{5.25in}{8in} % Original. American.<br/>
-\SetMargins{0.36in}{0.4in}{0.38in}{0.65in} % Original. American<br/>
-\ReworkTrimSize{5.06in}{7.81in} % New. Equivalent to British 129mmW x 198mmH.<br/>
+<code>\documentclass{novel}<br>
+\SetTrimSize{5.25in}{8in} % Original. American.<br>
+\SetMargins{0.36in}{0.4in}{0.38in}{0.65in} % Original. American<br>
+\ReworkTrimSize{5.06in}{7.81in} % New. Equivalent to British 129mmW x 198mmH.<br>
\ReworkMargins{12mm}{12mm}{12mm}{15mm} % New. British.
</code></p>
<p>Result with original layout (above Rework commands commented out):</p>
-<p class="centerimg"><img src="html-resources/originalspread.png" width="726" height="544" alt="original spread, before rework"/></p>
+<p class="centerimg"><img src="html-resources/originalspread.png" width="726" height="544" alt="original spread, before rework"></p>
<p>Result after Rework:</p>
-<p class="centerimg"><img src="html-resources/reworkedspread.png" width="700" height="531" alt="spread after rework"/></p>
+<p class="centerimg"><img src="html-resources/reworkedspread.png" width="700" height="531" alt="spread after rework"></p>
<a id="a4.3.4"></a>
@@ -344,8 +344,8 @@
<p>&bull; The biggest obstacle occurs when you specify some internal length in terms of absolute units (such as pt). It is always best to use relative units (such as <code>em</code>, or sometimes <code>\nbs</code>), so that they can be scaled along with the text:</p>
<p class="code">
-Bad: <code>\hspace{6pt}</code> &nbsp; Good: <code>\hspace{0.5em}</code><br/>
-Bad: <code>\kern1pt</code> &nbsp; Good: <code>\kern.08em</code><br/>
+Bad: <code>\hspace{6pt}</code> &nbsp; Good: <code>\hspace{0.5em}</code><br>
+Bad: <code>\kern1pt</code> &nbsp; Good: <code>\kern.08em</code><br>
Bad: <code>\vspace{0.5in}</code> &nbsp; Good: <code>\vspace{2.4\nbs}</code>
</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html
index 4093a12f802..394eb63a993 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 5 - Fonts</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -23,15 +23,15 @@
<li><a href="#a5.1.1">5.1.1 Licensing</a></li>
<li><a href="#a5.1.2">5.1.2 Technical</a></li>
<li><a href="#a5.1.3">5.1.3 Appearance</a></li>
- <li style="margin-bottom:0px;"><a href="#a5.1.4">5.1.4 The Default Fonts</a><br/>
+ <li style="margin-bottom:0px;"><a href="#a5.1.4">5.1.4 The Default Fonts</a><br>
<span style="visibility:hidden">5.1.4 </span>Libertinus and NovelDeco</li>
</ul></li><!-- end 5.1 -->
<li><a href="#a5.2">5.2 Font Names, Files, Features</a>
<ul>
<li><a href="#a5.2.1">5.2.1 Font Family vs. File Name</a></li>
<li><a href="#a5.2.2">5.2.2 Set/New by Family/Filename</a></li>
- <li><a href="#a5.2.3">5.2.3 Open Type Features</a><br/>
- <span style="visibility:hidden">5.2.3 </span>kerning, ligatures, numbers,<br/>
+ <li><a href="#a5.2.3">5.2.3 Open Type Features</a><br>
+ <span style="visibility:hidden">5.2.3 </span>kerning, ligatures, numbers,<br>
<span style="visibility:hidden">5.2.3 </span>letters, and many others</li>
<li><a href="#a5.2.4">5.2.4 Scale Pseudo-Feature</a></li>
<li><a href="#a5.2.5">5.2.5 Color and Opacity</a></li>
@@ -39,9 +39,9 @@
</ul></li><!-- end 5.2 -->
<li><a href="#a5.3">5.3 Setting and Defining Fonts</a>
<ul>
- <li><a href="#a5.3.1">5.3.1 General-Purpose Fonts</a><br/>
+ <li><a href="#a5.3.1">5.3.1 General-Purpose Fonts</a><br>
<span style="visibility:hidden">5.3.1 </span>master, sans, mono</li>
- <li style="margin-bottom:0px;"><a href="#a5.3.2">5.3.2 Novel-Specific Fonts</a><br/>
+ <li style="margin-bottom:0px;"><a href="#a5.3.2">5.3.2 Novel-Specific Fonts</a><br>
<span style="visibility:hidden">5.3.2 </span>chapter, header, and others</li>
<li style="margin-bottom:0px;"><a href="#a5.3.3">5.3.3 New Font Commands</a></li>
<li><a href="#a5.3.4">5.3.4 Which Font Features?</a></li>
@@ -66,7 +66,7 @@
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
<p><b>User Guide</b></p>
@@ -75,11 +75,11 @@
<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>5. Choosing Fonts</p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br/>
+<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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -177,8 +177,8 @@
<p class="centerimg">
-<img src="html-resources/win10libser.png" width="268" height="184" alt="Windows 10 font viewer"/> &nbsp;
-<img src="html-resources/ublibser.png" width="431" height="176" alt="Ubuntu font viewer"/>
+<img src="html-resources/win10libser.png" width="268" height="184" alt="Windows 10 font viewer"> &nbsp;
+<img src="html-resources/ublibser.png" width="431" height="176" alt="Ubuntu font viewer">
</p>
@@ -189,7 +189,7 @@
<p>When you set an existing font, or create a new font command, you can use either the font (family) name, or the specific font file name. However, there may be a big difference in results!</p>
<p style="margin-top:10px"><b>By family name:</b></p>
-<p><img class="floatright" style="padding-top:12px" src="html-resources/fontbyfamily.png" width="338" height="42" alt="font family defined"/> When you use the <em>font family name</em>, you configure all of the Regular, Italic, Bold, and BoldItalic variants. The usual TeX commands will be applied:</p>
+<p><img class="floatright" style="padding-top:12px" src="html-resources/fontbyfamily.png" width="338" height="42" alt="font family defined"> When you use the <em>font family name</em>, you configure all of the Regular, Italic, Bold, and BoldItalic variants. The usual TeX commands will be applied:</p>
<p>Preamble:</p>
<p class="code" style="clear:both"><code>\NewFontFamily\rway{Raleway}</code></p>
<p>Document Body:</p>
@@ -197,7 +197,7 @@
<p style="margin-top:10px"><b>By file names:</b></p>
-<p><img class="floatright" style="padding-top:12px" src="html-resources/fontbyfilenamei.png" width="335" height="44" alt="font file defined"/> However, if you specify the <em>font file name</em>, then <em>only</em> that font file will be used, regardless of requests for bold or italic. Small caps will be honored, if the specific file has them:</p>
+<p><img class="floatright" style="padding-top:12px" src="html-resources/fontbyfilenamei.png" width="335" height="44" alt="font file defined"> However, if you specify the <em>font file name</em>, then <em>only</em> that font file will be used, regardless of requests for bold or italic. Small caps will be honored, if the specific file has them:</p>
<p>Preamble:</p>
<p class="code" style="clear:both"><code>\NewFontFamily\rwayi{Raleway-Regular-Italic.otf}</code></p>
<p>Document Body:</p>
@@ -205,13 +205,13 @@
<p style="margin-top:10px"><b>File Name Combinations:</b></p>
-<p><img class="floatright" style="padding-top:12px" src="html-resources/frankenfont.png" width="312" height="41" alt="frankenfont"/> What you write is what you get. You can customize a font family by individually selecting its members. Here is the syntax.</p>
+<p><img class="floatright" style="padding-top:12px" src="html-resources/frankenfont.png" width="312" height="41" alt="frankenfont"> What you write is what you get. You can customize a font family by individually selecting its members. Here is the syntax.</p>
<p>Preamble:</p>
-<p class="code" style="clear:both"><code>\NewFontFamily\frankenfont[% note the % at linebreaks<br/>
-&nbsp; ItalicFont=BaskervilleF-Italic.otf,%<br/>
-&nbsp; BoldFont=libertinusserif-semibold.otf,%<br/>
-&nbsp; BoldItalicFont=texgyrepagella-bolditalic.otf,%<br/>
+<p class="code" style="clear:both"><code>\NewFontFamily\frankenfont[% note the % at linebreaks<br>
+&nbsp; ItalicFont=BaskervilleF-Italic.otf,%<br>
+&nbsp; BoldFont=libertinusserif-semibold.otf,%<br>
+&nbsp; BoldItalicFont=texgyrepagella-bolditalic.otf,%<br>
]{Raleway-Medium.otf}</code></p>
<p>Document Body:</p>
@@ -220,10 +220,10 @@
<p style="margin-top:10px"><b>Semibold, Light, etc.:</b> The above syntax is especially useful when you wish to specify semibold (if available), rather than bold. It is also a way to select something such as light versions:</p>
-<p class="code"><code>\NewFontFamily\rwlight[% note the % at linebreaks<br/>
-&nbsp; ItalicFont=Raleway-Light-Italic.otf,%<br/>
-&nbsp; BoldFont=Raleway-Medium.otf,%<br/>
-&nbsp; BoldItalicFont=Raleway-Medium-Italic.otf,%<br/>
+<p class="code"><code>\NewFontFamily\rwlight[% note the % at linebreaks<br>
+&nbsp; ItalicFont=Raleway-Light-Italic.otf,%<br>
+&nbsp; BoldFont=Raleway-Medium.otf,%<br>
+&nbsp; BoldItalicFont=Raleway-Medium-Italic.otf,%<br>
]{Raleway-Light.otf}</code></p>
<p>Note that the font file in braces is the one used as the "regular" font, in this definition.</p>
@@ -252,17 +252,17 @@ Some Frequently-Used Open Type Features
<tr>
<td><p>kerning</p></td>
<td><p>kern</p></td>
-<td><p>Kerning=On<br/><em>enabled by default</em></p></td>
+<td><p>Kerning=On<br><em>enabled by default</em></p></td>
</tr>
<tr>
<td><p>common ligatures</p></td>
<td><p>liga</p></td>
-<td><p>Ligatures=Common<br/><em>enabled: mainfont, sansfont</em></p></td>
+<td><p>Ligatures=Common<br><em>enabled: mainfont, sansfont</em></p></td>
</tr>
<tr>
<td><p>Tex ligatures</p></td>
<td><p>tlig</p></td>
-<td><p>Ligatures=TeX<br/><em>enabled by default</em></p></td>
+<td><p>Ligatures=TeX<br><em>enabled by default</em></p></td>
</tr>
<tr>
<td><p>lowercase letters to small caps</p></td>
@@ -282,7 +282,7 @@ Some Frequently-Used Open Type Features
<tr>
<td><p>oldstyle numerals</p></td>
<td><p>onum</p></td>
-<td><p>Numbers=OldStyle<br/><em>enabled: mainfont, sansfont</em></p></td>
+<td><p>Numbers=OldStyle<br><em>enabled: mainfont, sansfont</em></p></td>
</tr>
</tbody>
</table>
@@ -293,16 +293,16 @@ Some Frequently-Used Open Type Features
<p>&bull; The SmallCaps feature applies only to lowercase letters; ordinary capitals remain ordinary capitals. UppercaseSmallCaps deals only with converting ordinary capitals to small caps. If you want both, use both. In most fonts that have them, small caps are slightly taller than lowercase, and slightly more widely spaced. What distinguishes real small caps from fake ones (obtained by scaling ordinary capitals) is that the weight and spacing are more compatible with surrounding text.</p>
-<p class="centerimg"><img src="html-resources/smallcapsrealfake.png" width="478" height="43" alt="real vs fake small caps"/></p>
+<p class="centerimg"><img src="html-resources/smallcapsrealfake.png" width="478" height="43" alt="real vs fake small caps"></p>
<p>&bull; Lining numerals are the ones most familiar to you, from math or accounting. They sit on the baseline and have the height of capital letters. That's just right for doing calculations, and doesn't look bad for things such as page numbers and chapter numbers.</p>
<p>&bull; When lining numerals are mingled with flowing text, they may stand out too much. OldStyle numerals are more like flowing text: Most of the numerals are at lowercase height, with ascenders and descenders. Compare the first number as OldStyle, the second as Lining:</p>
-<p class="centerimg"><img src="html-resources/jollybeers.png" width="499" height="52" alt="oldstyle vs lining numerals"/></p>
+<p class="centerimg"><img src="html-resources/jollybeers.png" width="499" height="52" alt="oldstyle vs lining numerals"></p>
<p>Most fonts use Lining numerals as their default. A few default to OldStyle numerals. Thus, you should explicitly call for the kind of numerals you wish to use.</p>
-<p>&bull; True OldStyle numerals have a flat top on <em>one</em>, and a very round <em>zero</em>: <img src="html-resources/10trueold.png" width="37" height="13" alt="true oldstyle 10"/> This may be a bit distracting. Some fonts use a transitional form, where the one has a tilted top (like big 1) and the zero is not so round: <img src="html-resources/10transold.png" width="37" height="13" alt="transitional oldstyle 10"/> Others offer you a choice, via an Open Type "style set." See the <code>fontspec</code> manual for how to code style sets.</p>
+<p>&bull; True OldStyle numerals have a flat top on <em>one</em>, and a very round <em>zero</em>: <img src="html-resources/10trueold.png" width="37" height="13" alt="true oldstyle 10"> This may be a bit distracting. Some fonts use a transitional form, where the one has a tilted top (like big 1) and the zero is not so round: <img src="html-resources/10transold.png" width="37" height="13" alt="transitional oldstyle 10"> Others offer you a choice, via an Open Type "style set." See the <code>fontspec</code> manual for how to code style sets.</p>
<p>&bull; There are many more Open Type features, most of which are not useful in ordinary fiction writing. Fonts rarely have more than a few features. Some features (such as the ones shown above) have a specific meaning. Other features, such as "style sets", have whatever meaning the font designer assigns them; Thus the "ss03" feature of one font may do something very different from "ss03" in a different font.</p>
@@ -320,7 +320,7 @@ Some Frequently-Used Open Type Features
<p class="code"><code>The message was brief: \textls{\orbitron DIE, EARTHLING.} Captain Withens smiled as he oiled his ray-gun. But ray-guns don't use oil.\par</code></p>
-<p class="centerimg"><img src="html-resources/charscaletext.png" width="522" height="63" alt="charscale text"/>
+<p class="centerimg"><img src="html-resources/charscaletext.png" width="522" height="63" alt="charscale text">
<p>Scale is more often used for fonts that are pre-defined to have a special meaning and location, such as chapter titles or page headers. There, the font is not mingled with ordinary text, and it is OK to use a larger Scale. Then, it is not necessary to use local font scaling commands each time the font is used.</p>
@@ -412,7 +412,7 @@ Some Frequently-Used Open Type Features
<p>Class <code>novel</code> comes with a variety of pre-configured header/footer styles and chapter titles. These are described in detail on other documentation pages. You do not have to set these unless you wish to do so, because all of them (except <code>decofont</code> will default to variations on the main font.</p>
<p>Each of these font commands has an "intended" usage, shown in the following map. When you allow <code>novel</code> to style your document, it will automatically choose the right font for the right place. But if you create custom styles, you will have to specify the fonts.</p>
-<p class="centerimg"><img src="html-resources/fonts-in-use.png" width="660" height="530" alt="map of standard font locations"/></p>
+<p class="centerimg"><img src="html-resources/fonts-in-use.png" width="660" height="530" alt="map of standard font locations"></p>
<div class="fontcommand">
<pre><b>chapterfont</b></pre>
@@ -484,18 +484,18 @@ Some Frequently-Used Open Type Features
<p>You have a font. It has Open Type features. But which features does it have? There are several ways to find out, but the simplest and most reliable way is to request a feature, and see what happens. For example:</p>
<p class="code"><code>
-% !TeX program = LuaLaTeX<br/>
-% !TeX encoding = UTF-8<br/>
-\documentclass{novel}<br/>
-\setlength\parindent{0pt}<br/>
-%<br/>
-\NewFontFace\testlibserit[VerticalPosition=Superior]{libertinusserif-italic.otf}<br/>
-\NewFontFace\testcin[VerticalPosition=Superior]{Cinzel-Regular.otf}<br/>
-%<br/>
-\begin{document}<br/>
-Libertinus Serif, Italic:\\{\testlibserit 0123456789 abcdefghijklmnopqrstuvwxyz \#‡}\par<br/>
-\null<br/>
-Cinzel, Regular:\\{\testcin 0123456789 abcdefghijklmnopqrstuvwxyz \#‡}\par<br/>
+% !TeX program = LuaLaTeX<br>
+% !TeX encoding = UTF-8<br>
+\documentclass{novel}<br>
+\setlength\parindent{0pt}<br>
+%<br>
+\NewFontFace\testlibserit[VerticalPosition=Superior]{libertinusserif-italic.otf}<br>
+\NewFontFace\testcin[VerticalPosition=Superior]{Cinzel-Regular.otf}<br>
+%<br>
+\begin{document}<br>
+Libertinus Serif, Italic:\\{\testlibserit 0123456789 abcdefghijklmnopqrstuvwxyz \#‡}\par<br>
+\null<br>
+Cinzel, Regular:\\{\testcin 0123456789 abcdefghijklmnopqrstuvwxyz \#‡}\par<br>
\end{document}\par</code></p>
@@ -524,10 +524,10 @@ Cinzel, Regular:\\{\testcin 0123456789 abcdefghijklmnopqrstuvwxyz \#‡}\par<br
<p>Two ways to accomplish the same thing:</p>
<p class="code"><code>
-\NewFontFamily\baskf{BaskervilleF}<br/>
-\NewFontFamily\baskftab[Numbers=Monospaced]{BaskervilleF} % tnum feature<br/>
-\begin{document}<br/>
-Some text {\baskftab hello 123} is here.<br/>
+\NewFontFamily\baskf{BaskervilleF}<br>
+\NewFontFamily\baskftab[Numbers=Monospaced]{BaskervilleF} % tnum feature<br>
+\begin{document}<br>
+Some text {\baskftab hello 123} is here.<br>
Some text {\baskf\addfontfeature{Numbers=Monospaced} hello 123} is here.
</code></p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html
index 3e3d6ea9a07..b06fb19eb97 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 6 - Headers and Footers</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -19,7 +19,7 @@
<ul>
<li><a href="#a6.1">6.1 Global Header/Footer Settings</a>
<ul>
- <li><a href="#a6.1.1">6.1.1 \SetHeadJump{}<br/><span style="visibility:hidden">6.1.1 </span>\SetFootJump{}</a></li>
+ <li><a href="#a6.1.1">6.1.1 \SetHeadJump{}<br><span style="visibility:hidden">6.1.1 </span>\SetFootJump{}</a></li>
<li><a href="#a6.1.2">6.1.2 \SetHeadFootStyle{}</a>
<li><a href="#a6.1.3">6.1.3 \SetEmblems{}{}</a></li>
<li><a href="#a6.1.4">6.1.4 \SetPageNumberStyle{}</a></li>
@@ -30,7 +30,7 @@
</li><!-- end 6.1 -->
<li><a href="#a6.2">6.2 Local Header/Footer Settings</a>
<ul>
- <li><a href="#a6.2.1">6.2.1 \SetVersoHeadText{}<br/><span style="visibility:hidden">6.2.1 </span>\SetRectoHeadText{}</a></li>
+ <li><a href="#a6.2.1">6.2.1 \SetVersoHeadText{}<br><span style="visibility:hidden">6.2.1 </span>\SetRectoHeadText{}</a></li>
<li><a href="#a6.2.2">6.2.2 \thispagestyle{}</a>
</ul>
</li><!-- end 6.2 -->
@@ -49,7 +49,7 @@
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
@@ -59,11 +59,11 @@
<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>6. Headers, Footers<br/>
+<p>6. Headers, Footers<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><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -101,52 +101,69 @@
<p>&nbsp;</p>
-
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot1.png" width="276" height="219" alt="style 1" title="style 1"/>
+<img class="floatright" src="html-resources/headfoot1.png" width="276" height="219" alt="style 1" title="style 1">
+<pre>
<b>\SetHeadFootStyle{1}</b></pre>
-<p>Only header.<br/>
-Page number at outside (left verso, right recto).<br/>
-Optional emblem adjacent to page number.<br/>
-Text centered. Default author verso, title recto.<br/>
+<p>Only header.<br>
+Page number at outside (left verso, right recto).<br>
+Optional emblem adjacent to page number.<br>
+Text centered. Default author verso, title recto.<br>
<em>This is the default for the novel document class.</em></p>
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot2.png" width="276" height="219" alt="style 2" title="style 2"/>
+<div style="clear:both"></div>
+
+<img class="floatright" src="html-resources/headfoot2.png" width="276" height="219" alt="style 2" title="style 2">
+<pre>
<b>\SetHeadFootStyle{2}</b></pre>
-<p>Only footer.<br/>
-Page number at outside (left verso, right recto).<br/>
+<p>Only footer.<br>
+Page number at outside (left verso, right recto).<br>
Optional emblem adjacent to page number.</p>
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot3.png" width="276" height="219" alt="style 3" title="style 3"/>
+<div style="clear:both"></div>
+
+<img class="floatright" src="html-resources/headfoot3.png" width="276" height="219" alt="style 3" title="style 3">
+<pre>
<b>\SetHeadFootStyle{3}</b></pre>
-<p>Only footer.<br/>
-Page number centered.<br/>
+<p>Only footer.<br>
+Page number centered.<br>
Disregards emblem, if coded.</p>
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot4.png" width="276" height="219" alt="style 4" title="style 4"/>
+<div style="clear:both"></div>
+
+<img class="floatright" src="html-resources/headfoot4.png" width="276" height="219" alt="style 4" title="style 4">
+<pre>
<b>\SetHeadFootStyle{4}</b></pre>
-<p>Only header.<br/>
-Page number at outside (left verso, right recto).<br/>
-Optional emblem adjacent to page number.<br/>
-Text towards outside, instead of centered.<br/>
-Text begins or ends 1em from the emblem.<br/>
+<p>Only header.<br>
+Page number at outside (left verso, right recto).<br>
+Optional emblem adjacent to page number.<br>
+Text towards outside, instead of centered.<br>
+Text begins or ends 1em from the emblem.<br>
Default author verso, title recto.</p>
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot5.png" width="276" height="219" alt="style 5" title="style 5"/>
+<div style="clear:both"></div>
+
+<img class="floatright" src="html-resources/headfoot5.png" width="276" height="219" alt="style 5" title="style 5">
+<pre>
<b>\SetHeadFootStyle{5}</b></pre>
-<p>Header and Footer.<br/>
-Page number centered in footer.<br/>
-Disregards emblem, if coded.<br/>
-Text centered in header.<br/>
+<p>Header and Footer.<br>
+Page number centered in footer.<br>
+Disregards emblem, if coded.<br>
+Text centered in header.<br>
Default author verso, title recto.</p>
-<pre style="clear:both"><img class="floatright" src="html-resources/headfoot6.png" width="276" height="219" alt="style 6" title="style 6"/>
+<div style="clear:both"></div>
+
+<img class="floatright" src="html-resources/headfoot6.png" width="276" height="219" alt="style 6" title="style 6">
+<pre>
<b>\SetHeadFootStyle{6}</b></pre>
-<p>Only header.<br/>
-Page number at outside (left verso, right recto).<br/>
-Optional emblem adjacent to page number.<br/>
-Text towards inside, instead of centered.<br/>
+<p>Only header.<br>
+Page number at outside (left verso, right recto).<br>
+Optional emblem adjacent to page number.<br>
+Text towards inside, instead of centered.<br>
Default author verso, title recto.</p>
+<div style="clear:both"></div>
+
<h5>Custom Style</h5>
<p>Before you think about writing custom header/footer styles, be sure to try the pre-configured choices. I have looked through a lot of fiction of all kinds. The pre-configured choices include every style I have seen, with the exception of the most highly decorative.</p>
<p>If none of the above are satisfactory, then you can write your own headers and footers using the syntax of the <code>fancyhdr</code> package.</p>
@@ -163,20 +180,20 @@ Default author verso, title recto.</p>
<p>If the style supports it, you may place an "emblem" that appears at a fixed distance (2.5em} from the outer margin. Thus, it will appear to the right of the page number on verso pages, and to the left of the page number on recto pages. In the case of style <code>4</code>, there will be a clearance of 1em between the emblem and the header text.</p>
<p>The font used for emblems will be the same as the headfont, unless you code the emblem to use a different font (perhaps one you specified with the <code>\NewFontFace</code> command), or unless you use one of the built-in <code>\decoglyph</code> codes.</p>
<p>An emblem is a minor decoration that should not distract the eye from the main text.</p>
-<p><img class="floatright" src="html-resources/emblembar.png" width="380" height="104" alt="simple emblems using vertical bar"/>&bull; Most books do not use emblems. When they do, it is typically a vertical bar, or a bullet, like this:</p>
+<p><img class="floatright" src="html-resources/emblembar.png" width="380" height="104" alt="simple emblems using vertical bar">&bull; Most books do not use emblems. When they do, it is typically a vertical bar, or a bullet, like this:</p>
<p class="code"><code>\SetHeadFootStyle{4}</code></p>
<p class="code"><code>\SetEmblems{|}{|}</code></p>
<p>The verso and recto emblems may be different. Whether they are the same or not, you must set them both, if you use emblems. Blanks are allowed.</p>
-<p><img class="floatright" src="html-resources/emblemdingbats.png" width="380" height="104" alt="dingbat emblems"/>&bull; Emblems may be styled. For example:</p>
+<p><img class="floatright" src="html-resources/emblemdingbats.png" width="380" height="104" alt="dingbat emblems">&bull; Emblems may be styled. For example:</p>
<p>The header emblems shown at right were produced using the code below. Dingbats from the NovelDeco font were specified, adjusted for size and position.</p>
<p style="clear:both" class="code"><code>\SetEmblems{\charscale{1.1}{\raisebox{-0.05em}{\decoglyph{l9825}}}}%</code></p>
<p class="code"><code>{\charscale{1.1}{\raisebox{-0.05em}{\decoglyph{l9826}}}}</code></p>
<p>&bull; You may also use images, or combined images and text. If you use images, they must be at the exact resolution required by your print service (usually 300dpi for gray, 600dpi for b/w), and at exact size without scaling. The <code>\InlineImage</code> command must be used. See novel's image documentation details. You may find that a vertical offset of <code>\nfs</code> (normal font size) is useful, as this will place the top of the emblem image at the top margin.</p>
-<p class="code" style="text-indent:0px"><img class="floatright" src="html-resources/emblemimg.png" width="295" height="77" alt="emblem image"/>
-<code>\SetHeadFootStyle{4}<br/>
-\SetEmblems{\InlineImage[0pt,b]{spy.png}}%<br/>
+<p class="code" style="text-indent:0px"><img class="floatright" src="html-resources/emblemimg.png" width="295" height="77" alt="emblem image">
+<code>\SetHeadFootStyle{4}<br>
+\SetEmblems{\InlineImage[0pt,b]{spy.png}}%<br>
{\InlineImage[0pt,b]{spy.png}}
</code></p>
@@ -189,7 +206,7 @@ Default author verso, title recto.</p>
<h4>6.1.4 <code>\SetPageNumberStyle{<em>code using \thepage</em>}</code></h4>
<p>By default, the page number is simply <code>\thepage</code>. In most cases, leave it that way. But if you wish to change how the page number is displayed, you can use this command to style how <code>\thepage</code> is displayed. Examples:</p>
-<p class="code" style="text-indent:0px"><code>\SetPageNumberStyle{\emph{thepage}} % Page number in italics.<br/>
+<p class="code" style="text-indent:0px"><code>\SetPageNumberStyle{\emph{thepage}} % Page number in italics.<br>
\SetPageNumberStyle{-- \thepage --} % En-dash on each side of number, for headstyle 3 or 5.</code></p>
<p>The headfont is applied automatically, unless you over-ride it in your code.</p>
<p>You could also get more involved, using a different font or size. Avoid over-doing it. If you are tempted to use a macro that counts page numbers backwards, be aware that your print service will likely reject it. Anyway, it has already been done in fiction.</p>
@@ -205,7 +222,7 @@ Default author verso, title recto.</p>
<h4>6.1.6 <code>\SetLooseHead{<em>number</em>}</code></h4>
<p>This command applies to both headers and footers.</p>
<p>If you are using a style that has header text, then for best appearance the characters should appear with a little extra space between them, so that they are more easily distinguished from the main text. This is especially true if you are using small caps. The name for such adjustment is "tracking."</p>
-<p class="centerimg"><img src="html-resources/looseheads.png" width="400" height="76" alt="loosehead 50 and 100"/></p>
+<p class="centerimg"><img src="html-resources/looseheads.png" width="400" height="76" alt="loosehead 50 and 100"></p>
<p>The argument of <code>\SetLooseHead</code> is a number from 0 to 1000. At <code>0</code> there is no extra space between the letters. Values from <code>50</code> (default) to <code>200</code> are most useful. Higher values are unusual.</p>
<p>Page number tracking will be clamped at a maximum of 50, even when a larger (looser) tracking is applied to text.</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html
index b9e2f6198f3..1ea6b810aab 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 7 - Text Sizes and Styling</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -58,7 +58,7 @@
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
<p><b>User Guide</b></p>
@@ -67,11 +67,11 @@
<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-06-header-footer.html">6. Headers, Footers</a><br>
<p>7. Text Sizes, Styles</p>
<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -119,10 +119,10 @@
<p>Here is an example illustrating the command in all its glory:</p>
-<p class="code"><img class="floatright" src="html-resources/badaboom.png" width="146" height="102" alt="badaboom"/><code>
-Bada \charscale*[1.25,5em,1.3\nbs]{Boom} Bam\par<br/>
-Bada Bam\par<br/>
-Bada\charscale[1.25,5em,1.3\nbs]{Bang} Bam\par<br/>
+<p class="code"><img class="floatright" src="html-resources/badaboom.png" width="146" height="102" alt="badaboom"><code>
+Bada \charscale*[1.25,5em,1.3\nbs]{Boom} Bam\par<br>
+Bada Bam\par<br>
+Bada\charscale[1.25,5em,1.3\nbs]{Bang} Bam\par<br>
Bada \charscale[1.25]{Bang} Bam\par
</code></p>
@@ -132,7 +132,7 @@ Bada \charscale[1.25]{Bang} Bam\par
<p class="code"><code>\FirstLine{\noindent\charscale[1.5]{I}t was a dark and stormy night. Lord Withens mounted his horse and rode through the gloom to Castle McDingle, where Baron von Feathering awaited. The pair had dirty deeds to do, but being members of the nobility, they commanded a high price.}</code></p>
-<p class="centerimg"><img src="html-resources/mcdingle.png" width="559" height="121" alt="larger first letter"/></p>
+<p class="centerimg"><img src="html-resources/mcdingle.png" width="559" height="121" alt="larger first letter"></p>
<p>In the above example, the initial I is 1.5x its normal size. It appears larger than that, by comparison to the adjacent small caps letters.</p>
@@ -198,17 +198,17 @@ Bada \charscale[1.25]{Bang} Bam\par
<p><code><b>\allsmcp{<em>text</em>}</b></code> places both uppercase and lowercase letters in small caps. If the font has the <code>c2sc</code> feature, it will be used; if not, the letters will be converted to lowercase first. Then, <code>smcp</code> is applied.</p>
<p>&bull; If you require small caps, but your font does not have them, you can fake them by scaling uppercase. But this is usually unattractive. A better method is described in the <code>fontspec</code> package documentation: You may appoint a different font that will provide small caps.</p>
<p>&bull; If you insist on using old-fashioned TeX fonts, which do not have the <code>smcp</code> Open Type feature, then you may need to write this code in the Preamble:</p>
-<p class="code"><code>\let\smcp\oldscshape\relax<br/>
-\let\textsc\oldscshape\relax<br/>
+<p class="code"><code>\let\smcp\oldscshape\relax<br>
+\let\textsc\oldscshape\relax<br>
\let\scshape\oldscshape\relax</code></p>
<p>The above code sends you in a time machine back to the Twentieth Century.</p>
<p><code><b>\acronym{<em>text</em>}</b></code> is special to <code>novel</code>. If the NovelDeco font is installed, uppercase letters in the text will be converted to "mid-size capitals," and lowercase will remain lowercase, but with ascenders slightly reduced. The purpose of this command is so that acronyms such as NASA and NATO blend well with surrounding text. I have found that whereas ordinary uppercase is too conspicuous, small caps also looks wrong. Example:</p>
-<p class="code"><img class="floatright" src="html-resources/acronym2.png" width="192" height="89" alt="acronym"/>
+<p class="code"><img class="floatright" src="html-resources/acronym2.png" width="192" height="89" alt="acronym">
<code>
-The NATO alliance...\par<br/>
-The \acronym{NATO} alliance...\par<br/>
+The NATO alliance...\par<br>
+The \acronym{NATO} alliance...\par<br>
The \allsmcp{NATO} alliance...\par
</code></p>
@@ -265,16 +265,16 @@ The \allsmcp{NATO} alliance...\par
<p><code><b>\color{<em>name</em>}</b></code> or <code><b>\color[gray]{<em>scale</em>}</b></code> is used within a group. All text will be in grayscale, from where the command is placed, until the group ends. If the command is not at the beginning of the group, it does not affect prior text. Example:</p>
<p class="code"><code>
-\begingroup<br/>
-This text is unaffected by the following command.<br/>
-\color{lightgray} % Alternative: \color[gray]{number 0 to 1}<br/>
-This text is in lightgray, until the group ends.<br/>
+\begingroup<br>
+This text is unaffected by the following command.<br>
+\color{lightgray} % Alternative: \color[gray]{number 0 to 1}<br>
+This text is in lightgray, until the group ends.<br>
\endgroup
</code></p>
<p style="margin-top:10px"><code><b>\textcolor{<em>text</em>}</b></code> or <code><b>\textcolor[gray]{<em>scale</em>}{<em>text</em>}</b></code> affects only the included text.</p>
-<p class="code"><code>\textcolor{gray7}{This text is in color gray7, a medium-light gray.}<br/>
+<p class="code"><code>\textcolor{gray7}{This text is in color gray7, a medium-light gray.}<br>
\textcolor[gray]{0.32}{This text is in 32 percent gray.}</code></p>
<p style="margin-top:10px">Whether you use <code>\color</code> or <code>\textcolor</code>, there are two ways to specify the color: by name, or by scale, using package <code>xcolor</code> syntax.</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html
index 681a603cce9..31b8a524b84 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Class novel - 8 - Images</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -48,7 +48,7 @@
<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.7.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
<p><b>User Guide</b></p>
@@ -57,11 +57,11 @@
<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-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>8. Using Images</p>
-<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p><a href="noveldocs-09-chapters-displays.html">9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</a></p>
</div>
@@ -127,7 +127,7 @@
<p>When you export your image, you may be asked whether or not to save the resolution. Be sure to save it.</p>
<p>Example dialog boxes for grayscale png exported from GIMP:</p>
-<p class="centerimg"><img src="html-resources/imgdialogs.png" width="600" height="192" alt="png image with resolution"/></p>
+<p class="centerimg"><img src="html-resources/imgdialogs.png" width="600" height="192" alt="png image with resolution"></p>
<a id="a8.2.2"></a>
@@ -221,7 +221,7 @@
<p>After a few moments, the Terminal will show some information. It should say that the type is grayscale, at 8 bits per pixel. The resolution is 118.11 pixels per centimeter (which is 300dpi). The page geometry, divided by 300, will give you the image size in inches (thus, a page geometry of 900+1200+0+0 represents an image 3" wide x 4" high).</p>
-<p class="floatright"><img src="html-resources/pngcolortype.png" width="270" height="46" alt="png color type"/><br/><img src="html-resources/jpgcolorspace.png" width="296" height="46" alt="jpg colorspace"/></p>
+<p class="floatright"><img src="html-resources/pngcolortype.png" width="270" height="46" alt="png color type"><br><img src="html-resources/jpgcolorspace.png" width="296" height="46" alt="jpg colorspace"></p>
<p>Most important of all: Scroll through the information. Near its end, you should see a line like this. The exact wording will depend on your software:</p>
<p class="code" style="clear:both">(For png images) &nbsp; <code>png: IHDR.color_type: 0 (grayscale)</code></p>
@@ -289,7 +289,7 @@
<p>Offsets may be written as combinations of lengths. If you use the baseline <code>b</code> as above, it must be the first character of voffset. If you use <code>\widthof</code> or <code>\heightof</code>, then its backslash must be the first character <em>unless</em> it is preceded by another length. Thus, an offset of <code>-\heightof{X}</code> is prohibited, but you can use <code>0pt-\heightof{X}</code>.
<p>Here are some examples of allowable code:</p>
<p class="code"><code>
-\InlineImage[2.3em, -0.4em]{imageFile.png}<br/>
+\InlineImage[2.3em, -0.4em]{imageFile.png}<br>
\InlineImage[0pt-\widthof{eee}, b+\heightof{X}-0.2em]{imageFile.jpg}
</code></p>
<p>The image occupies zero vertical space. So, it will not push apart baselines. The next line(s) of text may overlie the image. In some cases, this is desirable. If you do not want that effect, then you can either insert a suitable number of <code>\null</code> lines after the image, or use <code>\BlockImage</code> instead.</p>
@@ -318,11 +318,11 @@
<p>Example:</p>
<p class="code"><code>
-\noindent\InlineImage*[0pt,1.2\nbs]{gavel.png} Lord Withens took a seat at the rear of the courtroom, attempting to be inconspicuous. Yet his effort was in vain, as he was the only person there with a riding crop and spurs.\par<br/>
+\noindent\InlineImage*[0pt,1.2\nbs]{gavel.png} Lord Withens took a seat at the rear of the courtroom, attempting to be inconspicuous. Yet his effort was in vain, as he was the only person there with a riding crop and spurs.\par<br>
He would have taken the car, had it not been stolen. But that was why he was here, at the arraignment of the person charged with the theft. It was most unfortunate that the accused was his own elderly father; but then, theft ran in the family line.\par
</code></p>
-<p class="centerimg"><img src="html-resources/inlineimagest.png" width="651" height="249" alt="example of InlineImage*"/></p>
+<p class="centerimg"><img src="html-resources/inlineimagest.png" width="651" height="249" alt="example of InlineImage*"></p>
@@ -344,13 +344,13 @@ He would have taken the car, had it not been stolen. But that was why he was her
<p>Example:</p>
<p class="code">
<code>
-It was a dark and stormy night. Lord Withens mounted his horse and rode through the darkness, accidentally trampling some petunias in Her Ladyship's garden.\par<br/>
-\BlockImage[l]{gnome.png}[\begin{adjustwidth}{8em}{0pt}\forceindent Suddenly he was confronted by an irate gnome, who expressed an opinion in the crudest of language, even for a gnome.\par<br/>
-Lord Withens was taken aback. How dare this mere gnome speak to him in such a tone of voice? But then he remembered that the gnomes had gone to college, where swearing was routine.\par\end{adjustwidth}]<br/>
+It was a dark and stormy night. Lord Withens mounted his horse and rode through the darkness, accidentally trampling some petunias in Her Ladyship's garden.\par<br>
+\BlockImage[l]{gnome.png}[\begin{adjustwidth}{8em}{0pt}\forceindent Suddenly he was confronted by an irate gnome, who expressed an opinion in the crudest of language, even for a gnome.\par<br>
+Lord Withens was taken aback. How dare this mere gnome speak to him in such a tone of voice? But then he remembered that the gnomes had gone to college, where swearing was routine.\par\end{adjustwidth}]<br>
\charscale[1, 5\nbs]{CENSORED}\forceindent Lord Withens shrugged, and rode on. There was nothing to do but remain silent, this time taking more care. He would speak with his wife about the gnome situation when he returned.\par
</code></p>
-<p class="centerimg"><img src="html-resources/irategnome.png" width="639" height="423" alt="example of BlockImage with accompanying text"/></p>
+<p class="centerimg"><img src="html-resources/irategnome.png" width="639" height="423" alt="example of BlockImage with accompanying text"></p>
<p>In the above example, the text to the right of the image happens to have just the right number of lines to fill the available area. But that is only because I wrote it that way. If I had written less, then there would be one or more blank lines before the subsequent text ("Lord Withens shrugged..."). If I had written more, then the subsequent text would have been pushed down by the necessary number of lines, and there would have been more white area underneath the gnome.</p>
<p>Thus, this technique requires careful inspection, particularly if there is the danger that the image or accompanying text may overflow the bottom of the page.</p>
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
index 96cb3aa35ea..a5ff7f9ceb0 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
@@ -1,9 +1,9 @@
<!DOCTYPE html>
<html lang="en">
<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Novel class documentation - Display, Start, Continued Pages, Footnotes, Endnotes</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css"/>
+<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
</head>
<body>
@@ -14,12 +14,12 @@
<p>Document class "novel"</p>
-<p><a href="#a9">Display, Start, and Continued Pages;<br/>
+<p><a href="#a9">Display, Start, and Continued Pages;<br>
Footnotes and Endnotes</a></p>
<ul>
- <li><a href="#a9.1">9.1 Display Pages</a><br/>
+ <li><a href="#a9.1">9.1 Display Pages</a><br>
<span style="visibility:hidden">9.1 </span> including blank
<ul>
<li><a href="#a9.1.1">9.1.1 Half-Title</a></li>
@@ -41,17 +41,17 @@ Footnotes and Endnotes</a></p>
<li><a href="#a9.2">9.2 Start Pages: General</a>
<ul>
<li><a href="#a9.2.1">9.2.1 \thispagestyle{}</a></li>
- <li><a href="#a9.2.2">9.2.2 \SetVersoHeadText{}<br/>
+ <li><a href="#a9.2.2">9.2.2 \SetVersoHeadText{}<br>
<span style="visibility:hidden">9.2.2 </span>\SetRectoHeadText{}</a>
</li>
</ul>
</li><!-- end 9.2 -->
- <li><a href="#a9.3">9.3 Start Pages in Front Matter</a><br/>
+ <li><a href="#a9.3">9.3 Start Pages in Front Matter</a><br>
<span style="visibility:hidden">9.3 </span>Foreword, Preface, etc.
</li><!-- end 9.3 -->
- <li><a href="#a9.4">9.4 Start Pages in Main Matter</a><br/>
+ <li><a href="#a9.4">9.4 Start Pages in Main Matter</a><br>
<span style="visibility:hidden">9.3 </span>New Chapters
<ul>
<li><a href="#a9.4.1">9.4.1 \SetChapterStart{}</a></li>
@@ -73,7 +73,7 @@ Footnotes and Endnotes</a></p>
</ul>
</li><!-- end 9.4 -->
- <li><a href="#a9.5">9.5 Continued Pages</a><br/>
+ <li><a href="#a9.5">9.5 Continued Pages</a><br>
<ul>
<li><a href="#a9.5.1">9.5.1 \QuickChapter[]{}</a></li>
<li><a href="#a9.5.2">9.5.2 Scene Breaks</a>
@@ -90,15 +90,15 @@ Footnotes and Endnotes</a></p>
<li><a href="#a9.6">9.6 Footnotes</a>
<ul>
<li><a href="#a9.6.1">9.6.1 \SetMarkers[]{}</a></li>
- <li><a href="#a9.6.2">9.6.2 \realmarker \fakemarker</li>
- <li><a href="#a9.6.3">9.6.3 \footnote[]{}</li>
+ <li><a href="#a9.6.2">9.6.2 \realmarker \fakemarker</a></li>
+ <li><a href="#a9.6.3">9.6.3 \footnote[]{}</a></li>
</ul>
</li><!-- end 9.6 -->
<li><a href="#a9.7">9.7 Endnotes</a>
<ul>
<li><a href="#a9.7.1">9.7.1 \endnote</a></li>
- <li><a href="#a9.7.2">9.7.2 \endnotetext{}{}</li>
+ <li><a href="#a9.7.2">9.7.2 \endnotetext{}{}</a></li>
</ul>
</li><!-- end 9.7 -->
@@ -112,7 +112,7 @@ Footnotes and Endnotes</a></p>
<div id="main">
<a id="a9"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.0.8.</p>
+<p>Documentation version: 1.0.9.</p>
<div class="pagetopage">
@@ -122,17 +122,17 @@ Footnotes and Endnotes</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-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. Display, Start Pages;<br/>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br/>
+<p>9. Display, Start Pages;<br>
+<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
<span style="visibility:hidden">9. </span>Footnotes, Endotes.</p>
</div>
-<h2 style="clear:none">Display, Start, and Continued Pages;<br/>
+<h2 style="clear:none">Display, Start, and Continued Pages;<br>
Footnotes and Endnotes</h2>
<p>A <em>display page</em> stands by itself, has a unique purpose, and is never continued to another page. A blank page is considered to be a display, even when there are several blanks.</p>
@@ -160,7 +160,11 @@ Footnotes and Endnotes</h2>
<p>If the preceding material ended with <code>\clearpage</code> or the following material begins with it, no problem. TeX wisely assumes that consecutive <code>\clearpage</code> commands are a mistake, and does not automatically skip a page between them. The <code>\null</code> command is the most effective way to show that you really did mean to create a page there.</p>
-<p>A novel, or collection of stories, may contain these display pages: Half-Title, Frontispiece, Title, Copyright, Dedication, Epigraph, Map, Acknowledgements, Separator.</p>
+<p>A novel, or collection of stories, may contain these display pages: Half-Title, Frontispiece, Title, Copyright, Dedication, Epigraph, Map, Acknowledgements, Separator. Almost all of them, if used, are in front matter.</p>
+
+<p>Note that a book's front matter does not have to be complicated. Here is an imitation of the entire front matter, from a detective novel written by a very famous author of such things. In order: Half-Title, Blank, Title, Copyright, duplicate Half-Title, Blank. A very decorative font is used for the book's title and the author's name.</p>
+
+<p class="centerimg"><img src="html-resources/fmsimple.png" width="716" height="177" alt="simple front matter"></p>
@@ -169,17 +173,17 @@ Footnotes and Endnotes</h2>
<p>Historically, the purpose of a Half-Title was to protect the title page during transportation and storage. This purpose has been obsolete for a long time, bcause modern books are printed and bound at once. But the tradition lives on. Use a Half-Title unless you absolutely must reduce the page count of your book.</p>
-<p>The Half-Title is the first page of front matter. It is lowercase roman page <cide>i</code>, even though the number is not printed. The only material on the page is the book's title (not author) and usually not even a subtitle. If the title is artistically designed, then the Half-Title may be designed the same way, but is usually at smaller size. Place the Half-Title wherever it looks good on the page (certainly not at top left). For example:</p>
+<p>The Half-Title is the first page of front matter. It is lowercase roman page <code>i</code>, even though the number is not printed. The only material on the page is the book's title (not author) and usually not even a subtitle. If the title is artistically designed, then the Half-Title may be designed the same way, but is usually at smaller size. Place the Half-Title wherever it looks good on the page (certainly not at top left). For example:</p>
-<p class="code"><code><img class="floatright" src="html-resources/htss.png" width="174" height="269" alt="sample half title"/>
-<small>\frontmatter <span class="ap">% Sets page numbers to lowercase roman.</span><br/>
-\thispagestyle{empty} <span class="ap">% No header or footer.</span><br/>
-\vspace*{6\nbs} <span class="ap">% Note asterisk. Skips 6 lines.</span><br/>
-<span class="ap">% Right-aligns half-title at 2x normal font size:</span><br/>
- <span class="ap">% \orbitron is defined as the non-TeX font Orbitron-Medium.otf</span><br/>
+<p class="code"><code><img class="floatright" src="html-resources/htss.png" width="174" height="269" alt="sample half title">
+<small>\frontmatter <span class="ap">% Sets page numbers to lowercase roman.</span><br>
+\thispagestyle{empty} <span class="ap">% No header or footer.</span><br>
+\vspace*{6\nbs} <span class="ap">% Note asterisk. Skips 6 lines.</span><br>
+<span class="ap">% Right-aligns half-title at 2x normal font size:</span><br>
+ <span class="ap">% \orbitron is defined as the non-TeX font Orbitron-Medium.otf</span><br>
\stake\hfill{\orbitron\charscale[2]{Star Smash}}\par
\vspace{0.4\nbs}
-<span class="ap">% Decorative portion of half-title:</span><br/>
+<span class="ap">% Decorative portion of half-title:</span><br>
\noindent\hspace{12em}\charscale[1.6]{\decoglyph{r10059}}
\bigemdash[2,2]\stake\par
\clearpage <span class="ap">% Ends the page.</span>
@@ -191,7 +195,7 @@ Footnotes and Endnotes</h2>
<a id="a9.1.2"></a>
<h4 style="clear:both">9.1.2 Frontispiece (usually blank)</h4>
-<p><img class="floatright" src="html-resources/blakemilt.png" width="200" height="309" alt="sample artwork frontispiece" title="Frontispiece to William Blake's poem about Milton. Public Domain in U.S.A. and artist's home nation. Source Library of Congress via Wikimedia Commons."/> The verso of the Half-Title has page number <code>ii</code>, number not printed. Normally, this page is blank.</p>
+<p><img class="floatright" src="html-resources/blakemilt.png" width="200" height="309" alt="sample artwork frontispiece" title="Frontispiece to William Blake's poem about Milton. Public Domain in U.S.A. and artist's home nation. Source Library of Congress via Wikimedia Commons."> The verso of the Half-Title has page number <code>ii</code>, number not printed. Normally, this page is blank.</p>
<p>In the good old days (looong ago), this page might show an illustration. Search the Internet for "frontispiece" to see examples. At right is the frontispiece by William Blake for his poetry regarding Milton. In the original, it was in color (spectacularly expensive, back then).</p>
@@ -201,13 +205,13 @@ Footnotes and Endnotes</h2>
<p>The preparation and placement of images is described on another documentation page.</p>
-<p class="clear:both"><img class="floatright" style="margin-top:40px" src="html-resources/blfr.png" width="134" height="207" alt="sample blank frontispiece"/> Some publishers put a centered list of &ldquo;Books by the Same Author&rdquo; here. Or, if the particular book is part of a set (&ldquo;Splork Chronicles, Volume VI&rdquo;) that can be mentioned. However, in the print-on-demand market, your printing and distribution service may not permit you to do that, unless they carry all of the books.</p>
+<p class="clear:both"><img class="floatright" style="margin-top:40px" src="html-resources/blfr.png" width="134" height="207" alt="sample blank frontispiece"> Some publishers put a centered list of &ldquo;Books by the Same Author&rdquo; here. Or, if the particular book is part of a set (&ldquo;Splork Chronicles, Volume VI&rdquo;) that can be mentioned. However, in the print-on-demand market, your printing and distribution service may not permit you to do that, unless they carry all of the books.</p>
<p>So, it is best to leave this page blank:</p>
-<p class="code"><code><small>\clearpage<br/>
-\thispagestyle{empty}<br/>
-\null<br/>
+<p class="code"><code><small>\clearpage<br>
+\thispagestyle{empty}<br>
+\null<br>
\clearpage</small></code></p>
@@ -225,37 +229,37 @@ Footnotes and Endnotes</h2>
<p>Here are some commands that may be helpful for building your Title Page:</p>
<p class="code"><code>
-\thispagestyle{empty} <span class="ap">% no header or footer</span><br/>
-\vspace*{<em>length</em>} <span class="ap">% puts space at top</span><br/>
-\charscale[<em>scale, position</em>]{<em>text</em>} <span class="ap">% changes text size and position</span><br/>
-{\centering <em>one line of text</em>\par} <span class="ap">% centers text</span><br/>
-\stake\hfill <em>text</em>\par <span class="ap">% pushes text to right</span><br/>
-\InlineImage[<em>options</em>]{<em>file</em>} <span class="ap">% see separate docs page</span><br/>
-\BlockImage[<em>options</em>]{<em>file</em>} <span class="ap">% see separate docs page</span><br/>
+\thispagestyle{empty} <span class="ap">% no header or footer</span><br>
+\vspace*{<em>length</em>} <span class="ap">% puts space at top</span><br>
+\charscale[<em>scale, position</em>]{<em>text</em>} <span class="ap">% changes text size and position</span><br>
+{\centering <em>one line of text</em>\par} <span class="ap">% centers text</span><br>
+\stake\hfill <em>text</em>\par <span class="ap">% pushes text to right</span><br>
+\InlineImage[<em>options</em>]{<em>file</em>} <span class="ap">% see separate docs page</span><br>
+\BlockImage[<em>options</em>]{<em>file</em>} <span class="ap">% see separate docs page</span><br>
\vfill <span class="ap">% pushes following text to bottom of textblock</span>
</code></p>
<p>Below is a sample Title Page. The <code>\orbitron</code> command calls for the font Orbitron-Medium.otf, which is not part of the TeX distribution. The <code>\decoglyph</code> command calls fo a decorative element from the NovelDeco.otf font, which comes with the <code>novel</code> class. The length <code>\nbs</code> is the normal baseline skip of the book's main font. The <code>\stake</code> commands place an invisible zero-width reference point, for the use of adjacent commands. Here is the code:</p>
-<p class="code"><img class="floatright" src="html-resources/starsmash.png" width="263" height="410" alt="sample title page"/>
+<p class="code"><img class="floatright" src="html-resources/starsmash.png" width="263" height="410" alt="sample title page">
<code><small>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\vspace*{6\nbs}<br/>
-\stake\hfill{\orbitron\charscale[3]{Star Smash}}\par<br/>
-\vspace{0.4\nbs}<br/>
-\noindent\charscale[3]{\decoglyph{r10059}}<br/>
-\bigemdash[3.4,3]\stake\par<br/>
-\vspace{0.4\nbs}<br/>
-\stake\hfill{\orbitron\charscale[1.42]{A Sci-Fi Murder Mystery}}\par<br/>
-\vspace{9\nbs}<br/>
-\begin{center}<br/>
-\charscale[4]{Dirk Hardcase}<br/>
-\vfill<br/>
-Meaningless Press\par<br/>
-Eschwege • Merthyr Tydfil • Lethbridge\par<br/>
-\end{center}<br/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\vspace*{6\nbs}<br>
+\stake\hfill{\orbitron\charscale[3]{Star Smash}}\par<br>
+\vspace{0.4\nbs}<br>
+\noindent\charscale[3]{\decoglyph{r10059}}<br>
+\bigemdash[3.4,3]\stake\par<br>
+\vspace{0.4\nbs}<br>
+\stake\hfill{\orbitron\charscale[1.42]{A Sci-Fi Murder Mystery}}\par<br>
+\vspace{9\nbs}<br>
+\begin{center}<br>
+\charscale[4]{Dirk Hardcase}<br>
+\vfill<br>
+Meaningless Press\par<br>
+Eschwege • Merthyr Tydfil • Lethbridge\par<br>
+\end{center}<br>
\clearpage
</small></code></p>
@@ -274,58 +278,58 @@ Eschwege • Merthyr Tydfil • Lethbridge\par<br/>
<p>Some commands useful on a Copyright Page:</p>
<p class="code"><code>
-\thispagestyle{empty} <span class="ap">% no header or footer</span><br/>
-\vspace*{<em>length</em>} <span class="ap">% creates vertical space</span><br/>
-<span class="ap">% legalese: ragged lines, no hyphenation, no indent.</span><br/>
-\begin{legalese} ... \end{legalese}<br/>
-\begin{adjustwidth}{<em>left</em>}{<em>right</em>} ... \end{adjustwidth} <span class="ap">% reduces width</span><br/>
-\begin{center} ... \end{center} <span class="ap">% if desired</span><br/>
-\begin{parascale} ... \end{parascale} <span class="ap">% shrinks text</span><br/>
-\itshape{<em>text</em>} <span class="ap">% italics, and can span paragraphs</span><br/>
-\textsc{<em>text</em>} <span class="ap">% lowercase to small caps (uppercase still uppercase)</span><br/>
-\allsmcp{<em>text</em>} <span class="ap">% uppercase and lowercase to small caps</span><br/>
-\acronym{<em>text</em>} <span class="ap">% uppercase to medium caps</span><br/>
-\lnum{<em>number</em>} <span class="ap">% lining numbers instead of old style</span><br/>
-\_ <span class="ap">% when underscore is in a URL</span><br/>
-\% <span class="ap">% when % is in a URL</span><br/>
-\&amp; <span class="ap">% when &amp; is in a URL</span><br/>
+\thispagestyle{empty} <span class="ap">% no header or footer</span><br>
+\vspace*{<em>length</em>} <span class="ap">% creates vertical space</span><br>
+<span class="ap">% legalese: ragged lines, no hyphenation, no indent.</span><br>
+\begin{legalese} ... \end{legalese}<br>
+\begin{adjustwidth}{<em>left</em>}{<em>right</em>} ... \end{adjustwidth} <span class="ap">% reduces width</span><br>
+\begin{center} ... \end{center} <span class="ap">% if desired</span><br>
+\begin{parascale} ... \end{parascale} <span class="ap">% shrinks text</span><br>
+\itshape{<em>text</em>} <span class="ap">% italics, and can span paragraphs</span><br>
+\textsc{<em>text</em>} <span class="ap">% lowercase to small caps (uppercase still uppercase)</span><br>
+\allsmcp{<em>text</em>} <span class="ap">% uppercase and lowercase to small caps</span><br>
+\acronym{<em>text</em>} <span class="ap">% uppercase to medium caps</span><br>
+\lnum{<em>number</em>} <span class="ap">% lining numbers instead of old style</span><br>
+\_ <span class="ap">% when underscore is in a URL</span><br>
+\% <span class="ap">% when % is in a URL</span><br>
+\&amp; <span class="ap">% when &amp; is in a URL</span><br>
</code></p>
<p>You normally do not need to write a lot of things on a Copyright Page. But if your novel has a lot of real-world material, some of it may require acknowledgements and permissions. They may be placed on the Copyright Page. If everything almost fits, but not quite, you can shrink it using the <code>parascale</code> environment. However, do not shrink it too much, and don't fill the whole page like it was ordinary story text. When you have a lot of acknowledgements and permissions, move them to a separate section. If your book has a Preface (uncommon in fiction), perhaps put them there. Or, create a separate Acknowledgements section (also uncommon in fiction).</p>
<p>Here is a sample abbreviated Copyright Page, centered style. Note that in the image, the text is displaced slightly to the left, because this is a verso page, and the right margin includes an allowance for gutter.</p>
-<p class="code"><img class="floatright" style="padding-top:2em" src="html-resources/coprcen.png" width="265" height="406" alt="sample copyright page"/>
+<p class="code"><img class="floatright" style="padding-top:2em" src="html-resources/coprcen.png" width="265" height="406" alt="sample copyright page">
<code><small>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\vspace*{5\nbs}<br/>
-\begin{center}<br/>
-\itshape{<br/>
-Copyright ©2017 Dirk Hardcase.\\<br/>
-All Rights Reserved.\par<br/>
-\null<br/>
-This is a work of fiction.\\<br/>
-All persons and events are imaginary.\\<br/>
-Resemblance to any real persons or events\\<br/>
-is entirely coincidental.\par<br/>
-\null<br/>
-Printed in the United States of America\\<br/>
-on acid-free paper.\par<br/>
-\null<br/>
-\allsmcp{FIRST EDITION}, March 2017.\par<br/>
-\null<br/>
-\allsmcp{ISBN} 9-876-54321-0\par<br/>
-\null<br/>
-Published by Dirk Hardcase,\\<br/>
-Anytown, U.S.A.\par<br/>
-\null<br/>
-Inquiries for Cataloging-in-Publication data\\<br/>
-should be directed to the author's web site:\par<br/>
-\null<br/>
-http://example.com/bigdealauthor.html\par<br/>
-} % end \itshape<br/>
-\end{center}<br/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\vspace*{5\nbs}<br>
+\begin{center}<br>
+\itshape{<br>
+Copyright ©2017 Dirk Hardcase.\\<br>
+All Rights Reserved.\par<br>
+\null<br>
+This is a work of fiction.\\<br>
+All persons and events are imaginary.\\<br>
+Resemblance to any real persons or events\\<br>
+is entirely coincidental.\par<br>
+\null<br>
+Printed in the United States of America\\<br>
+on acid-free paper.\par<br>
+\null<br>
+\allsmcp{FIRST EDITION}, March 2017.\par<br>
+\null<br>
+\allsmcp{ISBN} 9-876-54321-0\par<br>
+\null<br>
+Published by Dirk Hardcase,\\<br>
+Anytown, U.S.A.\par<br>
+\null<br>
+Inquiries for Cataloging-in-Publication data\\<br>
+should be directed to the author's web site:\par<br>
+\null<br>
+http://example.com/bigdealauthor.html\par<br>
+} % end \itshape<br>
+\end{center}<br>
\clearpage
</small></code></p>
@@ -333,36 +337,36 @@ http://example.com/bigdealauthor.html\par<br/>
<p style="clear:both">Sample abbreviated Copyright Page, alternative style. This style is more effective when there are more details, particularly if there is a complete Cataloging-in-Publication data block:</p>
-<p class="code"><img class="floatright" style="padding-top:2em" src="html-resources/coprbot.png" width="266" height="411" alt="sample copyright page"/>
+<p class="code"><img class="floatright" style="padding-top:2em" src="html-resources/coprbot.png" width="266" height="411" alt="sample copyright page">
<code><small>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\null\vfill<br/>
-\begin{adjustwidth}{0em}{8em}<br/>
-\begin{legalese}<br/>
-Copyright ©2017 Dirk Hardcase.\\<br/>
-All Rights Reserved.\par<br/>
-\null<br/>
-This is a work of fiction.\\<br/>
-All persons and events are imaginary.\\<br/>
-Resemblance to any real persons or events\\<br/>
-is entirely coincidental.\par<br/>
-\null<br/>
-Printed in the United States of America\\<br/>
-on acid-free paper.\par<br/>
-\null<br/>
-\allsmcp{FIRST EDITION}, March 2017.\par<br/>
-\null<br/>
-\allsmcp{ISBN} 9-876-54321-0\par<br/>
-\null<br/>
-Published by Dirk Hardcase,\\<br/>
-Anytown, U.S.A.\par<br/>
-\null<br/>
-Inquiries for Cataloging-in-Publication data\\<br/>
-should be directed to the author's web site:\par<br/>
-http://example.com/bigdealauthor.html\par<br/>
-\end{legalese}<br/>
-\end{adjustwidth}<br/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\null\vfill<br>
+\begin{adjustwidth}{0em}{8em}<br>
+\begin{legalese}<br>
+Copyright ©2017 Dirk Hardcase.\\<br>
+All Rights Reserved.\par<br>
+\null<br>
+This is a work of fiction.\\<br>
+All persons and events are imaginary.\\<br>
+Resemblance to any real persons or events\\<br>
+is entirely coincidental.\par<br>
+\null<br>
+Printed in the United States of America\\<br>
+on acid-free paper.\par<br>
+\null<br>
+\allsmcp{FIRST EDITION}, March 2017.\par<br>
+\null<br>
+\allsmcp{ISBN} 9-876-54321-0\par<br>
+\null<br>
+Published by Dirk Hardcase,\\<br>
+Anytown, U.S.A.\par<br>
+\null<br>
+Inquiries for Cataloging-in-Publication data\\<br>
+should be directed to the author's web site:\par<br>
+http://example.com/bigdealauthor.html\par<br>
+\end{legalese}<br>
+\end{adjustwidth}<br>
\clearpage
</small></code></p>
@@ -378,15 +382,15 @@ http://example.com/bigdealauthor.html\par<br/>
<p>If used, a Dedication is normally on page <code>v</code>, immediately following the Copyright Page. An exception might be if your work is a reprint of someone else's work, in which case you do not want the original author's Dedication to be interpreted as being your own.</p>
-<p><img class="floatright" src="html-resources/dedic.png" width="133" height="205" alt="sample dedication page"/> Keep it simple. If your book is combat fiction, it might be:</p>
+<p><img class="floatright" src="html-resources/dedic.png" width="133" height="205" alt="sample dedication page"> Keep it simple. If your book is combat fiction, it might be:</p>
<p class="code"><code><small>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\vspace*{12\nbs}<br/>
-\begin{center}<br/>
-\charscale[1.25]{\textsc{To Those Who Served}}\par<br/>
-\end{center}<br/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\vspace*{12\nbs}<br>
+\begin{center}<br>
+\charscale[1.25]{\textsc{To Those Who Served}}\par<br>
+\end{center}<br>
\clearpage
</small></code></p>
@@ -402,15 +406,15 @@ http://example.com/bigdealauthor.html\par<br/>
<p>Here is a sample Epigraph, in which the fictional speaker appears as a character in the book. A glance at this, and you know where the story is headed:</p>
-<p class="code"><img class="floatright" src="html-resources/dorfmcnorf.png" width="131" height="208" alt="sample epigraph"/>
+<p class="code"><img class="floatright" src="html-resources/dorfmcnorf.png" width="131" height="208" alt="sample epigraph">
<code><small>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\vspace*{10\nbs}<br/>
-\begin{adjustwidth}{7em}{7em}<br/>
-Let me tell you, there's nothing more exciting than the brouhaha at Mickey's Pub each Saturday night in April.\par<br/>
-\stake\hfill---Dorf McNorf\par<br/>
-\end{adjustwidth}<br/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\vspace*{10\nbs}<br>
+\begin{adjustwidth}{7em}{7em}<br>
+Let me tell you, there's nothing more exciting than the brouhaha at Mickey's Pub each Saturday night in April.\par<br>
+\stake\hfill---Dorf McNorf\par<br>
+\end{adjustwidth}<br>
\clearpage
</small></code></p>
@@ -434,16 +438,16 @@ Let me tell you, there's nothing more exciting than the brouhaha at Mickey's Pub
<p>Note that I subsequently added the black border during image editing; it is not part of the Epigraph.</p>
-<p class="code"><img class="floatright" src="html-resources/epigrcom.png" width="131" height="204" alt="Epigraph page"/>
+<p class="code"><img class="floatright" src="html-resources/epigrcom.png" width="131" height="204" alt="Epigraph page">
<code><small>
-\thispagestyle{empty} % no header or footer<br/>
-\vspace*{10\nbs} % for vertical position<br/>
-<img class="floatright" src="html-resources/epibjorn.png" width="265" height="91" alt="Epigraph text"/>
-\Epigraph[c]{% percent prevents newline</span><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/>
+\thispagestyle{empty} % no header or footer<br>
+\vspace*{10\nbs} % for vertical position<br>
+<img class="floatright" src="html-resources/epibjorn.png" width="265" height="91" alt="Epigraph text">
+\Epigraph[c]{<span class="ap">% percent prevents newline</span><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 of Epigraph
</small></code></p>
@@ -493,29 +497,29 @@ Then shall Shan-Sun wreak revenge.\\<br/>
<p><b>Example of toc:</b> 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" src="html-resources/toc.png" width="317" height="490" alt="toc example"/>
+<p class="code" style="text-indent:0px; font-size:small"><img class="floatright" src="html-resources/toc.png" width="317" height="490" alt="toc example">
<code>
-\clearpage<br/>
-\thispagestyle{empty}<br/>
-\begin{toc}[0.25]{3em}<br/>
-\vspace*{4\nbs}<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/>
+\clearpage<br>
+\thispagestyle{empty}<br>
+\begin{toc}[0.25]{3em}<br>
+\vspace*{4\nbs}<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>
\clearpage
</code>
</p>
@@ -531,14 +535,14 @@ In which Lord Withens, fresh from a program in horticulture, unleashes secret de
<p>A Part Separator is part of main matter, and has an arabic page number. However, the page number is not printed (possible exception if the separator also contains substantial text, by way of introduction). Thus, the first Part Separator would be page <code>1</code>, and its story would begin on page <code>3</code>. Wihout a Part Separator, the story would begin on page <code>1</code>.
-<p class="code"><img class="floatright" src="html-resources/partsep.png" width="134" height="202" alt="part separator"/>
+<p class="code"><img class="floatright" src="html-resources/partsep.png" width="134" height="202" alt="part separator">
<code><small>
-\clearpage<br/>
-<span class="ap">% \mainmatter % if needed to begin at page 1</span><br/>
-\thispagestyle{empty}<br/>
-\vspace*{10\nbs}<br/>
-% the tilde provides better separation:<br/>
-{\centering\charscale[2]{PART~ I}\par}<br/>
+\clearpage<br>
+<span class="ap">% \mainmatter % if needed to begin at page 1</span><br>
+\thispagestyle{empty}<br>
+\vspace*{10\nbs}<br>
+% the tilde provides better separation:<br>
+{\centering\charscale[2]{PART~ I}\par}<br>
\clearpage
</small></code></p>
@@ -580,7 +584,7 @@ In which Lord Withens, fresh from a program in horticulture, unleashes secret de
<p>The following image shows three pages of a Foreword, from a book that uses header but no footer. On its start page, the folio has been dropped inside. Color added for illustration.</p>
-<p class="centerimg"><img src="html-resources/dfi.png" width="534" height="267" alt="example of inside drop folio"/></p>
+<p class="centerimg"><img src="html-resources/dfi.png" width="534" height="267" alt="example of inside drop folio"></p>
<p class="code"><code>\thispagestyle{dropfoliobeneath}</code></p>
@@ -610,28 +614,28 @@ In which Lord Withens, fresh from a program in horticulture, unleashes secret de
<p>The header text will appear in the font chosen as <code>headerfont</code>. You may over-ride that with a local font command. The text may be styled with commands such as <code>\textsc</code> or <code>\textls</code> or <code>\emph</code> if desired. Do not use underline or bold.</p>
-<p><img class="floatright" src="html-resources/preface.png" width="259" height="820" alt="example preface"/> Here is an example, where the author wrote a Preface several pages long, and the book layout uses a header. The <code>ChapterStart</code> environment is used, but this is not a requirement. The <code>lipsum</code> package was used for text fill:</p>
+<p><img class="floatright" src="html-resources/preface.png" width="259" height="820" alt="example preface"> Here is an example, where the author wrote a Preface several pages long, and the book layout uses a header. The <code>ChapterStart</code> environment is used, but this is not a requirement. The <code>lipsum</code> package was used for text fill:</p>
<p class="code"><code><small>
-\clearpage<br/>
-\thispagestyle{footer} <span class="ap">% or dropfolioinside or dropfoliobeneath</span><br/>
-\SetVersoHeadText{\textsc{Preface}}<br/>
-\SetRectoHeadText{\textsc{Preface}}<br/>
-\begin{ChapterStart}<br/>
-\vspace*{2\nbs}<br/>
-\ChapterTitle{Preface}<br/>
-\end{ChapterStart}<br/>
-The inspiration for this book...\par<br/>
-\lipsum<br/>
-But while I was held captive...\par<br/>
-\lipsum<br/>
-Clawing my way to the sunlight...\par<br/>
-\lipsum<br/>
-... And I hope you will enjoy it.\par<br/>
-\null<br/>
-\stake\hfill Dirk Hardcase.\par<br/>
-\stake\hfill Springfield, March 14, 2017\par<br/>
-\clearpage<br/>
+\clearpage<br>
+\thispagestyle{footer} <span class="ap">% or dropfolioinside or dropfoliobeneath</span><br>
+\SetVersoHeadText{\textsc{Preface}}<br>
+\SetRectoHeadText{\textsc{Preface}}<br>
+\begin{ChapterStart}<br>
+\vspace*{2\nbs}<br>
+\ChapterTitle{Preface}<br>
+\end{ChapterStart}<br>
+The inspiration for this book...\par<br>
+\lipsum<br>
+But while I was held captive...\par<br>
+\lipsum<br>
+Clawing my way to the sunlight...\par<br>
+\lipsum<br>
+... And I hope you will enjoy it.\par<br>
+\null<br>
+\stake\hfill Dirk Hardcase.\par<br>
+\stake\hfill Springfield, March 14, 2017\par<br>
+\clearpage<br>
<span class="ap">% Be sure to re-set the head texts now!</span>
</small></code></p>
@@ -696,7 +700,7 @@ Clawing my way to the sunlight...\par<br/>
<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.4.3.1"></a>
-<p class="h5"><img class="floatright" style="margin-top:40px;" src="html-resources/chapst.png" width="263" height="409" alt="example chapter start"/>
+<p class="h5"><img class="floatright" style="margin-top:40px;" src="html-resources/chapst.png" width="263" height="409" alt="example chapter start">
<b>9.4.3.1\ChapterTitle{<em>text</em>}</b> sets its text using <code>chapterfont</code>. The default is the main font scaled 1.6, with lining numbers.</p>
<a id="a9.4.3.2"></a>
@@ -708,13 +712,13 @@ Clawing my way to the sunlight...\par<br/>
<p style="margin-top:20px">Example, where <code>\clearpage</code> and <code>\mainmatter</code> were already issued:</p>
<p class="code"><code><small>
-\thispagestyle{dropfolioinside}<br/>
-\begin{ChapterStart} <span class="ap">% default 10 lines</span><br/>
- \null <span class="ap">% for positioning title</span><br/>
- \ChapterTitle{Prologue}<br/>
- \ChapterDeco[4]{\decoglyph{r9548}}<br/>
- \ChapterSubtitle{The Finding of the Manuscript}<br/>
-\end{ChapterStart}<br/>
+\thispagestyle{dropfolioinside}<br>
+\begin{ChapterStart} <span class="ap">% default 10 lines</span><br>
+ \null <span class="ap">% for positioning title</span><br>
+ \ChapterTitle{Prologue}<br>
+ \ChapterDeco[4]{\decoglyph{r9548}}<br>
+ \ChapterSubtitle{The Finding of the Manuscript}<br>
+\end{ChapterStart}<br>
<span class="ap">% then the main text</span>
</small></code></p>
@@ -728,21 +732,21 @@ Clawing my way to the sunlight...\par<br/>
<a id="a9.4.4.1"></a>
-<p class="h5"><img class="floatright" src="html-resources/ctimg35.png" width="79" height="196" alt="example of chapter title image, text over"/><b>9.4.4.1 Text Over Image:</b> 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 class="h5"><img class="floatright" src="html-resources/ctimg35.png" width="79" height="196" alt="example of chapter title image, text over"><b>9.4.4.1 Text Over Image:</b> 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><small>\begin{ChapterStart}<br/>
-\BlockImage{sword.png} <span class="ap">% centered by default</span><br/>
-{\unifrak\centering\charscale[3,0pt,4\nbs]{35}\par}<br/>
+<p class="code"><code><small>\begin{ChapterStart}<br>
+\BlockImage{sword.png} <span class="ap">% centered by default</span><br>
+{\unifrak\centering\charscale[3,0pt,4\nbs]{35}\par}<br>
</small>\end{ChapterStart}</code></p>
<a id="a9.4.4.2"></a>
<p class="h5"><b>9.4.4.2 Text as Part of Image:</b> 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><small>\begin{ChapterStart}<br/>
-\BlockImage[l]{smfingerprint8.png}<br/>
+<p class="code"><img class="floatright" src="html-resources/smfingerprint8.png" width="86" height="70" alt="example of chapter title image, raster text"><code><small>\begin{ChapterStart}<br>
+\BlockImage[l]{smfingerprint8.png}<br>
\end{ChapterStart}</small></code></p>
@@ -766,12 +770,12 @@ Clawing my way to the sunlight...\par<br/>
<p>Example:</p>
-<p class="code"><code><small>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/>
+<p class="code"><code><small>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. ...</small></code></p>
-<p class="centerimg"><img src="html-resources/quickchapter.png" width="629" height="240" alt="quick chapter"/></p>
+<p class="centerimg"><img src="html-resources/quickchapter.png" width="629" height="240" alt="quick chapter"></p>
<a id="a9.5.2"></a>
@@ -790,18 +794,18 @@ The bouncer wasn't the biggest one I'd ever seen, but he was the ugliest. ...</s
<p style="margin-top:20px">Examples:</p>
-<p class="code"><img style="float:right; margin-left:16px;" src="html-resources/scenebreaks.png" width="331" height="236" alt="scene breaks" />
+<p class="code"><img style="float:right; margin-left:16px;" src="html-resources/scenebreaks.png" width="331" height="236" alt="scene breaks" >
<code><small>
-\noindent It was a dark and stormy night.\par<br/>
-Lord Withens, the last of his line, hurried through the gloom to Castle McWhistle, where Lady McWhistle awaited.\par<br/>
-\scenebreak<br/>
-Well, maybe it was not very dark.\par<br/>
-But to Lord Withens, it seemed dark enough. Or rather, he hoped it was dark enough. Lord McWhistle was suspicious.\par<br/>
-\sceneline<br/>
-Actually, it was not all that stormy, either. But the Withens clan never tolerated drizzle, much less a storm.\par<br/>
-Who could blame them? It's not like they lived in Italy.\par<br/>
-\scenestars<br/>
-Ah, such ill fortune haunted the Withens!\par<br/>
+\noindent It was a dark and stormy night.\par<br>
+Lord Withens, the last of his line, hurried through the gloom to Castle McWhistle, where Lady McWhistle awaited.\par<br>
+\scenebreak<br>
+Well, maybe it was not very dark.\par<br>
+But to Lord Withens, it seemed dark enough. Or rather, he hoped it was dark enough. Lord McWhistle was suspicious.\par<br>
+\sceneline<br>
+Actually, it was not all that stormy, either. But the Withens clan never tolerated drizzle, much less a storm.\par<br>
+Who could blame them? It's not like they lived in Italy.\par<br>
+\scenestars<br>
+Ah, such ill fortune haunted the Withens!\par<br>
Unfortunately, novelists of that era had so little to write about, or they would have chosen another family to pursue.\par
</small></code></p>
@@ -887,12 +891,12 @@ Unfortunately, novelists of that era had so little to write about, or they would
<p class="code">
<code><small>
-\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{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 terrible 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}
</small></code></p>
-<p class="centerimg"><img src="html-resources/endnotetext.png" width="637" height="219" alt="using endnotetext"/></p>
+<p class="centerimg"><img src="html-resources/endnotetext.png" width="447" height="151" alt="using endnotetext"></p>