texlive[45302] Master/texmf-dist: novel (14sep17)
commits+karl at tug.org
commits+karl at tug.org
Thu Sep 14 22:53:14 CEST 2017
Revision: 45302
http://tug.org/svn/texlive?view=revision&revision=45302
Author: karl
Date: 2017-09-14 22:53:13 +0200 (Thu, 14 Sep 2017)
Log Message:
-----------
novel (14sep17)
Modified Paths:
--------------
trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-cover-template.tex
trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.pdf
trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.tex
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/overflowrule.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/preface.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/toc.png
trunk/Master/texmf-dist/doc/lualatex/novel/novel.pdf
trunk/Master/texmf-dist/doc/lualatex/novel/novel.tex
trunk/Master/texmf-dist/tex/lualatex/novel/novel-CGATSTR001.clo
trunk/Master/texmf-dist/tex/lualatex/novel/novel-CalculateLayout.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-ChapterScene.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-FOGRA39.clo
trunk/Master/texmf-dist/tex/lualatex/novel/novel-FileData.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-FontDefaults.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-Footnotes.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-HeadFootStyles.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-Images.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-JC200103.clo
trunk/Master/texmf-dist/tex/lualatex/novel/novel-LayoutSettings.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-TextMacros.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-glyphtounicode.tex
trunk/Master/texmf-dist/tex/lualatex/novel/novel-microtype.cfg
trunk/Master/texmf-dist/tex/lualatex/novel/novel-pdfx.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel-xmppacket.sty
trunk/Master/texmf-dist/tex/lualatex/novel/novel.cls
Added Paths:
-----------
trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png
trunk/Master/texmf-dist/doc/lualatex/novel/novel-documentation.html
Removed Paths:
-------------
trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-template.tex
trunk/Master/texmf-dist/doc/lualatex/novel/extras/swop240gamutHSV-monitorlimit.png
trunk/Master/texmf-dist/doc/lualatex/novel/extras/swop240gamutHSV.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknow.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/blakemilt.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/blfr.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/chapst.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/charscaletitle.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/coprbot.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/coprcen.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/difnl.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/epibjorn.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/epigrcom.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/famface.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/gears20.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/greensmile.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/halftitle.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/htgb.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/htss.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/linegrid.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/megatitlepage.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/novel-doc.css
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/redfrown.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/tbrecto.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/tbrectomar.png
trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/titlepage.png
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-10-cover-art.html
trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-11-debugging.html
Added: trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/extras/CPmodified.otf
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-cover-template.tex
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-cover-template.tex 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-cover-template.tex 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,6 +1,6 @@
% !TeX program = LuaLaTeX
% !TeX encoding = UTF-8
-\documentclass[coverart]{novel} % v. 1.38 or later
+\documentclass[coverart]{novel} % v. 1.40 or later
\SetMediaSize{width}{height} % includes bleed
\SetTrimSize{width}{height} % without bleed
\SetTitle{example} % title required, might not be book title
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.tex
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.tex 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-example.tex 2017-09-14 20:53:13 UTC (rev 45302)
@@ -3,7 +3,7 @@
%
% EXAMPLE OF NOVEL DOCUMENT CLASS
% Uses mostly default layout.
-\documentclass{novel} % v. 1.38 or later
+\documentclass{novel} % v. 1.40 or later
\SetTitle{Dark and Stormy}
\SetSubtitle{A Tale of Nights}
\SetAuthor{Dirk Hardcase}
@@ -90,14 +90,8 @@
Then shall the rivers overflow with mead.\par
\hfill---\textit{Prophecy of Claudius}\par
\end{adjustwidth}
-\clearpage
+\cleartorecto % here, inserts blank, so mainmatter begins recto
-% vi. Blank page:
-\thispagestyle{empty}
-\null
-\clearpage
-
-% Must use even number of pages in frontmatter.
% Now to begin your story:
\mainmatter
@@ -114,7 +108,7 @@
\lipsum
% Chapter Two:
-\clearpage
+\clearpage % next chapter may begin recto or verso
\begin{ChapterStart}
\vspace*{3\nbs}
\ChapterTitle{Chapter Two}
@@ -126,14 +120,8 @@
\lipsum
-% Don't forget: The final page must be verso, and must be blank.
-\clearpage
-\thispagestyle{empty}
-\null
-% If necessary, insert an additional blank page, so that the total page count is even:
-\clearpage
-\thispagestyle{empty}
-\null
+\cleartoend % ensures final page is blank verso
+
\end{document}
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-template.tex
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-template.tex 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/extras/novel-template.tex 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,29 +0,0 @@
-% !TeX program = LuaLaTeX
-% !TeX encoding = UTF-8
-\documentclass{novel} % v. 1.38 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:
-% \SetTrimSize{}{}
-% \SetMargins{}{}{}{}
-% \SetHeadFootStyle{}
-% \SetParentFont[]{}
-% \SetTitle{}
-% \SetAuthor{}
-% \SetPDFX[]{}
-
-\begin{document}
-% Some popular commands:
-% \frontmatter
-% \SetVersoHeadText{}
-% \SetRectoHeadText{}
-% \thispagestyle{}
-% \mainmatter
-% \begin{ChapterStart}
-% \ChapterTitle{}
-% \end{ChapterStart}
-
-It was a dark and stormy night.\par
-
-\end{document}
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/extras/swop240gamutHSV-monitorlimit.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/extras/swop240gamutHSV.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknow.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/acknowledgements.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/authorsnote-frontmatter.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/bixby-compare.jpg
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/blakemilt.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/blfr.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/chapst.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/charscaletitle.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/colormap-brown.jpg
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/coprbot.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/coprcen.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightcentered.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/copyrightoffset.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/difnl.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/epibjorn.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/epigrcom.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/famface.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/fmsimple.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/foreword.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/gears20.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/greensmile.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/halftitle.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/htgb.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/htss.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/linegrid.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/map.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/medieval-painting.jpg
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/megatitlepage.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/novel-doc.css
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/novel-doc.css 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/novel-doc.css 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,100 +0,0 @@
-
-/* Style sheet for "novel" class documentation. */
-
-
-body {font-family:sans-serif; line-height:150%; font-size:16pt; background:#cccccc none;}
-#master {position:relative;}
-#toc {font-size:14pt; width:30%; background:#ffffff none; position:fixed; overflow:scroll; height:98%;}
-#toc p {margin-left:8px; margin-top:8px; margin-bottom:8px; font-weight:bold; text-indent:0px;}
-#toc ul {list-style-type:none; margin-left:8px;}
-#toc li {list-style-type:none; margin-left:8px; margin-top:3px;}
-#main {float:right; background:#ffffff none; width:68%; padding-bottom:40px;}
-#finish {clear:both;}
-a {text-decoration:none; color:#990000}
-ol, ul, li {margin:0px; padding:0px;}
-h1 {font-size:1.33em; margin:32px 16px 16px 16px; font-weight:bold; clear:both;}
-h1 em {font-weight:normal}
-h2 {font-size:1.25em; margin:32px 16px 8px 16px; font-weight:bold; clear:both;}
-h2 em {font-weight:normal}
-h3 {font-size:1.15em; margin:32px 16px 8px 16px; font-weight:bold; clear:both;}
-h3 em {font-weight:normal}
-h4 {font-size:1em; margin:24px 16px 8px 16px; font-weight:bold; clear:both;}
-h4 em {font-weight:normal}
-h5 {font-size:1em; margin:16px 16px 8px 16px; font-weight:bold; clear:both;}
-h5 em {font-weight:normal}
-h6 {font-size:1em; margin:0.5em 16px 8px 16px; font-weight:bold; clear:both;}
-h6 em {font-weight:normal}
-div.h1 {margin:0px 16px 16px 16px;}
-div.h2 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-left:1px dotted #666666; border-bottom: 1px dotted #666666;}
-div.h3 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-left:1px dotted #666666; border-bottom: 1px dotted #666666;}
-div.h4 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-left:1px dotted #666666; border-bottom: 1px dotted #666666;}
-div.h5 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-left:1px dotted #666666; border-bottom: 1px dotted #666666;}
-div.h6 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-left:1px dotted #666666; border-bottom: 1px dotted #666666;}
-div.pagetopage {float:right; border:1px solid #000000; margin-left:12px; margin-right:16px; margin-top:32px;}
-div.pagetopage p {text-indent:0px; margin:4px;}
-div.codeblock {overflow:auto; margin:16px; padding: 8px; border: 1px solid #000000;}
-div.codeblock p {text-indent:0px; white-space:nowrap;}
-p {font-family:serif;}
-pre, code {font-family:monospace,monospace; font-size:1em;}
-p, pre {margin: 0px 16px 0px 16px; text-indent: 16px;}
-p.h5 {text-indent:0px; margin-top:1em; clear:both;}
-p.h5 b {font-family:sans-serif; font-weight:bold;}
-*.technote {font-weight:normal; color:#333333; margin-bottom:6px;}
-*.technote img {position:relative; top:4px;}
-*.noindent {text-indent:0px;}
-*.noindentcmd {text-indent:0px; margin-top:16px;}
-*.underh2 {text-indent:0px; font-style:italic; margin-bottom:0px; margin-top:0px; padding-top:6px; padding-bottom:0.5em; padding-left:20px; border-left:1px dotted #666666;}
-*.underh3 {text-indent:0px; font-style:italic; margin-bottom:0px; margin-top:0px; padding-top:6px; padding-bottom:0.5em; padding-left:18px; border-left:1px dotted #666666;}
-*.underh4 {text-indent:0px; font-style:italic; margin-bottom:0px; margin-top:0px; padding-top:6px; padding-bottom:0.5em; padding-left:16px; border-left:1px dotted #666666;}
-*.underh5 {text-indent:0px; font-style:italic; margin-bottom:0px; margin-top:0px; padding-top:6px; padding-bottom:0.5em; padding-left:16px; border-left:1px dotted #666666;}
-*.underh6 {text-indent:0px; font-style:italic; margin-bottom:0px; margin-top:0px; padding-top:6px; padding-bottom:0.5em; padding-left:16px; border-left:1px dotted #666666;}
-*.bull {padding-left:20px;}
-*.bull::before {content : "• ";}
-*.bullist {text-indent:80px;}
-*.bull0 {text-indent:-1em; margin-left:2em; margin-top:0.5em;}
-*.bull0::before {content : "• ";}
-*.bullist0 {margin-left:2em;}
-*.isolate {padding-left:10px;margin-top:10px; margin-bottom:10px; text-indent:0px;}
-table.preconf {margin-left:auto; margin-right:auto; margin-top:20px; margin-bottom:20px; border:1px solid #000000}
-table.preconf caption {font-weight:bold;}
-table.preconf th {text-align:left; padding:6px; font-weight:normal; border-bottom:1px solid #000000;}
-table.preconf td {text-align:left; padding:6px;}
-table.preconf tfoot td {border-top:1px solid #000000;}
-table.preconf p {text-indent:0px; margin:6px;}
-*.onedown {font-size:smaller}
-*.menuitem {text-indent:-8px; margin-left:24px; margin-top:0px; margin-bottom:0px;}
-small {line-height:50%;}
-span.ap {color: #996633;} /* percent comment in code */
-span.apdk {color: #502000;}
-span.flat {
- font-family: "Lucida Sans Unicode", "DejaVu Sans", "Lucida Grande", "Helvetica Neue", sans-serif;
- color:#00cc00;
- padding-right:0.3em;
- position:relative;
- bottom:0.1em;
- left:-0.33em;
-}
-span.flat::before {content: "▶";}
-span.expanded {
- font-family: "Lucida Sans Unicode", "DejaVu Sans", "Lucida Grande", "Helvetica Neue", sans-serif;
- color:#cc0000;
- cursor:pointer;
- padding-right:0.3em;
- position:relative;
- bottom:0.1em;
- left:-0.33em;
-}
-span.expanded::before {content: "▼";}
-*.floatright {float:right; margin-left:1em; margin-right:16px;}
-p.centerimg {text-indent:0px; text-align:center; margin-top:0.5em; margin-bottom:0.5em;}
-p.code {text-indent:0px; margin: 4px 16px 4px 16px; padding-left:32px;}
-div.fontcommand {padding-left:32px; margin-top:8px; margin-bottom:8px;}
-div.fontcommand p, pre {margin-left:16px; text-indent:-16px;}
-b em {font-weight:normal;}
-
- at media print {
-#toc {display:none;}
-#main {width:auto; float:none;}
-}
-
-
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/overflowrule.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/plusminus.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/preface.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/redfrown.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/signature.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/sixpage-frontmatter.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Added: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png
===================================================================
(Binary files differ)
Index: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png 2017-09-14 20:53:13 UTC (rev 45302)
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/smythsewn.png
___________________________________________________________________
Added: svn:mime-type
## -0,0 +1 ##
+application/octet-stream
\ No newline at end of property
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/tbrecto.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/tbrectomar.png
===================================================================
(Binary files differ)
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/titlepage.png
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/html-resources/toc.png
===================================================================
(Binary files differ)
Added: trunk/Master/texmf-dist/doc/lualatex/novel/novel-documentation.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/novel-documentation.html (rev 0)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/novel-documentation.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -0,0 +1,3206 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
+<title>Document class "novel" - documentation</title>
+
+<style type="text/css">
+body {font-family:sans-serif; line-height:150%; font-size:14pt; background:#cccccc none;}
+p {font-family:sans-serif,sans-serif; font-size:1em; margin:0px 16px 0px 16px; text-indent:16px;}
+ol, ul {list-style-type:none; margin:0px; padding:0px;}
+li {margin:3px 8px 3px 16px; padding:0px;}
+li p {margin: 0px 8px 0px 44px; text-indent:-44px;}
+a {text-decoration:none; color:#990000}
+h1 {font-size:1.33em; margin:16px 16px 0px 8px; font-weight:bold; clear:both; padding-top:8px;}
+h2 {font-size:1.25em; margin:8px 16px 0px 8px; font-weight:bold; clear:both; padding-top:8px;}
+h3 {font-size:1.15em; margin:8px 16px 0px 8px; font-weight:bold; clear:both; padding-top:8px;}
+h4 {font-size:1em; margin:8px 16px 0px 8px; font-weight:bold; clear:both; padding-top:8px;}
+h5 {font-size:1em; margin:8px 16px 0px 8px; clear:both; padding-top:8px;}
+h6 {font-size:1em; margin:8px 16px 0px 8px; clear:both; padding-top:8px;}
+em {font-weight:normal}
+img {max-width:100%;}
+img.nodisplaynav {display:none; height:1em;}
+*.noimg {padding-left:1.5em;}
+div.d1 {margin:0px 16px 16px 16px;}
+div.d2 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-top:0; border-right: 0px; border-bottom:1px dotted #666666; border-left:1px dotted #666666;}
+div.d3 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-top:0; border-right: 0px; border-bottom:1px dotted #666666; border-left:1px dotted #666666;}
+div.d4 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-top:0; border-right: 0px; border-bottom:1px dotted #666666; border-left:1px dotted #666666;}
+div.d5 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-top:0; border-right: 0px; border-bottom:1px dotted #666666; border-left:1px dotted #666666;}
+div.d6 {margin:0px 0px 16px 16px; padding-bottom:0.5em; border-top:0; border-right: 0px; border-bottom:1px dotted #666666; border-left:1px dotted #666666;}
+div.page {padding:16px 0px 16px 0px; border-top:4px solid #505050;}
+div.codeblock {overflow:auto; margin:16px; padding: 8px; border: 1px solid #000000;}
+div.codeblock p {text-indent:0px; white-space:nowrap;}
+code {font-family:sans-serif,sans-serif; font-size:1em; background:#dddddd none; padding:0px 3px 0px 3px;}
+*.noindent {text-indent:0px;}
+*.noindent1 {text-indent:0px; margin-top:8px;}
+*.noindent2 {text-indent:0px; margin-bottom:8px;}
+*.noindentcmd {text-indent:0px; margin-top:16px;}
+*.isolate {padding-left:10px;margin-top:10px; margin-bottom:10px; text-indent:0px;}
+table.preconf {margin-left:auto; margin-right:auto; margin-top:20px; margin-bottom:20px; border:1px solid #000000}
+table.preconf caption {font-weight:bold;}
+table.preconf th {text-align:left; padding:6px; font-weight:normal; border-bottom:1px solid #000000;}
+table.preconf td {text-align:left; padding:6px;}
+table.preconf tfoot td {border-top:1px solid #000000;}
+table.preconf p {text-indent:0px; margin:6px;}
+*.onedown {font-size:smaller}
+*.menuitem {text-indent:-8px; margin-left:24px; margin-top:0px; margin-bottom:0px;}
+small {line-height:50%;}
+span.ap {color: #996633;} /* percent comment in code */
+*.floatright {float:right; margin-left:1em; margin-right:16px;}
+p.centerimg {text-indent:0px; text-align:center; margin-top:0.5em; margin-bottom:0.5em;}
+p.code {text-indent:0px; margin: 4px 16px 4px 16px; padding-left:32px;}
+b em {font-weight:normal;}
+hr.newpage {margin-top:2em; margin-bottom:2em; height:4px; color:#505050; background:#505050;}
+p.overhang {margin-left:32px; text-indent:-16px;}
+#master {position:relative;}
+#toc {font-size:14pt; width:30%; background:#ffffff none; position:fixed; overflow:scroll; height:98%;}
+#main {float:right; background:#ffffff none; width:68%; padding-bottom:40px;}
+#finish {clear:both;}
+ at media print {
+ #toc {display:none;}
+ #main {width:auto; float:none;}
+}
+</style>
+
+<script type="text/javascript">
+var imgsrc = new Image;
+imgsrc.src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAGAAAABACAYAAADlNHIOAAAArklEQVR42u3cYQ5AMAyA0Vbc/8p1Af6I6dj7DiCRl2IZMiIqFq6q9/S3EAAAamuf7Zo4usw0AQIAQAAACAAAAAJgJdyzIs2TVXiZAAEAIAAABACAAAAQAAACAEAAAAjA37q1IfPQ63014rhf29MxAQAACICb8Os3Om9FmAAAAgAAgAAAEAAAAgBAAAAIAAABWKW2z1RX3HwxAQAEAIAAANDlY+hs/9U0AQIAQMM6AO8BGoYCRA/4AAAAAElFTkSuQmCC";
+function placenav(){
+ navimgs = document.getElementsByClassName("nodisplaynav");
+ for(var n=0; navimgs.length>n; n++){
+ navimgs[n].src=imgsrc.src;
+ navimgs[n].style.display="inline";
+ navimgs[n].alt="1";
+ plusminus(navimgs[n].id);
+ }
+}
+function plusminus(whichid){
+ thisimg = document.getElementById(whichid);
+ thisid = "u" + whichid.substring(1);
+ thisul = document.getElementById(thisid);
+ if(thisimg.alt=="1") {hideul(thisul);}
+ if(thisimg.alt=="0") {showul(thisul);}
+ thisimg.alt = 1 - thisimg.alt;
+}
+function hideul(thisul){
+ thisul.style.display="none";
+ thisimg.style.backgroundColor="#000000";
+}
+function showul(thisul){
+ thisul.style.display="block";
+ thisimg.style.backgroundColor="#ffffff";
+}
+</script>
+
+</head>
+
+<body>
+<div id="master">
+
+
+<div id="toc" class="toc">
+
+<h3><a href="#main">Table of Contents</a></h3>
+
+<ul><!-- master toc ul -->
+
+ <li><p><img id="i1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h1"><b>1. Overview</b></a></p>
+ <ul id="u1">
+ <li><p><img id="i1.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h1.1">1.1 Description</a></p>
+ <ul id="u1.1">
+ <li><p class="noimg"><a href="#h1.1.1">1.1.1 Installation</a></p></li>
+ <li><p class="noimg"><a href="#h1.1.2">1.1.2 Licensing</a></p></li>
+ <li><p class="noimg"><a href="#h1.1.3">1.1.3 Credits</a></p></li>
+ <li><p class="noimg"><a href="#h1.1.4">1.1.4 Success Story</a></p></li>
+ <li><p class="noimg"><a href="#h1.1.5">1.1.5 Help Wanted</a></p></li>
+ </ul>
+ </li><!-- end 1.1 -->
+ <li><p><img id="i1.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h1.2">1.2 Important Behavior</a></p>
+ <ul id="u1.2">
+ <li><p class="noimg"><a href="#h1.2.1">1.2.1 Always UTF-8, No fontenc</a></li>
+ <li><p class="noimg"><a href="#h1.2.2">1.2.2 Fonts Not Loaded by \usepackage or \RequirePackage</a></li>
+ <li><p class="noimg"><a href="#h1.2.3">1.2.3 LuaLaTeX, Open Type Fonts</a></p></li>
+ <li><p class="noimg"><a href="#h1.2.4">1.2.4 Standard TeX Size Commands Disabled</a></li>
+ <li><p class="noimg"><a href="#h1.2.5">1.2.5 Academic Style Commands Disabled</a></li>
+ <li><p class="noimg"><a href="#h1.2.6">1.2.6 Raster png/jpg Images Only</a></li>
+ <li><p class="noimg"><a href="#h1.2.7">1.2.7 Beware of Special Characters</a></li>
+ <li><p class="noimg"><a href="#h1.2.8">1.2.8 Avoid TeX Editors, IDEs</a></li>
+ <li><p class="noimg"><a href="#h1.2.9">1.2.9 Write Using Word Processor</a></li>
+ <li><p class="noimg"><a href="#h1.2.10">1.2.10 Think for Yourself</a></li>
+ </ul>
+ </li><!-- end 1.2 -->
+ </ul>
+ </li><!-- end 1 -->
+
+ <li><p><img id="i2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h2"><b>2. Document Class Options</b></a></p>
+ <ul id="u2">
+ <li><p class="noimg"><a href="#h2.1">2.1 draft</a></p></li>
+ <li><p class="noimg"><a href="#h2.2">2.2 graytext</a></p></li>
+ <li><p class="noimg"><a href="#h2.3">2.3 shademargins</a></p></li>
+ <li><p class="noimg"><a href="#h2.4">2.4 cropmarks</a></p></li>
+ <li><p class="noimg"><a href="#h2.5">2.5 cropview</a></p></li>
+ <li><p class="noimg"><a href="#h2.6">2.6 closecrop</a></p></li>
+ <li><p class="noimg"><a href="#h2.7">2.7 xml</a></p></li>
+ <li><p class="noimg"><a href="#h2.8">2.8 coverart</a></p></li>
+ <li><p class="noimg"><a href="#h2.9">2.9 unblock (dev)</a></p></li>
+ </ul>
+ </li><!-- end 2 -->
+
+ <li><p><img id="i3" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h3"><b>3. Metadata, File Data, PDF/X</b></a></p>
+ <ul id="u3">
+ <li><p><img id="i3.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h3.1">3.1 Definitions of Terms</a></p>
+ <ul id="u3.1">
+ <li><p class="noimg"><a href="#h3.1.1">3.1.1 ISBN Metadata</a></p></li>
+ <li><p class="noimg"><a href="#h3.1.2">3.1.2 Printed Metadata</a></p></li>
+ <li><p class="noimg"><a href="#h3.1.3">3.1.3 File (PDF) Metadata</a></p></li>
+ </ul>
+ </li><!-- end 3.1 -->
+ <li><p><img id="i3.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h3.2">3.2 Rules for File Data</a></p>
+ <ul id="u3.2">
+ <li><p class="noimg"><a href="#h3.2.1">3.2.1 Required, Prohibited?</a></p></li>
+ <li><p class="noimg"><a href="#h3.2.2">3.2.2 Limited to Latin-1?</a></p></li>
+ <li><p class="noimg"><a href="#h3.2.3">3.2.3 TeX Escapes</a></p></li>
+ <li><p class="noimg"><a href="#h3.2.4">3.2.4 Forbidden Characters</a></p></li>
+ </ul>
+ </li><!-- end 3.2 -->
+ <li><p><img id="i3.3" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h3.3">3.3 File Data Commands</a></p>
+ <ul id="u3.3">
+ <li><p class="noimg"><a href="#h3.3.1">3.3.1 \SetTitle{}</a></p></li>
+ <li><p class="noimg"><a href="#h3.3.2">3.3.2 \SetAuthor{}</a></p></li>
+ <li><p class="noimg"><a href="#h3.3.3">3.3.3 \SetSubtitle{}</a></p></li>
+ <li><p class="noimg"><a href="#h3.3.4">3.3.4 \SetApplication{}, \SetProducer{}</a></p></li>
+ </ul>
+ </li><!-- end 3.3 -->
+ <li><p><img id="i3.4" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h3.4">3.4 PDF/X</a></p>
+ <ul id="u3.4">
+ <li><p class="noimg"><a href="#h3.4.1">3.4.1 Compliance Standards</a></p></li>
+ <li><p class="noimg"><a href="#h3.4.2">3.4.2 Output Intents</a></p></li>
+ <li><p class="noimg"><a href="#h3.4.3">3.4.3 Built-IN OI Codes</a></p></li>
+ <li><p class="noimg"><a href="#h3.4.4">3.4.4 Other Output Intents</a></p></li>
+ <li><p class="noimg"><a href="#h3.4.5">3.4.5 Embed *.icc or Not?</a></p></li>
+ <li><p class="noimg"><a href="#h3.4.6">3.4.6 Finding *.icc Files</a></p></li>
+ </ul>
+ </li><!-- end 3.4 -->
+ </ul>
+ </li><!-- end 3 -->
+
+ <li><p><img id="i4" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h4"><b>4. Book Size and Page Layout</b></a></p>
+ <ul id="u4">
+ <li><p><img id="i4.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h4.1">4.1 Book Dimensions</a></p>
+ <ul id="u4.1">
+ <li><p class="noimg"><a href="#h4.1.1">4.1.1 Trim Size</a></p></li>
+ <li><p class="noimg"><a href="#h4.1.2">4.1.2 Media Size, TrimBox</a></p></li>
+ <li><p class="noimg"><a href="#h4.1.3">4.1.3 Margins</a></p></li>
+ </ul>
+ </li><!-- end 4.1 -->
+ <li><p><img id="i4.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h4.2">4.2 Layout Commands</a></p>
+ <ul id="u4.2">
+ <li><p class="noimg"><a href="#h4.2.1">4.2.1 \SetTrimSize{}{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.2">4.2.2 \SetMargins{}{}{}{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.3">4.2.3 \SetFontSize{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.4">4.2.4 \SetLinesPerPage{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.5">4.2.5 \SetHeadFootStyle{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.6">4.2.6 \SetHeadJump{}, \SetFootJump{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.7">4.2.7 \SetMediaSize[]{}{}</a></p></li>
+ <li><p class="noimg"><a href="#h4.2.8">4.2.8 \SetCropmarkGap{}</a></p></li>
+ </ul>
+ </li><!-- end 4.2 -->
+ </ul>
+ </li><!-- end 4 -->
+
+ <li><p><img id="i5" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h5"><b>5. Fonts</b></a></p>
+ <ul id="u5">
+ <li><p><img id="i5.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h5.1">5.1 Parent Font and Descendants</a></p>
+ <ul id="u5.1">
+ <li><p class="noimg"><a href="#h5.1.1">5.1.1 Where Fonts Are Used</a></p></li>
+ <li><p class="noimg"><a href="#h5.1.2">5.1.2 Text Font</a></p></li>
+ <li><p class="noimg"><a href="#h5.1.3">5.1.3 Chapter Font</a></p></li>
+ <li><p class="noimg"><a href="#h5.1.4">5.1.4 Subch Font</a></p></li>
+ <li><p class="noimg"><a href="#h5.1.5">5.1.5 Head Font</a></p></li>
+ </ul>
+ </li><!-- end 5.1 -->
+ <li><p><img id="i5.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h5.2">5.2 Other Pre-Defined Fonts</a></p>
+ <ul id="u5.2">
+ <li><p class="noimg"><a href="#h5.2.1">5.2.1 Sans and Mono Fonts</a></p></li>
+ <li><p class="noimg"><a href="#h5.2.2">5.2.2 Math Font: Forget It</a></p></li>
+ <li><p class="noimg"><a href="#h5.2.3">5.2.3 Deco Font</a></p></li>
+ </ul>
+ </li><!-- end 5.2 -->
+ <li><p class="noimg"><a href="#h5.3">5.3 Defining New Fonts</a></p></li>
+ <li><p><img id="i5.4" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h5.4">5.4 Font Customization Syntax</a></p>
+ <ul id="u5.4">
+ <li><p class="noimg"><a href="#h5.4.1">5.4.1 Font Family vs. File Name</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.2">5.4.2 Set/New by Family/Filename</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.3">5.4.3 Open Type Features</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.4">5.4.4 Scale Pseudo-Feature</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.5">5.4.5 Color and Opacity</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.6">5.4.6 \CreateFeature{}{}</a></p></li>
+ <li><p class="noimg"><a href="#h5.4.7">5.4.7 Local Feature Changes</a></p></li>
+ </ul>
+ </li><!-- end 5.4 -->
+ <li><p><img id="i5.5" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h5.5">5.5 Superscripts, Subscripts</a></p>
+ <ul id="u5.5">
+ <li><p class="noimg"><a href="#h5.5.1">5.5.1 \SetMarkers[]{}</a></p></li>
+ <li><p class="noimg"><a href="#h5.5.2">5.5.2 \realmarker, \fakemarker</a></p></li>
+ </ul>
+ </li><!-- end 5.5 -->
+
+ </ul>
+ </li><!-- end 5 -->
+
+ <li><p><img id="i6" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h6"><b>6. Headers and Footers</b></a></p>
+ <ul id="u6">
+ <li><p><img id="i6.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h6.1">6.1 Global Header/Footer Settings</a></p>
+ <ul id="u6.1">
+ <li><p class="noimg"><a href="#h6.1.1">6.1.1 \SetHeadJump{}, \SetFootJump{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.1.2">6.1.2 \SetHeadFootStyle{}</a></p>
+ <li><p class="noimg"><a href="#h6.1.3">6.1.3 \SetEmblems{}{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.1.4">6.1.4 \SetPageNumberStyle{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.1.5">6.1.5 \SetHeadFont[]{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.1.6">6.1.6 \SetLooseHead{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.1.7">6.1.7 \SetChapterStart{}</a></p></li>
+ </ul>
+ </li><!-- end 6.1 -->
+ <li><p><img id="i6.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h6.2">6.2 Local Header/Footer Settings</a></p>
+ <ul id="u6.2">
+ <li><p class="noimg"><a href="#h6.2.1">6.2.1 \SetVersoHeadText{}, \SetRectoHeadText{}</a></p></li>
+ <li><p class="noimg"><a href="#h6.2.2">6.2.2 \thispagestyle{}</a></p></li>
+ </ul>
+ </li><!-- end 6.2 -->
+ </ul>
+ </li><!-- end 6 -->
+
+ <li><p><img id="i7" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h7"><b>7. Text</b></a></p>
+ <ul id="u7">
+ <li><p><img id="i7.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h7.1">7.1 Text Sizes</a></p>
+ <ul id="u7.1">
+ <li><p class="noimg"><a href="#h7.1.1">7.1.1 Standard Sizes: Disabled!</a></p></li>
+ <li><p class="noimg"><a href="#h7.1.2">7.1.2 Local sizing: \charscale[]{}</a></p></li>
+ <li><p class="noimg"><a href="#h7.1.3">7.1.3 Environment: parascale</a></p></li>
+ <li><p class="noimg"><a href="#h7.1.4">7.1.4 Open Type Scale</a></p></li>
+ </ul>
+ </li><!-- end 7.1 -->
+ <li><p><img id="i7.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h7.2">7.2 General Styling</a></p>
+ <ul id="u7.2">
+ <li><p class="noimg"><a href="#h7.2.1">7.2.1 Italics and Emphasis</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.2">7.2.2 Bold and Semibold</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.3">7.2.3 Underlining</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.4">7.2.4 Small Caps, Acronyms</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.5">7.2.5 Local Tracking</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.6">7.2.6 Local Font Selection</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.7">7.2.7 Local Font Features</a></p></li>
+ <li><p class="noimg"><a href="#h7.2.8">7.2.8 Text Color (grayscale)</a></p></li>
+ </ul>
+ </li><!-- end 7.2 -->
+ <li><p><img id="i7.3" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h7.3">7.3 Positioning and Alignment</a></p>
+ <ul id="u7.3">
+ <li><p class="noimg"><a href="#h7.3.1">7.3.1 What to Avoid</a></p></li>
+ <li><p class="noimg"><a href="#h7.3.2">7.3.2 Some Useful Commands</a></p></li>
+ </ul>
+ </li><!-- end 7.3 -->
+ </ul>
+ </li><!-- end 7 -->
+
+ <li><p><img id="i8" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h8"><b>8. Images</b></a></p>
+ <ul id="u8">
+ <li><p class="noimg"><a href="#h8.1">8.1 Use Raster Images</a></p></li>
+ <li><p><img id="i8.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h8.2">8.2 Use Flattened png or jpg</a></p>
+ <ul id="u8.2">
+ <li><p class="noimg"><a href="#h8.2.1">8.2.1 Saving the Resolution</a></p></li>
+ <li><p class="noimg"><a href="#h8.2.2">8.2.2 Removing Private Metadata</a></p></li>
+ </ul>
+ </li><!-- end 8.2 -->
+ <li><p><img id="i8.3" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h8.3">8.3 Line Art vs. Grayscale</a></p>
+ <ul id="u8.3">
+ <li><p class="noimg"><a href="#h8.3.1">8.3.1 Line Art in GIMP</a></p></li>
+ <li><p class="noimg"><a href="#h8.3.2">8.3.2 Grayscale in GIMP</a></p></li>
+ <li><p class="noimg"><a href="#h8.3.3">8.3.3 Scaling After \Rework</a></p></li>
+ </ul>
+ </li><!-- end 8.3 -->
+ <li><p><img id="i8.4" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h8.4">8.4 Placing Images</a></p>
+ <ul id="u8.4">
+ <li><p class="noimg"><a href="#h8.4.1">8.4.1 \charscale</a></p></li>
+ <li><p class="noimg"><a href="#h8.4.2">8.4.2 \InlineImage</a></p></li>
+ <li><p class="noimg"><a href="#h8.4.3">8.4.3 Text Over \InlineImage</a></p></li>
+ <li><p class="noimg"><a href="#h8.4.4">8.4.4 \BlockImage</a></p></li>
+ <li><p class="noimg"><a href="#h8.4.5">8.4.5 \BlockImage and Text</a></p></li>
+ </ul>
+ </li><!-- end 8.4 -->
+ </ul>
+ </li><!-- end 8 -->
+
+ <li><p><img id="i9" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h9"><b>9. Front Matter</b></a></p>
+ <ul id="u9">
+ <li><p class="noimg"><a href="#h9.1">9.1 Useful Commands in Front Matter</a></p></li><!-- end 9.1 -->
+ <li><p class="noimg"><a href="#h9.2">9.2 Chapter-Like Sections in Front Matter</a></p></li><!-- end 9.2 -->
+ <li><p><img id="i9.3" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h9.3">9.3 Examples of Front Matter Pages</a></p>
+ <ul id="u9.3">
+ <li><p class="noimg"><a href="#h9.3.1">9.3.1 Sample Title Page</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.2">9.3.2 Sample Copyright Page</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.3">9.3.3 Sample Dedication</a></p>
+ <li><p class="noimg"><a href="#h9.3.4">9.3.4 Sample Epigraph</a></p>
+ <li><p class="noimg"><a href="#h9.3.5">9.3.5 Sample Table of Contents</a></p>
+ <ul>
+ <li><p class="noimg"><a href="#h9.3.5.1">9.3.5.1 Environment: toc</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.5.2">9.3.5.2 \tocitem and \tocitem*</a></p></li>
+ </ul>
+ </li>
+ <li><p class="noimg"><a href="#h9.3.6">9.3.6 Sample Foreword</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.7">9.3.7 Sample Preface</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.8">9.3.8 Sample Acknowledgements</a></p></li>
+ <li><p class="noimg"><a href="#h9.3.9">9.3.9 Sample Map</a></p></li>
+ </ul>
+ </li><!-- end 9.3 -->
+ </ul>
+ </li><!-- end 9 -->
+
+ <li><p><img id="i10" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h10"><b>10. Front/Main Matter Transition</b></a></p>
+ <ul id="u10">
+ <li><p class="noimg"><a href="#h10.1">10.1 Introduction in Front Matter</a></p></li>
+ <li><p><img id="i10.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h10.2">10.2 Author's Note in Front Matter</a></p>
+ <ul id="u10.2">
+ <li><p><a href="#h10.2.1">10.2.1 Sample Author's Note</a></p></li>
+ </ul>
+ </li><!-- end 10.2 -->
+ <li><p class="noimg"><a href="#h10.3">10.3 Second Half-Title in Front Matter</a></p></li>
+ <li><p class="noimg"><a href="#h10.4">10.4 Part Separator in Main Matter</a></p></li>
+ <li><p class="noimg"><a href="#h10.5">10.5 Second Half-Title in Main Matter</a></p></li>
+ <li><p class="noimg"><a href="#h10.6">10.6 Introduction in Main Matter</a></p></li>
+ <li><p class="noimg"><a href="#h10.7">10.7 Prologue in Main Matter</a></p></li>
+ <li><p class="noimg"><a href="#h10.8">10.8 Chapters</a></p></li>
+ </ul>
+ </li><!-- end 10 -->
+
+ <li><p><img id="i11" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h11"><b>11. Chapter Structure</b></a></p>
+ <ul id="u11">
+ <li><p><img id="i11.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h11.1">11.1 Environment: ChapterStart</a></p>
+ <ul id="u11.1">
+ <li><p class="noimg"><a href="#h11.1.1">11.1.1 Chapter Title, Subtitle, Deco</a></p></li>
+ <li><p class="noimg"><a href="#h11.1.2">11.1.2 Default ChapterStart Header/Footer</a></p></li>
+ <li><p class="noimg"><a href="#h11.1.3">11.1.3 \thispagestyle at ChapterStart</a></p></li>
+ <li><p class="noimg"><a href="#h11.1.4">11.1.4 ChapterStart With Image</a></p>
+ <ul>
+ <li><p class="noimg"><a href="#h11.1.4.1">11.1.4.1 Text Over Image</a></p></li>
+ <li><p class="noimg"><a href="#h11.1.4.2">11.1.4.2 Text Within Image</a></p></li>
+ </ul>
+ </li>
+ </ul>
+ </li><!-- end 11.1 -->
+ <li><p><img id="i11.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h11.2">11.2 \QuickChapter and Scene Breaks</a></p>
+ <ul id="u11.2">
+ <li><p class="noimg"><a href="#h11.2.1">11.2.1 \QuickChapter</a></p></li>
+ <li><p class="noimg"><a href="#h11.2.2">11.2.2 \scenebreak and Others</a></p></li>
+ <li><p class="noimg"><a href="#h11.2.3">11.2.3 \IndentAfterScenebreak</a></p></li>
+ </ul>
+ </li><!-- end 11.2 -->
+ </ul>
+ </li><!-- end 11 -->
+
+ <li><p><img id="i12" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h12"><b>12. Footnotes, Endnotes</b></a></p>
+ <ul id="u12">
+ <li><p class="noimg"><a href="#h12.1">12.1 Footnotes</a></p></li>
+ <li><p><img id="i12.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h12.2">12.2 Endnotes</a></p>
+ <ul id="u12.2">
+ <li><p class="noimg"><a href="#h12.2.1">12.2.1 \endnote, \ResetEndnote, \memo{}</a></p></li>
+ <li><p class="noimg"><a href="#h12.2.2">12.2.2 \endnotetext{}{}</a></p></li>
+ </ul>
+ </li><!-- end 12.2 -->
+ <li><p class="noimg"><a href="#h12.3">12.3. Regarding Back Matter</a></p></li>
+ </ul>
+ </li><!-- end 12 -->
+
+ <li><p><img id="i13" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#h13"><b>13. Cover Artwork</b></a></p>
+ <ul id="u13">
+ <li><p class="noimg"><a href="#h13.1">13.1 Begin with PNG</a></p></li>
+ <li><p class="noimg"><a href="#h13.2">13.2 Get Some Software</a></p></li>
+ <li><p class="noimg"><a href="#h13.3">13.3 Convert to CMYK at Ink Limit</a></p></li>
+ <li><p class="noimg"><a href="#h13.4">13.4 Convert to PDF/X</a></p></li>
+ <li><p class="noimg"><a href="#h13.5">13.5 Final Check</a></p></li>
+ </ul>
+ </li><!-- end 13 -->
+
+ <li><p><img id="iA" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hA"><b>Appendix A. Book Terminology</b></a></p>
+ <ul id="uA">
+ <li><p class="noimg"><a href="#hA.1">A.1 Sheet, Page, Leaf</a></p></li>
+ <li><p class="noimg"><a href="#hA.2">A.2 Folio, Spine</a></p></li>
+ <li><p class="noimg"><a href="#hA.3">A.3 Signature, Imposition</a></p></li>
+ <li><p class="noimg"><a href="#hA.4">A.4 Perfect Binding</a></p></li>
+ <li><p class="noimg"><a href="#hA.5">A.5 Library Binding</a></p></li>
+ <li><p class="noimg"><a href="#hA.6">A.6 Paper and Cover Materials</a></p></li>
+ </ul>
+ </li><!-- end A -->
+
+ <li><p><img id="iB" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hB"><b>Appendix B. Six-Page Front Matter</b></a></p>
+ <ul id="uB">
+ <li><p class="noimg"><a href="#hB.1">B.1 Half-Title to Copyright</a></p></li>
+ <li><p class="noimg"><a href="#hB.2">B.2 Post-Copyright</a></p></li>
+ </ul>
+ </li><!-- end B -->
+
+ <li><p><img id="iC" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hC"><b>Appendix C. Shopping for Fonts</b></a></p>
+ <ul id="uC">
+ <li><p class="noimg"><a href="#hC.1">C.1 Licensing Issues</a></p></li>
+ <li><p class="noimg"><a href="#hC.2">C.2 Technical Issues</a></p></li>
+ <li><p class="noimg"><a href="#hC.3">C.3 Appearance Issues</a></p></li>
+ </ul>
+ </li><!-- end C -->
+
+ <li><p><img id="iD" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hD"><b>Appendix D. 240% Ink Limit</b></a></p>
+ <ul id="uD">
+ <li><p class="noimg"><a href="#hD.1">D.1 Bright Colors Preserved</a></p></li>
+ <li><p class="noimg"><a href="#hD.2">D.2 Natural Light Preserved</a></p></li>
+ <li><p class="noimg"><a href="#hD.3">D.3 Dark, Rich Colors Lost</a></p></li>
+ </ul>
+ </li><!-- end D -->
+
+ <li><p><img id="iE" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hE"><b>Appendix E. Command Summary</b></a></p>
+ <ul id="uE">
+ <li><p><img id="iE.1" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hE.1">E.1 Preamble</a></p>
+ <ul id="uE.1">
+ <li><p class="noimg"><a href="#hE.1.1">E.1.1 Class Options</a></p></li>
+ <li><p class="noimg"><a href="#hE.1.2">E.1.2 Metadata (File Data)</a></p></li>
+ <li><p class="noimg"><a href="#hE.1.3">E.1.3 Layout</a></p></li>
+ <li><p class="noimg"><a href="#hE.1.4">E.1.4 Specifying Fonts</a></p></li>
+ <li><p class="noimg"><a href="#hE.1.5">E.1.5 Other Configuration</a></p></li>
+ </ul>
+ </li>
+ <li><p><img id="iE.2" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hE.2">E.2 Document Body</a></p>
+ <ul id="uE.2">
+ <li><p class="noimg"><a href="#hE.2.1">E.1.1 Book Divisions</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.2">E.2.2 Page Management</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.3">E.2.3 Environments and Other Blocks</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.4">E.2.4 Scene Breaks, First Lines</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.5">E.2.5 Inline Text Effects</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.6">E.2.6 Footnotes and Endnotes</a></p></li>
+ <li><p class="noimg"><a href="#hE.2.7">E.2.7 Images</a></p></li>
+ </ul>
+ </li>
+ <li><p class="noimg"><a href="#hE.3">E.3 Disabled LaTeX Commands</a></p></li>
+ <li><p class="noimg"><a href="#hE.4">E.4 Discouraged LaTeX Commands</a></p></li>
+ </ul>
+ </li><!-- end E -->
+
+ <li><p><img id="iF" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAAC0lEQVQI12NgAAIAAAUAAeImBZsAAAAASUVORK5CYII=" class="nodisplaynav" onclick="plusminus(this.id);" title="open/close" alt=""/><a href="#hF"><b>Appendix F. Emergency Rework</b></a></p>
+ <ul id="uF">
+ <li><p class="noimg"><a href="#hF.1">F.1 \ReworkTrimSize</a></p></li>
+ <li><p class="noimg"><a href="#hF.2">F.2 \ReworkMargins</a></p></li>
+ <li><p class="noimg"><a href="#hF.3">F.3 Example of Rework</a></p></li>
+ <li><p class="noimg"><a href="#hF.4">F.4 Limitations of Rework</a></p></li>
+ <li><p class="noimg"><a href="#hF.5">F.5 Scaling Images</a></p></li>
+ </ul>
+ </li><!-- end F -->
+
+</ul><!-- end master toc ul -->
+
+<div style="height:1em"><script type="text/javascript">placenav();</script></div>
+
+</div><!-- end toc -->
+
+
+<!-- **************************************************************************************** -->
+
+<div id="main">
+<!-- **************************************************************************************** -->
+
+<h1 id="h0">Document class <i>novel</i> - documentation</h1>
+<p class="noindent">Version: 1.40, 2017/09/14. This is a complete re-write of the documentation, with the HTML in a single file, and many improvements.</p>
+<p> </p>
+
+
+<div id="page01" class="page">
+
+
+<h2 id="h1">1. Overview</h2>
+<div class="d2" id="d1">
+
+<h3 id="h1.1">1.1. Description</h3>
+<div class="d3" id="d1.1">
+<p class="noindent">The <i>novel</i> document class is intended for writers of original fiction, such as novels and collections of short stories. For this purpose, it provides easy-to-use settings that are pre-configured for the most common book Trim Sizes, according to publishing standards.</p>
+<p>The class uses the advanced typographic features of LuaTeX, fontspec, and microtype, and has the built-in capability to produce files compliant with PDF/X. All these capabilities are accessed via simple front-end commands that do the work for you, thereby reducing the learning curve.</p>
+<p>You will be using utf-8 encoding throughout, and Open Type fonts (or TrueType). That means built-in support for many languages.</p>
+<p>PDF/A and other formats pertaining to digital publication (e-books) are not supported, and never will be. If that is what you need, then this is the wrong document class for you.</p>
+<p>Bibliography, Floats, Tables, Math Mode, automatic generation of title page and table of contents... Forget them! Many of the TeX features used for academic work have reduced functionality, or are entirely disabled, in <i>novel</i> class. There is a reason for this. If you need those capabilities, find another document class. There is some support for page-bottom footnotes, but good support for raster (not vector) images.</p>
+<p>The class makes typographic choices that are best suited to <em>original</em> fiction, where you can easily resolve problematic typesetting by re-writing your own work. Note that modern commercial publishing is often very tolerant of widows and orphans, so <i>novel</i> makes no effort to control them.</p>
+<p>The <i>novel</i> class has a lot of possible settings, and a command structure that differs from other document classes in many ways. So, there is a lot of documentation. But you probably do not have to read most of it.</p>
+<p>Before you panic, look at the <i>novel-example.tex</i> demonstration file, in the documentation <i>extras</i> folder. It uses mostly default settings. See how easy that can be?</p>
+<p>If you are ready to typeset your great detective novel, or your collection of sci-fi short stories, then <i>novel</i> is for you. And, if you are unfamiliar with the terminology of commercial book publishing, have no fear! This documentation is here to help you.</p>
+
+<h4 id="h1.1.1">1.1.1. Installation</h4>
+<div class="d4" id="d1.1.1">
+<p class="noindent">Your TeX installation must be based on TeXLive 2016 or later (including any recent MiKTeX). If you are on Linux and your distro is something such as Ubuntu 16.04 LTS (Xenial), then the distro version of TeXLive is too old. However, you can sill install a more recent version of TeXLive manually, to your home directory, from <a class="external" rel="external" target="new" href="https://www.tug.org/texlive/"></a>.</p>
+<p>The <i>novel</i> package is not (yet) included with default TeX distribution. Once you have TeX working, use its package manager to install <i>novel</i>. The TeX package will be placed in <i>(texroot)/tex/lualatex/novel/</i>, the documentation will be placed in <i>(texroot)/doc/lualatex/novel/</i>, and the included font will be placed in <i>(texroot)/fonts/opentype/novel/</i>.</p>
+<p>Fonts from the <i>libertinus</i> package are required, and may be installed via your TeX package manager. Note that a <i>novel</i> document does not request the package, so you will not see an error if the fonts are not installed! 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 <i>luatex-cache</i> 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>
+</div>
+
+<h4 id="h1.1.2">1.1.2. Licensing</h4>
+<div class="d4" id="d1.1.2">
+<p class="noindent">The <i>novel</i> 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.</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. See this documentation regarding fonts.</p>
+</div>
+
+<h4 id="h1.1.3">1.1.3. Credits</h4>
+<div class="d4" id="d1.1.3">
+<p class="noindent">My method of "programming" largely involves using or modifying code provided by others under 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. Names or organizations are credited in-place within the TeX code, according to license.</p>
+<p>Various clipart graphics were obtained from <a class="external" rel="external" target="new" href="https://openclipart.org">openclipart.org</a>. The <i>NovelDeco.otf</i> font is partly derived from <i>Linux Libertine O</i>, using <a class="external" rel="external" target="new" href="https://fontforge.github.io/en-US/">FontForge.</a></p>
+<p>I read popular fiction a lot, usually books from my local public library. Even if I do not read a particular book, I often look a how it is designed. Throughout this documentation, where I recommend a design or style, it is most often based on the preponderance of designs/styles as I have seen in softcover or hardcover popular fiction, from major publishers in the U.S.A. That does not include "mass-market paperback" versions (the kind seen at supermarkets, rather than at bookstores). I may mention several common alternatives.</p>
+<p>I have also consulted the authoritative Chicago Manual of Style (CMoS) hardcover 16th Edition. In the case of fiction, CMoS occasionally notes that publishers sometimes don't do things the official way.</p>
+<p>Although I have looked at a variety of web sites concerning book design, I give these the least credence, because (a) often they merely duplicate each other's opinions, right or wrong, and (b) they may simply echo CMoS.</p>
+</div>
+
+<h4 id="h1.1.4">1.1.4. Success Story</h4>
+<div class="d4" id="d1.1.4">
+<p class="noindent">In August 2017, an original novel using this document class was published. The text block used nearly all the default settings, and was electronically submitted as PDF/X-1a:2001.</p>
+<p>The color cover image was designed in RGB using <a class="external" rel="external" target="new" href="https://inkscape.org">Inkscape</a> and <a class="external" rel="external" target="new" href="https://www.gimp.org">GIMP</a>, coverted to CMYK at 240% ink limit using <a class="external" rel="external" target="new" href="http://www.graphicsmagick.org">GraphicsMagick</a> and the methods described in this documentation, then finally converted to PDF/X-1a:2001 using this document class.</p>
+<p>Both files were automatically reviewed and accepted <i>on first attempt</i>, with the actual printed books for sale within a few days of file submission.</p>
+</div>
+
+<h4 id="h1.1.5">1.1.5. Help Wanted</h4>
+<div class="d4" id="d1.1.5">
+<p class="noindent">Although this package works for me, and there are no known issues, bugs are always possible. You may file an issue at the <a class="external" rel="external" target="new" href="https://github.com/RobtAll/novel">GitHub project page</a>, or contact the author by e-mail if you do not have a GitHub account. My e-mail address is towards the top of the <i>novel.cls</i> file.</p>
+<p>I, the original author of this package, am a retiree who prefers to move on to other things. If you are of a mind to take up long-term maintenance, then contact me by e-mail. If you already are a package developer with a <a class="external" rel="external" target="new" href="https://ctan.org/contact">CTAN</a> login, also contact them. You will need to understand elementary LuaLaTeX, fontspec, Unicode, Open Type fonts, PDF/X, and the general needs of ficion writers in the printed (not e-book) market. However, Lua, XeTeX, TiKz, math, and physics are not required (possibly counterproductive).</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h1.2">1.2. Important Behavior</h3>
+<div class="d3" id="d1.2">
+<p class="noindent">There are several ways that <i>novel</i> 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 <i>novel</i> best for its intended purpose.</p>
+
+<h4 id="h1.2.1">1.2.1. Always Use UTF-8, Without fontenc</h4>
+<div class="d4" id="d1.2.1">
+<p class="noindent">You must create your document in utf-8 encoding. No OT1, no T1, no LY1, or other TeX font encoding that pre-dates cell phones.</p>
+<p>Instead of typing TeX codes such as \`{e} you can simply paste è from a Unicode character map. Other alphabets such as Greek and Cyrillic are directly supported, as long as you choose fonts that support those character sets.</p>
+<p>Do not call for <i>fontenc</i> in your Preamble. The <i>novel</i> class is pre-configured for utf-8.</p>
+<p>If you use a plain text editor, or TeXWorks, or export plain text from a word processor, be sure that your text is encoded as utf-8, without byte order mark (BOM).</p>
+<p>If you are on Windows, do not use Notepad! The free <a class="external" rel="external" target="new" href="https://notepad-plus-plus.org">Notepad++</a> (also <a class="external" rel="external" target="new" href="https://portableapps.com/apps/development/notepadpp_portable">Portable</a> version) is a suitable plain text editor. Configure it as specified.</p>
+</div>
+
+<h4 id="h1.2.2">1.2.2. Do Not Load Fonts via \usepackage or \RequirePackage</h4>
+<div class="d4" id="d1.2.2">
+<p class="noindent">The method for loading fonts is described elsewhere on this page. Be sure you read that! For example, you cannot load a font with \usepackage{fontname} in this document class.</p>
+</div>
+
+<h4 id="h1.2.3">1.2.3. Use LuaLaTeX and Open Type fonts</h4>
+<div class="d4" id="d1.2.3">
+<p class="noindent"><img class="floatright" src="html-resources/doordie.png" width="279" height="300" alt="Thou Shalt"/> With <i>novel</i>, you will be using the <i>LuaLaTeX</i> engine, whether you like it or not. No <i>pdfTeX</i>, no <i>XeTeX</i>, no <i>dvips</i>. You do not have to understand <i>Lua</i> code, since the heavy lifting is already done for you.</p>
+<p>The built-in <i>fontspec</i> 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, and you probably have them. You will wonder why you never did this before.</p>
+</div>
+
+<h4 id="h1.2.4">1.2.4. Disabled standard text size commands</h4>
+<div class="d4" id="d1.2.4">
+<p class="noindent">Would you like to size text, using command such as \small or \LARGE ? Bah! They will be ignored. Write these commands, and the text will appear at its usual size, just as if the commands did not exist.</p>
+<p>There is a reason for this behavior, related to the need for constant line spacing. Thus, <i>novel</i> provides its own capability to size text, using different commands.</p>
+</div>
+
+<h4 id="h1.2.5">1.2.5. Disabled academic-purpose commands</h4>
+<div class="d4" id="d1.2.5">
+<p class="noindent"><img class="floatright" src="html-resources/fpaper.png" width="134" height="215" alt="flunked math"/> Commands such as \section, \chapter, \abstract, \index, \tableofcontents, \maketitle, and many other structural commands will not work with <i>novel</i>. 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 <i>novel</i> there are commands specifically created for the needs of fictional works. They are described below.</p>
+<p>Also, the <i>float</i> and <i>table</i> environments are ineffective. In <i>novel</i> there are specific ways to place images or construct a table of contents.</p>
+</div>
+
+<h4 id="h1.2.6">1.2.6. Images must be raster png or jpg</h4>
+<div class="d4" id="d1.2.6">
+<p class="noindent">You read that correctly. Sometimes fiction uses images, especially for the title page and chapter titles. With <i>novel</i>, do not use vector formats such as <i>eps</i>, <i>svg</i>, or <i>pdf</i> images. Use raster images in <i>png</i> or <i>jpg</i> format.</p>
+<p>There is a reason for this, explained below, where the use of images is discussed in detail. Be sure to read it, as <i>novel</i> has its own way to place images, in a way that is most likely to work well with fiction.</p>
+</div>
+
+<h4 id="h1.2.7">1.2.7. Beware of $, %, and Other TeX Special Characters</h4>
+<div class="d4" id="d1.2.7">
+<p class="noindent">This is standard TeX behavior. Just a reminder!</p>
+<p><img class="floatright" src="html-resources/trdol.png" width="238" height="67" alt="dollar is math mode"/> TeX has a number of special characters. If you type them in a document, they will not appear as an ordinary printed character, but will do something else. These are:</p>
+<p class="code"><code>$ % # _ ^ & ~ \ { }</code> and sometimes <code>[ ]</code></p>
+<p>In most cases, an incorrect usage will provide an error message that can be easily deciphered. However, the dollar sign and percent symbol are tricky. Incorrect use of the dollar sign may either place your text in math mode (not your intent) or produce a baffling error message that points to an innocent package. The percent symbol normally produces no error, since it is a comment character. But then, whatever text follows on that line will be missing from your PDF.</p>
+<p>Special characters, other than the backslash, are escaped by placing a backslash in front, thus: \$ for the dollar sign, \% for percent. If you must print a backslash, \string\ does it.</p>
+<p class="noindent"><b>• Tip:</b> To avoid unforeseen problems, you should review your document in a text editor, prior to compiling. Search for any instances of special characters, particularly dollar and percent. Backslash them as needed.</p>
+</div>
+
+<h4 id="h1.2.8">1.2.8. Avoid TeX Editors and IDEs</h4>
+<div class="d4" id="d1.2.8">
+<p class="noindent">You must create your document in utf-8 encoding. You may use a plain text editor (with or without TeX code highlighting), export plain text from a word processor (recommended), or use the minimal <i>TeXWorks</i> GUI. If you use <i>TeXWorks</i>, be sure that you are not running scripts that change the content of your document.</p>
+<p>Do not use another TeX editor, such as <i>Lyx</i> or <i>TeXstudio</i>, or an Integrated Development Environment (IDE). Those programs are often capable of inserting standard LaTeX code from menus. However, <i>novel</i> does not necessarily use that standard LaTeX code. The result may be unexpected.</p>
+</div>
+
+<h4 id="h1.2.9">1.2.9. Suggestion: Write Using a Word Processor</h4>
+<div class="d4" id="d1.2.9">
+<p class="noindent">I suggest that you write your novel in a word processor rather than in a text editor. <i>MS Word</i> and similar programs work. I use <a class="external" rel="external" target="new" href="https://www.libreoffice.org">LibreOffice</a> (also <a class="external" rel="external" target="new" href="https://portableapps.com/apps/office/libreoffice_portable">Portable</a> version). If you use <i>LibreOffice</i>, version 5.3 or later is much better than earlier versions.</p>
+<p>Why begin with a word processor? These programs can automatically substitute curly quotes and other characters. Remember than since you are using utf-8 encoding, you don't need to use TeX code for that, since you can simply insert the character directly. And, word processors have much better support for spell checking (and sometimes grammar). Just be sure that the word processor does not <i>automatically</i> correct your spelling, because any TeX code won't be in its dictionary.</p>
+<p>Remember that TeX closes paragraphs by skipping lines, or by \par. Also remember that in most word processors, the emdash is <i>two</i> hyphens, not the three used in TeX. You can always insert an emdash (or endash) directly. You can write TeX code into the word processor, where it will be treated like ordinary text, so use \textit{italicized} or similar command, rather than the word processor's italics menu.</p>
+<p>In any case, be sure to export plain text as utf-8, then compile it with <i>lualatex</i>.</p>
+<p class="noindent"><b>• Tip:</b> For the editing and proofreading phase, where spelling and grammar are carefully reviewed, I use a special font <i>CPmodified.otf</i>. This is my custom derivative of the <a class="external" rel="external" target="new" href="https://quoteunquoteapps.com/courierprime/">Courier Prime</a> regular font. <i>Cpmodified</i> can be found in the documentation <i>extras</i> folder. It is released under the SIL Open Font License v.1.1. To use this font for editing, install it in your <i>operating system</i>, not TeX. Then, call it from your word processor. The font includes Latin-1 and ANSI characters, and a few others. It is not quite monospaced (the em dash and ellipsis are longer). Punctuation is highly exaggerated, so you can see it more easily. My own experience is that most errors in the nearly-finished document involve punctuation.</p>
+</div>
+
+<h4 id="h1.2.10">1.2.10. Think for yourself</h4>
+<div class="d4" id="d1.2.10">
+<p>When TeX processes a document on a paragraph-by-paragraph basis, it chooses the layout that has the least total "penalty." Penalties are assessed based on factors such as word spacing, inter-line spacing, hyphenation, widows, and orphans. You may choose the value of each penalty.</p>
+<p>With <i>novel</i>, inter-line spacing is fixed, and there is no padding between paragraphs. No plus-or-minus. Hyphens are allowed, but strongly penalized. A reasonable amount of altered word spacing is allowed, and the built-in <i>microtype</i> package allows reasonable changes to letter spacing and the letters themselves. These choices achieve a high level of visual appeal and readability for flowing text.</p>
+<p>However, there is little penalty for widows or orphans. When you process a document with <i>novel</i> you are likely to find widows and orphans on many pages. This choice was made for several reasons. First, attention to widows and orphans would reduce the effectiveness of the other, more important, layout penalties. Second, fiction often has numerous short paragraphs (especially with dialogue), and it is very difficult for software to deal with all of them. Third, a great deal of contemporary fiction has widows and orphans. Fourth, it's your book... You can rewrite it!</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page01 -->
+<!-- ********************************************************************** -->
+<div id="page02" class="page">
+
+
+<h2 id="h2">2. Document Class Options</h2>
+<div class="d2" id="d2">
+<p class="noindent">As with other LaTeX classes, <i>novel</i> is called this way:</p>
+<p><code>\documentclass[options]{novel}</code></p>
+<p>As with other document classes, <i>novel</i> chooses a default paper size, and font size, if you do not make the choice. But there, the similarity ends. The default paper size in <i>novel</i> is 5.5" wide by 8.5" high, which is a popular book Trim Size for softcover fiction in the US, and close to the Demy Octavo (C novel) British size. And, the default font size is not an integer point size!</p>
+<p>In fact, you <em>cannot</em> set either the paper size or font size in the class options. You set them via other commands, in the Preamble. The commands are explained on other pages of this documentation.</p>
+<p>Still, there are a number of class options. As usual, options must be enclosed in braces and be separated by commas.</p>
+<p>Note: The <i>debug</i> option, unique to version 1.38, has been removed.</p>
+
+<h3 id="h2.1">2.1. draft</h3>
+<div class="d3" id="d2.1">
+<p class="noindent">The word DRAFT will appear at the upper left of each page.</p>
+<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="155" 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 <i>microtype</i> package will always be in final mode, and the included <i>hyperref</i> package will always be in draft mode.</p>
+<p>In draft mode, PDF/X compliance is turned off, no matter what you specify.</p>
+</div>
+
+<h3 id="h2.2">2.2. graytext</h3>
+<div class="d3" id="d2.2">
+<p class="noindent">The <i>novel</i> document class is intended for black/white book interiors. Normally, any color command, even gray, will be ignored, and the text will be rendered black. This does not affect images.</p>
+<p>The <i>graytext</i> option over-rides this restriction, and obeys grayscale color commands from the <i>xcolor</i> package, which is already loaded with the class. Non-grayscale colors will be converted to shades of gray.</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. Therefore, do not use very small text, or characters with fine lines.</p>
+<p>Sometimes the halftone operation extends 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>
+<p>You may place darker text over a lighter background. But even though the resulting PDF meets standards, lighter text over darker background is unlikely to print as intended.</p>
+</div>
+
+<h3 id="h2.3">2.3. shademargins</h3>
+<div class="d3" id="d2.3">
+<p class="noindent">This option is ignored unless using draft mode. It is not necessary to use the <i>graytext</i> option.</p>
+<p><img class="floatright" style="margin-top:6px" src="html-resources/shademargins.png" width="132" height="205" title="shademargins" alt="shademargins"/> The <i>shademargins</i> 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 \SetMediaSize 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 <i>shademargins</i> you can more easily see centering.</p>
+<p>Note that headers and footers are not part of the margins.</p>
+</div>
+
+<h3 id="h2.4">2.4. cropmarks</h3>
+<div class="d3" id="d2.4">
+<p class="noindent"><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 <i>cropmarks</i> 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 <i>cropmarks</i> 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 class="code"><code>\SetCropmarkGap{<em>length</em>}</code></p>
+<p>The cropmark gap is the distance between the Trim Box and where the crop lines begin. The purpose of the gap is so that the marks do not show on the trimmed paper, if the cut is a little bit off. In all cases, the far end of the cropmarks is 0.5in from the Trim Area. The gap is marked G in this diagram. The length must be least 0pt, and is more typically 0.125in or 0.250in. The default is 0.125in. </p>
+<p>If your Trim is placed off-center in the Media, then only one pair of cropmarks will be visible.</p>
+</div>
+
+<h3 id="h2.5">2.5. cropview</h3>
+<div class="d3" id="d2.5">
+<p class="noindent"><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 <i>cropview</i>, 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>
+<p>The accompanying image is the <i>cropview</i> display of the same page that was used to illustrate the <i>cropmarks</i> command. However, you do not need to have cropmarks, to use <i>cropview</i>.</p>
+</div>
+
+<h3 id="h2.6">2.6. closecrop</h3>
+<div class="d3" id="d2.6">
+<p class="noindent"><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>
+</div>
+
+<h3 id="h2.7">2.7. xml</h3>
+<div class="d3" id="d2.7">
+<p class="noindent">If you request your PDF to comply with PDF/X standards, it will automatically include XMP Metadata that can be seen as document properties in some (mostly professional) PDF reader software. The <i>xml</i> option exports this data with an xml header added, so that it can be independently viewed in software such as a browser.</p>
+<p>This option is only for your information; the exported xml file is not necessary. Whether or not you choose this option will not affect the structure or content of your PDF. If you set PDF/X compliance to <i>off</i>, then there will be no exported xml file.</p>
+<p>The exported file will be named <i>jobname-XMPasXML.xml</i>, where <i>jobname</i> is the file name of your *.tex document. If you wish to obtain the XMP packet, without the xml header, you can easily do that with a Unicode-compatible text editor. The necessary editing is obvious.</p>
+</div>
+
+<h3 id="h2.8">2.8. coverart</h3>
+<div class="d3" id="d2.8">
+<p class="noindent">This option is only used for cover artwork. See section 12.</p>
+</div>
+
+<h3 id="h2.9">2.9. unblock (primarily for developer use)</h3>
+<div class="d3" id="d2.9">
+<p class="noindent">A number of LaTeX packages are known to be incompatible with <i>novel</i>, because "the way those packages do things" conflicts with "the way <i>novel</i> does things." If you attempt to load one of those packages, then the results you get may not be in agreement with the formats and styles described in this documentation, because the other package over-rides some of <i>novel's</i> own macros.</p>
+<p>Therefore, at the end of your Preamble, <i>novel</i> reviews the loaded packages, and throws an error message if you included any of them via <i>\usepackage</i> or <i>\RequirePackage</i>. That also applies if you call some other package that chain-loads one of the forbidden packages.</p>
+<p>The odds that you will need a forbidden package are small, because they generally pertain to layout for mathematical and academic papers (tables, floats, equations, diagrams, etc.).</p>
+<p>If you specify document class option <i>unblock</i> then the list of forbidden packages will be disregarded by <i>novel</i>. Use at your own risk! This option is really intended for the convenience of developers, rather than ordinary users.</p>
+</div>
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page02 -->
+<!-- ********************************************************************* -->
+<div id="page03" class="page">
+
+<h2 id="h3">3. Metadata, File Data, and PDF/X</h2>
+<div class="d2" id="d3">
+<p class="noindent">The commands described on this page are used only in the Preamble.</p>
+<p>These commands write non-printing information to the PDF file. Some of the information is used to identify and classify the file. Other information is read by the printer, to assist it with printing choices.</p>
+<p>Unfortunately, some of the terms have slightly different meaning, depending on whether they are used in the context of printing, book distribution, or ebooks. To avoid confusion <em>within this documentation</em> I will use different terms when they mean different things. When you are communicating with your printing and distribution service, take care to ensure that your understanding of terminology is what they really mean.</p>
+
+<h3 id="h3.1">3.1. Definition of Terms</h3>
+<div class="d3" id="d3.1">
+<p class="noindent">This section is more detailed than it needs to be, because my review of various online forums (unrelated to TeX) shows a lot of user confusion.</p>
+
+<h4 id="h3.1.1">3.1.1. ISBN Metadata</h4>
+<div class="d4" id="d3.1.1">
+<p class="noindent"><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 a PDF ebook, 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>
+<p>Note: The ISBN refers to your <em>printed book</em>, not to the PDF file. You are not selling copies of the PDF.</p>
+</div>
+
+<h4 id="h3.1.2">3.1.2. Printed Metadata</h4>
+<div class="d4" id="d3.1.2">
+<p class="noindent"><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>
+<p>Some print services may object to artwork that is too fancy, on the grounds that it is difficult to discern the title and author. Although this is very unlikely, it is better to ask before committing resources.</p>
+</div>
+
+<h4 id="h3.1.3">3.1.3. File Data (PDF Metadata)</h4>
+<div class="d4" id="d3.1.3">
+<p class="noindent"><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>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 <i>novel</i> class.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h3.2">3.2. Rules for File Data</h3>
+<div class="d3" id="d3.2">
+<p class="noindent">File Data must conform to several specifications, in terms of what you may or may not write. Some of the limitations are imposed by the book distribution industry, which stores information in its databases a certain way.</p>
+
+<h4 id="h3.2.1">3.2.1. Required, Prohibited, Optional?</h4>
+<div class="d4" id="d3.2.1">
+<p class="noindent">If PDF/X compliance is required, then you <em>must</em> at least set the title in File Data, using the \SetTitle{} command. Note that this title is not styled in any way.</p>
+<p>Some print services require a minimum amount of file data, particularly title and author, which must match the printed metadata and ISBN metadata for these fields. Other services may require that the book's ISBN number, with something like <i>_text</i> added, be used in place of the title (remember that underscore is a special character in LaTeX). You will have to communicate with your service, and determine their requirements.</p>
+<p>Many print services do not care about File Data, one way or the other. Your PDF is passed through production according to its file name, not its internals. In such a case, assume that title and author are required.</p>
+<p>Caution: Be sure that any included images are stripped of their own image metadata. The procedure is described on farther along in this documentation.</p>
+</div>
+
+<h4 id="h3.2.2">3.2.2. Limited to Latin-1?</h4>
+<div class="d4" id="d3.2.2">
+<p class="noindent">At least in the USA, your print service may require that File Data be limited to characters in the Latin-1 set. This is because their production and distribution software uses Latin-1 for the database. Note that Latin-1 does not include curly quotes or em dash. You will still be using utf-8 encoding in your document files, but your choice of characters is restricted.</p>
+<p>If it were not for the database limitation to Latin-1, you could give your book a Greek or Cyrillic title, because <i>novel</i> can do it, and so can the PDF.</p>
+<p>If your book has File Data using quotes, then use the special commands \straightquote{} and \straightdblquote{}. Be sure to use the braces, so that you don't have to worry about gobbled space. When you use these commands instead of typing ' or " you eliminate the risk that your software will automatically convert them to the forbidden curly quotes. Example title:</p>
+<p class="code"><code>\SetTitle{That\straightquote{}s Amore} % That's Amore</code></p>
+<p>If you are limited to Latin-1 in File Data, you can still use curly quotes and em dash on the cover and title page, and in headings. In <i>novel</i> there is no \maketitle command, so you may (and should) apply styling to the printed title, even though the File Data title cannot be styled.</p>
+</div>
+
+<h4 id="h3.2.3">3.2.3. TeX escapes</h4>
+<div class="d4" id="d3.2.3">
+<p class="noindent">In File Data, you must obey the same TeX rules that apply everywhere: Certain characters have special meaning, and must be preceded by a backslash, if you wish to use them as ordinary characters. These are:</p>
+<p><code># $ % & _ { }</code> (hash, dollar, percent, ampersand, underscore, left and right curly brackets)</p>
+<p>Example: The title <em>Doing 9% & Gone</em> is coded:</p>
+<p class="code"><code>\SetTitle{Doing 9\% \& Gone}</code></p>
+<p>The above characters are rarely needed in File Data. Sometimes they must be spelled out, in order to agree with your book's ISBN Metadata. For example, you may need to write "and" rather than the ampersand.</p>
+</div>
+
+<h4 id="h3.2.4">3.2.4. Forbidden Characters</h4>
+<div class="d4" id="d3.2.4">
+<p class="noindent">• Do not use the backslash <code>\</code> except as described above.</p>
+<p class="noindent">• Do not use the tilde <code>~</code> or the circumflex <code>^</code>.</p>
+<p class="noindent">• Do not use TeX code, such as <code>\`e</code> for e with grave; instead paste è directly from a character map.</p>
+<p class="noindent">• Do not use styling, such as {\small text} or \textit{text}.</p>
+<p class="noindent">• Use only \straightquote{} and \straightdblquote{} if necessary, not TeX code for apostrphe or quote.</p>
+<p class="noindent">• Do not use multiple hyphens to create longer dahses. Do not use em dash or en dash.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h3.3">3.3. File Data Commands</h3>
+<div class="d3" id="d3.3">
+<p class="noindent">Now that you understand what File Data means, and how it may be written, you can use commands to write it.</p>
+
+<h4 id="h3.3.1">3.3.1. \SetTitle{}</h4>
+<div class="d4" id="d3.3.1">
+<p class="noindent">If you do not use the \SetTitle{} command, or leave it empty or blank, then the resulting PDF cannot comply with PDF/X standards. In very rare cases, that is desirable. Note that this information is not automatically transferred to your book's title page. It will be used as default in certain page heading styles, but you can over-ride it. The information can be retrieved as \theTitle anywhere in your document.</p>
+</div>
+
+<h4 id="h3.3.2">3.3.2. \SetAuthor{}</h4>
+<div class="d4" id="d3.3.2">
+<p class="noindent">This information is not automatically transferred to your book's title page. It will be used as default in certain page heading styles, but you can over-ride it. The information can be retrieved as \theAuthor anywhere in your document.</p>
+</div>
+
+<h4 id="h3.3.3">3.3.3. \SetSubtitle{}</h4>
+<div class="d4" id="d3.3.3">
+<p class="noindent">There is no file data for subtitle! The only reason for using this command is if you wish to later retrieve the information as \theSubtitle in your document.</p>
+</div>
+
+<h4 id="h3.3.4">3.3.4 Advanced: \SetApplication{} and \SetProducer{}</h4>
+<div class="d4" id="d3.3.4">
+<p class="noindent">The <i>Application</i>, also known as <i>CreatorTool</i>, is the program used to create your source document. Text editors, word processors, and page layout programs are the most common Applications (not particular to TeX). The PDF <i>Producer</i> is the program that converts the source document to PDF. In many cases, the Producer is a back-end, directly linked to the Application.</p>
+<p>These details are automatically created when you compile your document, without any input from you. However, if you have the need to provide a custom text string for the Application or Producer, these commands will do it.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h3.4">3.4. PDF/X</h3>
+<div class="d3" id="d3.4">
+<p class="noindent">Commercial printers are very likely to require PDF/X compliance. This ensures that your PDF meets a variety of criteria, by containing those things it must contain, and omitting those things it must not contain. Most perfectly valid PDF files are <em>not</em> PDF/X compliant, simply because they are not intended for commercial printing.</p>
+<p class="code"><code>\SetPDFX[<em>output intent</em>]{<em>compliance standard</em>}</code> and starred version</p>
+<p>If the \SetPDFX command is not used, it is <i>off</i> by default. Note that a non-compliant file is not a defective file! It complies with PDF standards, but not PDF/X standards. Some print services insist on PDF/X, and others don't care as long as the fonts are embedded (which they always are).</p>
+
+<h4 id="h3.4.1">3.4.1. Compliance Standards</h4>
+<div class="d4" id="3.4.1">
+<p class="noindent">The following choices are available:</p>
+<p><code>X-1a:2001</code></p>
+<p><code>X-1a:2003</code></p>
+<p><code>X-3:2002</code></p>
+<p><code>X-3:2003</code></p>
+<p><code>off</code> (default)</p>
+<p>The first of these is the one that is most widely accepted in commercial printing. Anything meeting X-1a:2001 necessarily meets the other standards. If your book involved complicated color artwork, then the correct choice might be crucial. But for a black and white book block, X-1a:2001 is the preferred choice unless your print service says otherwise.</p>
+</div>
+
+<h4 id="h3.4.2">3.4.2. Output Intent</h4>
+<div class="d4" id="d3.4.2">
+<p class="noindent">Unless compliance is <i>off</i>, an Output Intent is always required. However, <i>novel</i> treats this as an optional argument, because it will automatically use CGATSTR001 as default Output Intent.</p>
+<p>Output Intent informs the printer that you "intend" your PDF to be printed according to certain printer capabilities. If you took the trouble to soft-proof your PDF on a color-controlled monitor using color managed software, and if the printer's capabilities actually correspond to the intent, then the printed result will closely match what you expected. This is very important in commercial color printing (such as for cover artwork), but nearly irrelevant for a black and white book block. Nevertheless, an Output Intent is required to meet PDF/X compliance.</p>
+</div>
+
+<h4 id="h3.4.3">3.4.3. Built-in Output Intent Codes</h4>
+<div class="d4" id="d3.4.3">
+<p class="noindent">There are three pre-defined choices:</p>
+<p><code>CGATSTR001</code> (default)</p>
+<p><code>FOGRA39</code></p>
+<p><code>JC200103</code></p>
+<p>The first of these, more properly named "CGATS TR 001" with spaces, is also known as "US Web Coated SWOP v2" in the USA, and is the most commonly-used American print standard for this kind of book. The second is widely used in Europe, the third in Japan.</p>
+</div>
+
+<h4 id="h3.4.4">3.4.4. Other Output Intents</h4>
+<div class="d4" id="d3.4.4">
+<p class="noindent">If you are required to use an Output Intent that is not one of the above three, then you have to code it yourself. Have a look at the three pre-configured Output Intents (files <i>novel-CGATSTR001.clo</i>, <i>novel-FOGRA39.clo</i>, and <i>novel-JC200103.clo</i>). Instructions are inside the files. There are several places where you can find the necessary data; the most comprehensive is at the <a class="external" rel="external" target="new" href="http://www.color.org/index.xalter">Inernational Color Consortium</a>.</p>
+<p>In essence: If you create a custom Output Intent file named <em>novel-MyFunkyPrinter.clo</em>, then you request <i>MyFunkyPrinter</i> (without the preceding <i>novel-</i> or the <i>.clo</i> extension) as Output Intent, and that file will be loaded.</p>
+</div>
+
+<h4 id="h3.4.5">3.4.5. Whether or Not to Embed *.icc</h4>
+<div class="d4" id="d3.4.5">
+<p class="noindent">Each Output Intent has a corresponding color profile, in the form of a file with extension <i>*.icc</i>.</p>
+<p>You usually do not need it. In fact, unless your print service specifically asks you to embed the file, <i>don't do it</i>. When you use \SetPDFX in its un-starred form, the *.icc file will not be embedded.</p>
+<p>If your print service demands that you embed the *.icc color profile, then use \SetPDFX* (with the asterisk).</p>
+<p>Repeat: Do not embed the *.icc color profile unless specifically requested by your print service.</p>
+<p>If your printer requests "US Web Coated SWOP v2" and, as usual, requests that you <em>not</em> embed the corresponding *.icc color profile, then some software will read the Output Intent as "CGATS TR 001" instead of "US Web Coated SWOP v2". They are identical. But not everyone knows that.</p>
+</div>
+
+<h4 id="h3.4.6">3.4.6. Where to Find *.icc Files</h4>
+<div class="d4" id="d3.4.6">
+<p class="noindent">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> [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>
+<p>You want printer profiles, usually CMYK. Don't worry about the files being "for Windows," as they are actually cross-platform.</p>
+<p>If your system has the necessary <i>*.icc</i> file for your Output Intent, but <i>novel</i> cannot find it, then copy the file to the same folder as your TeX document.</p>
+<p>Again: Do not embed the file unless the printer requests it.</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page03 -->
+<!-- ************************************************************ -->
+<div id="page04" class="page">
+
+
+<h2 id="h4">4. Book Size and Page Layout</h2>
+<div class="d2" id="d4">
+<p class="noindent">There are many layout settings available, but you do not have to use them all. In fact, you may not need to use any of them! Your <i>novel</i> is pre-configured with settings that will often be suitable for the 5.5"W x 8.5"H Trim Size that is widely used in the American softcover fiction market.</p>
+<p>If you choose a different Trim Size, then some of the other defaults will be automatically tweaked, so that your starting point is reasonable for the requested size.</p>
+
+<h3 id="h4.1">4.1. Book Dimensions</h3>
+<div class="d3" id="d4.1">
+
+<h4 id="h4.1.1">4.1.1. Trim Size</h4>
+<div class="d4" id="d4.1.1">
+<p class="noindent"><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>
+</div>
+
+<h4 id="h4.1.2">4.1.2. Media Size, TrimBox</h4>
+<div class="d4" id="d4.1.2">
+<p class="noindent"><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. <i>Do not specify the Media Size, unless the commercial printer requests it.</i></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>
+</div>
+
+<h4 id="h4.1.3">4.1.3. Margins</h4>
+<div class="d4" id="d4.1.3">
+<p class="noindent"><b>Margins</b> are required on all four edges of the page. They do not have to be the same width. Generally the margin at the spine edge (inside margin) is wider.</p>
+<p>The accompanying illustration shows a typical recto page, on a layout with header and footer. The margins have been shaded gray in the picture (but, not in the book). The inside (spine) margin is at the left of this page. In the case of fiction, where there are no marginal notes, it is typically the case that the inside margin is the widest. But this is not a rule for all books. All that is required is that each margin be "wide enough" for the printing process.</p>
+<p>Keep in mind that the print services are not used to seeing books with exotic margins (such as bottom margin twice the size of top margin). They may think that there is a mistake in your PDF, or in the print job, if you do that.</p>
+<p>The <i>novel</i> document class does not provide for marginal notes.</p>
+<p>Normally, your TeX document will be compiled to a PDF that is electronically at the exact Trim Size. And normally, print services want it to be that way. When you view your PDF, the text will shift from side to side as you move through the pages, due to the slightly increased margin at the inside edge.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h4.2">4.2. Layout Commands</h3>
+<div class="d3" id="d4.2">
+<p class="noindent">Now that you understand how the terms are used, you are ready to use <i>novel</i> layout commands.</p>
+<p>Remember that everything is pre-configured, specifically for the purpose of fiction. You only need to write a layout command if you don't like the defaults.</p>
+
+<h4 id="h4.2.1">4.2.1. \SetTrimSize{<em>width</em>}{<em>height</em>}</h4>
+<div class="d4" id="d4.2.1">
+<p class="noindent">Command \SetTrimSize{}{} sets the size of your book. Both values must be written, using units such as <i>in</i> or <i>mm</i>. If you do not use this command, the default Trim Size will be the widely-used 5.5in wide x 8.5in high.</p>
+<p>This setting is most crucial. Unless your book is very exceptional, its Trim Size will be one of several standard sizes available from the print service. Among those sizes, only one or two will be "standard" for your genre.</p>
+<p>In the USA, 5.5in x 8.5in is often used for softcover fiction. Some fiction, and most nonfiction, prefers the slightly larger 6in x 9in trim size. Both of these are known as "trade" sizes.</p>
+<p>If you ever need to retroactively change Trim Size, see Appendix F.</p>
+<p>Do not request a <em>mass-market paperback</em> size unless you really, truly, know what you are doing. Since you are not a major writer for a major publishing house, you don't know; so, don't do it.</p>
+</div>
+
+<h4 id="h4.2.2">4.2.2. \SetMargins{<em>top</em>}{<em>outside</em>}{<em>bottom</em>}{<em>inside</em>}</h4>
+<div class="d4" id="d4.2.2">
+<p class="noindent"><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 \SetMargins lets you choose your own margins. If you use it, all four must be written, using units such as <i>in</i> or <i>mm</i>.</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 <i>novel</i> class uses <em>inside margin</em>, also known as <em>spine margin</em>, to mean C.</p>
+<p>If you ever need to retroactively change margins, see Appendix F.</p>
+</div>
+
+<h4 id="h4.2.3">4.2.3. \SetFontSize{<em>length</em>}</h4>
+<div class="d4" id="d4.2.3">
+<p class="noindent">In the <i>novel</i> document class, you do not set point size as a class option. Instead you use \SetFontSize in the Preamble.</p>
+<p>The size may be any units TeX understands, including decimal values. So, <i>12.8bp</i> and <i>13.1pt</i> are acceptable. This is because you will be using scalable, Open Type and TrueType fonts throughout your document. They do not need TeX metrics.<p>
+<p>If you insist on using ancient TeX fonts, then you may need to specify a convenient integer font size such as 11pt or 12pt. But why? Forget those fonts! Welcome to the Twenty-First Century.</p>
+<p>The minimum normal font size is 8pt, and the maximum is 18bp. On a local basis, text may be larger or smaller than this.</p>
+</div>
+
+<h4 id="h4.2.4">4.2.4. \SetLinesPerPage{<em>integer</em>}</h4>
+<div class="d4" id="d4.2.4">
+<p class="noindent">Lines per page refers only to the textblock, and does <em>not</em> include header/footer. Lines are not stretched to fill short pages.</p>
+<p>By default, a suitable number of lines per page are set, based on other dimemsions. You can change the default with this command. Any non-integer will be rounded. There is no direct command to set the <em>leading</em>, also known as line-to-line spacing or <em>baselineskip</em>. Instead, is is calculated from the textblock height and number of lines.</p>
+<p>If the calculated leading is less than 1.2x the font size, an error will result. It is difficult for TeX to honor all layout settings with such a small leading, which would normally be unacceptable for fiction in any case. If the calculated leading is at least 1.2x the font size, but less than 1.25x the font size, then the log file will have an Alert message, suggesting that you should consider using fewer lines per page. If the leading exceeds 1.4x the font size, then the log will have an Alert, suggesting more lines per page. The Alert messages are friendly; you do not necessarily have to do anything.</p>
+</div>
+
+<h4 id="h4.2.5">4.2.5. \SetHeadFootStyle{<em>number</em>}</h4>
+<div class="d4" id="d4.2.5">
+<p class="noindent"><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 \SetHeadFootStyle to choose the closest available style, then use <i>fancyhdr</i> commands for your custom style. The reason is that \SetHeadFootStyle tells the layout engine how much space it needs to reserve.</p>
+</div>
+
+<h4 id="h4.2.6">4.2.6. \SetHeadJump{<em>number</em>} and \SetFootJump{<em>number</em>}</h4>
+<div class="d4" id="d4.2.6">
+<p class="noindent">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>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>
+<p>The maximum is 3, minimum 1. The two jumps do not need to be identical. If your layout does not have a header and/or footer, then the corresponding setting does not matter.</p>
+<p>Don't worry about <em>headheight</em>. Whether you like it or not, headers (if used) will have only one line, and footers (if used) will have only one line. The necessary heights are calculated automatically.</p>
+</div>
+
+<h4 id="h4.2.7">4.2.7. Advanced: \SetMediaSize[<em>alignment</em>]{<em>width</em>}{<em>height</em>}</h4>
+<div class="d4" id="d4.2.7">
+<p class="noindent">Normally, the book Trim Size will also set the same size for the PDF pages. What you see is what you get.</p>
+<p>Some print services prefer that the Trim Size be floated in a standard paper size, such as US Letter or A4. That's not a technical necessity, but "the way things are done around here." If you must do that, use the \SetMediaSize command.</p>
+<p>The width and height must be specified with units, such as <i>in</i> or <i>mm</i>. If the optional <em>alignment</em> is not specified, then The Trim Size will be centered horizontally and vertically in the Media Size. That is the preferred method.</p>
+<p>If you write <i>edge</i> for the optional alignment, then the Trim Size will be off-center in the Media Size. Do not do this unless your print service specifically wants it that way. If you are making a hand-made book with a home printer, then this option might be convenient.</p>
+<p>Note that margins are measured relative to the Trim Size, not the Media Size. The extra white space between Trim Size and Media Size is just that: extra white space, unrelated to the margins of your book.</p>
+<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 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 <i>shademargins</i> 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>
+</div>
+
+<h4 id="h4.2.8">4.2.8. Advanced: \SetCropmarkGap{<em>length</em>}</h4>
+<div class="d4" id="d4.2.8">
+<p class="noindent"><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 <i>cropmarks</i> 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>
+</div>
+</div><!-- end class="d3" -->
+
+</div><!-- end class="d2" -->
+</div><!-- end page04 -->
+<!-- ************************************************************ -->
+<div id="page05" class="page">
+
+
+<h2 id="h5">5. Fonts</h2>
+<div class="d2" id="d5">
+<p class="noindent">This section describes how to choose fonts and font features, and how to apply fonts within your document. Local styling (such as italics) is described farther down this page.</p>
+<p><b>EEEK!</b> If you are like me, you <em>first</em> try to do something the way you did it before, then when it fails, you <em>finally</em> read the instructions. So, before you came to this page, you tried these things, and none of them worked:</p>
+<p class="code"><code>
+\usepackage{somefont} % FAILS!<br/>
+\renewcommand\rmdefault{smf} \normalfont % FAILS!<br/>
+\setmainfont{Some Font} % FAILS!
+</code></p>
+<p><b>DON'T PANIC.</b> In <i>novel</i>, the essential fonts are specified with different code. Fortunately, they are all pre-configured. If you accept the carefully-chosen defaults, then you do not need to worry about fonts. You do not even need to specify the font families. Sit back and relax.</p>
+<p>You can do something like this, if you have the font license. Then let <i>novel</i> do the rest:</p>
+<p class="code"><code>\SetParentFont{Adobe Garamond Pro} % WORKS!</code></p>
+<p><b>It's that simple.</b> But TeX being what it is, there are complicated ways to customize things. The rest of this page shows you how to do it. You will be using Open Type fonts, or perhaps TrueType fonts. Forget the old Type 1 fonts.</p>
+
+<h3 id="h5.1">5.1. The Parent Font and Descendants</h3>
+<div class="d3" id="d5.1">
+<p class="noindent">In <i>novel</i>, you do not directly set the default font, or the main font, or the roman font, or whatever. Instead, you set the parent font. The command:</p>
+<p class="code"><code>\SetParentFont[optional,features]{Font Family}</code></p>
+<p>The parent font, or <em>parentfont</em>, is the ancestor of several other fonts, wich will use the same font family unless you manually set them to something else:</p>
+<p class="centerimg"><img src="html-resources/font-tree.png" width="600" height="150" alt="parent and descendant fonts"/></p>
+<p>The <em>parentfont</em> has TeX ligatures and kerning, applied by default. All of the descendant fonts will also have TeX ligatures and kerning. (Note: TeX ligatures allow you to type `` to get “ and so forth.)</p>
+<p>If you specify any optional features for the <em>parentfont</em>, they will automatically be applied to descendants: <em>textfont</em>, <em>chapterfont</em>, <em>subchfont</em>, and <em>headfont</em>.</p>
+<p>If you do not set the <em>parentfont</em> yourself, then the following will be used as default, in order of priority: <em>Libertinus Serif</em>, <em>Linux Libertine O</em>, <em>Latin Modern Roman</em>.
+<p>The <em>Libertinus Serif</em> fonts are well-suited to fiction. If in doubt, use them. They can be downloaded as TeX <i>libertinus</i> package, but do not write \usepackage{libertinus} in your Preamble. Those fonts are a more up-to-date fork of the <em>Linux Libertine O</em> fonts, which are in the <i>libertine</i> package. Alas, even though <em>Latin Modern Roman</em> is a fine font, its style and weight are not well-suited to fiction; the only reason they are a last-choice default, is because just about every TeX system has them.</p>
+<p style="font-size:small">Note: In class version 1.0.10 and earlier, the <em>parentfont</em> was known as the <em>masterfont</em>, and the <em>textfont</em> was known as the <em>mainfont</em>. For backwards compatibility, both will work.</p>
+
+<h4 id="h5.1.1">5.1.1. Where Fonts Are Used</h4>
+<div class="d4" id="d5.1.1">
+<p class="noindent">The <em>parentfont</em> is not directly used, anywhere in your document. Instead, its descendants are specialized for use in different situations. Here is a typical page spread, using some of the pre-configured choices for chapters and headings:</p>
+<p class="centerimg"><img src="html-resources/fonts-in-use.png" width="532" height="408" alt="fonts in use"/></p>
+<p>If you use the <i>novel</i> pre-configured style commands, then the correct font will automatically be applied. That is the recommended, no-brainer method. If instead you choose to write your own custom styles, then you will also need to specify the fonts; but this allows you more TeX coding flexibility.</p>
+</div>
+
+<h4 id="h5.1.2">5.1.2. The Text Font</h4>
+<div class="d4" id="d5.1.2">
+<p class="noindent">The text font, or <em>textfont</em>, is the default main font used used for ordinary, flowing text. It uses the <em>parentfont</em>, with added features: common ligatures, and oldstyle numbers.</p>
+<p>Common ligatures (the Open Type <em>liga</em> feature) are such things as replacing f<span style="position:relative; left:2px">f</span> with the single character ff. Oldstyle numbers are designed to blend with surrounding text. Not every font has these features; if they are missing, then whatever the font actually has, is used instead.</p>
+<p>Normally, you do not need to call the <em>textfont</em> explicity, because it is the default for ordinary text. But in the event that you have a small passage in <em>textfont</em>, within a passage in some other font, you can do this:</p>
+<p class="code"><code>{\textfont <em>text</em>}</code></p>
+<p>Note that {\textfont <em>text</em>} and {\rmfamily <em>text</em>} mean the same thing.</p>
+<p>You do not set the <em>textfont</em> itself. It inherits from the <em>parentfont</em>.</p>
+</div>
+
+<h4 id="h5.1.3">5.1.3. The Chapter Title Font</h4>
+<div class="d4" id="d5.1.3">
+<p class="noindent">The <i>novel</i> command \ChapterTitle{<em>text</em>} automatically styles its text in the <em>chapterfont</em>.</p>
+<p>If you write custom code for chapter titles, then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
+<p class="code"><code>{\chapterfont <em>text</em>}</code></p>
+<p>You may customize the <em>chapterfont</em>:</p>
+<p class="code"><code>\SetChapterFont[optional,features]{Font Family} % Note command case!</code></p>
+<p>If you do not use the above command to customize the <em>chapterfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 1.6 scale.</p>
+</div>
+
+<h4 id="h5.1.4">5.1.4. The Chapter Subtitle Font</h4>
+<div class="d4" id="d5.1.4">
+<p class="noindent">The <i>novel</i> commands \ChapterSubtitle{<em>text</em>} and \QuickChapter{<em>text</em>} automatically style their text in the <em>subchfont</em>.</p>
+<p>If you write custom code for chapter subtitles or quick chapters, then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
+<p class="code"><code>{\subchfont <em>text</em>}</code></p>
+<p>You may customize the subchfont:</p>
+<p class="code"><code>\SetSubchFont[optional,features]{Font Family} % Note command case!</code></p>
+<p>If you do not use the above command to customize the <em>subchfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 1.2 scale.</p>
+</div>
+
+<h4 id="h5.1.5">5.1.5. The Header/Footer Font</h4>
+<div class="d4" id="d5.1.5">
+<p class="noindent">The <i>novel</i> pre-configured header/footer layouts automatically style their text in the <em>headfont</em>.
+<p>If you write a customer header/footer layout (using <code>fancyhdr</code> syntax), then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
+<p class="code"><code>{\headfont <em>text</em>}</code></p>
+<p>You may customize the headfont:</p>
+<p class="code"><code>\SetHeadFont[optional,features]{Font Family} % Note command case!</code></p>
+<p>If you do not use the above command to customize the <em>headfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 0.92 scale.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h5.2">5.2. Other Pre-Defined Fonts</h3>
+<div class="d3" id="d5.2">
+<p class="noindent">There are also a few pre-defined font commands that are "unrelated to" the <em>parentfont</em>.</p>
+
+<h4 id="h5.2.1">5.2.1. Sans and Mono Fonts</h4>
+<div class="d4" id="d5.2.1">
+<p class="noindent">You probably do not need a sans-serif or monospaced font in a work of fiction. The most prominent exception might be headers/footers, where the use of a light sans-serif font is fashionable. But in that case, set the <em>headfont</em> to the desired sans-serif font, instead of inheriting from <em>parentfont</em>.</p>
+<p>The <i>novel</i> class does not have its own commands for setting or using sans-serif or monospaced fonts. If you wish, you may use ordinary <i>fontspec</i> syntax to set them:</p>
+<p class="code"><code>
+\setsansfont[optional,features]{Font Family}<br/>
+\setmonofont[optional,features]{Font Family}
+</code></p>
+<p>Then, you may use them with ordinary LaTeX commands:</p>
+<p class="code"><code>
+{\sffamily <em>sans-serif text</em>}<br/>
+{\ttfamily <em>monospaced text</em>}
+</code></p>
+<p>If you do not set these fonts, then the defaults are: <em>Libertinus Sans</em>, or <em>Linux Biolinum O</em>, or <em>Latin Modern Sans</em> for the sans-serif font; <em>Libertinus Mono</em>, or <em>Linux Libertine Mono O</em>, or <em>Latin Modern Mono</em> for the monospaced font.</p>
+</div>
+
+<h4 id="h5.2.2">5.2.2. Math Font: Forget It!</h4>
+<div class="d4" id="d5.2.2">
+<p class="noindent">The <i>novel</i> class is not set up to do math. Seriously.</p>
+<p>Nevertheless, TeX being what it is, there is a behind-the-secene choice of a math font, which (hopefully) your document will never use. The code automatically looks for <em>Libertinus Math,</em> or <em>Asana-Math</em>, or <em>Latin Modern Math</em>.</p>
+<p>Otherwise, there is no special command for choosing a math font, and no special command for using it. Proof left to student.</p>
+</div>
+
+<h4 id="h5.2.3">5.2.3. The Deco Font</h4>
+<div class="d4" id="d5.2.3">
+<p class="noindent">The <i>novel</i> class ships with its own custom font, <em>NovelDeco.otf</em>. This Open Type font is specifically designed to provide a number of decorative glyphs, and some other characters. It is <em>not</em> a general-purpose font, and can <em>not</em> be replaced by any other font, except by a modified version of <em>NovelDeco</em>.</p>
+<p>The <em>decofont</em> is automatically configured. You do not need to set it. However, if you use a font editor to create a modified version, then your modification must have a different font name (to avoid confusion with the original). In such a rare case, you may point to your modified font like this:</p>
+<p class="code"><code>\SetDecoFont[optional,features]{YourDecoFont}</code></p>
+<p>The <em>decofont</em> is automatically called by other commands, such as \decoglyph{} and \acronym{}. Normally you do not request <em>decofont</em> directly. But if you wish to do so:</p>
+<p class="code"><code>{\decofont <em>text</em>}</code></p>
+<p>The decorative glyphs in this font (not including its ordinary characters) are shown in file <i>NovelDeco-glyphs.pdf</i>, which can be found in these docs in the documentation <i>extras</i> folder.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h5.3">5.3. Defining New Fonts</h3>
+<div class="d3" id="d5.3">
+<p class="noindent">You can define new font commands. The syntax depends on whether the new font is part of a family (where you might have bold and italic variants), or just a single file (no variants). If part of a family, use \NewFontFamily. If alone, use \NewFontFace.</p>
+<p>Note that if you define a font <em>family</em> when you should have just defined a font <em>face</em>, there will be complaints in the log file, because the font loaded cannot find the (nonexistent) other members of the family. But the document will compile. On the other hand, if you define a font <em>face</em> when you should have defined a font <em>family</em>, then commands for bold or italic will have no effect, since the other family members were not loaded. Again, the document will compile.</p>
+<p>The \NewFontFamily command (or \NewFontFace) takes three arguments: First, the name of the new font command is required. Second, font features are optional. Third, the font name is required.</p>
+<p style="margin-top:16px"><b>Example:</b> Suppose your work is science fiction, and one if its characters is a talking robot. You wish to depict its utterances in a robotic-looking font, which will be called using a new \robovoice command. You shop around, and find that the <em>Orbitron</em> font suits your purpose, except that it is too large compared to your <em>textfont</em>. So, you scale it.</p>
+<p>In the Preamble, you define the new font command:</p>
+<p class="code"><code>\NewFontFace\robovoice[Scale=0.8]{Orbitron} % not part of a family</code></p>
+<p>After some experimentation, you realize that the \robovoice letters need to be spread apart a bit. Do not use the standard LaTeX \textls command. Instead, go back and change the font definition like this:
+<p class="code"><code>\NewFontFace\robovoice[Scale=0.8,LetterSpace=<em>number</em>]{Orbitron} % pick a number</code></p>
+<p>In the document body:</p>
+<p class="code"><code>
+``Want some oil?'' asked Captain Withens.\par<br/>
+{\robovoice ``Is it Gamma-42 Special oil?''} asked the robot.\par<br/>
+``No, I got it on sale at Cosmo-Mart.''\par<br/>
+{\robovoice ``Forget it. I'm an oil gourmet.''}\par
+</code></p>
+<p>The result:</p>
+<p class="centerimg"><img src="html-resources/human-robot-talk.png" width="483" height="127" alt="conversation, human-robot"/></p>
+<p>Caution: If you are using a new font within body text (as above), then it is a bad idea to use Scale greater than 1.0. Reason: An excessively tall font will cause lines to spread apart.</p>
+<p style="margin-top:16px"><img class="floatright" src="html-resources/fluffy-conspiracy.png" width="265" height="409" alt="the fluffy conspiracy"/> <b>Example:</b> Suppose that you wish to style the title of your book, in a font that is not used for other things such as chapter titles. You purchase a license for the <em>Bernhard Modern Std</em> fonts, in Regular and Italic.</p>
+<p>In the Preamble:</p>
+<p class="code"><code>\NewFontFamily\booktitlefont{Bernhard Modern Std}</code></p>
+<p>The title page, using <code>\charscale</code> for size:</p>
+<p class="code"><code>
+\thispagestyle{empty}<br/>
+\vspace*{7\nbs}<br/>
+\begin{center}<br/>
+\charscale[3]{\booktitlefont The \textit{Fluffy} Conspiracy}\par<br/>
+\vspace{6\nbs}<br/>
+\charscale[2]{Priscilla Milde}\par<br/>
+\vfill<br/>
+Nonexistent Publications • Portland, Oregon\par<br/>
+\end{center}
+</code></p>
+<p style="clear:both; margin-top:16px; font-size:small">Note: Command \NewFontFamily is identical to \newfontfamily, and command \NewFontFace is identical to \newfontface.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h5.4">5.4. Font Customization Syntax</h3>
+<div class="d3" id="d5.4">
+<p class="noindent">You will be using <code>fontspec</code> syntax to select your own fonts. Much of what follows is a digested portion of the full <code>fontspec</code> documentation. There are many more features, and ways to use them, than will be described below.</p>
+
+<h4 id="h5.4.1">5.4.1. Font (Family) Name vs. Font File Name</h4>
+<div class="d4" id="d5.4.1">
+<p class="noindent">A <em>font file</em> is an individual file, with its own <em>file name</em>, including file extension. For example, libertinusserif-regular.otf and libertinusserif-italic.otf are two different font files. This much is obvious.</p>
+<p>A <em>font family name</em>, often merely called <em>font name</em>, refers to one or more font files that are variations of the same basic font. Some fonts are so unique that the family consists of just one file. For example, the NovelDeco font family consists of the one file NovelDeco.otf. Typically, a font family has four files, consisting of Regular, Italic, Bold, and BoldItalic variants. Even though there are four font files, there is a single font family name. Many font families have more than four files, including Semibold and Light weights, and Condensed tracking. It is up to the font designer to decide whether a Condensed variation of the "Bubble Turble" font should be treated as a member of the "Burble Turble" family, or as a separate "Burble Turble Condensed" family.</p>
+<p>The font (family) name can be learned by opening font files in your system font viewer. Currently, the Windows 10 font viewer uses "Font name" and the Ubuntu font viewer puts the font name in more prominent type. A font (family) name may contain more than one word, with or without spaces, and may contain a general classification such as <em>serif</em>, <em>sans</em>, or <em>mono</em>, because those are actually different families. But it will not contain words such as <em>regular</em>, <em>medium</em>, <em>semibold</em>, <em>bold</em>, or <em>italic</em>; those are for individual members of the same family. Within TeX, some of the older PostScript fonts have been re-worked as newer TrueType and Open Type fonts. The family names are slightly different, so pay attention.</p>
+<p class="centerimg">
+<img src="html-resources/win10libser.png" width="268" height="184" alt="Windows 10 font viewer"/>
+<img src="html-resources/ublibser.png" width="431" height="176" alt="Ubuntu font viewer"/>
+</p>
+</div>
+
+<h4 id="h5.4.2">5.4.2. Set/New by Font Name vs. File Name</h4>
+<div class="d4" id="d5.4.2">
+<p class="noindent">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>Preamble:</p>
+<p class="code" style="clear:both"><code>\NewFontFamily\rway{Raleway}</code></p>
+<p>Document Body:</p>
+<p class="code"><code>{\rway I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
+<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>Preamble:</p>
+<p class="code" style="clear:both"><code>\NewFontFamily\rwayi{Raleway-Regular-Italic.otf}</code></p>
+<p>Document Body:</p>
+<p class="code"><code>{\rwayi I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
+<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>Preamble:</p>
+<p class="code" style="clear:both"><code>\NewFontFamily\frankenfont[% note the % at linebreaks<br/>
+ ItalicFont=BaskervilleF-Italic.otf,%<br/>
+ BoldFont=libertinusserif-semibold.otf,%<br/>
+ BoldItalicFont=texgyrepagella-bolditalic.otf,%<br/>
+]{Raleway-Medium.otf}</code></p>
+<p>Document Body:</p>
+<p class="code"><code>{\frankenfont I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
+<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/>
+ ItalicFont=Raleway-Light-Italic.otf,%<br/>
+ BoldFont=Raleway-Medium.otf,%<br/>
+ 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>
+</div>
+
+<h4 id="h5.4.3">5.4.3 Open Type Features</h4>
+<div class="d4" id="d5.4.3">
+<p class="noindent">Features are variations, contained within a single font file. In the bad old days, when you wanted true small caps, you had to load a separate font file that had them (and did not have ordinary lowercase letters). Now, if an Open Type font file has the "smcp" feature, you obtain the small caps from within the same file, by asking for them. Requests for the feature may be made on-the-fly, or pre-loaded for global use.</p>
+<p>Here are several of the most frequently-used features, relevant to fiction writing. There are many more, and most fonts have only a few of them. Even when a font has a feature, it may be limited to some portion of the characters. For example, it is common for small caps to be available only for Latin-1 letters, even though the font also contains Greek and Cyrillic. To put this another way: The availability of a feature does not tell you its breadth of coverage. Unless the font has documentation showing coverage of its features, the only way to find out is to create and print a test page.</p>
+<table class="preconf">
+<caption>
+Some Frequently-Used Open Type Features
+</caption>
+<thead>
+<tr>
+<th>Description</th>
+<th>Open Type code </th>
+<th>fontspec code</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td><p>kerning</p></td>
+<td><p>kern</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: textfont, 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>
+</tr>
+<tr>
+<td><p>lowercase letters to small caps</p></td>
+<td><p>smcp</p></td>
+<td><p>Letters=SmallCaps</p></td>
+</tr>
+<tr>
+<td><p>uppercase letters to small caps</p></td>
+<td><p>c2sc</p></td>
+<td><p>Letters=UppercaseSmallCaps</p></td>
+</tr>
+<tr>
+<td><p>lining numerals</p></td>
+<td><p>lnum</p></td>
+<td><p>Numbers=Lining</p></td>
+</tr>
+<tr>
+<td><p>oldstyle numerals</p></td>
+<td><p>onum</p></td>
+<td><p>Numbers=OldStyle<br/><em>enabled: textfont, sansfont</em></p></td>
+</tr>
+</tbody>
+</table>
+<p>• Kerning is the automatic adjustment of spacing between letters, so that they fit together nicely. Common ligatures are substitutions, such as a combined <i>ff</i> character for two consecutive <i>f</i> characters. It is up to the font designer to determine which ligatures, if any, are common.</p>
+<p>• TeX ligatures (such as replacing `` with “ and --- with —) are not actually an Open Type feature, but they are treated that way by the software. All of these are enabled by default. The <i>fontspec</i> manual explains how to disable them, if necessary.</p>
+<p>• 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>• 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>• 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>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>• 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>• 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>
+</div>
+
+<h4 id="h5.4.4">5.4.4. Scale as Pseudo-Feature</h4>
+<div class="d4" id="d5.4.4">
+<p class="noindent">Although it is not an Open Type feature, <i>Scale=number</i> may be written like a feature. <i>Scale</i> globally adjusts the size of the font, relative to what it would otherwise be. If a local font size command is also applied, then the result is the compounded value.</p>
+<p>If the font will be mingled with other fonts in the same place, Scale can tweak a font so that it does not stand out. If Scale does not exceed 1, then the baselineskip will not be affected. Over 1 risks spreading lines to accomodate the extra size; this should not be done for fonts that will appear in the flowing main text. But over 1 is acceptable for display fonts that do not wrap lines and do not mingle with main text.</p>
+<p>Example: <em>Orbitron</em> is a special-purpose font with a mechanical or futuristic look. Its characters are much larger and heavier than would be found in book fonts. If I wish to mingle Orbitron with ordinary text, I might load the font like this:</p>
+<p class="code"><code>\NewFontFace\orbitron[Scale=0.6]{Orbitron} % Preamble</code></p>
+<p>Then in the document body, I could use it like this:</p>
+<p class="code"><code>The message was brief: {\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>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>
+</div>
+
+<h4 id="h5.4.5">5.4.5 Color and Opacity</h4>
+<div class="d4" id="d5.4.5">
+<p class="noindent">Even though the <i>fontspec</i> syntax allows you to set <i>Color</i> and <i>Opacity</i> as pseudo-features when you define a font, <em>the novel class blocks these features.</em> If you attempt to set them as features in a font definition, an error will result. The same applies if you attempt to add them, using \addfontfeature. However, you can still make use of grayscale using ordinary, local color commands.</p>
+<p>When you use the <i>graytext</i> class option, you may write text in grayscale, using commands from the included <i>xcolor</i> package. You should only do this for text that is in special locations. For example, if you begin each chapter with a number that is very large, you might wish to make that number gray, so that it does not overpower the main text.</p>
+<p>To avoid possible conflicts, the color specification should be chosen from a limited list of names. In order from dark to light: black, blue, violet, darkgray, purple, red, teal, olive, magenta, gray, brown, green, orange, cyan, lightgray, lime, pink, yellow, white. They will all be rendered in <em>shades of gray</em> (of course, black and white will be themselves). You may also choose from this more convenient list: black, gray1, gray2, gray3, gray4, gray5, gray6, gray7, gray8, gray9, white.</p>
+<p>If <i>graytext</i> is not chosen as class option, then any color (even white) will be rendered as black.</p>
+</div>
+
+<h4 id="h5.4.6">5.4.6. \CreateFeature{<em>code</em>}{<em>substitutions</em>}</h4>
+<div class="d4" id="d5.4.6">
+<p class="noindent">Once in a while, a font has a glyph that you would like to use, but it is not included in any of the font's Open Type feature sets. So, how to you grab that particular glyph? For example: One well-known font has a glyph named <em>emdash.alt</em>, which is not as long as the font's ordinary <em>emdash</em> glyph, and looks better in text. Unfortunately, <em>emdash.alt</em> is not in any of the font's style sets. Without some trickery, only a program such as InDesign can grab that glyph.</p>
+<p>Thanks to <i>fontspec</i>, <i>novel</i> has the necessary trickery. Command \CreateFeature creates a fake Open Type feature code, and assigns your list of substitutions to that code. Use comma-separated entries if there are multiple substitutions. For the case in question:</p>
+<p class="code"><code>\CreateFeature{myem}{emdash=emdash.alt}</code></p>
+<p>The code <i>myem</i> was randomly chosen as something that is not already defined among Open Type feature codes. Once specified, the fake feature may be used in any font definition, such as this:</p>
+<p class="code"><code>\SetMasterFont[RawFeature=+myem]{Adobe Garamond Pro}</code></p>
+<p>Of course, the fake feature has no effect if the font does not have the substitution character.</p>
+<p>This technique may be used for more complicated features, but that is beyond the scope of this documentation. See the <i>fontspec</i> manual if you need to do more.</p>
+</div>
+
+<h4 id="h5.4.7">5.4.7. Local Modifications to Open Type Features</h4>
+<div class="d4" id="d5.4.7">
+<p class="noindent">If you specify a particular Open Type feature, it will be generally used for that font command. So if you define a new font command with <i>Letters=SmallCaps</i> as a feature (and if the font actually has them), then small caps will be used for that font, whether or not you locally request them with a command such as \textsc.</p>
+<p>Often, you can add (or sometimes remove) features on a local basis. For example, suppose that you defined the font without using is <i>ss03</i> style set. You can locally add that feature to some text, using a command that looks like this:</p>
+<p class="code"><code>{\addfontfeature{<em>which feature</em>} <em>applied to this text</em>}</code></p>
+<p>The above code assumes that you are already using the font in that location. You cannot apply <i>ss03</i> from one font to an entirely different font!</p>
+<p>See the <i>fontspec</i> documentation for details of \addfontfeature.</p>
+<p>As an alternative to changing features locally, you can define different font commands to call the same underlying font, but with different features.</p>
+<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/>
+Some text {\baskf\addfontfeature{Numbers=Monospaced} hello 123} is here.
+</code></p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h5.5">5.5 Superscripts, Subscripts</h3>
+<div class="d3" id="d5.5">
+<p class="noindent">In <i>novel</i>, superscripts and subscripts are called "markers." Most book-quality Open Type fonts have markers in style sets (<i>sups</i>, <i>sinf</i>, <i>subs</i>).</p>
+<p>In professional fonts, marker glyph weights are adjusted for consistent appearance compared to ordinary glyphs. However, many free fonts do not adjust marker glyph weights, so the markers may appear too small, or too light. You may choose whether to use a font's own markers, or allow <i>novel</i> to generate markers, depending on whichever you think looks better.</p>
+
+<h4 id="h5.5.1">5.5.1 \SetMarkers[<em>real,fake</em>]{<em>asterisk, dagger, number</em>}</h4>
+<div class="d4" id="d5.5.1">
+<p>This command is used only in the Preamble. Default is <i>real</i> and <i>asterisk</i>.</p>
+<p>• The option <i>real</i> (default) attempts to use the Open Type feature <i>sups</i> for superscripts, and the feature <i>sinf</i> (preferred) or <i>subs</i> (alternate) for subscripts. If the requested feature is not available, then it will be automatically faked, by scaling/raising/lowering ordinary characters from the basefont (lining numerals will be used).</p>
+<p>• Option <i>fake</i> ignores whether the Open Type features are available, and simply fakes them.</p>
+<p>Thus, you may choose whether real or fake markers look better, depending on the font you are using. What looks better in one font may not look better in another.</p>
+<p>• The required argument applies only to markers created by the \footnote command. It does not apply to endnotes, or to manually placed superscripts and subscripts.</p>
+<p><i>asterisk</i> (default) uses symbolic footnote markers. The symbols rotate in order * † ‡ § ** †† ‡‡ §§ until reset.</p>
+<p><i>dagger</i> uses symbolic footnote markers, but without asterisks. The symbols rotate in order † ‡ § †† ‡‡ §§ until reset.</p>
+<p><i>number</i> uses numerical markers. Due to possible conflict, the log file will have a "Big Bad Warning" if you use a numerical footnote marker in a document that also has endnotes, since endnotes alays have numerical markers.</p>
+</div>
+
+<h4 id="h5.5.2">5.5.2 \realmarker, \fakemarker</h4>
+<div class="d4" id="d5.5.2">
+<p class="noindent">Within the body of the document, you may use \realmarker and \fakemarker to change your preference. The choice remains in effect until you change it again.</p>
+<p>The option real/fake applies wherever superscripts or subscripts are used, not just for footnotes or endnotes.</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page05 -->
+<!-- ************************************************************ -->
+<div id="page06" class="page">
+
+
+<h2 id="h6">6. Headers and Footers</h2>
+<div class="d2" id="d6">
+<p class="noindent">The <i>novel</i> class has a default header style. If you like it, then you do not have to use any of the configuration commands. So, before studying these commands, do a test document that uses the defaults.</p>
+<p>You may choose among several pre-configured header/footer styles. Then, you may change the appearance, content, and position. If none of it works for you, then you may define your own headers/footers using <i>fancyhdr</i> syntax. However, just about every style used in fictional works can be obtained using the pre-configured styles and adjustments.</p>
+<p>Individual pages, such as title, copyright, and new chapters, can have the header/footer style changed locally, on a per-page basis.</p>
+
+<h3 id="h6.1">6.1. Global Header/Footer Settings, only in Preamble.</h3>
+<div class="d3" id="d6.1">
+<p class="noindent">These commands determine whether your book will have headers and/or footers, and set the default style that is used for nearly all pages of the text. Per-page exceptions, such as for blank pages, title, copyright, and new chapters, are performed using the local settings commands.</p>
+
+<h4 id="h6.1.1">6.1.1. <code>\SetHeadJump{<em>number</em>}</code>, <code>\SetFootJump{<em>number</em>}</code></h4>
+<div class="d4" id="d6.1.1">
+<p class="noindent">These two commands control the separation between the header/footer and the main text. Since they pertain to page layout, rather than style, their usage is described above, in the layout section.</p>
+</div>
+
+<h4 id="h6.1.2">6.1.2. <code>\SetHeadFootStyle{<em>number</em>}</code></h4>
+<div class="d4" id="d6.1.2">
+<p class="noindent">Command \SetHeadFootStyle{<em>number</em>} chooses among several pre-configured header/footer styles, numbered 1 through 6. The default is style 1. The internals of the configuration can then be changed using a variety of commands.</p>
+<p>Some styles support an optional "emblem", which applies a decoration near the page number.</p>
+<p>Style 0 means neither header nor footer. Not practical for fiction, but it exists.</p>
+<p> </p>
+<img class="floatright" src="html-resources/headfoot1.png" width="276" height="219" alt="style 1" title="style 1"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{1}</b></p>
+<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>
+<div style="clear:both"></div>
+<img class="floatright" src="html-resources/headfoot2.png" width="276" height="219" alt="style 2" title="style 2"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{2}</b></p>
+<p>Only Footer.<br/>
+Page number at outside (left verso, right recto).<br/>
+Optional emblem adjacent to page number.</p>
+<div style="clear:both"></div>
+<img class="floatright" src="html-resources/headfoot3.png" width="276" height="219" alt="style 3" title="style 3"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{3}</b></p>
+<p>Only Footer.<br/>
+Page number centered.<br/>
+Disregards emblem, if coded.</p>
+<div style="clear:both"></div>
+<img class="floatright" src="html-resources/headfoot4.png" width="276" height="219" alt="style 4" title="style 4"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{4}</b></p>
+<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>
+<div style="clear:both"></div>
+<img class="floatright" src="html-resources/headfoot5.png" width="276" height="219" alt="style 5" title="style 5"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{5}</b></p>
+<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>
+<div style="clear:both"></div>
+<img class="floatright" src="html-resources/headfoot6.png" width="276" height="219" alt="style 6" title="style 6"/>
+<p style="padding-left:16px">
+<b>\SetHeadFootStyle{6}</b></p>
+<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 id="h6.1.2.1">Custom Style</h5>
+<div class="d5" id="d6.1.2.1">
+<p class="noindent">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>
+<p>• In the Preamble, use one of the above \SetHeadFootStyle{<em>integer</em>} to pick a starting point, in terms of whether or not there is a header and/or footer. <em>This is required, so that the layout engine knows how to calculate space.</em> After that, write the <i>fancyhdr</i> code for your custom header/footer in the Preamble. It will over-ride the numerical style in terms of appearance, but occupy the same space.</p>
+<p>• You cannot use a header or footer with more than one line. No exceptions.</p>
+<p>• See the file <i>novel-HeadFootStyles.sty</i> for how it is done in the pre-configured styles. In the file, the relevant portion follows <em>Look here for the pre-defined styles, for use as models.</em></p>
+<p>• Particularly note that your own style will not automatically use the headfont, or loose tracking, unless you include the necessary code in your own definition. Do not use the \textls command.</p>
+<p>• No cheating! If you choose a numerical style that does not have a header, then do not attempt to write a custom style that includes a header. Same with footer. Also, if you you choose a numerical style with both header and footer, then you cannot only customize one of them; you must customize both.</p>
+</div></div><!-- end class="d4" -->
+
+<h4 id="h6.1.3">6.1.3. <code>\SetEmblems{<em>verso</em>}{<em>recto</em>}</code></h4>
+<div class="d4" id="d6.1.3">
+<p class="noindent">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 4, 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 \NewFontFace command), or unless you use one of the built-in \decoglyph 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"/>• 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"/>• 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>• 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 \InlineImage command must be used. See <i>novel's</i> image documentation details. You may find that a vertical offset of \nfs (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/>
+{\InlineImage[0pt,b]{spy.png}}
+</code></p>
+<p>• At the small size of an emblem, it is difficult to use detailed artwork. A black/white image at 600dpi will print similarly to a font dingbat. Grayscale at 300dpi will probably not be satisfactory unless the emblem is a single shade of gray. For the above example, a character from the "Fontawesome" font was converted to a png image at mid-gray. It is less distracting than a black character from the font, but hard to discern. Note that there is no "gray ink" for directly writing text in gray.</p>
+<p>• Ask your print service whether the presence of a small image in each page header will affect production costs. Probably not, but if there is a different per-page charge when pages have an image... Oops!</p>
+<p>• The layout calculation does not care whether emblems intrude into the margins. You will have to inspect your PDF to determine whether a header emblem is too tall, or a footer emblem too deep, for the allowed top and bottm margin clearance. Class option <i>shademargins</i> (in draft mode only) is helpful.</p>
+</div>
+
+<h4 id="h6.1.4">6.1.4. <code>\SetPageNumberStyle{<em>code using \thepage</em>}</code></h4>
+<div class="d4" id="d6.1.4">
+<p class="noindent">By default, the page number is simply \thepage. 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 \thepage is displayed. Examples:</p>
+<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 head/foot style 3 or 5.</code></p>
+<p>The <i>headfont</i> 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>
+</div>
+
+<h4 id="h6.1.5">6.1.5. <code>\SetHeadFont[<em>features</em>]{<em>font</em>}</code></h4>
+<div class="d4" id="d6.1.5">
+<p class="noindent">This setting is described earlier on this page.</p>
+</div>
+
+<h4 id="h6.1.6">6.1.6. <code>\SetLooseHead{<em>number</em>}</code></h4>
+<div class="d4" id="d6.1.6">
+<p class="noindent">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>Note: Do not use the \textls command. It is disabled in this class.</p>
+<p class="centerimg"><img src="html-resources/looseheads.png" width="400" height="76" alt="loosehead 50 and 100"/></p>
+<p>The argument of \SetLooseHead is a number from 0 to 1000. At 0 there is no extra space between the letters. Values from 50 (default) to 200 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>
+<p>The looseness applies to inter-letter spacing, but not to inter-word spacing. To increase inter-word spacing, use extra code such as \, (which is a LaTeX thin space) as needed.</p>
+</div>
+
+<h4 id="h6.1.7">6.1.7. <code>\SetChapterStart{<em>choice</em>}</code></h4>
+<div class="d4" id="d6.1.7">
+<p class="noindent">This command is only applied if you begin new chapters with the ChapterStart environment. You may pick one of the \thispagestyle choices, described in the next section. For example:</p>
+<p class="code"><code>\SetChapterStart{dropfolioinside}</code></p>
+<p>Then, that choice will be applied to each page that uses ChapterStart, without you having to write \thispagestyle each time.</p>
+<p>The default is <i>footer</i>. This allows a ChapterStart page to show its footer (only if it has one), but not header.</p>
+<p>If you use this command, you may still over-ride it on a particular page, by using \thispagestyle{<em>choice</em>} <em>before</em> \begin{ChapterStart}.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h6.2">6.2. Local Header/Footer Settings, in Document Body</h3>
+<div class="d3" id="d6.2">
+<p class="noindent">These commands are used when a page header/footer style is an exception to the general rule. Examples are blank pages, titles, copyright, and new chapters. You can also dynamically change the header text.</p>
+
+<h4 id="h6.2.1">6.2.1. <code>\SetVersoHeadText{<em>text</em>}</code><code>\SetRectoHeadText{<em>text</em>}</code></h4>
+<div class="d4" id="d6.2.1">
+<p class="noindent">If you are using style 1, 4, 5, or 6, the header text can be dynamically changed from page to page. This feature is useful if your wish to include chapter titles in the header. It is also useful if your work is a collection of stories with different titles, perhaps by different authors. But before you use this feature, speak with your print service! Many print-on-demand services will insist that the content of headers must not vary from place to place, because different headers may be confused with portions of different books, during the assembly process.</p>
+<p class="code"><code>\SetVersoHeadText{New Verso Head}</code><br/><code>\SetRectoHeadText{New Recto Head}</code></p>
+<p>These two commands may be used at any time, in the Preamble or document body. When a command is used, it stores its argument in \versoheadtext or \rectoheadtext. In turn, the current value of \versoheadtext or \rectoheadtext is immediately used for the header, and will remain in effect until changed again by \SetVersoHeadText or \SetRectoHeadText.<p>
+<p>If you do not use these commands in the Preamble, then at the beginning of the document body they will be automatically set to the author (verso) and the title (recto). However, you may find that the inter-word space is closer than you would like.<p>
+<p>For improved inter-word space, use \, (the LaTeX thin space) in addition to ordinary space. You may use as many as you need.</p>
+<p>You may use ordinary LaTeX styling commands for the text:</p>
+<p class="code"><code>\SetRectoHeadText{The \,\emph{Bad \,Boy} \,Chronicles}</code></p>
+<p>The most popular styling uses lowercase to small caps:</p>
+<p class="code"><code>\SetRectoHeadText{\smcp{The \,Danton \,Code}}</code></p>
+<p>• Avoid bold. Avoid underline. Really. Don't do it. No, no, no!</p>
+<p>• From <i>novel</i> version 1.32, you are no longer required to use tilde instead of space.</p>
+</div>
+
+<h4 id="h6.2.2">6.2.2. <code>\thispagestyle{<em>choice</em>}</code></h4>
+<div class="d4" id="d6.2.2">
+<p class="noindent">When you choose a style with header, then space is allocated above the text block, where the header will be placed. That space will be allocated whether or not the header is full or empty. The same applies to the footer. This allocation is global, and cannot be changed in your document body. All standard books work this way, not just with TeX.</p>
+<p>However, on a per-page basis you can change whether or not a header or footer has visible content. This is routinely done for blank pages, title page, copyright page, and some others. It is also the norm for pages that begin a new chapter.</p>
+<p>• The word "folio" has several meanings: It may refer to a particular paper size, or to a folded piece of paper at any size, or simply to a page number. Below, "folio" means page number.</p>
+<p>• When you use the \thispagestyle command, your choice is applied only to the one page on which the command is written. It is best to use this command at or towards the top of the affected page. If the page uses the ChapterStart environment, and you use \thispagestyle, then you <em>must</em> place \thispagestyle before \begin{ChapterStart}.</p>
+<p>• The following choices are allowed: <i>fancy</i>, <i>empty</i>, <i>footer</i>, <i>forcenumber</i>, <i>dropfoliobeneath</i>, and <i>dropfolioinside</i>.</p>
+<p>For compatibility reasons, <i>plain</i> and <i>fancyplain</i> are also allowed, and have the same effect as <i>footer</i>.</p>
+<p> <b>\thispagestyle{fancy}</b></p>
+<p>This applies the default (fancy) page style, so it is not normally needed. Only use this command to over-ride some other \thispagestyle command, or to over-ride the \SetChapterStart setting.</p>
+<p> <b>\thispagestyle{empty}</b></p>
+<p>Header and footer are both blank.</p>
+<p> <b>\thispagestyle{footer}</b></p>
+<p>Ignored if the style has no footer. If it does, then the usual footer appears. Header, if any, is blank.</p>
+<p>This command is an alias for <i>fancyplain</i>. It is like the <i>plain</i> style, except that the footer (which is presumed to contain the page number) is fully styled. But unlike <i>plain</i>, the <i>footer</i> style does <em>not</em> cause a page number to appear when no footer exists. If that is what you need, then use either style <i>dropfoliobeneath</i> or <i>dropfolioinside</i>, depending on whether you have extra room in the bottom margin.</p>
+<p> <b>\thispagestyle{forcenumber}</b></p>
+<p>If the style has a footer, then it appears as usual, and the header (if any) is blank. If the style has a header but no footer, then the outside portion of the header (which is presumed to contain the page number and emblem) appears, but the text portion of the header is blank.</p>
+<p>The <i>forcenumber</i> choice is non-standard. Use it only if you must have a page number, and no other choice is suitable.</p>
+<p> <b>\thispagestyle{dropfoliobeneath}</b></p>
+<p>The header (if any) is blank. If there is a footer, then it appears as usual. But if there is no footer, this command creates a one-page fake footer, which contains the centered page number. The fake footer is located where the next line of text would be, if the textblock were one line longer than its actual value.</p>
+<p>• For the fake footer to be acceptable in print, the bottom margin must be wider than the minimum amount required by your print service. For example, suppose that the minimum bottom margin is 0.5in, but you set the bottom margin to 0.75in. That gives you 0.25in wiggle room, into which the fake footer will probably fit, because typical baselineskip is 0.2in to 0.25in.</p>
+<p>• The document class does not know whether or not you have extra space available in the bottom margin. It is your responsibility to know.</p>
+<p> <b>\thispagestyle{dropfolioinside}</b></p>
+<p>The header (if any) is blank. If there is a footer, then it appears as usual. But if there is no footer, this commands temporarily reduces the number of lines per page by one line. At the bottom, where the last line of text would normally be, the page number is centered. Thus, there is no intrusion into the bottom margin.</p>
+<p>This command may only be used following the \clearpage command. Thus, it may be used at the start of new chapters, or on pages (such as copyright page) that do not flow from a previous page. If you use it elsewhere, the print will have incorrect layout, but there will be no error or warning, since the compiler is not sure what you are trying to do.</p>
+<p>If used on a page with ChapterStart environment, you must place \thispagestyle{dropfolioinside} <em>before</em> \begin{ChapterStart}. The ChapterStart block has a disposable blank line at its top, which is removed when <i>dropfolioinside</i> is used (instead of removing a line from the following text block).</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page06 -->
+<!-- ************************************************************ -->
+<div id="page07" class="page">
+
+
+<h2 id="h7">7. Text Sizes and Styling</h2>
+<div class="d2" id="d7">
+<p class="noindent">This section describes how to change the size of text, how to style text (such as italics), and how to move it around. It also describes some miscellaneous commands that are intended to modify text.</p>
+<p>Information about how to choose the main text point size is described earlier on this page. Information about choosing fonts and font features is also described earlier on this page.</p>
+<p>There is no direct setting for normal baselineskip; it is automatically calculated from the size of the textblock and lines per page.</p>
+
+<h3 id="h7.1">7.1. Text Sizes</h3>
+<div class="d3" id="d7.1">
+<p class="noindent">Be sure to read through this. In <i>novel</i>, standard TeX font size commands are disabled. There are new commands that address the limited needs for font sizing, in the context of fiction. These new commands are primarily for local adjustments of a few characters, or for display pages that are outside the main flow of text.</p>
+
+<h4 id="h7.1.1">7.1.1. Surprise! Traditional TeX Font Size Commands Are Disabled.</h4>
+<div class="d4" id="d7.1.1">
+<p class="noindent">Ah, the simplicity of TeX font size commands, such as \small and \LARGE. But in <i>novel</i>, they don't work. If you write {\LARGE text}, then the incuded text appear at normal size. This is by design.</p>
+<p>Why? In <i>novel</i>, the focus is on maintaining a constant baselineskip, so that facing pages have text aligned. This is impossible with the standard TeX commands. In particular, commands to increase font size will change the baselineskip, whether you like it or not, even if you try to code for a constant baselineskip. That's just the way TeX works.</p>
+<p>The one exception is that footnotes will appear with smaller than normal size and skip. But this is done automatically. You cannot manipulate it with a size command.</p>
+<p>Fortunately, there are not a lot of occasions where fiction needs to change font size. In <i>novel</i>, there are new commands to address each situation.</p>
+</div>
+
+<h4 id="h7.1.2">7.1.2. \charscale[<em>scale,hoffset,voffset</em>]{<em>text</em>}, \charscale*[<em>scale,hoffset,voffset</em>]{<em>text</em>}</h4>
+<div class="d4" id="d7.1.2">
+<p class="noindent">The \charscale command may be used for a short amount of text, where there is no line break. The command will throw an error if the included text has \\ or \par or any other command that breaks the line. You may not place an image in \charscale.</p>
+<p>This command is built into some other <i>novel</i> commands, such as \ChapterTitle.</p>
+<p>When used without the option, \charscale echoes the included text. However, the text gains the magical ability to extend above or below the normal line of text, without pushing apart the baselines. This is useful if the text has some unusual character that is extraordinarily tall or deep.</p>
+<p>Using the option, you may uniformly scale the text by any amount, and displace it horizontally and vertically. The text can overlie other text, or any previously-placed image.</p>
+<p>With the unstarred command, the scaled width of the text will occupy horizontal space, even if the text is displaced far away. But with the starred command, the text does not occupy any horizontal space.</p>
+<p>The single optional argument may include up to three comma-separated values. The first value is a number, indicating the scale. If a second argument is used, it is the length of horizontal offset (positive is right). If a third number is used, it is the length of the vertical offset (positive is up). Remember that if all you want to do is scale the text, without positioning it, then you only need to provide the scale.</p>
+<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/>
+Bada \charscale[1.25]{Bang} Bam\par
+</code></p>
+<p>In the result (above right), notice how the starred command leaves no gap where the word Boom would have been. The unstarred command leaves a gap where the word Bang would have been located. In each case, the baseline grid is maintained.</p>
+<p>The most practical application of \charscale is styling the first character of chapter text. Drop capitals are out of fashion, but enlarged capitals (rising above the baseline) are in fashion. Example, also using the \FirstLine command (from package <i>magaz</i>, included with <i>novel</i>:</p>
+<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>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>
+</div>
+
+<h4 id="h7.1.3">7.1.3. <code>\begin{parascale}[<em>scale</em>] ... \end{parascale}</code></h4>
+<div class="d4" id="d7.1.3">
+<p class="noindent">The parascale environment is used on a paragraph basis. More than one paragraph may be included. The scale is applied to the font size and to the baselineskip within.</p>
+<p>Since the text within parascale generally will not occupy an integral number of normal baselineskips, the following text will be off-grid. This may not be a problem, if parascale is used in places where maintaining the grid does not matter (such as on a title page or copyright page).</p>
+<p>• If parascale is used within body text, then it will be necessary to restore the line grid for the following text. This cannot be done automatically; you will have to make a preliminary run, look at the results, and adjust accordingly.</p>
+<p>For example, suppose you use \begin{parascale}[0.92]...text...\end{parascale}. The preliminary run shows that the included text occupies 7 lines. The following baseline will then be 7x(1–0.92)=0.56 normal baselineskip too high. This can be fixed by adding \vspace{0.56\nbs}. For best appearance, the \vspace should be split above and below the parascale environment, but not nessarily in half.</p>
+<p>• If parascale crosses to the next page, then you will need to make vertical adjustment for each page independently. For example, if a 7-line parascale has 3 lines at the bottom of a page, followed by 4 lines on the following page, then you need to restore only a 4 line deficit on the following page.</p>
+<p>• Within parascale you may need to manually indent paragraphs, or remove indents if necessary.</p>
+</div>
+
+<h4 id="h7.1.4">7.1.4. Open Type Scale (fontspec)</h4>
+<div class="d4" id="d7.1.4">
+<p class="noindent">If you will be using a font in a way that it will <em>always</em> be at a size different from the normal font size, you may use the <i>Scale</i> feature when you first define the font. This is defined by the <i>fontspec</i> package, which is automatically loaded with <i>novel</i>.</p>
+<p>A scaled font can be used anywhere. It is not limited to a single line, and it will maintain the line grid at scales not exceeding 1. However, scaled text may disturb the line grid if its scale is more than 1.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h7.2">7.2. General Styling</h3>
+<div class="d3" id="d7.2">
+<p class="noindent">Many of these commands are directly from LaTeX, and are mentioned here because they are frequently used. Other commands are specific to <i>novel</i>.</p>
+
+<h4 id="h7.2.1">7.2.1. Italics and Emphasis</h4>
+<div class="d4" id="d7.2.1">
+<p class="noindent"><b>\textit{<em>text</em>}</b> puts the text in italics, provided that the font family has an Italic font. If it does not have an Italic font, then the letters will remain normal, <em>not</em> fake slanted.</p>
+<p>If the italicized text leans too far into the following space, try adding \/ (back and forward slashes) just before closing the braces.</p>
+<p><b>\emph{<em>text</em>}</b> changes regular text to italics, and italic text to regular. You may nest \emph commands. Many writers opine that this is the preferred way to specify Italics.</p>
+</div>
+
+<h4 id="h7.2.2">7.2.2. Bold, Semibold, etc.</h4>
+<div class="d4" id="d7.2.2">
+<p class="noindent"><b>\textbf{<em>text</em>}</b> puts the text in whatever font you specified as the Bold font, when you defined the currently-used font family.</p>
+<p>If the font family has no Bold font, then it will <em>not</em> be faked.</p>
+<p>The default main font used by <i>novel</i>, namely <i>Libertinus Serif</i>, has both Bold and Semibold weights. Given this choice, <i>novel</i> explicitly calls for the Semibold weight. If you intend to use a font such as Adobe Garamond Pro, which also has a Semibold weight, then you can request it instead of Bold when you define the font family.</p>
+<p>What if you want both Bold and Semibold, or maybe even a Light weight? Only one can be assigned to \textbf when you define the font. For the others, use \NewFontFace to assign the desired weight to its own font command, which you will use (but inside the braces) instead of \textbf.</p>
+<p>Actually, you should not be using Bold in fiction. It <em>might</em> be the case that this weight is useful for titles, but you ought to consider a fancy-looking font for that purpose, rather than mere Bold. Or, make the letters big and bold, but balance the effect by using gray.</p>
+</div>
+
+<h4 id="h7.2.3">7.2.3. Underlining</h4>
+<div class="d4" id="d7.2.3">
+<p class="noindent">Underlining is inappropriate for fiction. Don't do it. Besides, there are some issues regarding line grid and appearance, which are not a problem in academic works, but are noticeable in fiction.</p>
+</div>
+
+<h4 id="h7.2.4">7.2.4. Small Caps and Acronyms</h4>
+<div class="d4" id="d7.2.4">
+<p class="noindent"><code><b>\textsc{<em>text</em>}</b></code> converts lowercase letters to small caps, leaving uppercase unchanged. The font's <code>smcp</code> Open Type feature will be used. But if the font does not have <code>smcp</code>, it will <em>not</em> be faked.</p>
+<p><code><b>\smcp{<em>text</em>}</b></code> is an alias for <code>\textsc{<em>text</em>}</code>.</p>
+<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>• 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 <i>fontspec</i> package documentation: You may appoint a different font that will provide small caps.</p>
+<p>• If you insist on using old-fashioned TeX fonts, which do not have the <i>smcp</i> 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/>
+\let\scshape\oldscshape\relax</code></p>
+<p>The above code sends you in a time machine back to the Twentieth Century.</p>
+<p><b>\acronym{<em>text</em>}</b> is special to <i>novel</i>. If the <i>NovelDeco</i> 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"/>
+<code>
+The NATO alliance...\par<br/>
+The \acronym{NATO} alliance...\par<br/>
+The \allsmcp{NATO} alliance...\par
+</code></p>
+<p>Whether or not to use the \acronym command, is up to you. Since its letters are drawn from the <i>NovelDeco</i> font, rather than your main font, there may be some stylistic differences if your <i>parentfont</i> is not Libertinus Serif.</p>
+</div>
+
+<h4 id="h7.2.5">7.2.5. Local Tracking Adjustment</h4>
+<div class="d4" id="d7.2.5">
+<p class="noindent"><b>\squeeze{<em>text</em>}</b> narrows the text by one percent.</p>
+<p><b>\crush{<em>text</em>}</b> narrows the text by two percent.</p>
+<p>These commands are for emergency use only. They temporarily apply a horizontal scale to the letters, so that they are very slightly narrower than usual. Inter-word spacing is not necessarily changed (it can even grow larger), because spacing is calculated during paragraph layout. The enclosed text may span paragraphs.</p>
+<p>The commands do not compound. That is, placing one crush inside another will not narrow the text by four percent. But any adjustments made by <i>microtype</i> will still apply, and may compound with these commands.</p>
+<p>The only application for these commands is when a paragraph does not quite fit where you would like it to be. For example: Perhaps one short word, or part of a word, dangles to an extra line. Try \squeeze first, then \crush, for all or most of the paragraph. These do not always produce a useful effect, since the actual paragraph layout depends on other factors. But <em>if you are lucky,</em> then the paragraph re-flows to a better layout.</p>
+<p>• If the commands do not help, then be sure to remove them, or the typography will be worse.</p>
+</div>
+
+<h4 id="h7.2.6">7.2.6. Local Font Selection</h4>
+<div class="d4" id="d7.2.6">
+<p class="noindent"><b>{\<em>fontcode</em> <em>text</em>}</b> where <i>fontcode</i> is a previously-defined font command.</p>
+<p>You locally change the font in use, by calling its font command. For example, \subchfont is a built-in command, automatically used in certain macros. You can use it yourself:</p>
+<p class="code"><code>{\subchfont <em>text</em>} % Note that the braces go on the outside.</code></p>
+<p>Likewise, if you used \NewFontFamily or \NewFontFace to define your own font, giving it the command name \mynewfont, then you would use it like this:</p>
+<p class="code"><code>{\mynewfont <em>text</em>} % Again, the braces go on the outside.</code></p>
+</div>
+
+<h4 id="h7.2.7">7.2.7. Local Feature Changes</h4>
+<div class="d4" id="d7.2.7">
+<p class="noindent"><b>{\addfontfeature{<em>feature</em>} <em>text</em>}</b> for changing Open Type features.</p>
+<p>If a font is already defined, you can locally add one or more features. For example, suppose that you defined \mynewfont without using its Open Type feature <i>ss03</i> (we will assume that the font actually has this feature). In a particular place, you wish to activate <i>ss03</i>. The code looks like this:</p>
+<p class="code"><code>{\mynewfont\addfontfeature{RawFeature=+ss03} <em>text</em>}</code> % Note + sign. Braces outside.</p>
+<p>That limits the scope of the feature to the included group, in TeX terminology.</p>
+<p>You can modify features used by any defined font, whether you defined it yourself or it is one of the <i>novel</i> built-in font commands. You can add more than one feature. If the requested feature does not exist in the font, then your request will be ignored.</p>
+<p>What about removing a feature that is already present in the font definition? Suppose you defined \mynewfont so that <i>Numbers=OldStyle</i> is used. On a local basis, can you change the style of numbers? Usually, yes. You could use <i>Numbers=Lining</i> to over-ride the feature. Sometimes it depends on how you chose the features, as a matter of syntax. See the <i>fontspec</i> documentation.</p>
+</div>
+
+<h4 id="h7.2.8">7.2.8. Color Text (actually, grayscale)</h4>
+<div class="d4" id="d7.2.8">
+<p class="noindent"><b>graytext</b> class option must be used, or any color command will be ignored, and its included text will be rendered in black (even if the requested color is white). Images are unaffected.</p>
+<p><b>\color{<em>name</em>}</b> or <b>\color[gray]{<em>scale</em>}</b> 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/>
+\endgroup
+</code></p>
+<p style="margin-top:10px"><b>\textcolor{<em>text</em>}</b> or <b>\textcolor[gray]{<em>scale</em>}{<em>text</em>}</b> affects only the included text.</p>
+<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 \color or \textcolor, there are two ways to specify the color: by name, or by scale, using package <i>xcolor</i> syntax.</p>
+<p>• The following color names are accepted, and will be converted to some shade of gray (from dark to light): black, blue, violet, darkgray, purple, red, teal, olive, magenta, gray, brown, green, orange, cyan, lightgray, lime, pink, yellow, white.</p>
+<p>The above names are often not helpful, so <i>novel</i> also allows you to use these: black, gray1, gray2, gray3, gray4, gray5, gray6, gray7, gray8, gray9, white. The scale is not uniform (gray5 is not 50 percent gray), but the values are usefully spaced.</p>
+<p>Other names "known to dvips," such as <i>Apricot</i>, do not work. An error will result.</p>
+<p>• To specify color by scale, follow the color command with <i>[gray]{<em>scale</em>}</i>, where the scale is a number between 0 (black) and 1 (white). Example: \color[gray]{0.63}.</p>
+<p>• If you use <i>xcolor</i> syntax to request an rgb color, it will be converted to 1-channel grayscale.</p>
+<p>• Absolutely no transparency!</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h7.3">7.3. Positioning and Alignment</h3>
+<div class="d3" id="d7.3">
+<p class="noindent">By now, you already know: In <i>novel</i> there are new ways to position or align text, and some of the standard TeX methods are discouraged or disabled.</p>
+
+<h4 id="h7.3.1">7.3.1. What to Avoid</h4>
+<div class="d4" id="d7.3.1">
+<p class="noindent">• The \raisebox command does not play well with novel. It can be used, but there is the great risk of disturbing the line grid. Use \charscale instead.</p>
+<p>• If you must use the \vspace command (or its relative, \vskip) be sure to measure the space in units of \nbs (normal baseline skip).</p>
+<p>• Avoid the minipage and parbox environments. These are likely to disrupt the line grid. When that happens, restoring the grid is your own responsibility. You may find the adjustwidth environment to be a useful alternative.</p>
+<p>• In most cases, do not use the center environment. You may use {\centering ... \par} instead, for a single paragraph. The center environment may cause the text to go off-grid. That's not a problem on some stand-alone pages where you don't care about the grid, but it is ugly in the middle of running text.</p>
+<p>• Avoid positioning via the textblock or textblock* environments (package <i>textpos</i>). Actually, novel uses that code internally. But if not handled with more care than usual, positioned text can disrupt the baseline and position of surrounding text. You may use \charscale to position small amounts of text safely, but not on a paragraph basis. Images have built-in positioning arguments, which may also be useful for positioned text.</p>
+<p>• Do not use floats. If you try, then <i>novel</i> may intercept them with a nasty message.</p>
+<p>• Do not use tables. Nasty message will result. But <i>novel</i> has its own provision for a Table of Contents, and the code may be used for other purposes as well.</p>
+<p>• If you use images, then use only the image commands provided by novel: \InlineImage and \BlockImage.<p>
+<p>• There is no built-in provision for a two-column environment. However, you can place text alongside an image.</p>
+</div>
+
+<h4 id="h7.3.2">7.3.2. Some Useful Commands</h4>
+<div class="d4" id="d7.3.2">
+<p class="noindent">This is not a complete list. It merely addresses a few situations that you are likely to encounter, without the need for elaborate code, and without loading additional packages.</p>
+<p style="margin-top:10pt"><b>\begin{adjustwidth}{<em>left</em>}{<em>right</em>}</b> ... <b>\end{adjustwidth}</b></p>
+<p>This environment, from the included <i>changepage</i> package, is the most useful way to create block indents. The included text may have multiple paragraphs and span pages. The left and right arguments are lengths, being the amount to <em>increase</em> the respective margins from their normal values.</p>
+<p style="margin-top:10pt"><b>\phantom{<em>text</em>}</b></p>
+<p>Does not print the text, but leaves a horizontal gap as if the text were there.</p>
+<p style="margin-top:10pt"><b>\mbox{<em>text</em>}</b></p>
+<p>Prevents a specific word from being hyphenated, or to ensure that two consecitive words always appear on the same line. The box will not be broken across lines. However, it may overhang the margin, which is undesirable.</p>
+<p style="margin-top:10pt"><b>\makebox[<em>width</em>][<em>alignment</em>]{<em>text</em>}</b></p>
+<p>Puts the text in a box of fixed width (usually much larger than the text's own width) and aligns it left, center, or right in the box. If using this across the full textwidth, be sure to precede it with \noindent to prevent offset.</p>
+<p style="margin-top:10pt"><b>\hspace{<em>length</em>}</b></p>
+<p>Creates a horizontal space.</p>
+<p style="margin-top:10pt"><b>\strut</b></p>
+<p>Places an invisible box with no width, which has the height and depth of the font. Sometimes used as a placeholder.</p>
+<p style="margin-top:10pt"><b>\indent, \noindent, \forceindent, \backindent</b></p>
+<p>Commands \indent and \noindent have their ordinary TeX meaning. Sometimes, the action of other macros will remove an indent that should be there, or add an indent that should not be there. If writing \indent and \noindent do not fix the problems, use \forceindent and \backindent as more forceful solutions.</p>
+<p style="margin-top:10pt"><b>\hfill</b></p>
+<p>Pushes the following text to the right end of the line. Actual effect depends on what precedes and follows. Sometimes a \strut is needed at the beginning of a line.</p>
+<p style="margin-top:10pt"><b>\vfill. \vfill*</b></p>
+<p>Pushes the following text to the bottom of the page. Actual effect depends on paragraph organization. Use the asterisk if there is nothing printed above this command, on the same page.</p>
+<p style="margin-top:10pt"><b>\kern</b></p>
+<p>Tweaks the spacing between consecutive letters. A tricky command, as it is always used without braces, and makes the surrounding text illegible in your source code. If you use it, the units of length should always be em, rather than pt. Example:</p>
+<p class="code"><code>It wa\kern-.02ems a da\kern.03emrk and stormy ni\kern-.004emght.</code></p>
+<p>The <code>\kern</code> command is not useful for globally changing kern values.</p>
+<p style="margin-top:10pt"><b>\bigemdash[<em>yoffset,thickness</em>]</b></p>
+<p>Simulates a "big emdash" of variable length. Horizontal width is from command to end of line marked by \par, or limited by a fixed width such as created by \makebox. If placed in other situations, the line may be missing or too long.</p>
+<p>The line's normal position is at the typical height of an emdash, which is slightly above half the height of lowercase x. Its normal width is typical of an emdash width. Thus, the line is like an extended emdash.</p>
+<p>You can tweak the line using its optional argument. The first value tweaks the vertical position by a scale factor, where 1 equals its normal position (so that 0.9 places it a little lower). The second argument, if used, is separated from the first by a comma. It tweaks the line thickness by a scale factor (so that 0.9 makes it a little thinner).</p>
+<p>Since \bigemdash allows an optional argument, but no mandatory argument, you may not immediately follow it with text. If it is boxed, then first close the box; otherwise, end the paragraph.</p>
+<p style="margin-top:10pt"><b>\straightquote \straightdblquote</b></p>
+<p>These insert the single quote (apostrophe), and double quote, as ASCII straight characters, without TeX (or your software) automatically substituting the curly characters.</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page07 -->
+<!-- ************************************************************ -->
+<div id="page08" class="page">
+
+
+<h2 id="h8">8. Images</h2>
+<div class="d2" id="d8">
+<p class="noindent">If you intend to place a lot of images in your document, or if you need to have text wrap around floating images, then the <i>novel</i> document class is not well-suited to your purpose. This is because the methods of formatting, and the emphasis on maintaining a constant baseline skip, sometimes interfere with the behavior you expect from other document classes.</p>
+<p>Yet you can place the occasional image. Most fiction does use imagery on the title page, and sometimes at chapter starts. Some stories include a map, or an image of ancient writing. In a detective novel, we might get a glimpse at handwritten evidence. The <i>novel</i> class has its own commands for easily dealing with these situations.</p>
+<p>Like it or not, you are restricted to <em>png</em> and <em>jpg</em> raster images. No vector artwork. No included <em>eps</em> or <em>pdf</em>. Forget about <i>pgf</i> and <i>TikZ</i>. Although you can "cheat" the <i>novel</i> commands, and circumvent the restrictions, don't do it. The restrictions are intentional. The reasons are explained below.</p>
+
+<h3 id="h8.1">8.1. Use Raster Images</h3>
+<div class="d3" id="d8.1">
+<p class="noindent">Place raster images, not vector images, in your document.</p>
+<p>You may think that the above sentence is a mistake. Haven't you been told that vector artwork is always preferable to rasterized artwork, because vector artwork is scalable? The part about being scalable is true. But if you do not need scalability, vector artwork is worse.</p>
+<p>How so? A PDF file can incorporate vector artwork, and if properly done it will meet commercial printing standards. <em>Sadly, it is often not properly done.</em> When vector artwork has technical errors, as it often does, then the appearance will depend on which software is used to view the image. The fact that it is within a PDF does not always help.</p>
+<p>When you design a vector image, or perhaps acquire one, you approve its appearance based on what you see on your computer. The odds are good that someone else, on a different computer, will be using the same software and thus see the same result. However, that is not true of the software built into commercial printing machines. That software may interpret ambiguous vector instructions in a different way than you expected.</p>
+<p>A good example is on pages 232-234 of the <i>Adobe PDF 1.7 Reference</i>. That's an enormous file, full of technical information. You don't need to read it. But Adobe provides an example of a vector drawing in the form of a five-pointed star, made with one continuous line that crosses itself. There are two possible rules for deciding whether the central pentagon should be filled or not. They produce different results. Adobe chooses a particular rule, and so should all compliant software. But is all software compliant? Without reading the Adobe spec, there is no particular reason to prefer one rule over the other. And, that's a simple example. Many vector drawings are very convoluted, in ways that make the artist's intent difficult to interpret.</p>
+<p>You normally do not need to scale images. Your finished work will be viewed at fixed size on the printed page, not at variable size in a PDF reader. So, scalability is not an advantage. Your image is placed on paper at its exact size and resolution. You are in complete control. If it is purely black/white line art, its detail will be about the same whether it was placed as vector or raster. If it is grayscale, it is subject to halftoning, which reduces the resolution in any case.</p>
+<p>Do not attempt to place an image by including a PDF within your TeX file. The reason is that the included PDF may carry its own File Data, which will differ from the File Data of the main PDF. There's nothing you can do about that, and commercial printers don't like it. So, don't do it. Indeed, <i>novel</i> may ban it!</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h8.2">8.2. Use Flattened png or jpg Image Format</h3>
+<div class="d3" id="d8.2">
+<p class="noindent">The <i>novel</i> image-handling commands require the <i>png</i> or <i>jpg</i> formats, exclusively. If you already have a raster image in another format, such as <i>tif</i>, you must convert it. If you have a vector image, such as <i>eps</i> or <i>svg</i> format, you must rasterize it. This must all be done in an external graphics program, such as <i>GIMP</i> or <i>Inkscape</i>. It cannot be done from within TeX.</p>
+<p>Both <i>jpg</i> and <i>png</i> images can store their resolution internally. When you export images from a graphics program, be sure that the resolution is stored. This may or may not be an option that you need to check.</p>
+<p>With <i>png</i>, the image must be flattened (no transparency). Be sure to flatten the image before you export it to <i>png</i>. With <i>jpg</i>, the exported image is always flattened.</p>
+<p>When using grayscale, be sure to convert the image to true grayscale, which has only one color channel. In GIMP, this is achieved with the <i>Image>Mode</i> menu. Note that an RGB or CMYK image "that only uses grays" is <em>not</em> the same thing, since these have three or four color channels!</p>
+<p>When using pure black/white (<i>png</i> only), you can get there with GIMP's <i>Image>Mode>Indexed</i> menu.</p>
+<p>Note that within the finished PDF file, images are stored in an internal format which differs from your input. If your image is in the wrong format, or contains transparency, it will not be detected by TeX.</p>
+
+<h4 id="h8.2.1">8.2.1. Saving the Resolution</h4>
+<div class="d4" id="d8.2.1">
+<p class="noindent">Image resolution is measured in dots per inch (dpi). In a graphics program, it may be called pixels per inch (ppi). And, if the software was written in Europe or Asia, it may be measured in pixels per centimetre!</p>
+<p>When you prepare an image in a graphics program, you must first ensure that it is at the correct resolution. Most U.S. print services require <i>300dpi</i> for grayscale images (or color covers), <i>600dpi</i> for black/white line art. Then, it is a simple matter of multiplying the image dimensions (in inches) by the resolution, to get the image dimensions in pixels.</p>
+<p>Example: A grayscale image that will print at 1.25" wide by 1.5" high, must be 375 pixels wide by 450 pixels high, at 300dpi. If the original image is at different dimensions, it must be cropped and scaled to the correct size. However, it is not enough to finish the image at 375x450 pixels. You must specifically set the resolution to 300dpi. If you fail to set the resolution correctly, then the image will not appear at its correct size in your PDF.</p>
+<p>In GIMP, you can use the <i>Image>Scale Image</i> dialog box to ensure that the image is at the proper size and resolution. When you change any of the settings, others may change in response. Be sure that all settings are satisfactory.</p>
+<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>
+</div>
+
+<h4 id="h8.2.2">8.2.2. Removing Private Metadata</h4>
+<div class="d4" id="d8.2.2">
+<p class="noindent">Your image may contain "private metadata" that records how the image was created, especially if it was converted from a digital photograph. It may also contain color profile data that is inappropriate for a grayscale or black/white image. Commercial printing standards prefer that such private metadata be removed from images; the PDF File Data should speak for everything, not the individual images.</p>
+<p>The simplest way to remove private metadata is via a command-line program: Use either <i>ImageMagick</i>, or <i>GraphicsMagick</i>. These programs work on Windows, Linux, and (so I am told) OS/X. Specific code is shown in the workflow examples, below. If you ever re-work an image, you must once again remove its private data.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h8.3">8.3. Line Art vs. Grayscale</h3>
+<div class="d3" id="d8.3">
+<p class="noindent">Two kinds of images may appear in a black-and-white book: <i>line art</i>, and <i>grayscale</i>.</p>
+<p>Line art contains only black and white. Moreover, there cannot be any places where the black or white areas are very tiny. Most print services request that your line art be rasterized at 600dpi (dots per inch), but that does not mean you can emulate gray with an alternating pattern of black and white, repeated 300 times per inch. All it means is that the sharp transition from black areas to white areas can be resolved to about 1/600" during printing (only "about" since the ink spreads a little).</p>
+<p>So, if you think you can use Floyd-Steinberg dithering to convert a grayscale image to "line art," that won't work: The printer will note that it cannot resolve such fine detail, and treat it as a grayscale. The result will be worse than if you had left it as grayscale instead of dithering to black and white.</p>
+<p>Think in terms of how an <i>offset press</i> works. Look it up on the Internet. You can have a sharp boundary between black and white, but you cannot closely mingle tiny black and white areas. Actually, at low production volume, your book may be printed with an inkjet technology that can resolve very fine details. But you cannot count on that; and, if your book does sell well, you may be shocked if the print technology changes.</p>
+<p>A PDF file can place ordinary (vector) text atop an image. However, if the underlying image is halftoned, there is the risk that the overlying text will also be halftoned, even if it sits atop white areas of the image. Ask your print service for advice. It may be better to make the text part of the image, and anticipate halftoning by using appropriately styled text.</p>
+
+<h4 id="h8.3.1">8.3.1. Workflow: Line Art in GIMP</h4>
+<div class="d4" id="d8.3.1">
+<p class="noindent">To create a suitable <b>line art</b> image in GIMP, with post-processing in ImageMagick or GraphicsMagick, follow these instructions:</p>
+<p>(1) Open the image file in GIMP. If it is a vector format (such as svg or pdf), ensure that it is resolved to 600 pixels/in with anti-aliasing, and that its size is the same as your intended dimensions (measured in inches or mm). You can also use a larger size, if you intend to crop some of the periphery; or you can use a smaller size, if you intend to make it larger by adding white space.</p>
+<p>(2) If you need to crop to a smaller size, or add to a larger size, do it now. Image > Canvas Size, with Resize Layers All.</p>
+<p>(3) If you need to edit the image, by adding or removing anything, do it now.</p>
+<p>(4) Image>Flatten Image.</p>
+<p>(5) Image>Mode>Grayscale.</p>
+<p>(6) View>Zoom to an appropriate amount that shows the image at approximately its print size. That depends on your monitor's resolution. On my own computer, 25% is about right. Does not need to be exact.</p>
+<p>(7) Colors>Threshold. If necessary, adjust the slider until the image looks best. It might be that the default 50% works for you. If you move it to the left, then black areas will become a little narrower. If to the right, black areas will become a little thicker.</p>
+<p>(8) Image>Mode>Indexed>(black and white 1-bit palette). Remove unused colors from colormap. No dithering.</p>
+<p>(9) File>Export. Use png (Portable Network Graphics) extension. When the dialog box appears, ensure that "save resolution" is checked. Use the highest level of compression offered. The exported image may look poor in some image viewers, because those viewers do not read the full resolution. Not a problem. The image will look good when seen in better viewers.</p>
+<p>(10) Command-Line Terminal, using GraphicsMagick or ImageMagick:</p>
+<p class="code">GraphicsMagick, Windows or Linux: <code>gm mogrify -strip nameofimage.png</code></p>
+<p class="code">ImageMagick, Windows: <code>magick mogrify -strip nameofimage.png</code></p>
+<p class="code">ImageMagick, Linux: <code>mogrify -strip nameofimage.png</code></p>
+<p>(11) Sanity check:</p>
+<p class="code">GraphicsMagick, Windows or Linux: <code>gm identify -verbose nameofimage.png</code></p>
+<p class="code">ImageMagick, Windows: <code>magick identify -verbose nameofimage.png</code></p>
+<p class="code">ImageMagick, Linux: <code>identify -verbose nameofimage.png</code></p>
+<p>After a few moments, the Terminal will show some information. It should say that the depth is 1-bits per pixel, that the only color is gray (1 bits), that the resolution is 236.22 pixels per centimeter (which is 600dpi). The page geometry, divided by 600, will give you the image size in inches (thus, a page geometry of 900+1200+0+0 represents an image 1.5" wide x 2" high).</p>
+</div>
+
+<h4 id="h8.3.2">8.3.2. Workflow: Grayscale in GIMP</h4>
+<div class="d4" id="d8.3.2">
+<p class="noindent">To produce a suitable <b>grayscale</b> image in GIMP, with post-processing in ImageMagick or GraphicsMagick, follow these instructions:</p>
+<p>(1) Open the image file in GIMP. If it is a vector format (such as svg or pdf), ensure that it is resolved to 300 pixels/in with anti-aliasing, and that its size is the same as your intended dimensions (measured in inches or mm). You can also use a larger size, if you intend to crop some of the periphery; or you can use a smaller size, if you intend to make it larger by adding white space.</p>
+<p>(2) If you need to crop to a smaller size, or add to a larger size, do it now. Image > Canvas Size, with Resize Layers All.</p>
+<p>(3) If you need to edit the image, by adding or removing anything, do it now.</p>
+<p>(4) Image>Flatten Image.</p>
+<p>(5) Image>Mode>Grayscale.</p>
+<p>(6) View>Zoom to an appropriate amount that shows the image at approximately its print size. That depends on your monitor's resolution. On my own computer, 25% is about right. Does not need to be exact.</p>
+<p>(7) Very dark grays are hard to produce accurately, and so are very light grays. If your image relies on areas that are nearly black and nearly white, then consider adjusting lightness and contrast so that they are not so close to black and white. GIMP's Colors>Levels might be more useful than Colors>Brightness/Contrast.</p>
+<p>(8) Ensure that white areas are truly white, not light gray. Use GIMP's <i>Select By Color</i> Tool, with a very low threshold, to choose areas that should be exactly white, then clear them.</p>
+<p>(9) File>Export. Use png (Portable Network Graphics) extension. When the dialog box appears, ensure that "save resolution" is checked. Use the highest level of compression offered. The exported image may look poor in some image viewers, because those viewers do not read the full resolution. Not a problem. The image will look good when seen in better viewers.</p>
+<p>(10) Command-Line Terminal, using GraphicsMagick or ImageMagick:</p>
+<p class="code">GraphicsMagick, Windows or Linux: <code>gm mogrify -strip nameofimage.png</code></p>
+<p class="code">ImageMagick, Windows: <code>magick mogrify -strip nameofimage.png</code></p>
+<p class="code">ImageMagick, Linux: <code>mogrify -strip nameofimage.png</code></p>
+<p>(11) Sanity check:</p>
+<p class="code">GraphicsMagick, Windows or Linux: <code>gm identify -verbose nameofimage.png</code></p>
+<p class="code">ImageMagick, Windows: <code>magick identify -verbose nameofimage.png</code></p>
+<p class="code">ImageMagick, Linux: <code>identify -verbose nameofimage.png</code></p>
+<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>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: <i>png: IHDR.color_type: 0 (grayscale)</i></p>
+<p class="code">For jpg images: <i>JPEG-Colorspace: 1</i> and <i>JPEG-Colorspace-Name: GRAYSCALE</i></p>
+<p>The above codes are the only ones that matter. Even if other information claims that the image is grayscale, or lists the colors and they are all shades of gray, <em>that is not good enough</em>. When automated software reviews your PDF for compliance, it will look at the png <i>IHDR.color_type</i>, which must be 0, or the <i>JPEG-Colorspace</i>, which must be 1. Anything else fails. If the information is different, it means that you forget to change the mode from RGB to grayscale before you exported the image.</p>
+<p>You may ask: If the image was not really grayscale, can it be converted to grayscale using a simple command line, with ImageMagick or GraphicsMagick? The answer is yes, but don't do it that way. The reason is that there are many ways to map colors (even "gray colors") to true grayscale, and an automated conversion may produce unexpectedly light or dark results. It is better to do the conversion in a graphics program, where you can see what you are doing.</p>
+</div>
+
+<h4 id="h8.3.3">8.3.3. Scaling Images after \Rework.</h4>
+<div class="d4" id="d8.3.3">
+<p class="noindent">When you use one or both of the \Rework commands (Appendix F), the font size and/or the baselineskip will change. However, it does not scale images. In many cases, there is no problem. But in some cases, an un-scaled image will disrupt the previous flow of text or pagination. See Appendix F.5 for how to re-work images.</p>
+</div>
+<!-- end class="d3" -->
+
+<h3 id="h8.4">8.4. Placing Images In Your Document</h3>
+<div class="d3" id="d8.4">
+<p class="noindent">An image may be placed as an inline element, using the \InlineImage or \InlineImage* command. This allows the image to mingle with text, and even have text as an overlay.</p>
+<p>\BlockImage places the image so that <em>subsequent</em> text will clear the bottom of the image, and be on the baseline grid. You may also <em>accompany</em> the image with text in its own block space, if you wish.</p>
+<p>If your book has a lot of images, then you should consider using a page layout program (such as Scribus) instead of TeX. That's because the best strategies for an image-intensive picture book are very different from the strategies adoped by <i>novel</i>.</p>
+<p>Beware of overlap. If images overlap each other, or overlap with text, no error will result. If text lies atop an image, the result may be desirable. All other situations are undesirable. Since TeX cannot detect such errors, you need to carefully review the result.</p>
+<p>Do not use the ordinary TeX commands, or environments, for floats or figures.</p>
+
+<h4 id="h8.4.1">8.4.1. \charscale[<em>scale,hoffset,voffset</em>]{<em>text</em>}, \charscale*[<em>scale,hoffset,voffset</em>]{<em>text</em>}</h4>
+<div class="d4" id="d8.4.1">
+<p class="noindent">The \charscale command pertains to text, not images. It is mentioned here because it can place text almost anywhere on a page, even overlapping other text or previously-placed images. Thus, it provides an image-like effect.</p>
+<p>The command is documented earlier on this page.</p>
+</div>
+
+<h4 id="h8.4.2">8.4.2 \InlineImage[<em>hoffset,voffset</em>]{<em>imageFile.png or .jpg</em>} and starred version</h4>
+<div class="d4" id="d8.4.2">
+<p class="noindent">This command places the image as an inline element, at 100% scale. The use of <i>png</i> or <i>jpg</i> images, with file extension, is required.<p>
+<p>You may offset the image horizontally or vertically. Positive direction is to the right and up. If you use one offset, then you must use both (if necessary, <i>0em</i>). Any units of length may be used, but the preferred units are <i>em</i> or <i>\textwidth</i> for horizontal, and <i>em</i> or <i>\nbs</i> for vertical, because these are most compatible with the \Rework commands.</p>
+<p>By default, the <em>top</em> of the image is at the text baseline. If you prefer that the <em>bottom</em> of the image be at the text baseline, use voffset <i>b</i>. Example:</p>
+<p class="code"><code>\InlineImage[0em,b]{imageFile.png}</code></p>
+<p>Thanks to the included <i>calc</i> package, offsets may use \widthof{<em>text</em>} and/or \heightof{<em>text</em>} as lengths. The most useful of these is when you wish to align the top of an image at the X-height of surrounding text:</p>
+<p class="code"><code>\InlineImage[0em,\heightof{X}]{imageFile.png}</code></p>
+<p>You may also use \heightof{\Aring} for the tallest accented letter normally found in Latin-1.</p>
+<p>Lengths <i>\imagewidth</i> and <i>\imageheight</i> may also be used for offsets. These lengths remain set, and can be used for other purposes (such as displacing text) until another image is placed.</p>
+<p>Offsets may be written as combinations of lengths. If you use the baseline <i>b</i> as above, it must be the first character of voffset. If you use <i>\widthof</i> or <i>\heightof</i>, then its backslash must be the first character <em>unless</em> it is preceded by another length. Thus, an offset of <i>-\heightof{X}</i> is prohibited, but you can use <i>0pt-\heightof{X}</i>.
+<p>Here are some examples of allowable code:</p>
+<p class="code"><code>
+\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 <i>\null</i> lines after the image, or use the \BlockImage command instead.</p>
+<p>With the un-starred \InlineImage command, the image occupies its natural horizontal width. That is, text following the image will (if it fits) continue from the right edge of the image. But with the starred \InlineImage* command, the image occupies zero width. In this case, text following the image will continue from the left of the image, and overlie the image.</p>
+<p>Having text overlie the image is allowable, and can create some interesting special effects. But when your print service sees what you have done, they may think that it is a mistake. Be sure that you discuss this with them.</p>
+<p>If you do allow text to overlie an image, be sure that the image is very light. Repeat: <em>very light</em>. Depending on the printing technology, an image may print darker than you see on your computer screen, and that would make text hard to read. At low print volume, your print service will probably use a technology that is like an industrial-strength home inkjet printer, which can make very sharp text over images. However, if your book goes to volume production, then the technology will be different. Volume printing will use halftoned images, and the text overlay may also become halftoned, which will reduce its sharpness considerably.</p>
+<p>Note that an image may be placed in a way that prints some of the image in the margin. That's allowable if your margin is wider than the minimum required for printing clearance. But even if it is not allowable, there will be no complaint or warning from TeX.</p>
+<p>Do not place an image so that it approaches or goes beyond the page edge. That requires a "bleed box" which is not part of <i>novel</i> capabilities. If your book needs that kind of image handling, use a page layout program instead.</p>
+<p>Do not place images so that they overlap. Although that is allowed in the PDF, it is likely to be flagged as an error by your print service.</p>
+</div>
+
+<h4 id="h8.4.3">8.4.3. Text Over \InlineImage</h4>
+<div class="d4" id="d8.4.3">
+<p class="noindent">As noted above, an \InlineImage (or its starred version) can be used as the background to any subsequent text. Just as with any other text, whatever sits atop an image must be pure black. If you need text in gray, then you must integrate the rasterized text with the image in an external graphics program, instead of typing the text in your document.</p>
+<p>When text overlies an image, it retains its identity as vector paths, as far as the PDF is concerned. In some printing processes, particularly those for very low volume production, the result will be as sharp and dark as ordinary text. However, if your book sells well (or is being prepared to sell well), the image will be converted to halftone, and the text that lies above it may also be converted to halftone. This will reduce the sharpness of the text. It is not necessarily a problem, unless your text is very small or has fine details.</p>
+<p>If the text-over-image is part of a title, then the text is naturally large and dark, and will easily withstand halftoning.</p>
+<p>Be aware that not all print services will accept text over images. It's not that they <em>cannot</em> do it; after all, your home and office printers can easily do it. The reason they object is because the pages of your book will be handled in small volume by persons who are unfamiliar with the book. Text over an image may be flagged as a printing error or a bug in the PDF. In the advertising world, text over image is routine. But in the world of fictional novels, it is unusual. Don't imagine that they will decide what you meant to do, by reading your book. Also, very sharp image/text, at low printing volume, will not appear as sharp when the technology changes for higher volume production. They know that, but are not sure if <em>you</em> know that.</p>
+<p>An inline image occupies zero vertical space. If you place its top near the bottom of the textblock, then the image will happily flow into the lower margin and perhaps off the bottom of the page, without an error (but the print service will reject it). The reason that TeX does not provide an error message is quite simple: Technically, it is not an error! It is just not what you meant to do. The software cannot read your mind.</p>
+<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/>
+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>
+</div>
+
+<h4 id="h8.4.4">8.4.4. \BlockImage[<em>alignment,hoffset,voffset</em>]{<em>imageFile.png or .jpg</em>}[<em>text</em>]</h4>
+<div class="d4" id="d8.4.4">
+<p class="noindent">Note that \BlockImage has an optional argument that <i>precedes</i> the mandatory image file name. It has another optional argument that <i>follows</i> the file name. If this second option is used, there must be no space between <code>}[</code>.</p>
+<p>The first optional argument has up to three comma-separated values. The first is alignment: <i>l</i>, <i>c</i>, or <i>r</i> for left, center, or right. The second and third values are hoffset and voffset. Unlike the \InlineImage command, do not use <i>b</i> to indicate vertical position relative to the image bottom; it is always at the top with this command. The default alignment is centered, without offsets.</p>
+<p>An automatic calculation clears the height of the image. Subsequent text will be on grid. This is the right thing to do when the image and included text fit on a single page. But if they cannot both fit on a single page, an unusual layout will result.</p>
+</div>
+
+<h4 id="h8.4.5">8.4.5. \BlockImage with Accompanying Text</h4>
+<div class="d4" id="d8.4.5">
+<p class="noindent">The second optional argument of \BlockImage, following the image file name, may contain text that will accompany the image in the same block of space. The text is left-aligned like ordinary text, no matter which alignment you use for the image. The text may be in more than one paragraph, and may use {\centering ...\par} or \begin{adjustwidth} ... \end{adjustwidth} for positioning relative to the image. The text may overlie the image, using \charscale. You may need to use \forceindent or \backindent to control how the text appears. Note that you cannot automatically "flow" text around an image in <i>novel</i> class.</p>
+<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/>
+\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>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>
+<p>Note that I used the start of the following text as a reference point for placing CENSORED over the gnome. That is not the only way it could have been done, but it was easy to discern the necessary offset.</p>
+<p>• In general, avoid using accompanying text with an image, with the possible exception of titles and other special layouts. There is little need for it in the flowing text of a novel. If you find that you need to use it frequently, then perhaps your book would benefit from a page layout program such as <i>Scribus</i>, instead of TeX.</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page08 -->
+<!-- ************************************************************ -->
+<div id="page09" class="page">
+
+
+<h2 id="h9">9. Front Matter</h2>
+<div class="d2" id="d9">
+<p class="noindent">The <b>\frontmatter</b> command must be written immediately after \begin{document}. This sets page numbering to lowercase roman, and performs some other actions.</p>
+<p>A book's front matter is <em>about the book</em>. It is not part of the story. The only mandatory front matter is the Title Page and its verso, the Copyright Page. On a practical basis, six pages of front matter are the minimum, and this minimum is often used, even by major publshers. See Appendix B for how to construct basic six-page front matter.</p>
+
+<h3 id="h9.1">9.1. Useful Commands in Front Matter</h3>
+<div class="d3" id="d9.1">
+<p class="noindent">Among the numerous commands available to you, here are some that are particularly useful in front matter, for styling and positioning:</p>
+<p class="code"><code>\thispagestyle{empty}</code> prevents header or footer from printing on that page. In most cases, this command should be the first to appear on each page of front matter. The only exceptions are lengthy Foreword, Preface, and Introduction. Those should be treated with the same styling as chapters, and may contain headers (except at their start) or footers.</p>
+<p class="code"><code>\strut</code> and <code>\stake</code> are invisible, zero-width placeholders. \strut occupies the vertical text height, but \stake does not. Once in a while, these are used to establish a reference point, where positioning is relative to prior code.</p>
+<p class="code"><code>\charscale</code> changes text size, and can also tweak position.</p>
+<p class="code"><code>\vspace*</code> (note the asterisk) placed at the top of the page, sets a blank area above the first line of text. Useful for moving things down on the page. Can also be used for vertical spacing between elements.</p>
+<p class="code"><code>\null\vfill</code> placed at the top of the page, pushes the remaining text down, so that its last line is at the bottom of the text block. Sometimes a copyright page is styled this way.</p>
+<p class="code"><code>\vfill</code> (without the \null) may be used between paragraphs of text. The subsequent text will be pushed to the bottom of the text block. This is useful for forcing a publisher's imprint downward, on the title page.</p>
+<p class="code"><code>center</code> environment. Although the center environment may sometimes cause vertical misalignment when used within flowing text (chapters), it is OK for front matter, where that is not a problem.</p>
+<p class="code"><code>adjustwidth</code> environment. Very useful for creating text areas do not occupy the full page text width. Often used for a Dedication or Epigraph. Also useful in conjunction with the center environment, for certain copyright page designs. In other cases, a non-centered copyright page may have its text limited to less than full width, so that it is visually different from an ordinary page.</p>
+<p class="code"><code>legalese</code> environment. Sets text ragged-right, and disables hyphenation. Useful for some copyright page designs.</p>
+<p class="code"><code>\smcp</code> and <code>\allsmcp</code> for small caps. \smcp is the same as \textsc, which converts lowercase letters to small caps, leaving uppercase letters unchanged. \allsmcp changes both uppercase and lowercase letters to small caps. These commands are useful for such expressions as FIRST EDITION, which are customarily set in small caps.</p>
+<p class="code"><code>\lnum</code> sets Lining numbers, which all have the height of a capital letter. Without using \lnum, numbers will probably be set Old Style, since that is the text default.</p>
+<p class="code"><code>\indent, \forceindent, \noindent, \backindent</code> control indentation. \forceindent and \backindent usually work when the others don't, and can also be used cumulatively. If your copyright page has CIP data, you will need to pay attention to how the data is indented, since that is part of the specification.</p>
+<p class="code"><code>\decoglyph</code> selects a decorative element from the deco font (normally NovelDeco.otf). The decoration will usually have to be magnified, using \charscale. This is a handy way to add something to a title page, if you do not otherwise have artwork there.</p>
+<p class="code"><code>\clearpage</code> or <code>\cleartorecto</code> terminates a page. With \clearpage, the following material will be placed recto or verso, in normal flow. With \cleartorecto, if the following page would normally be verso, then a blank verso is inserted, so that the following material is forced to recto. The blank page has no header/footer.</p>
+<p class="code"><code>\itshape</code> or <code>\textit</code> for italics. The \itshape command is used when the text includes multiple paragraphs. Sometimes a copyright page is styled in all italics. The \textit command cannot cross paragraphs.</p>
+<p class="code"><code>\straightquote</code> and <code>\straightdblquote</code> insert a character. A following space is gobbled, in usual TeX fashion. This commands may be helpful if (for some technical reason) you must place a straight quote, and cannot allow the typesetter to convert it to a curly quote.</p>
+<p class="code"><code>parascale</code> environment. Unlike \charscale, this command works with line breaks and multiple paragraphs. The scaled text also has its line spacing scaled, which is not a problem in most front matter. Possibly useful if your copyright information does not quite fit on one page, at normal text size.</p>
+<p class="code"><code>\strut\hfill</code> right-aligns the following text. Be sure to finish with \par. Useful for attributing an Epigraph, or for things such as a signed Foreword.</p>
+<p class="code"><code>toc</code> environment. Specifically designed for a Table of Contents.</p>
+<p class="code"><code>\tocitem</code> is an entry in a Table of Contents.</p>
+<p>You may also use image commands, as needed. In fiction, the title page often has graphical elements.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h9.2">9.2. Chapter-Like Sections in Front Matter</h3>
+<div class="d3" id="d9.2">
+<p class="noindent">By "chapter-like section" I mean something such as a Foreword, Preface, or Introduction that may be styled in the same manner as a chapter. Most fiction does not have them. Before you place such sections in front matter, ask yourself: Do your readers really want to hear about your travails in writing the book? Maybe they'd rather get directly to the sex and violence in your main story.</p>
+<p>You may begin a chapter-like section with the \ChapterStart environment, and use \ChapterTitle. These commands may be used anywhere.</p>
+<p>Such a section always begins recto. If it does not extend for more than two pages, then you should use \thispagestyle{empty} to ensure that headers and footers do not appear. Since you don't know where a two-page section will break, the second \thispagestyle{empty} may be placed at the end of the second page, before \clearpage.</p>
+<p>However, if the section is longer than two pages, it may have headers and footers. For example, suppose you have a lengthy Preface, in a book that ordinarily has page headings. At the start of the Preface:</p>
+<p class="code"><code>\SetVersoHeadText{\allsmcp{Preface}}<br/>
+\SetRectoHeadText{\allsmcp{Preface}}</code></p>
+<p>In the above case, small caps were chosen as style. Then, instead of the author and title of your book, the word <small>PREFACE</small> will appear in headings. Page numbers will be lowercase roman, because those were set by the \frontmatter command.</p>
+<p>Note: If your book is of the genre that pretends to be a "lost manuscript," with the main story being a transcription or translation of the manuscript, then your own explanation of its finding should go in main matter, not front matter. That's because your explanation is fictional, and is part of the total story. Something like that might be titled "Author's Note" or "About the Manuscript," or maybe "Prologue," and be designed like a chapter.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h9.3">9.3. Examples of Front Matter Pages</h3>
+<div class="d3" id="d9.3">
+
+<h4 id="h9.3.1">9.3.1. Sample Title Page</h4>
+<div class="d4" id="d9.3.1">
+<p class="noindent">Below is a sample title page. The <code>\orbitron</code> command would be defined in Preamble using \NewFontFace. It calls for the font <i>Orbitron-Medium.otf</i>, which is not part of the TeX distribution. The \decoglyph command calls for a decorative element from the <i>NovelDeco.otf</i> font, which comes with the <i>novel</i> class. The length \nbs is the normal baseline skip of the book's main font. The \stake 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"/>
+<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
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+
+<h4 id="h9.3.2">9.3.2. Sample Copyright Page</h4>
+<div class="d4" id="d9.3.2">
+<p class="noindent">The Copyright Page should be styled differently from the main text. Note that you may past the copyright symbol © from a Unicode character map.</p>
+<p> </p>
+<p class="noindent"><img class="floatright" style="padding-top:2em" src="html-resources/copyrightcentered.png" width="264" height="408" alt="sample copyright page, centered"/> First Example: centered italics, limited width. This design is most effective when you don't have a lot to say.</p>
+<p class="code"><code><small>
+\clearpage\thispagestyle{empty}\vspace*{6\nbs}<br/>
+\begin{center}\itshape{<br/>
+Dark and Stormy: A Tale of Nights / Dirk Hardcase\par<br/>
+Copyright ©2017 Dirk Hardcase. 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.\par<br/>
+\null<br/>
+\allsmcp{FIRST EDITION}, March 2017.\par<br/>
+\null<br/>
+ISBN 9-876-54321-0\par<br/>
+\null<br/>
+Independently Published\\Dirkstown, 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{center}\clearpage % note initial closing brace ends itshape
+</small></code></p>
+<p> </p>
+<p class="noindent" style="clear:both"><img class="floatright" style="padding-top:2em" src="html-resources/copyrightoffset.png" width="264" height="408" alt="sample copyright page, not centered"/> Second example: offset block. This style is more effective when there are many details, particularly if there is complete Cataloging-in-Publication data.</p>
+<p class="code"><code><small>
+\clearpage\thispagestyle{empty}\null\vfill<br/>
+\begin{adjustwidth}{0em}{5em}\begin{legalese}<br/>
+Dark and Stormy: A Tale of Nights / Dirk Hardcase\par<br/>
+Copyright ©2017 Dirk Hardcase. 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.\par<br/>
+\null<br/>
+\allsmcp{FIRST EDITION}, March 2017.\par<br/>
+\null<br/>
+ISBN 9-876-54321-0\par<br/>
+\null<br/>
+Independently Published\\Dirkstown, 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}\end{adjustwidth}\clearpage
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+</div><!-- end class="d3" -->
+
+<h4 id="h9.3.3">9.3.3. Sample Dedication</h4>
+<div class="d4" id="d9.3.3">
+<p class="noindent">A Dedication is not required. But sadly, nowadays many authors write a Dedication, which is often frivolous and detracts from the book. If you feel that you need a Dedication, why not put it on your web site? Then you can always edit or remove it, if the subject or your affection runs off with someone else.</p>
+<p>Keep it simple. This one might be used for a novel of military combat.</p>
+<p class="code"><img class="floatright" src="html-resources/dedic.png" width="133" height="205" alt="sample dedication page"/> <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
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+
+<h4 id="h9.3.4">9.3.4. Sample Epigraph</h4>
+<div class="d4" id="d9.3.4">
+<p class="noindent">An Epigraph may be placed verso or recto. If your book has a Dedication and Table of Contents, a possible place for an Epigraph would be on the otherwise-blank verso between them.<p>
+<p>In this sample Epigraph, the fictional speaker will appear 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"/>
+<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
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+
+<h4 id="h9.3.5">9.3.5. Sample Table of Contents</h4>
+<div class="d4" id="d9.3.5">
+<p class="noindent">Most fiction does not have, and does not need, a Table of Contents. It is more useful when the story consists of discrete episodes with distinctive names, not just numbers. Or, if the book is a collection of short stories, a table of contents is mandatory. If your book is a critical edition, with sections by different authors, then a Table of Contents is appropriate. Avoid any of the table environments that come with TeX or its packages. These do not provide the most attractive presentation for fiction, without a lot of work on your part.</p>
+<p>A Table of Contents has no header or footer, and no printed page number. Use \thispagestyle{empty}. If it continues to a second page, add \thispagestyle{empty} at the end, if you don't know where the page breaks.</p>
+<p>If you use a Table of Contents, it must begin on a recto page.</p>
+<p>The Table of Contents does not include itself, Dedication, or Epigraph.</p>
+<p>A single front matter map, wherever it appears, need not be listed in a Table of Contents. If there are numerous maps and diagrams strewn throughout the book, then you may list them in the Table, or provide a separate List of Illustrations.</p>
+<p>A basic Table of Contents uses the center environment, so that the Table's title and each entry appear centered on the page, without any fancy layout. So simple. So effective. However, if you prefer a more formal table, <i>novel</i> has commands for this purpose.</p>
+
+<h5 id="h9.3.5.1">9.3.5.1. The toc Environment</h5>
+<div class="d5" id="d9.3.5.1">
+<p class="code"><code>\begin{toc}[<em>extra entry separation</em>]{<em>extra margins</em>} <em>...</em> \end{toc}</code></p>
+<p>The table is not indented, and text within it is not indented.</p>
+<p>• The optional argument is a number. It is the portion of normal baselineskip that will be added beneath each \tocitem entry (see next section). Default is 0, meaning that there is no extra skip between items, and normal baselineskip is maintained. A value greater than 0 spreads the entries, which could be attractive if there are only a few chapters and you'd like to use more space on the page. For example, a value of 0.25 means that a gap of 0.25 normal baselineskip will be added beneath each entry. A small negative value will crowd the lines together, but there is a limit (approximately -0.1) before the lines cannot be squeezed any tighter.</p>
+<p>Note that the optional argument only applies to \tocitem entries, not to any other text within the environment.</p>
+<p>• The required argument is a length, which will be the amount of extra margin added at left and right of the table (using adjustwidth). A value of 0em allows the table to occupy the full width of the textblock. A value of 2em adds 2em to the margin on each side, so that the width of the table is 4em less than the width of the textblock.</p>
+<p>It is best to specify horizontal lengths in units of <i>em</i> or the proportional <i>\parindent</i> or <i>\textwidth</i>.</p>
+<p>• Place at least empty line above the Table, using \null or \vspace*. This will prevent the Table's title (which is normally anlarged using \charscale) from encroaching into the top margin.</p>
+</div>
+
+<h5 id="h9.3.5.2">9.3.5.2. \tocitem and \tocitem* Entries</h5>
+<div class="d5" id="d9.3.5.2">
+<p class="code"><code>\tocitem[<em>chapter number</em>]{<em>description</em>}{<em>page number</em>} and starred version</code></p>
+<p>• Use this command for entries in the Table. Do not use it for non-Table text on the page.</p>
+<p>• The optional argument is the chapter number, at most two digits. The number will be left-aligned, with a period automatically added. Following the period will be the amount of space needed to keep the following description aligned.</p>
+<p>• If the optional argument is omitted (or empty), then there is no space, and the following description will align to the left of the table.</p>
+<p>• If the optional argument is the tilde character ~ then no number or period is printed, but the space is occupied, so that the following description aligns as if you had entered a chapter number.</p>
+<p>• The description is usually the chapter title. If it cannot easily fit on one line, then use an additional \tocitem, because the text cannot be wrapped. The following example shows how this can be done.</p>
+<p>• Without the asterisk, \tocitem fills the area between the description and the page number with empty space. The more popular, starred \tocitem* command fills with a dotted line, and is very attractive.</p>
+<p>• You may use ordinary style commands, such as \textit{}, in the entries.</p>
+<p><b>Example of toc:</b></p>
+<p class="code" style="text-indent:0px; font-size:small"><img class="floatright" src="html-resources/toc.png" width="264" height="408" alt="toc example"/>
+<code>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+\begin{toc}[0.25]{3em}<br/>
+\vspace*{4\nbs}<br/>
+{\centering\charscale[1.25]{Contents}\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>
+<div style="clear:both"></div>
+</div></div><!-- end class="d4" -->
+
+<h4 id="h9.3.6">9.3.6. Sample Foreword</h4>
+<div class="d4" id="d9.3.6">
+<p>A Foreword is very rare in fiction, because its normal purpose (in nonfiction) is to endorse, or add credence to, the rest of the book. Thus, a Foreword is not written by the author, but by an editor, expert, or celebrity. You should be so lucky.</p>
+<p><img src="html-resources/foreword.png" class="floatright" width="178" height="826" alt="example foreword"/> A Foreword begins recto. Its start page has no header, but may have a footer. If there is only one more page, then again have no header, possibly footer. More than two pages, use both header and footer if they are available. The header text is not the author and title of the book. Usually, it is "Foreword" (perhaps in small caps) recto and verso. Typically the Foreword is signed at its end. A very lengthy Foreword might have its writer's name and credentials shown on its start page.</p>
+<p>We will imagine that your book <i>Zombie Chemists</i> was once approved for the reading list of some low-income elementary school. Four years later, all the kids who read it were accepted in chemical engineering programs at elite colleges. Now, someone from the National Bureau of Schools wants to recommend the book everywhere. The lengthy Foreword is styled like a chapter (see below), using header/footer book layout:</p>
+<p class="code"><code><small>
+\cleartorecto <span class="ap">% always start with this</span><br/>
+\thispagestyle{footer} <span class="ap">% the book has a footer</span><br/>
+\SetVersoHeadText{\textsc{Foreword}}<br/>
+\SetRectoHeadText{\textsc{Foreword}}<br/>
+\begin{ChapterStart}<br/>
+\vspace*{2\nbs}<br/>
+\ChapterTitle{Foreword}<br/>
+\end{ChapterStart}<br/>
+It is my great pleasure to recommend...\par<br/>
+\lipsum<br/>
+... And I urge all schools to adopt it.\par<br/>
+\null<br/>
+\stake\hfill Bigg Wigg, Ph.D.\par<br/>
+\stake\hfill Honcho, National Bureau of Schools, 2017\par<br/>
+\clearpage <span class="ap">% always end with this or \cleartorecto</span><br/>
+<span class="ap">% Be sure to re-set the head texts!</span>
+</small></code></p>
+<p style="clear:both">Once again: It is very unlikely that your book will have a Foreword. Ever.</p>
+</div>
+
+<h4 id="h9.3.7">9.3.7. Sample Preface</h4>
+<div class="d4" id="d9.3.7">
+<p>A Preface is written by the author. Usually, it is an explanation of the circumstances that led to the writing of this book. That is common in nonfiction, where a how-to book might self-praise expertise; a lifestyle book might mention the author's own success with the following advice; an account of an incident might explain that the author was really there.</p>
+<p><img class="floatright" src="html-resources/preface.png" width="178" height="826" alt="example preface"/> A Preface is uncommon in fiction, but it is sometimes used as a catch-all for a variety of things, perhaps including acknowledgements and permissions when they are not shown separately. Or, if the fiction was "inspired by" some real events, that might be mentioned. Don't you dare say that your book was inspired by the writing style of [famous living author] or the setting and characters of [television, movie, another author's book].</p>
+<p>Here, we will imagine that the author is a combat veteran who is writing combat fiction. He will explain his own experience in the armed forces, so we can understand that the setting is realistic:</p>
+<p class="code"><code><small>
+\cleartorecto <span class="ap">% always start with this</span><br/>
+\thispagestyle{footer} <span class="ap">% the book has a footer</span><br/>
+\SetVersoHeadText{\textsc{Preface}}<br/>
+\SetRectoHeadText{\textsc{Preface}}<br/>
+\begin{ChapterStart}<br/>
+\vspace*{2\nbs}<br/>
+\ChapterTitle{Preface}<br/>
+\end{ChapterStart}<br/>
+In the 1990s I served three tours of duty in...\par<br/>
+\lipsum[1-2]<br/>
+Our platoon successfully...\par<br/>
+\lipsum[1-2]<br/>
+By the time I returned home...\par<br/>
+\lipsum[1-2]<br/>
+... And finally, I would like to thank....\par<br/>
+\null<br/>
+\stake\hfill Dirk Hardcase\par<br/>
+\stake\hfill Springfield, March 14, 2017\par<br/>
+\clearpage <span class="ap">% always end with this or \cleartorecto</span><br/>
+<span class="ap">% Be sure to re-set the head texts!</span>
+</small></code></p>
+<p style="clear:both">Note that a <i>fictional</i> tale of the book's creation does not belong in a Preface, or anywhere in front matter. Put it in main matter.</p>
+</div>
+
+<h4 id="h9.3.8">9.3.8. Sample Acknowledgements</h4>
+<div class="d4" id="d9.3.8">
+<p class="noindent">Most books don't need acknowledgements. As with a Dedication, don't write Acknowledgements just because you can. Acknowledgements are for those who provided real assistance. If you want to provide a shout-out to your friends for their encouragement, do that on a web page.</p>
+<p>If you have a Preface, you can include acknowledgements there, so you don't need a separate Acknowledgements section. If you obtained permission to use copyrighted material, and if that can be documented on the copyright page, do it there; or do it in the Preface, if you have one.</p>
+<p>Acknowledgements begin on a recto page. If lengthy, style the section like a chapter. See the above sample Foreword and Preface. If very brief, it is better to use the style of a Dedication or Epigraph, with the material in a block that does not fill the page width. In the following, the width was manually adjusted until the text looked good, without hyphenation:</p>
+<p class="code"><img class="floatright" src="html-resources/acknowledgements.png" width="178" height="274" alt="sample acknowledgements"/>
+<code><small>
+\cleartorecto <span class="ap">% always start with this</span><br/>
+\thispagestyle{empty}<br/>
+\vspace*{6\nbs}<br/>
+\begin{adjustwidth}{3.6em}{3.6em}<br/>
+{\centering\charscale[1.6]{Acknowledgements}\par}<br/>
+\null<br/>
+\null<br/>
+\noindent The author would like to thank the antiquities research staff at the Erewhon County Library, without whose assistance the material regarding Eighteenth Century axe murderers would never have come to light.\par<br/>
+\end{adjustwidth}<br/>
+\clearpage <span class="ap">% always end with this or \cleartorecto</span>
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+
+<h4 id="h9.3.9">9.3.9. Sample Map</h4>
+<div class="d4" id="d9.3.9">
+<p class="noindent">Many works of fiction have a map or other diagram. It might be the map of a real or fictional geographic area. It might be the map of a crime scene. It might be an inheritance chart. Even though fictional, it may be placed in front matter.</p>
+<p>A map may be placed verso or recto, as long as it does not visually interfere with material on the facing page. In particular, do not place a map on the verso that faces the opening of your story.</p>
+<p>Typically, a map appears late in front matter, but I have sometimes seen it early in front matter. I have not seen an authoritative guide to placement. A single map, or maybe two, need not be mentioned in a table of contents or illustrations. If you have a lot of them strewn around the book, then they should be listed in such a table; but this is very rare in fiction.</p>
+<p>As with all images in <i>novel</i>, a map must be raster png or jpg (not vector artwork), of correct resolution, placed using <i>novel's</i> own image placement commands. These are described elsewhere in this documentation.</p>
+<p>Normally, a map in front matter has no header/footer. For example:</p>
+<p class="code"><img class="floatright" src="html-resources/map.png" width="178" height="274" alt="sample map"/>
+<code><small>
+\clearpage <span class="ap">% always start with this or \cleartorecto</span><br/>
+\thispagestyle{empty}<br/>
+\BlockImage{areamap.png} <span class="ap">% 600dpi b/w</span>
+\vspace{2\nbs}<br/>
+\begin{center}<br/>
+1. Alice Springs\\<br/>
+2. Tuktoyaktuk\\<br/>
+3. Pflugerville\\<br/>
+4. Pucallpa\\<br/>
+5. Kolwezi\\<br/>
+6. Dushanbe\\<br/>
+7. Mittenwald\\<br/>
+8. Sanya\\<br/>
+9. Ice Station 414\par<br/>
+\end{center}<br/>
+\clearpage <span class="ap">% always end with this or \cleartorecto</span>
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page09 -->
+<!-- ************************************************************ -->
+<div id="page10" class="page">
+
+
+<h2 id="h10">10. Transition from Front Matter to Main Matter</h2>
+<div class="d2" id="d10">
+<p class="noindent">Main matter always begins with the \mainmatter command, immediately following \clearpage or \cleartorecto. The \mainmatter command sets page numbering to Arabic 1.</p>
+<p>There is no middle-matter between front matter and main matter. So, it is necessary to decide whether a page belongs in one or the other. The final page of front matter is verso, with a lowercase roman page number that is almost never printed. The first page of main matter has Arabic page number 1, which may or may not be printed, depending on layout.</p>
+<p>In general, anything that is "about the book" is meta-information that belongs in front matter. "The story itself," and any aftermath, belongs in main matter. This section provides a guide to determining which is which.</p>
+<p>Some situations are judgement calls. Where I provide an opinion, it is based on my obervations of popular fiction books, or the <i>Chicago Manual of Style, 16th Edition (CMoS)</i>, favoring actual books when there is room for disagreement. Opinions offered by non-authoritative web sites have been disregarded.</p>
+
+<h3 id="h10.1">10.1. Introduction in Front Matter</h3>
+<div class="d3" id="d10.1">
+<p class="noindent">An Introduction is a chapter-like section, written by the author.</p>
+<p>In nonfiction, the purpose of an Introduction is to familiarize the reader with background material, so that the main material can be properly understood in context. Such an Introduction appears after Foreword and Preface (if any), and is placed in front matter. It begins recto.</p>
+<p>In fiction, a front matter Introduction is very rare (I have never seen any), because it is supposed to be factual, not a part of the story. Perhaps a fictional front matter Introduction might be used in a novel that requires extensive world-building; but that's not my genre, so I do not know. If in doubt, look at some actual books in that genre.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.2">10.2. Author's Note in Front Matter</h3>
+<div class="d3" id="d10.2">
+<p class="noindent">An Author's Note is brief, preferably one page (at most two), beginning recto. If very brief, it may be styled like an Epigraph. Otherwise, it is styled like a chapter. No header, but page numbers may appear in footer.</p>
+<p>Typically, an Author's Note is used when an author has something to say, but there is no Preface (or the Note is inappropriate in a Preface). The Note directly addresses the reader, from the author, and is often signed with place and date.</p>
+<p>For example, I recall a book (crime genre) where the Author's Note mentions that a certain aspect of animal behavior, which will appear in the story, is actually based in reality. Otherwise, it sounds ridiculous, and we would assume that the author just made that up. The author is making a truthful remark about the book, rather than telling a story, so the Note properly belongs in front matter.</p>
+<p>On the other hand, in the "lost manuscript" genre, the Author's Note may tell how the information came into possession of the author. That is fiction, but since it is brief and pretends to be about the book, it is placed in front matter. However, a long tale about the discovery of the manuscript belongs in a main matter Introduction, as described below. You can also have a front matter Author's Note mentioning how the material was acquired by the author from some adventurer, followed by a main matter Introduction, with the adventurer's own tale of the manuscript's finding.</p>
+
+<h4 id="h10.2.1">10.2.1. Sample Author's Note</h4>
+<div class="d4" id="d10.2.1">
+<p class="noindent">For example, in a book of historical fiction:</p>
+<p class="code"><img class="floatright" src="html-resources/authorsnote-frontmatter.png" width="178" height="274" alt="sample author's note in frontmatter"/>
+<code><small>
+\cleartorecto <span class="ap">% always start with this</span><br/>
+\thispagestyle{empty}<br/>
+\vspace*{6\nbs}<br/>
+{\centering\charscale[1.6]{Author's Note}\par}<br/>
+\null<br/>
+\null<br/>
+\noindent The Third-Century burial practices of the Roman Empire, for those of the lesser nobility, were generally as described in this story. The description of Alemanni tribes is based on a pastiche of opinions by contemporaneous writers, who saw them from the perspective of Graeco-Roman culture.\par<br/>
+In the chapters pertaining to transmontane trade and cultural exchange, I have taken great liberty with the likely behavior and responses of the characters as events unfold. Nevertheless, the goods and services available to them, in ordinary commerce, are as described in the story.\par<br/>
+\clearpage <span class="ap">% always end with this or \cleartorecto</span>
+</small></code></p>
+<div style="clear:both"></div>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.3">10.3. Second Half-Title in Front Matter</h3>
+<div class="d3" id="d10.3">
+<p class="noindent">If a second Half-Title is used, <i>CMoS</i> acknowledges that theory and practice often differ. Here, I will go with the common practice in fiction.</p>
+<p>If front matter is short, a second Half-Title is sometimes used to prevent verso front matter from clashing with recto main matter. This is one of the possibilities discussed in the basic six-page front matter (Appendix B). In this case, the second Half-Title is front matter, and so is its verso. Main matter begins at the following recto.</p>
+<p>You can also do this for more than the basic six pages of front matter, if you wish. However, there are situations where a second Half-Title should be the start of main matter. See below.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.4">10.4. Part Separator in Main Matter</h3>
+<div class="d3" id="d10.4">
+<p class="noindent">Some books are partitioned into distinct sub-books. A sub-book is of substantial length, not individual short stories.</p>
+<p>If your book has distinct sub-books, then each of them has its own recto cover page, known as a Part Separator. Its verso is blank or Epigraph. Then the accompanying story begins recto.</p>
+<p>A Part Separator is always main matter. So, the first Part Separator is page 1. Its text begins on page 3. Do not re-initalize the page count when you get to the next Part Separator.</p>
+<p>The simplest Part Separator is <i>Part I</i>, followed by <i>Part II</i>. You could also call them <i>Book I</i> and <i>Book II</i>, or perhaps <i>First Invasion</i> and <i>Second Invasion</i>. These are not chapters; each of them occupies a substantial portion of the entire book, and contains its own chapters.</p>
+<p>Sometimes a Part Separator has a brief description of its purpose, as in <i>Book I. On Earth</i> followed by <i>Book II. On Mars</i>.</p>
+<p>Unless your book has a very complex structure, do not use both a second Half-Title and a Part Separator. Combine them as the recto main matter page 1: <i>The Withens Chronicles. Part I</i>. Then the next Part Separator might simply be <i>Part II</i>.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.5">10.5. Second Half-Title in Main Matter</h3>
+<div class="d3" id="d10.5">
+<p class="noindent">When front matter is <i>lengthy</i>, and there is no Part Separator, then a second Half-Title is used as the start of main matter. It is recto page 1. Its verso (blank, sometimes Epigraph) is page 2, and the beginning of the story is page 3.</p>
+<p>How long is <i>lengthy</i>? No specific value. If in doubt, place a second Half-Title in main matter, rather than in front matter. If the front matter contains any chapter-like sections (such as Foreword, Preface, Introduction) then consider it to be <i>lengthy</i> regardless of the number of pages.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.6">10.6. Introduction in Main Matter</h3>
+<div class="d3" id="d10.6">
+<p class="noindent">An Introduction is a chapter-like section. If the book is nonfiction and the Introduction is factual, it belongs in front matter, as described above. But in fiction, where an Introduction is a lead-in to the larger story, it belongs in main matter.</p>
+<p>A main matter Introduction is typically used in the "lost manuscript" genre, where some fictional adventurer or archaeologist describes how the manuscript was found and translated. Usually the narration is told in the first person. Sometimes the author pretends to be the adventurer or achaeologist. Often the narrator is someone else. Following such an Introduction, the various chapters will reveal the contents of the manuscript. If the voice of the Introduction returns at the end, it is called a Conclusion.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.7">10.7. Prologue in Main Matter</h3>
+<div class="d3" id="d10.7">
+<p class="noindent">A Prologue, even if one page, is styled as a chapter. It belongs in main matter.</p>
+<p>The purpose of a Prologue is to provide a quick lead-in or setting for the story, and get the reader's attention. It is fiction, confined in place and time (one scene, one perspective). The narrator may be first-person or third-person.</p>
+<p>Do not use a Prologue for the voice of the author speaking about the book, as author; that goes in an Introduction or Author's Note.</p>
+<p>If a book has a Prologue, then it is likely to have an Epilogue after the main story ends. An Epilogue also belongs in main matter.</p>
+<p>I do not know of any fiction with both a fictional Introduction and a Prologue. If so, Introduction precedes Prologue.</p>
+<p>Note: I have seen some web pages advising that a Prologue should go in front matter, and be told by a character (who appears in the following story). Based on <i>CMoS</i> and actual books, I do not think that is correct.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h10.8">10.8. Chapters</h3>
+<div class="d3" id="d10.8">
+<p class="noindent">Finally, you have arrived at Chapter One! It is always recto, in main matter. As described above, its page number may be 1 or 3. If your book is a collection of short stories, the same applies to the first story.</p>
+<p>Subsequent chapters may begin recto or verso, or the book may be designed so that each chapter always begins recto. In the majority of novels I have seen, recto/verso is used. The \clearpage command starts a new page (recto or verso), and the \cleartorecto command will (if necessary) insert a blank verso, so that the following material is always recto.</p>
+<p>In the case of short stories, especially if they are by different authors, it is customary to begin each one as recto.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page10 -->
+<!-- ************************************************************ -->
+<div id="page11" class="page">
+
+
+<h2 id="h11">11. Chapter Structure</h2>
+<div class="d2" id="d11">
+<p class="noindent">This section describes how chapters, and chapter-like material such as Preface, are designed. The <i>novel</i> class has commands specifically for this purpose. Do not use the ordinary TeX \chapter command, or any other TeX partitioning such as \section.</p>
+<p>The last command of the document body must be \cleartoend. This ensures that the final page will be a blank verso, if necessary preceded by a blank recto.</p>
+
+<h3 id="h11.1">11.1. ChapterStart Environment</h3>
+<div class="d3" id="d11.1">
+<p class="noindent">Unless your book has numerous short, rapid-fire chapters, begin each chapter with the ChapterStart environment. Also do this for chapter-like sections such as Foreword, Preface, Introduction, Prologue, Epilogue, and other places where the design resembles a chapter:</p>
+<p class="code"><code>
+\clearpage % or \cleartorecto<br/>
+% \thispagestyle{<em>choose</em>} % if not default<br/>
+% \SetVersoHeadText{<em>text</em>} % sometimes
+% \SetRectoHeadText{<em>text</em>} % sometimes
+\begin{ChapterStart}[<em>lines</em>]<br/>
+% contents of chapter start<br/>
+\end{ChapterStart
+</code></p>
+<p>The environment reserves a block of space, 10 lines high. The number may be changed (for an individual chapter) with the optional <i>lines</i> argument. Its minimum value is 4.</p>
+<p>You can put almost anything you like within this environment. Its height does not shrink or expand with content. However, if you put too much for the reserved space, then the excess will flow out the bottom of the reserved area, and mingle with the main text below. That is usually undesirable. If you do put too much, no error or warning is generated (because it might have been by intent).</p>
+<p>Note that ChapterStart does not, by itself, begin a new page. You have to issue the \clearpage (or \cleartorecto) command before ChapterStart. This is to allow for exotic designs with small ChapterStart space, and more than one chapter per page. But if that is the nature of your book, have a look at the \QuickChapter command.</p>
+<p>If the header/footer style for this particular chapter is <i>not</i> the same as the ChapterStart default style, then locally over-ride the default using \thispagestyle <i>prior to</i> ChapterStart. See below.</p>
+<p>In some books that have headers, their content varies from chapter to chapter. Commands \SetVersoHeadText and \SetRectoheadText control that content. Once issued, they do not expire at the end of a chapter, but remain in effect until re-issued.</p>
+
+<h4 id="h11.1.1">11.1.1. Chapter Title, Subtitle, Deco</h4>
+<div class="d4" id="d11.1,1">
+<p class="noindent">These commands are intended for use within the ChapterStart environment. In each case the optional <i>alignment</i> is <i>l</i> for left, <i>c</i> for center (default), <i>r</i> for right.</p>
+<p class="code">\ChapterTitle[<em>alignment</em>]{<em>text</em>}</p>
+<p>The chapter title will automatically use the font specifications of <i>chapterfont</i>, unless you locally over-ride them using other font commands.</p>
+<p class="code">\ChapterSubtitle[<em>alignment</em>]{<em>text</em>}</p>
+<p>The chapter subtitle will automatically use the font specifications of <i>subchfont</i>, unless you locally over-ride them using other font commands.</p>
+<p class="code">\ChapterDeco[<em>alignment</em>]{<em>text, image</em>}</p>
+<p>The chapter deco is a non-committal way to place almost anything. It uses the ordinary text font, unless you over-ride it with a font command. Perhaps you will use the \decoglyph command to pick an item from the deco font. You can also use an image.</p>
+<p>Each of the above commands is limited to one, non-wrapping line. However, they may be issued more than once in the same ChapterStart. So, if the chapter title requires two lines, use \ChapterTitle twice.<p>
+<p>If you don't like the vertical positioning, you can change it using \vspace commands. You will usually need to use \vspace* above the chapter title, so that it is not too high on the page.</p>
+</div>
+
+<h4 id="h11.1.2">11.1.2. Default Header/Footer at Chapter Start</h4>
+<div class="d4" id="d11.1,2">
+<p>By default, <i>novel</i> automatically uses \thispagestyle{footer} when it sees the ChapterStart environment. Then, no header will print above the chapter start. However, if there is a footer, it will print.</p>
+<p>If you wish to use a different default behavior for ChapterStart, then write this command <i>in the Preamble</i>:</p>
+<p class="code"><code>\SetChapterStart{<em>choice</em>}</code></p>
+<p>In the above, <i>choice</i> is one of the choices available for \thispagestyle, as listed below.</p>
+</div>
+
+<h4 id="h11.1.3">11.1.3. \thispagestyle at Chapter Start</h4>
+<div class="d4" id="d11.1.3">
+<p>No matter whether a book is fiction or nonfiction,the first page of a chapter almost never has a header. However, it may have a footer if the book design normally has one (typically the page number).</p>
+<p>If the setting provided by \SetChapterStart is inappropriate for a particular chapter (or anything using ChapterStart environment), then locally over-ride it using one of these choices:</p>
+<p class="code"><code>\thispagestyle{footer}</code></p>
+<p>The above choice actually means, “footer, if normally available.” It does not create a footer that would not otherwise be present in your general book layout. This is the built-in default.</p>
+<p class="code"><code>\thispagestyle{empty}</code></p>
+<p>The above choice prints neither header nor footer. Not best, since it is usually appropriate to print a footer when it exists.</p>
+<p class="code"><code>\thispagestyle{dropfoliobeneath}</code></p>
+<p>The above choice is the same as \thispagestyle{footer}, if the layout has a footer. Otherwise, a fake footer is created just below the text block, in the lower margin. The page number is centered there. This choice can be used if your lower margin is much taller than the minimum required by the printer's safe clearance zone. Since TeX does not know what that requirement is, you will have to inspect the result yourself.</p>
+<p class="code"><code>\thispagestyle{dropfolioinside}</code></p>
+<p>The above choice is the same as \thispagestyle{footer}, if the layout has a footer. Otherwise, it is very tricky. It reduces the height of the ChapterStart environment by one line. Then, the text on that page is moved upward by one line, leaving a vacancy where the last line would normally be. The page number is centered there. This does not intrude into the lower margin.</p>
+<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="code"><code>\thispagestyle{forcenumber}</code></p>
+<p>The above choice is the same as \thispagestyle{footer}, if the layout has a footer. Otherwise, it assumes that the page number is located at the outside of a header, and prints only that outside header portion. This is a very rare situation that I have only seen in some nonfiction, where the number of each new chapter (usually by different authors) must be printed somewhere on the page. Avoid it unless you are certain that you need it.</p>
+</div>
+
+<h4 id="h11.1.4">11.1.4. ChapterStart With Image</h4>
+<div class="d4" id="d11.1.4">
+<p class="noindent">You can use an image in chapter titles. If you place an image, use one of the image commands defined by <i>novel</i> elsewhere in the documentation. Any other method is likely to push the following text off-grid.</p>
+<p>Be sure that you are licensed to use the image. Many clipart catalogs "for personal use only," prohibit usage in commercial books. One possible source is <a href="http://openclipart.org" rel="external" target="new">openclipart.org</a> (note the <em>.org</em>).</p>
+
+<h5 id="h11.1.4.1">11.1.4.1 Text Over Image</h5>
+<div class="d5" id="d11.1.4.1">
+<p class="noindent"><img class="floatright" src="html-resources/ctimg35.png" width="79" height="196" alt="example of chapter title image, text over"/> You may position text over an image. Be aware that overlapping text and graphics may be interpreted as a mistake, by human reviewers. It is best to use black text, or grayscale text that is much darker than the underlying image. Results are uncertain if you try to place light text over a dark image.</p>
+<p>Example, where the command \unifrac calls for the font <i>UnifrakturMaguntia.ttf</i>. Note that the font command is <i>outside</i> \charscale:</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/>
+</small>\end{ChapterStart}</code></p>
+</div>
+
+<h5 id="h11.1.4.2">11.1.4.2. Text Within Image</h5>
+<div class="d5" id="d11.1.4.2">
+<p class="noindent">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 may appear as expected in PDF, and print that way on many printers, there are many 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/>
+\end{ChapterStart}</small></code></p>
+</div></div><!-- end class="d4" -->
+</div><!-- end class="d3" -->
+
+<h3 id="h11.2">11.2. QuickChapter and Scene Breaks</h3>
+<div class="d3" id="d11.2">
+<p class="noindent">These commands are used for indicating a break, without the formality ChapterStart.</p>
+<p>You will need to inspect your layout, to ensure that the break does not occur at an inconvenient location, such as at the bottom of the page. This is not automated. If the break occurs in a bad place, you will simply have to re-write so that it occurs elsewhere.</p>
+
+<h4 id="h11.2.1">11.2.1. \QuickChapter[<em>linelength</em>]{<em>chapter title</em>}</h4>
+<div class="d4" id="d11.2.1">
+<p class="noindent">If your novel is the kind of story that consists of numerous short chapters in rapid succession, then you probably do not wish to begin each chapter on its own page, with a block of whitespace at the top. The \QuickChapter command provides an alternative to ChapterStart.</p>
+<p>\QuickChapter inserts two blank lines. In the gap, the chapter title is left-justified using <i>subchfont</i> (not <i>chapterfont</i>). It is slightly raised from the normal baseline, because this looks better; but the following text is back on-grid. By default, the start of the following text will be un-indented.</p>
+<p>If the optional <i>linelength</i> is provided, then a dash will be written after the title, at the position and thickness typical of the em dash in <i>subchfont</i>. If <i>linelength</i> is specified in units of length, then that will be the length of the line. But if <i>linelength</i> is an asterisk, then the line will fill to the right margin.</p>
+<p>Note that this command is too obstrusive for mere scene changes within a chapter.</p>
+<p>Example:</p>
+<p class="code"><code><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>
+</div>
+
+<h4 id="h11.2.2">11.2.2. Scene Breaks</h4>
+<div class="d4" id="d11.2.2">
+<p class="noindent">There are several commands dedicated to the purpose of scene breaks.</p>
+<p class="code"><b>\scenebreak</b> inserts a one-line blank skip. The following line of text is not indented.</p>
+<p class="code"><b>\sceneline</b> inserts a one-line skip, containing a short centered line. The following line of text is not indented.</p>
+<p class="code"><b>\scenestars</b> inserts a one-line skip, containing three spaced, centered asterisks. The following line of text is not indented.</p>
+<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"/>
+<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/>
+Unfortunately, novelists of that era had so little to write about, or they would have chosen another family to pursue.\par
+</small></code></p>
+<p>If you are using \scenebreak and the gap occurs at the very bottom or top of a page, then manually substitute \sceneline or \scenestars there. This is a standard way to indicate that the gap is intentional. The subtitution is not automatic.</p>
+</div>
+
+<h4 id="h11.2.3">11.2.3. \IndentAfterScenebreak</h4>
+<div class="d4" id="d11.2.3">
+<p class="noindent">This global command may only be used in the Preamble.</p>
+<p>Normally, text begins without a paragraph indent, after each scene break. This is standard in fiction. If you prefer that each new scene begins indented, use this command. It works with \scenebreak, \sceneline, and \scenestars.</p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page11 -->
+<!-- ************************************************************ -->
+<div id="page12" class="page">
+
+
+<h2 id="h12">12. Footnotes, Endnotes, Back Matter</h2>
+<div class="d2" id="d12">
+<p class="noindent">The <i>novel</i> class has <em>limited</em> support for footnotes, because they are rarely used in fiction. Nevertheless, I have seen them. The notes may be factual or imaginary.</p>
+<p>If there are more than a handful of notes, then use endnotes to avoid a constant disruption of the text flow. You may use both footnores and endnotes.</p>
+<p>Footnotes and endnotes use superscripts at the appropriate point in the main text. The actual footnote or endnote begins with ordinary text, not a superscript. You can control the appearance of superscripts using \SetMarkers and related commands. See the section regarding fonts, earlier in this document.</p>
+
+<h3 id="h12.1">12.1 Footnotes</h3>
+<div class="d3" id="d12.1">
+<p>Footnotes appear at the bottom of the page where they are placed. There is no option to accumulate them to another location. Very long footnotes might straddle pages, but that situation is uncommon in fiction (and not within your control).</p>
+<p class="code"><code>\footnote[<em>option</em>]{<em>text</em>}</code></p>
+<p>The \footnote command places a superscript "marker" at the place where the command is written. The included text is written at the bottom of the page, beneath a short line that separates it from the main text. The footnote text is at smaller size and line skip, and has the same marker placed before it (but not as superscript). All of this is automatic.</p>
+<p>You may, if necessary, apply some style to the footnote text. For example, if you are referring to another work, its title might be in italics.</p>
+<p>Normally, no option is used. If you use option <i>0</i> (zero) then no marker will appear in the main text, and the footnote text will also appear without a marker. The count of markers is not incremented. This applies whether the markers are numbers or symbols.</p>
+<p>• Trick: If you are using footnote numbers, but wish to place a special footnote using a symbol, you can do it manually. For example:</p>
+<p class="code"><code>He blinked.*\footnote[0]{* No, he didn't.}</code></p>
+<p>• Avoid use of underlining, as it is considered bad style, due to visual distraction. If necessary, use italics.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h12.2">12.2 Endnotes</h3>
+<div class="d3" id="d12.2">
+<p class="noindent">Endnotes are sometimes used in fiction. For example, J.R.R. Tolkien's <i>Lord of the Rings</i> trilogy has a large number of them.</p>
+<p>You may use both footnotes and endnotes, if you wish. However, if endnotes are used, then footnotes must be marked by symbols, rather than by numbers, to avoid confusion. The counts for endnotes and footnotes are independent.</p>
+
+<h4 id="h12.2.1">12.2.1 \endnote, \ResetEndnote, \memo{}</h4>
+<div class="d4" id="d12.2.1">
+<p class="noindent">The \endnote command inserts a numerical superscript in the text. A running count of the numbers is automatically updated. This command does nothing else.</p>
+<p>The endnote numbers run continuously through the text, without reset. If you wish to reset the count (perhaps at new chapters), you have to do it manually, using \ResetEndnote.</p>
+<p>When you use \endnote, there is no provision for the actual note. The <i>novel</i> class does not know, and does not care, whether or not you actually write the endnote later. If you wish to write a reminder to yourself, about why you put an endnote marker there, use \memo{<i>text</i>}. The argument of \memo{} will not be printed, and will not be remembered for later use. Note that \memo is not like the percent % comment, because anything following \memo{} will be honored.</p>
+</div>
+
+<h4 id="h12.2.2">12.2.2 \endnotetext{<em>number</em>}{<em>text</em>}</h4>
+<div class="d4" id="d12.2.2">
+<p class="noindent">The <code>\endnotetext</code> command is a simple way of styling endnotes. You do not have to use it, if you have your own method. These may be placed per-chapter, or at the final end. The <i>novel</i> class does not keep track of them.</p>
+<p>The first argument is usually the endnote number. A period and following space will automatically be added, so that the text of the note is block-indented. You may use <code>\emph{<em>number</em>}</code> if you prefer the number to be in italics.</p>
+<p>The text must be one paragraph. Be sure to end with <code>\par</code> or equivalent.</p>
+<p>If the note needs more than one paragraph, then continue like this, with an empty note number:</p>
+<p class="code"><code>\endnotetext{}{\indent <em>text</em>}</code></p>
+<p>• In <i>novel</i>, you must create and style the page(s) with endnotes yourself! There is no provision for bibliography, and no provision for any other kind of automated styling. This is because the endnotes, being fictional, are more like the main text than any academic style. Think of the endnotes as just another chapter, but starting with something that identifies them as being endnotes. Pagination continues as main matter, with Arabic page numbers. This is recommended by the <i>Chicago Manual of Style</i>, for both fiction and nonfiction.</p>
+<p>Example of an endnote:</p>
+<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 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="447" height="151" alt="using endnotetext"/></p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="h12.3">12.3 Regarding Back Matter</h3>
+<div class="d3" id="d12.3">
+<p class="noindent">TeX has a do-nothing \backmatter command. No different with <i>novel</i> class, from version 1.40. Earlier versions tried to do something with that command, but the tactic was abandoned.</p>
+<p>Anything following the end of your story is still treated as main matter. Epilogue, Conclusion, Endnotes, Appendix, whatever: all of them continue the Arabic page numbers. This is recommended by <i>CMoS</i> and is also best on a practical basis. For example, J.R.R. Tolkien's <i>The Return of the King</i> has very extensive post-story material, such as a history of the Elves, some linguistics, and notes. Nevertheless, the page numbering is Arabic, continued from the main story without reset.</p>
+<p>Of course, you may add anything you wish, after your story ends. Call it what you wish. Such material must begin recto, and may have its own cover page.</p>
+<p>If your book is available in both hardcover and softcover, then the dust jacket of the hardcover may have "About the Author" on its interior flap. This information is not present on the soft cover, which has no flap. You may, if you wish, place it as an About the Author section, recto, after your story ends. However, I sugest that such material is better on a web site, where you can change or remove it.</p>
+<p>The last command of the document body must be \cleartoend. This ensures that the final page will be a blank verso, if necessary preceded by a blank recto.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page12 -->
+<!-- ************************************************************ -->
+<div id="page13" class="page">
+
+
+<h2 id="h13">13. Cover Artwork</h2>
+<div class="d2" id="12">
+<p class="noindent">This portion serves a limited purpose. It is for the benefit of those who need to submit color print cover artwork in the form of a PDF/X-1a:2001 file, with the artwork as CMYK and 240% ink limit. This is the format required by some American print-on-demand services. It is also generally acceptable to others, whose requirements are less restrictive.</p>
+<p><b>Before you begin:</b> Do you really need to do this? Many print-on-demand services are perfectly happy to accept something such as an ordinary RGB jpeg image, as long as it has the correct size (with bleed area). They can easily process it for print production in a few moments, using professional software. If they do it, then whether or not you are surprised by the resulting colors, will depend on whether or not your original image is within the printer gamut. In other cases, the print service prefers (or insists) that you do the image print production processing yourself. Then, you get to see an emulation of the print colors <em>before</em> you submit the file, and can change your artwork if the resulting colors are disappointing.</p>
+<p>The <em>novel</em> document class does not provide any support for creating the original artwork, either image or text. In fact, TeX is not the best way to do that. Use a graphics program (such as the free GIMP) to do your artwork, including text. In the end, your text will be rasterized, just like any background image. For this reason, avoid using small text, or consider using a sans-serif typeface on the cover (even though there is no sans-serif in the book itself).</p>
+<p>DO NOT PLACE A BARCODE. If your print service requests a white rectangle where the barcode will go, then include it in your image. Almost every print service is willing to create the barcode from your ISBN, and place the barcode image into your PDF during post-processing. Most of them even demand that they do it themselves. Do-it-yourself barcodes are incompatible with the following instructions.</p>
+<p><b>DISCLAIMER:</b> This documentation, and its accompanying software, is offered AS-IS, WITHOUT WARRANTY EXPRESS OR IMPLIED. USE ONLY AT YOUR OWN RISK. The author is an amateur who does not profess expertise in these matters. The best I can say is, "It works for me."</p>
+
+<h3 id="h13.1">13.1. Begin With PNG</h3>
+<div class="d3" id="12.1">
+<p class="noindent">Create your artwork, including all text (but not barcode or barcode text) using whatever means you have. How you do it is not relevant. To follow these instructions, you must provide the artwork as a flattened (no transparency) PNG format image, at correct size (including bleed area) and resolution (dpi).</p>
+<p style="margin-top:8px"><b>Example:</b> Suppose your book is 5.5" x 8.5" softcover, a typical size for American fiction. Based on its page count and paper, you are told that the spine width must be 0.62". The required bleed width, on all four sides, must be 0.125".</p>
+<p>Then, the image is 0.125 + 5.5 + 0.62 + 5.5 + 0.125 = 11.87in wide.</p>
+<p>The image is 0.125 + 8.5 + 0.125 = 8.75in high.</p>
+<p>At 300dpi resolution (a typical value) the image must be 11.87 x 300 = 3561 pixels wide, and 8.75 x 300 = 2625 pixels high. In case of fractional pixels, round upward. The exact pixel count is important.</p>
+<p style="margin-top:8px"><img src="html-resources/example-adobergb.png" class="floatright" width="445" height="328" alt="example rgb image"/> It is best to use the AdobeRGB1998 color workspace, or equivalent. But you can also use sRGB, or equivalent, and in many cases you will not notice much difference. It is helpful to attach (embed) the workspace color profile in your PNG image, especially if it is something other than AdobeRGB1998 or sRGB. Note that the workspace is NOT the color profile of your monitor (if you have it). If you do not attach (embed) the workspace color profile, then remember whether you were using AdobeRGB1998 or sRGB. If you make a mistake here, it is not fatal. It merely means that some colors (particularly bright greens and blue-greens) will print somewhat brighter or duller than you were expecting.</p>
+<p>When done, export it as a flattened PNG.</p>
+<p>If you are provided with an image other than PNG, you have to convert it to PNG. No alternative. It is easy enough to use GIMP to convert most image formats. If you have a PDF (which is not already in the required format), GIMP can probably open it as an image. Be sure you import it with the correct resolution. Again, the pixel width and height are important.</p>
+<p><b>Cover Text:</b> These instructions assume that your cover text is rasterized, and is part of the image rather than vector text. In many cases your graphics program has enough text capability to do what you need.</p>
+<p>If you wish to use TeX to typeset the cover text, do it this way: Use TeX to create one or more PDFs of the cover text, without images. You can create several blocks of text at different pages sizes, if you wish. Open your background artwork in GIMP. Add a new transparent layer above it. Open a text PDF in GIMP. Choose resolution 300dpi, full antialiasing, grayscale or color. The opened text is now a raster image. Copy it, and paste it atop the transparent layer. Anchor it. Use Color: Color to Alpha: white to alpha filter. That removes the white area from the PDF image. Finally, move the text to where it should go. You can rotate the text 90 degrees, but do not resize it! If you would rather the text be at a different size, then either change it in TeX, or use a different resolution when you open the PDF in GIMP. Note that even when you open the PDF at a different resolution, it will still be at 300dpi when you place it over the 300dpi background image; but its size will change.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h13.2">13.2. Get Some Software</h3>
+<div class="d3" id="12.2">
+<p class="noindent">Get the 238% total ink limit color profile from <a href="http://www.newselfpublishing.com/TotalInkLimit.html" rel="external" target="new">Aaron Shepard</a>. This does the magic of ensuring that you comply with the 240% ink limit (the profile provides a little headroom, which seems necessary). It can also be used for softproofing, if you know how to do that. This is not the only possible profile, but it seems to me that it is the best of several available.</p>
+<p>You might (or might not) need the <a href="https://www.adobe.com/support/downloads/iccprofiles/iccprofiles_win.html" rel="external" target="new">Adobe icc profiles</a> (for end users). This link works for Windows or Linux (even though it says "for Windows"). I am told that there is a different link for Mac, but I don't have a Mac.</p>
+<p>Get GraphicsMagick or ImageMagick. On Linux, you can install it via your system package manager. On Windows, get GraphicsMagick Q16 binaries for your system (32 or 64 bit) from <a href="https://sourceforge.net/projects/graphicsmagick/files/graphicsmagick-binaries/" rel="external" target="new">SourceForge</a>. I am told that versions for Mac are available via homebrew and macports, but again, I do not have a Mac, so I cannot check that. Or, get ImageMagick Q16 for various platforms from <a href="https://www.imagemagick.org/script/download.php" rel="external" target="new">here</a>.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h13.3">13.3. Convert Your Image to CMYK at 240% (or less) Ink Limit</h3>
+<div class="d3" id="12.3">
+<p class="noindent"><img src="html-resources/example-cmyk238.png" class="floatright" width="445" height="328" alt="example cmyk238 image, back to rgb"/> At right, you can see an emulation of cover artwork, softproofed to CMYK at 238% ink limit. It is not the CMYK file itself, but an RGB image that is supposed to help you visualize what happens during conversion. You will notice that the colors are less intense, because the original image contained colors that didn't fit the gamut of the printing process. Colors don't always change; I could have planned ahead, and selected from a palette of colors that fit within the gamut.</p>
+<p><b>Get ready:</b> Make a copy of the above 238% ink limit color profile, and re-name the copy as "238.icc".
+<p>I will call your original PNG image "yourimage.png". Put this image, the 238.icc file, and (if necessary) the AdobeRGB1998.icc file in a single working folder.</p>
+<p>I will also assume that the image resolution is 300dpi. If it is something else, then modify 300 to the other number, when you see it below.</p>
+<p style="margin-top:16px"><b>Step 1:</b> Open a Terminal (Command Prompt) and navigate to that folder.</p>
+<p>In the following commands, the initial "gm" calls GraphicsMagick (same code Linux and Windows). If you prefer ImageMagick, then eliminate the initial "gm" on Linux, or change the "gm" to "magick" on Windows.</p>
+<div class="codeblock">
+<p><code>gm convert yourimage.png embedded.icc</code></p>
+</div>
+<p>The above command may return the message "No color profile available" and generate a zero-byte embedded.icc file. Not a problem. Discard the zero-byte file. But if it generates a non-zero embedded.icc file, keep it.</p>
+<p style="margin-top:16px"><b>Step 2:</b> Next (note the file extensions):</p>
+<div class="codeblock">
+<p><code>gm convert -strip yourimage.png yourimage-stripped.tif</code></p>
+</div>
+<p style="margin-top:16px"><b>Step 3:</b> At this point, there are three possibilities:</p>
+<p><b>(a)</b> You have a non-zero embedded.icc file. In this case:</p>
+<div class="codeblock">
+<p><code>gm convert -profile embedded.icc -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
+</div>
+<p><b>(b)</b> No embedded.icc, but you know that the artwork was create using AdobeRGB1998 workspace, or equivalent. Then:</p>
+<div class="codeblock">
+<p><code>gm convert -profile AdobeRGB1998.icc -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
+</div>
+<p><b>(c)</b> Neither of the above. The image is probably sRGB (default), so:</p>
+<div class="codeblock">
+<p><code>gm convert -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
+</div>
+<p style="margin-top:16px"><b>Step 4:</b> Now, regardless of which possibility you used above:</p>
+<div class="codeblock">
+<p><code>gm mogrify -strip yourimage-temp.tif</code></p>
+</div>
+<p style="margin-top:16px"><b>Step 5:</b> And finally:</p>
+<div class="codeblock">
+<p><code>gm convert -units PixelsPerInch -density 300 -quality 100 yourimage-temp.tif yourimage-cmyk240.jpg</code></p>
+</div>
+<p style="margin-top:16px"><b>Step 6:</b> Now verify your work:</p>
+<div class="codeblock">
+<p><code>gm identify -verbose yourimage-cmyk240.jpg</code></p>
+</div>
+<p>The report should show that the image is CMYK, that it is at 300 pixels/inch, and that there is NO entry for "Profile-color". It will not have anything to say about ink limit, or SWOP.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h13.4">13.4. Convert your CMYK Image to PDF/X.</h3>
+<div class="d3" id="12.4">
+<p class="noindent">Up to now, you did not need TeX. Now you do. Be sure that you have a working TeX installation, with the <em>novel</em> document class package.</p>
+<p>In folder (your TeX root)/doc/lualatex/novel/extras you will find file "novel-cover-template.tex". Place a copy in the same working folder as your image, and modify it as needed.</p>
+<p><code>\SetMediaSize</code> refers to the full size of the image, with units (usually in). This includes the bleed box. For the example image, <code>\SetMediaSize{11.87in}{8.75in}</code>.</p>
+<p><code>\SetTrimSize</code> refers to the trimmed image, without bleed. For the example image, <code>\SetTrimSize{11.62in}{8.5in}</code>.</p>
+<p><code>\SetPDFX[CGATSTR001]{X-1a:2001}</code> will get you "Us Web Coated SWOP v2" output intent (most common the USA), and PDF/X-1a:2001 compliance. The Output Intent *.icc color profile will NOT be embedded, because this is almost always the way that print services want it. The PDF contains a code identifying the intent, so there is no need to embed the color profile (and disadvantages to embedding it). In the unlikely event that they demand the Output Intent color profile embedded, put an asterisk on the command.</p>
+<p>For compliance you need to use <code>\SetTitle</code>. The title for this file might not be the title of your book, because this file isn't your book. Ask you print service what they want. Same with <code>\SetAuthor</code>.</p>
+<p>You can use <code>\SetApplication</code> and <code>\SetProducer</code> to change internal identifiers. Don't use these unless you have a reason.</p>
+<p><code>\SetCoverImage</code> is self-explanatory. Must have file extension jpg, jpeg, JPG, or JPEG. Must be CMYK. Note that TeX cannot verify whether the image is in correct color space. It will compile, even if the image is wrong. Beware!</p>
+<p>Do not attempt to write anything between <code>\begin{document}</code> and <code>\end{document}</code>. If you erroneously put some text there, the document will probably compile, and it may even be a valid PDF/X file. However, the resulting text color will almost surely be wrong. If so, the problem will be detected when you submit your file (wrong ink limit or color space). However, this is not a fundamental limit. It is possible to place TeX text over the image, but this documentation (as of version 1.32) does not show you how to do that.</p>
+<p>Compiling may take a little longer than expected. If your TeX system opens a PDF viewer automatically, the image might be missing (or partial) until a few seconds after the viewer opens. Be patient. The file size is large.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="h13.5">13.5. Final Check</h3>
+<div class="d3" id="12.5">
+<p class="noindent">Open the PDF in Adobe Reader, which does a trick that no other free software will do, to my knowledge. If your platform does not have Adobe Reader, then find a friend who has it. May be a different platform.</p>
+<p>In Adobe Reader, go to Edit, Preferences, Documents. Check "Save As optimizes for fast web view." Then go to Edit, Preferences, Page Display. Check "Show art, trim, and bleed boxes." Then OK.</p>
+<p>Open your PDF. You should see a light green box, just inside the image boundary. This shows the Trim Area. This box does not print; it is only for visualization. Go to File, Properties, Fonts. There should be no fonts listed.</p>
+<p>Then, "Save As" the same file name (or another one, if you prefer). This will optimize the file. You probably do not need to do that, but it does not hurt, and a few services expect it.</p>
+<p>There will always be some difference between color as viewed on your monitor, and color as printed. This is due to the difference between emitted light (your monitor) and reflected light (print). In professional use, the monitor will be calibrated, and operated at a specific screen brightness. The print will be viewed under lighting with a specific color temperature and illumination. Your own colors are not that critical, are they? If you have a calibrated monitor, and view the PDF and images in color-managed software, then what you see on your computer will be reasonably close to what prints. If your monitor is not calibrated, or you are not using color-managed software, then the printed cover may have its greens a bit more colorful than you were expecting. That doesn't mean there will be a greenish cast. It merely means that things such as spring leaves and shamrocks will be a bit greener (in print) than you expected.</p>
+<p><b>Remember the Disclaimer!</b> Your PDF file should now be ready for submission. Only "should," not "is," because this documentation and its accompanying software comes without warranty. Submit at your own risk!</p>
+<p>All I can say is that it "works for me." Screenshot from Adobe Acrobat Pro:</p>
+<p class="centerimg"><img src="html-resources/verified238.png" width="700" height="446" alt="works for me"/></p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end page13 -->
+<!-- ************************************************************ -->
+
+<!-- ************************************************************ -->
+<div id="pageA" class="page">
+
+
+<h2 id="hA">Appendix A. Book Terminology and Manufacturing</h2>
+<div class="d2" id="dA">
+<p class="noindent">Most authors in P.O.D. use an ordinary word processor, particularly MS Word. For that reason, many print services, and most online user forums, refer to the terminology and settings of MS Word, rather than to the meanings in traditional book publishing. In the case of images, Photoshop settings are often described.</p>
+<p>Since you are neither using MS Word nor Photoshop, you must understand the terminology of printed book design. Then, you can apply that knowledge to the physical layout and internal design of your book, using <i>novel</i> document class.</p>
+
+<h3 id="hA.1">A.1 Sheet, Page, Leaf</h3>
+<div class="d3" id="dA.1">
+<p class="noindent">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>
+</div><!-- end class="d3" -->
+
+<h3 id="hA.2">A.2 Folio, Spine</h3>
+<div class="d3" id="dA.2">
+<p class="noindent">Imagine a single sheet of 8.5"Wx11"H paper. It has two pages, since you can print on both sides (even if one is empty).</p>
+<p>If you fold that sheet in half across its width, it is still one sheet. But now you have a <b>folio</b>, consisting of two leaves of size 5.5"Wx8.5"H. Each leaf has two pages, so you now have four pages. The fold is at the <b>spine</b>.</p>
+<p>Caution: The term "folio" has several different meanings, even in the narrow field of book publishing. It may refer to folded paper, as mentioned above. Or it may refer to a particular sheet size of paper ("foolscap"). Or, it may simply refer to the number printed on a page. This last use of "folio" is discussed in the context of headers and footers.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hA.3">A.3 Signature, Imposition</h3>
+<div class="d3" id="dA.3">
+<p class="noindent"><img class="floatright" src="html-resources/signature.png" width="133" height="102" alt="signature"/> When a book is commercially manufactured, folios are nested to form <b>signatures</b>. The number of folios in a signature is typically 6 to 16 (that would be 24 to 64 pages). If you were hand-making a single book at home, you might use only one folio per signature.</p>
+<p>Now, think about how those pages must be ordered. Suppose a book contains a single signature of 4 folios. The outermost folio is printed with pages 1 and 16 on one side (before folding), and pages 2 and 15 on its other side. The next nested folio has pages 3/14 and 4/13. Nested inside is 5/12 and 6/11. Innermost is 7/10 and 8/9.</p>
+<p>Re-arranging the page order is part of the <b>imposition</b> process. The process may involve tweaking the position of each page slightly, to account for offset due to paper thickness when the folios are grouped into signatures. If numerous folios are printed on a larger sheet of paper before cutting, the process may involve rotating folios so that they waste less paper.</p>
+<p>Your home printer software can probably do imposition for a single-folio design (four pages). Anything beyond that is left to professional software. You don't need to do it. The print service does it for you, automatically.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hA.4">A.4 Perfect Binding</h3>
+<div class="d3" id="dA.4">
+<p class="noindent"><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>.
+<p>In Perfect Binding, the signatures are clamped together, and the folded area is removed by a cutting machine. Then there are no longer any folios, just individual leaves.</p>
+<p>The leaves are glued together at the spine, possibly with reinforcement. Note that the glue is not merely at the edge of the leaves; it penetrates the paper slightly, for better strength. Finally, the cover is attached.</p>
+<p>The Perfect Binding method is inexpensive, and is more than adequate for a book that will not receive rough handling. Whether using P.O.D. or a major mass-quantity publisher, most softcover books have been made this way for a long time. Unless you know that your book will be acquired by libraries for addition to their long-term literary collection, there is little reason to have your book manufactured by any other process. The possible exception would be books for small children, which receive rough handling under all circumstances.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hA.5">A.5 Library Binding</h3>
+<div class="d3" id="dA.5">
+<p class="noindent">Libraries rarely purchase Perfect Binding books (regardless of soft or hard cover) due to lack of durability in a library environment. The exceptions are popular books of no lasting literary value, and how-to books for evolving technologies. These may be obtained by libraries in the cheapest softcover version, because such books will be discarded long before they wear out.</p>
+<p>Unless you are sure that your book will be acquired by numerous libraries for long-term addition to their collections, there is little reason to produce a quality hardcover version. Not all P.O.D. services offer hardcover. If you do need a hardcover version, then be sure to carefully inquire regarding its manufacture, and preferably obtain a copy of someone else's book manufactured that way.</p>
+<p><img class="floatright" src="html-resources/smythsewn.png" width="177" height="141" alt="perfect binding"/> The best hardcovers, suitable for library use, are made using the <b>Smyth Sewing</b> process. A Smyth Sewn book has signatures of (typically) 12 or 16 folios. But instead of removing the creases after folding, each signature is sewn through its crease using strong thread, onto a durable spine material. The pages will remain attached, even with hard usage. If the spine material is sufficiently flexible, then the book will lie flat when opened.</p>
+<p>Be sure to ask about spine flexibility. The most flexible methods have a soft, curved spine, and are best suited to thick novels. There is also a variety that has a square (flat) spine, which will not quite lie flat when opened. Square-spine Smyth Sewn books seem to be the fashion for documenting intellectual property.</p>
+<p>If a major publisher is producing a book that is sure to be ordered by many libraries, due to its author's popularity or maybe a movie tie-in, then it is likely to be released as a Smyth Sewn hardcover. That's because the production method is affordable in quantity. But on a P.O.D. basis, it is a significant expense.</p>
+<p>Note that it is possible to retroactively add a hard cover to what was originally a Perfect Binding softcover book. Depending on the technology, the result may be more durable, or not. But it will still be nothing like a Smyth Sewn library binding, because that has to be done at original manufacture. If you want a couple of Smyth Sewn copies for private use (your good children inherit the ranch, the bad ones inherit your books) then there are businesses that can build them, at fabulous cost, from your original PDF (minus its ISBN). If you need to change the Trim Size or margins to accomodate the different technology, then <i>novel</i> can help you. See the \ReworkTrimSize and \ReworkMargins commands.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hA.6">A.6 Paper and Cover Materials</h3>
+<div class="d3" id="dA.6">
+<p class="noindent">The interior paper may be white or "creme" (off-white). White paper is generally used for nonfiction, and must be used if there are interior color images. Creme paper is generally used for fiction. The idea is that white paper creates an air of authority, whereas creme paper is more comfortable for lengthy reading. I agree. I recently read a novel that was (mis-) printed on white paper, and it was hard to read in a bright area. So, for your novel, choose creme paper.</p>
+<p>The cover of a Perfect-Binding softcover book may be produced with a glossy or a matte finish. The fashion is to use glossy for nonfiction, matte for fiction. Again, the idea is authority versus comfort. But you may choose what you wish. "Instant Best-Seller" paperbacks mass-market publishers often have an embossed teture, and maybe even metal foil. In the print-on-demand market, forget it. Don't even think about it.</p>
+<p>If you do request a hardcover edition, then it may or may not have a dust jacket (costs extra). The general rule is that books for libraries have a dust jacket, which will be encased in plastic by the library. Books for documentation generally have no dust jacket, with the title and other info embossed in the cover material, for permanance.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end Appendix A -->
+<!-- ************************************************************ -->
+<div id="pageB" class="page">
+
+
+<h2 id="hB">Appendix B. Basic Six-Page Front Matter</h2>
+<div class="d2" id="dB">
+<p class="imgcentered"><img src="html-resources/sixpage-frontmatter.png" width="740" height="189" alt="Six-page front matter, with Epigraph on page v." title="Six-page front matter."/></p>
+<p class="noindent1">In many instances, six pages of front matter are all you need for fiction. This is often true for major publishers, not just self-published P.O.D. authors.</p>
+<p class="noindent1">You can use six pages, provided that:</p>
+<p class="overhang">• Your front matter does not contain material written by someone else (such as a Foreword), no matter how short. Exception: You may use an Epigraph.</p>
+<p class="overhang">• Your front matter contains at most one of the following, limited to a single page: Dedication, Epigraph, Table of Contents, Acknowledgements, Author's Note, Map.</p>
+<p class="noindent2">If both of the above points apply, then your front matter is organized as follows. Be sure that your document begins with the \frontmatter command, and that each page begins with \thispagestyle{empty} and ends with \clearpage.</p>
+
+<h3 id="hB.1">B.1 Half-Title to Copyright</h3>
+<div class="d3" id="dB.1">
+<p class="noindent">The first four pages (i - iv) are the same for nearly every book.</p>
+<p class="overhang"><b>Page i. Half-Title.</b></p>
+<p class="overhang"><b>Page ii. Blank.</b> Alternatively, if you wrote numerous books, you can provide a list of them. However, many print/distribution services will not allow such a list, unless they carry everyhing on the list.</p>
+<p class="overhang"><b>Page iii. Title Page.</b></p>
+<p class="overhang"><b>Page iv. Copyright Page.</b></p>
+</div><!-- end class="d3" -->
+
+<h3 id="hB.2">B.2 Post-Copyright</h3>
+<div class="d3" id="dB.2">
+<p class="noindent">After the copyright page, there may be some variation.</p>
+<p class="overhang"><b>Page v. Varies.</b> One of: Dedication, Epigraph, Table of Contents, Acknowledgements, Author's Note, Map. If you have none of them, then repeat the Half-Title.</p>
+<p>Don't be afraid to simply repeat the Half-Title. Even major publishers do it, when they have nothing else to say in front matter.</p>
+<p class="overhang"><b>Page vi. Blank.</b> Exception: If Page v does not have an Epigraph or Half-Title, you may place an Epigraph here, provided that it does not visually detract from the story that begins on the facing page.</p>
+<p class="noindent1"><b>The TeX code looks like this:</b></p>
+<div style="margin-left:32px">
+<p class="code"><code>
+\begin{document}<br/>
+\frontmatter % Sets page number to i.<br/>
+\thispagestyle{empty}<br/>
+% Half-Title Page.<br/>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+\null % Necessary for blank page.<br/>
+% Alternatively, List of Books.<br/>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+% Title Page.<br/>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+% Copyright Page.<br/>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+% Dedication or Epigraph or TOC or Acknowledgements or Author's Note or Map.<br/>
+% Alternatively, repeat the Half-Title.<br/>
+\clearpage<br/>
+\thispagestyle{empty}<br/>
+\null % Necessary for blank page.<br/>
+% Alternatively, Epigraph if it does not detract from facing page.<br/>
+\clearpage<br/>
+\mainmatter % Sets page number to 1 for following material.
+</code></p>
+</div>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end Appendix B -->
+<!-- ************************************************************ -->
+<div id="pageC" class="page">
+
+
+<h2 id="hC">Appendix C. Shopping for Fonts</h2>
+<div class="d2" id="dC">
+<p class="noindent1">Since the <i>novel</i> class uses only <i>LuaLaTeX</i> and <i>fontspec</i> with utf-8 encoding, you may use any Open Type or TrueType font, subject to licensing. You are not limited to TeX fonts.</p>
+<p>Many TeX fonts are only available in older Type 1 format (PostScript) or even as bitmap metafonts. <i>Do not use them.</i></p>
+<p>In some other cases, a TeX font package provides both the older format, and a newer Open Type (*.otf or *.ttf) format. The different formats will have different font names. Sometimes the difference is very slight. Carefully look at the font name for the Open Type format. Remember that most on-line discussions will refer to the older fonts, simply because they have been around longer. For example: <i>Linux Biolinum</i> is a sans-serif font available via TeX as a PostScript font. But <i>Linux Biolinum O</i> (note the O) is an Open Type font. If you need this font, then call for <i>Linux Biolinum O</i>, not simply <i>Linux Biolinum</i>.</p>
+<p><b>Important:</b> Do not attempt to load a font by the \RequirePackage or \usepackage commands. Instead, if you choose to use fonts other than the defaults, load them via the font setting commands described in this documentation. If you attempt to load a font the wrong way, you may get an error message.</p>
+
+<h3 id="hC.1">C.1 Licensing Issues</h3>
+<div class="d3" id="dC.1">
+<p class="noindent1">Presumably, you are writing your novel for commercial value, and do not intend to give anything away for free. For that reason, avoid any font licensed under the GPL (GNU Public License) unless it has the <em>font exception</em> clause. Some TeX fonts, and some non-TeX free fonts, are licensed under GPL. Be careful!</p>
+<p>Beware of fonts "free for personal use" from download sites. Your commercial application is not "personal use." Of course, if you like the font, you may purchase its commercial license.</p>
+<p>Also beware of fonts generically labeled as "freeware" with no particular designer name. If you don't know who created the font, then how do you know that it can be given away for free? Even if there is a designer name, some of them had second thoughts about "freeware." They intended the fonts to be free only if you give your own work away for free. But they didn't mention it. Maybe they have no legal recourse, but you don't want them making anonymous negative reviews of your book.</p>
+<p>You have numerous fonts already installed in your operating system, and perhaps others that came bundled with a particular application. If you intend to use those fonts, carefully read their licenses. It is often the case that fonts bundled with an application may <em>only</em> be used for documents created within, or processed by, that application. Or, the fonts may be OK to use for printing directly by your own home printer, but not for embedding in a PDF that will go to a commercial printer.</p>
+<p>Although it does not pertain to TeX, another issue can arise if you later publish an ebook version. Fonts licensed for printing are often not licensed for an ebook. Indeed, the ebook distributor may ban them.</p>
+<p>Always look for a Copyright notice, which can be identified with a particular person or organization. Copyright is good! It means that someone is claiming authorship of the font software. Only the Copyright owner has the right to give the font away for free, or license it to you after payment (often through an intermediary).</p>
+<p>If you prefer free fonts, the most widely accepted license is the <em>SIL Open Font License</em>. This allows you to use the font for commercial purposes, embed it in PDF, modify it to suit your needs (if you change the font name), and even re-distribute the modifications. The recommended default <i>Libertinus</i> bears this font license.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hC.2">C.2 Technical Issues</h3>
+<div class="d3" id="dC.2">
+<p class="noindent1">Many fonts have technical errors, even among professional fonts. Some of the errors are so minor that they are not worth fixing.</p>
+<p>However, beware of fonts based on traced artwork. The late 1990s had an explosion of amateur dingbat and decorative fonts produced this way, by scanning images from old books and digitizing the scan. The resulting vector glyphs rarely meet standards, and often are quite awful. The problem is that when a commercial printer renders your PDF to print, the printer's software is very different from what you have on your home computer. A technically erroneous glyph might look OK at home, but be rejected commercially.</p>
+<p>If you have the knowledge, you can open a font in font editor software (such as <i>FontForge</i>) and ask it for validation. Missing extrema are rarely a problem, even if a lot of them are missing. Self-intersecting glyphs are not a problem if the the glyph is composed of two elements stuck together, such as Ç composed of C with separate cedilla. However, a self-intersecting glyph may be a problem if its lines criss-cross each other. Open paths, and outer paths drawn the wrong way, are often a problem. If the errors are confined to glyphs that you will not be using, then it can pass.</p>
+</div><!-- end class="c3" -->
+
+<h3 id="hC.3">C.3 Appearance Issues</h3>
+<div class="d3" id="dC.3">
+<p class="noindent1">There are general expectations for book fonts, in terms of character sizes and shapes, and weights. Many of the widely-used TeX fonts, including Latin Modern, are unacceptable in fiction for this reason. Times New Roman is not quite acceptable for fiction; but it is often mis-used by amateurs with a word processor.</p>
+<p>The best way to assess a font is to print it to paper. Computer screens rarely show details, except at large magnification. Depending on whom you ask for an opinion, fiction is most easily read when there are about 60 to 66 characters (including spaces) per line. To evaluate a font for the main text, print out some paragraphs about 4" to 4.25" wide, and scale the font's point size so that you get an average number of characters per line in that range. Be sure to do that: Adobe Garamond Pro at 12pt, Libertinus Serif at 11.4pt, and Libre Caslon Text at 9.6pt (!) provide about the same number of characters per line of text. At the proper point size, some fonts will look too dark, and others will look too light.</p>
+<p>Things to look for: (1) Are the lowercase letters too tall? If they are, then it is hard for readers in many Western languages to find where sentences start, by looking for capital letters. Also, there is less white space between lines, which makes the text appear dense and harder to read. (2) Is the shape of the characters so natural that you don't notice them? That's good! It is your writing, not the font, that is to be noticed. (3) Remember that some fonts are designed for use at large size, in posters; such fonts tend to look mechanical in fiction. Other fonts are designed for computer screens; the letters will be too widely-spaced in fiction. Nearly all modern fonts have decent kerning and important ligatures, so that's not usually a decisive factor.</p>
+<p>The prevailing rule: If you notice the font, it's wrong.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!--end Appendix C -->
+<!-- ************************************************************ -->
+<div id="pageD" class="page">
+
+
+<h2 id="hD">Appendix D. The 240% Ink Limit (TAC) Color Gamut</h2>
+<div class="d2" id="dD">
+<p class="noindent">The <i>gamut</i>, or range of available colors, is not the same for your computer monitor as it is for a printer. Obviously that depends on the technology of your monitor, and the technology of the printer. By and large, a good CMYK commercial printer can provide blue-greens that your monitor cannot accurately display. And, your monitor can display purple-violet colors that cannot accurately be printed. The monitor's advantage in purple-violet largely disappears for inexpensive LCD flat panels, which is what most of us have.</p>
+<p>However, the full CMYK gamut is only realized when each ink channel can act independently. That is, each spot on the paper must be able to retain as much as a full dose of each ink. At 0%-100% ink per channel, a spot of paper would have to hold up to 400% ink. For a variety of reasons, most printing technologies cannot apply that much ink. Or rather, if they did try to apply that much, the resulting print might smear, fail to dry, lift off, or soak through to the opposite side of the paper. Subsequent lamination might fail to adhere.</p>
+<p>Quality books and magazines, using coated paper, can typically hold 300%-360% ink (the technical name is TAC, Total Area Coverage). However, the color cover of a print-on-demand book might be produced by a method that holds less ink. The operative word is "might." Common P.O.D. printers are industrial-strength inkjet machines, capable of very high quality when used with suitable paper. However, the print job will be sent out to any number of different print shops, who may use other technology. Therefore, P.O.D. services may require that the color gamut be limited to those printable by a "lowest common denominator" process. One widely-used "lowest common denominator" is 240% ink limit.</p>
+<p>At 240% ink limit, brightly colored areas are generally unaffected. Deep, rich colors cannot be produced, since they would require too much ink. You will be required to provide an image with colors that fit within the ink limit, or the P.O.D. service may quietly do it for you.</p>
+<p>Print simulation, or <i>softproofing</i>, is a method of viewing an image on your computer, "as if it were printed" to some standard. GIMP can do this, as long as you provide the necessary *.icc color profile for the printer. Then you can decide whether or not the result is acceptable. The actual CMYK image is produced by the methods described in <a href="#h13">Chapter 13</a>, above.</p>
+
+<h3 id="hD.1">D.1. Example: Bright Colors Preserved</h3>
+<div class="d3" id="dD.1">
+<p>Below is a painting from the Middle Ages (photo by me) on display at the San Francisco Legion of Honor museum. The photo, at left, is as originally seen on a computer monitor. At right, the image is softproofed using the SWOP 238% ink limit color profile mentioned in Chapter 13. You can see that the brightest blue is about the same, The brightest reds and greens are almost the same. But the images differ in the dark areas. Especially look at the lion's leg (lower left corner) and the writer's hair and beard (right foreground).</p>
+<p class="centerimg"><img src="html-resources/medieval-painting.jpg" width="707" height="321" title="Medieval Painting, monitor and softproof" alt="Medieval Painting, monitor and softproof"/></p>
+</div><!-- end class="d3" -->
+
+<h3 id="hD.2">D.2. Example: Natural Light Preserved</h3>
+<div class="d3" id="dD.2">
+<p>Below is a photograph taken on a dull day along the California coast, near Bixby Creek. Whether in monitor color or softproofed, the results are almost exactly the same. With the exception of some tiny shadowed areas in the foreground (hard to notice), just about everything in the picture can print with not more than 238% ink.</p>
+<p class="centerimg"><img src="html-resources/bixby-compare.jpg" width="738" height="340" title="Medieval Painting, monitor and softproof" alt="Bixby Creek, monitor and softproof"/></p>
+</div><!-- end class="d3" -->
+
+<h3 id="hD.3">D.3. Example: Dark, Rich Colors Lost</h3>
+<div class="d3" id="dD.3">
+<p>The biggest problem occurs when the artwork is naturally dark. That might occur in night scenes, or with dark-skinned humans. For copyright reasons I cannot show you the original image by Hyacinthe Rigaud, on display in a European museum. But if it is reduced to a map of 256 colors (as with GIF images), you can see the effect. The original, at left, has many rich browns and reddish-browns. When softproofed, those become nearly gray. The original image still is attractive when softproofed, but is colors might be surprising if you were unaware of the ink limit effect.</p>
+<p class="centerimg"><img src="html-resources/colormap-brown.jpg" width="674" height="305" title="Medieval Painting, monitor and softproof" alt="Dark color map, monitor and softproof"/></p>
+<p>You might wonder why the ink limit caused rich browns to appear <i>darker</i>. That's because a blend of yellow, magenta, and black (with too much ink) was changed to one with much less yellow and magenta, but more black (and not too much ink).</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end Appendix D -->
+<!-- ************************************************************ -->
+<div id="pageE" class="page">
+
+
+<h2 id="hE">Appendix E. Command Summary by Topic</h2>
+<div class="d2" id="dE">
+<p class="noindent">Here is a list of commands created by <i>novel</i> class, plus a few of the many LaTeX commands that are likely to be most useful in fiction. Commands are sorted according to where they would be used.</p>
+<p>Do not let the many Preamble settings intimidate you. All of them are pre-configured with default values that were carefully chosen for use in fiction. You may not need to write many settings.</p>
+<p>Since <i>novel</i> is specifically intended for fiction, such as novels and collections of short stories, it does not implement many of the commands familiar to academic writers. In some cases, where such commands would interfere with <i>novel</i> commands, the academic commands have been entirely disabled.</p>
+<p>LaTeX has many other commands. Only the most popular ones are mentioned here. If you know something that is not on the list, you can try it.</p>
+
+<h3 id="hE.1">E.1 Command Summary: Preamble</h3>
+<div class="d3" id="dE.1">
+
+<h4 id="hE.1.1">E.1.1 Class Options</h4>
+<div class="d4" id="dE.1.1">
+<p class="noindent2">Unlike other document classes, <i>novel</i> does not use class options to set layout dimensions or font point size.</p>
+<p class="overhang"><code>draft</code> Marks horizontal overflow. Enables some other options.</p>
+<p class="overhang"><code>graytext</code> Allows text in gray, not just pure K black.</p>
+<p class="overhang"><code>shademargins</code> Only in draft. Gray background in page margins.</p>
+<p class="overhang"><code>cropmarks</code> Adds basic cropmarks. Do not use unless required!</p>
+<p class="overhang"><code>cropview</code> Only in draft. Removes excess area surrounding TrimBox.</p>
+<p class="overhang"><code>closecrop</code> Only in draft. Crops to just clear the live text area.</p>
+<p class="overhang"><code>xml</code> Exports XMP Metadata as an xml file.</p>
+<p class="overhang"><code>coverart</code> For use with cover artwork only.</p>
+<p class="overhang"><code>unblock</code> Allows some normally-banned packages to load.</p>
+</div>
+
+<h4 id="hE.1.2">E.1.2 Metadata (File Data)</h4>
+<div class="d4" id="dE.1.2">
+<p class="noindent2">Metadata can be seen by PDF viewers. Some of it can only be seen by professional software. The data identifies your file and describes some of its properties. In the case of PDF/X, choosing a compliance standard will also affect how LaTeX compiles your document. You may <em>not</em> apply styling to metadata!</p>
+<p class="overhang"><code>\SetTitle{<em>title of your book</em>}</code> Default: empty. The value of this setting is available as \thetitle everywhere.</p>
+<p class="overhang"><code>\SetSubtitle{<em>subtitle of your book, if any</em>}</code> Default: empty. The value of this setting is available as \thesubtitle everywhere.</p>
+<p class="overhang"><code>\SetAuthor{<em>author of your book</em>}</code> Default: empty. The value of this setting is available as \theauthor everywhere.</p>
+<p class="overhang"><code>\SetPDFX[<em>embed-icc or no-embed</em>]{<em>compliance standard</em>}{<em>output intent</em>}</code> Default: off.</p>
+<p class="overhang"><code>\SetApplication{<em>software that created the source document</em>}</code> Advanced. Default: an identifying string, automatically inserted by TeX.</p>
+<p class="overhang"><code>\SetProducer{<em>software that compiled the PDF</em>}</code> Avanced. Default: an identifying string, automatically inserted by TeX.</p>
+<p class="overhang"><code>\straightquote</code> and <code>\straightdblquote</code> Inserts the character in text string.</p>
+</div>
+
+<h4 id="hE.1.3">E.1.3 Layout</h4>
+<div class="d4" id="dE.1.3">
+<p class="noindent2">The <i>novel</i> class provides improved alternatives to papersize, offset, and other layout commands used by other document classes. These commands have been carefully chosen to do what you need to do.<p>
+<p class="overhang"><code>\SetTrimSize{width}{height}</code> Default: {5.5in}{8.5in}. The finished size of your book.</p>
+<p class="overhang"><code>\SetMargins{top}{outside}{bottom}{inside}</code> Default: {0.5in}{0.5in}{0.5in}{0.75in}</p>
+<p class="overhang"><code>\SetHeadFootStyle{number}</code> Default: 1 (header, but no footer)</p>
+<p class="overhang"><code>\SetHeadJump{number}</code> Default: 1.5. Gap between header and main text.</p>
+<p class="overhang"><code>\SetFootJump{number}</code> Default: 1.5. Gap between main text and footer.</p>
+<p class="overhang"><code>\SetFontSize{<em>size</em>}</code> Default: Varies. Usually 11.4pt</p>
+<p class="overhang"><code>\SetLinesPerPage{<em>integer</em>}</code> Default: Calculated automatically from other layout settings.</p>
+<p class="overhang"><code>\SetMediaSize[alignment]{width}{height}</code> Advanced. Default: Identical to Trim Size.</p>
+<p class="overhang"><code>\SetCropmarkGap{<em>size of gap</em>}</code> Advanced. Default: 0.125in if cropmarks option.</p>
+<p class="overhang"><code>\ReworkTrimSize{width}{height}</code> Advanced. For emergency re-layout.</p>
+<p class="overhang"><code>\ReworkMargins{top}{outside}{bottom}{inside}</code> Advanced. For emergency re-layout.</p>
+</div>
+
+<h4 id="hE.1.4">E.1.4 Specifying Fonts</h4>
+<div class="d4" id="dE.1.4">
+<p class="noindent2">In <i>novel</i>, you do not load a font using \usepackage{<em>fontname</em>}.</p>
+<p class="overhang"><code>\SetParentFont[features]{font family}</code> Default: Libertinus Serif. Alternate: Linux Libertine O. Last Choice: Latin Modern Roman.</p>
+<p class="overhang"><code>\SetHeadFont[features]{font family}</code> Default: [Numbers=Lining,Scale=0.92]{<em>based on parent font</em>}.</p>
+<p class="overhang"><code>\SetChapterFont[features]{font family}</code> Default: [Numbers=Lining,Scale=1.6]{<em>based on parent font</em>}</p>
+<p class="overhang"><code>\SetSubchFont[features]{font family}</code> Default: [Numbers=Lining,Scale=1.2]{<em>based on parent font</em>}</p>
+<p class="overhang"><code>\SetDecoFont[features]{font}</code> Advanced. Default: NovelDeco.</p>
+<p class="overhang"><code>\SetSansFont[features]{font family}</code> Advanced. Default: Libertinus Sans. Alternate: Linux Biolinum O. Last Choice: Latin Modern Sans.</p>
+<p class="overhang"><code>\SetMonoFont[features]{font family}</code> Advanced. Default: Libertinus Mono. Alternate: Linux Libertine Mono O. Last Choice: Latin Modern Mono.</p>
+<p class="overhang"><code>\NewFontFamily\<i>yourfontcommand</i>[features]{font family}</code>. Advanced. Uses <i>fontspec</i> notation.</p>
+<p class="overhang2">\NewFontFace\<i>yourfontcommand</i>[features]{font}. Advanced. Uses <i>fontspec</i> notation.</p>
+</div>
+
+<h4 id="hE.1.5">E.1.5 Other Preamble Configuration</h4>
+<div class="d4" id="dE.1.5">
+<p class="noindent2">These commands perform miscellaneous setup.</p>
+<p class="overhang"><code>\SetEmblems{<em>verso</em>}{<em>recto</em>}</code> Advanced. Default: empty. Applies decoration near page number, only for selected header/footer styles.</p>
+<p class="overhang"><code>\SetPageNumberStyle{<em>code using \thepage</em>}</code> Advanced. Default: \thepage.</p>
+<p class="overhang"><code>\SetLooseHead{number}</code> Advanced. Default: 50. Adjusts header tracking.</p>
+<p class="overhang"><code>\SetChapterStart{<em>choice</em>}</code> Advanced. Default: footer (if present).</p>
+<p class="overhang"><code>\SetIndentAfterScenebreak</code> Advanced. Default: no indent after scenebreak.</p>
+<p class="overhang"><code>\SetMarkerStyle[real/fake]{asterisk/dagger/number}</code> Advanced. Default: [real][asterisk].</p>
+<p class="overhang"><code>\microtypesetup{<em>see microtype package docs</em>}</code> Advanced.<br/>Default: config=novel-microtype,stretch=20,shrink=20,final,tracking.</p>
+<p class="overhang"><code>\setmainlanguage{<em>language</em>}</code> Advanced. Default: english.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="hE.2">E.2 Command Summary: Document Body</h3>
+<div class="d3" id="dE.2">
+<p class="noindent">Note that standard font size commands, such as \small and \Large, are disabled.</p>
+
+<h4 id="hE.2.1">E.2.1 Book Divisions</h4>
+<div class="d4" id="dE.2.1">
+<p class="overhang"><code>\frontmatter</code> Page numbering (if shown) is lowercase roman.</p>
+<p class="overhang"><code>\mainmatter</code> Page numbering re-starts at 1, and is Arabic.</p>
+<p class="noindent">From version 1.40, \backmatter commands are ignored. Page numbering continues in Arbaic, as main matter. This is standard style. If your book must have back matter with different numbering, you must code it yourself.</p>
+</div>
+
+<h4 id="hE.2.2">E.2.2 Page Management</h4>
+<div class="d4" id="dE.2.2">
+<p class="overhang"><code>\thispagestyle{<em>choose</em>}</code> Whether header/footer appears, for current page.</p>
+<p class="overhang"><code>\SetRectoHeadText{<em>text</em>}</code> Content of recto heading (if present).</p>
+<p class="overhang"><code>\SetVersoHeadText{<em>text</em>}</code> Content of verso heading (if present).</p>
+<p class="overhang"><code>\enlargethispage{<em>usually -\nbs</em>}</code> Changes textblock height. Use with caution.</p>
+<p class="overhang"><code>\clearpage</code> Page break.</p>
+<p class="overhang"><code>\cleartorecto</code> Page break, if necessary inserts blank, continues recto.</p>
+<p class="overhang"><code>\clearpage\thispagestyle{empty}\null\clearpage</code> Blank page.
+<p class="overhang"><code>\cleartoend</code> Use only at end. Inserts 1 or 2 blank pages, so final page is blank verso.</p>
+</div>
+
+<h4 id="hE.2.3">E.2.3 Environments and Related Commands</h4>
+<div class="d4" id="dE.2.3">
+<p class="overhang"><code>legalese</code> (env.) Text alignment left (ragged right), hyphenation disabled.</p>
+<p class="overhang"><code>toc</code> (env.) Table of Contents.</p>
+<div style="margin-left:16px">
+<p class="overhang"><code>\tocitem[<em>number</em>]{<em>title</em>}{<em>page</em>}</code> Item in the toc environment.</p>
+</div>
+<p class="overhang"><code>ChapterStart</code> (env.) Creates an area of fixed height.</p>
+<div style="margin-left:16px">
+<p class="overhang"><code>\ChapterTitle{<em>text</em>}</code> Single line. May be used more than once.</p>
+<p class="overhang"><code>\ChapterSubtitle{<em>text</em>}</code> Single line. May be used more than once.</p>
+<p class="overhang"><code>\ChapterDeco[<em>scale</em>]{<em>deco code</em>}</code> Single line. May be used more than once.</p>
+</div>
+<p class="overhang"><code>parascale</code> (env.) Entire paragraph scaled, off-grid. Also see \charscale.</p>
+<p class="overhang"><code>adjustwidth</code> (env.) Block indenting, left and/or right.</p>
+</div>
+
+<h4 id="hE.2.4">E.2.4 Scene Breaks and First Lines</h4>
+<div class="d4" id="dE.2.4">
+<p class="noindent2">Also see Preamble command \SetIndentAfterScenebreak.</p>
+<p class="overhang"><code>\QuickChapter[<em>dash size</em>]{<em>chapter title</em>}</code> Chapters without page breaks.</p>
+<p class="overhang"><code>\scenebreak</code> Skips a line, gap is blank.</p>
+<p class="overhang"><code>\sceneline</code> Skips a line, gap has centered long dash.</p>
+<p class="overhang"><code>\scenestars</code> Skips a line, gap has asterisks.</p>
+<p class="overhang"><code>\FirstLine{<em>text</em>}</code> First line of paragraph in small caps.</p>
+</div>
+
+<h4 id="hE.2.5">E.2.5 Inline Text Effects</h4>
+<div class="d4" id="dE.2.5">
+<p class="noindent2">Note that standard LaTeX font size commands, such as <code>\small</code> and <code>\Large</code>, have no effect.</p>
+<p class="overhang"><code>\charscale[<em>scale,x,y</em>]{<em>text</em>}</code> Scales and moves text. Single line. See also \parascale environment.</p>
+<p class="overhang"><code>{\somefontcommand <em>text</em>}</code> Applies font defined by \somefontcommand to the included text.</p>
+<p class="overhang"><code>\forceindent</code> When \indent fails. May be used multiple times.</p>
+<p class="overhang"><code>\backindent</code> When \noindent fails. May be used multiple times.</p>
+<p class="overhang"><code>\hangindent{<em>text</em>}</code> Place text to the left of the command insertion point.</p>
+<p class="overhang"><code>\acronym{<em>text</em>}</code> Requires NovelDeco font. Caps become "medium" caps.<p>
+<p class="overhang"><code>\decoglyph{<em>code</em>}</code> Places decoration from the decofont, by code.</p>
+<p class="overhang"><code>\squeeze{<em>text</em>}</code> Horizontally shrinks text 1%.</p>
+<p class="overhang"><code>\crush{<em>text</em>}</code> Horizontally shrinks text 2%.</p>
+<p class="overhang"><code>\begingroup\color[<em>gray</em>]{<em>name or code</em>}\endgroup</code> Only when graytext option.</p>
+<p class="overhang"><code>\textcolor[<em>gray</em>]{<em>name or code</em>}{<em>text</em>}</code> Only when graytext option.</p>
+<p class="overhang"><code>\memo{<em>text</em>}</code> Ignores its argument. Does not ignore following.</p>
+<p class="overhang"><code>\nfs</code> (Length) Normal font size.</p>
+<p class="overhang"><code>\nbs</code> (Length) Normal baseline skip.</p>
+<p class="overhang"><code>\textit{<em>text</em>}, \emph{<em>text</em>}, \itshape{<em>text</em>}</code> Italics.</p>
+<p class="overhang"><code>\textsc{<em>text</em>}, \smcp{<em>text</em>}</code> Lowercase to small caps. Not faked.</p>
+<p class="overhang"><code>\allsmcp{<em>text</em>}</code> Uppercase and lowercase to small caps. Not faked.</p>
+<p class="overhang"><code>\realmarker, \fakemarker</code> Changes superscripts/subscripts real or fake.</p>
+<p class="overhang"><code>\sups{<em>text</em>}</code> Superscripts.</p>
+<p class="overhang"><code>\subs{<em>text</em>}</code> Subscripts (scientific inferiors).</p>
+<p class="overhang"><code>\null</code> Inserts a blank line between paragraphs.</p>
+<p class="overhang"><code>\mbox{<em>text</em>}</code> Puts contents in a box. Useful for preventing hyphenation.</p>
+<p class="overhang"><code>\makebox[<em>width</em>][<em>alignment</em>]{<em>text</em>}</code> Box with adjustments.</p>
+<p class="overhang"><code>\hspace{<em>length</em>}</code> Creates a horizontal space.</p>
+<p class="overhang"><code>\vspace{<em>length</em>}</code> Creates a vertical space. Caution: May disturb baseline grid.</p>
+<p class="overhang"><code>\kern<em>length</em></code> Tweaks kerning between characters.</p>
+<p class="overhang"><code>\strut</code> Ensures that a line of text maintains its proper height.</p>
+<p class="overhang"><code>{\centering <em>text</em>\par}</code> Limited to single paragraph.</p>
+<p class="overhang"><code>\hfill</code> Precedes right-aligned text.</p>
+<p class="overhang"><code>\vfill</code> Forces text downward on page.</p>
+<p class="overhang"><code>\\</code> Ordinary line break, not justified.</p>
+<p class="overhang"><code>\linebreak</code> Justified line break. Use with caution.</p>
+<p class="overhang"><code>\bigemdash[<em>voffset,thickness</em>]</code> Simulated emdash of variable width.</p>
+</div>
+
+<h4 id="hE.2.6">E.2.6 Footnotes and Endnotes</h4>
+<div class="d4" id="dE.2.6">
+<p class="noindent2">See also \realmarker and \fakemarker.</p>
+<p class="overhang"><code>\footnote[<em>option</em>]{<em>note text</em>}</code> Marker, with footnote at page bottom.</p>
+<p class="overhang"><code>\endnote</code> Places marker for subsequent endnote.</p>
+<p class="overhang"><code>\endnotetext{<em>number</em>}{<em>note text</em>}</code> Text of an endnote.</p>
+</div>
+
+<h4 id="hE.2.7">E.2.7 Images</h4>
+<div class="d4" id="dE.2.7">
+<p class="overhang"><code>\InlineImage[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}</code> Inline image.
+<p class="overhang"><code>\InlineImage*[<em>hoffset</em>][<em>voffset</em>]{<em>filename.ext</em>}</code> Inline image, no cursor width.</p>
+<p class="overhang"><code>\BlockImage[<em>alignment,hoffset,voffset</em>]{<em>filename.ext</em>}[<em>accompanying text</em>]</code> Image block element.</p>
+</div>
+</div><!-- end class="d3" -->
+
+<h3 id="hE.3">E.3 Disabled LaTeX Commands</h3>
+<div class="d3" id="dE.3">
+<p class="noindent2">These commands are disabled or ineffective. Depending on the command, it may silently do nothing, or simply echo its argument, or generate a Warning or Error. Some of these commands are part of standard LaTeX document classes, but others are part of widely-used packages.</p>
+<p>There are other commands that <em>should</em> be disabled, but it is difficult to keep track of all of them. This list only includes some popular commands.</p>
+<p class="overhang"><code>\small, \LARGE, etc.</code> Use \characale or parascale environment.</p>
+<p class="overhang"><code>\textls</code> Use {\addfontfeature{LetterSpace=<em>number</em>}text} instead.</p>
+<p class="overhang"><code>\includegraphics</code> Use \InsertImage or \BlockImage instead.</p>
+<p class="overhang"><code>\maketitle</code> Do it yourself.</p>
+<p class="overhang"><code>bibliography, index, part, chapter, section, floats, captions, tables, etc.</code> This ain't no stinking thesis. LaTeX "academic layout" commands don't work.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hE.4">E.4 Discouraged LaTeX Commands</h3>
+<div class="d3" id="dE.4">
+<p class="noindent2">These commands may be used, but are likely to interfere with other commands defined by <i>novel</i>, 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 class="overhang"><code>\parbox, \minipage</code> Perhaps use adjustwidth environment.</p>
+<p class="overhang"><code>center</code> (env.) If used, pay careful attention to line space above/below.</p>
+<p class="overhang"><code>\raisebox</code> Use \charscale instead.</p>
+<p class="overhang"><code>\backmatter</code> Avoid in fictional works.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end Appendix E -->
+<!-- ************************************************************ -->
+<div id="pageF" class="page">
+
+
+<h2 id="hF">Appendix F. <img src="html-resources/amb.png" width="30" height="22" alt="emergency icon"/> Emergency Clinic: Rework Layout</h2>
+<div class="d2" id="dF">
+<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>
+<p>But if you re-size the book and don't knock the margins down, then the text width and height won't be the same. Your text doesn't fit the way it used to. All your lines re-flow, the page breaks are different, and all that work you put into getting just the right appearance must be re-done.</p>
+<p><em>Oh, nooooo ...</em></p>
+</div>
+<p>Relax. Here is all you need to do: add \ReworkTrimSize{5.06in}{7.81in}. That's it. Your existing margins will be preserved. The font size, and line skip, will be cleverly re-scaled to fit the new dimensions. Paragraphs and pagination are the same as before.</p>
+<p>There are two Rework commands available. One changes the Trim Size without changing the margins. The other changes the margins without changing the Trim Size. If you wish to change both Trim Size and margins, you may use both commands.</p>
+
+<h3 id="hF.1">F.1. \ReworkTrimSize{<em>width</em>}{<em>height</em>}</h3>
+<div class="d3" id="dF.1">
+<p>This command changes the <em>existing</em> Trim Size. If you do not use the <code>\SetTrimSize</code> command, then the existing Trim Size is the default. But if you do use <code>\SetTrimSize</code>, then you must leave that command as-is, and place <code>\ReworkTrimSize</code> later in the Preamble.</p>
+<p>If you used <code>\SetMediaSize</code>, you may leave that command as-is, or change it if you wish; the Trim Size does not care.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hF.2">F.2. \ReworkMargins{<em>top</em>}{<em>outside</em>}{<em>bottom</em>}{<em>inside</em>}</h3>
+<div class="d3" id="dF.2">
+<p>This command changes the <em>existing</em> margins. If you do not use the <code>\SetMargins</code> command, then the existing margins are the defaults. But if you do use <code>\SetMargins</code>, then you must leave that command as-is, and place <code>\ReworkMargins</code> later in the Preamble.</p>
+</div><!-- end class="d3" -->
+
+<h3 id="hF.3">F.3. Example of Rework</h3>
+<div class="d3" id="dF.3">
+<p>Here is an example of the Rework commands in use. When the layout is reworked, the font size and (if necessary) baseline skip is scaled to fit the new dimensions, in a way that preserves the original paragraphs and pagination. This is done in a single pass: The method simultaneously works and re-works the layout.</p>
+<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/>
+\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>Result after Rework:</p>
+<p class="centerimg"><img src="html-resources/reworkedspread.png" width="700" height="531" alt="spread after rework"/></p>
+</div><!-- end class="d3" -->
+
+<h3 id="hF.4">F.4. Limitations of Rework</h3>
+<div class="d3" id="dF.4">
+<p>• The technique has been tested, but it might not always work. Be sure to inspect the result carefully.</p>
+<p>• If you use Rework to make a radical size change, then the resulting font size or line skip might be unattractive.</p>
+<p>• If the reworked pages have one less line than expected (or one more), this is due to roundoff in the calculations. It can usually be fixed by adding or substracting as little as <code>0.001\nbs</code> from the top or bottom rework margin.</p>
+<p>• 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> Good: <code>\hspace{0.5em}</code><br/>
+Bad: <code>\kern1pt</code> Good: <code>\kern.08em</code><br/>
+Bad: <code>\vspace{0.5in}</code> Good: <code>\vspace{2.4\nbs}</code>
+</p>
+<p>• When you use <code>\Rework</code>, images are <em>not</em> scaled. Thus, they will have a different relationship to the surrounding text than they did before. In many cases, this is not a problem. However, an un-scaled image may disrupt the flow of text, or the number of lines in a page, or overlap text that was previously cleared. Look in the log file for an Alert message, which suggests an appropriate image scale, depending on how an image was placed. Problem areas can often be fixed be scaling the related image(s) in an external graphics program (see <a href="noveldocs-08-images.html#a8.3.3">Page 8</a>) then re-compiling with the scaled image(s).</p>
+<p>• Note that you may see the Alert whether or not there are problem images, so scaling images will not make the Alert go away. It is a friendly message.</p>
+<div style="clear:both"></div>
+</div><!-- end class="d3" -->
+
+<h3 id="hF.5">F.5. Scaling Images after \Rework.</h3>
+<div class="d3" id="dF.5">
+<p>When you use one or both of the \Rework commands, the font size and/or the baselineskip will change. However, it does not scale images. In many cases, there is no problem. But in some cases, an un-scaled image will disrupt the previous flow of text or pagination. If you look in the log file, you will see an Alert message, which suggests (only suggests) appropriate values for scaling problem images, depending on whether they are placed inline or block. Then, you should re-work the image in an external image editor. When you scale the image, be sure that the revised version is at the correct resolution of 300dpi or 600dpi, or whatever is necessary.</p>
+<p>It is best to go back to your copy of the original artwork, before you exported it to <i>png</i> or <i>jpg</i>. But what if you do not have anything but the 1-bit or grayscale images that you created earlier? Then do this (in GIMP):</p>
+<p>(1) If the image is 1-bit, change to Color>Mode grayscale.</p>
+<p>(2) Use Image>Scale Image to get new dimensions, at 600 or 300 pixels per inch. Careful: Sometimes when you change size, it auto-changes resolution, or vice-versa. Click back and forth in the dialog box, to ensure that both the dimensions and resolution are correct. Use Cubic interpolation or better.</p>
+<p>(3) Change View to something that puts the image at its approximate print size.</p>
+<p>(4) If desired, play with Filters>Enhance>Sharpen.</p>
+<p>(5) Image>Flatten.</p>
+<p>(6) If the image is to be 1-bit line art, then use GaphicsMagick or ImageMagick as described in section 8.3.1.</p>
+<p>(7) Export as png, then use GraphicsMagick or Image Magick as described in section 8.3.2.</p>
+<p>The above does not take too much time, and will provide superior results. Note that when an image is placed within text, the calculation for text positioning is different than the calculation for image positioning. It is possible (although unlikely) that a \Rework situation will cause an unexpected page break, due to roundoff error in the placement of the final line on a page. This can be fixed by subtracting (or, in some cases, adding) as little as <i>\vspace{-0.001\nbs}</i> before or after the re-scaled image.</p>
+</div><!-- end class="d3" -->
+
+
+</div><!-- end class="d2" -->
+</div><!-- end Appendix F -->
+<!-- ************************************************************ -->
+
+
+
+
+</div><!-- end main -->
+<div id="finish"></div>
+</div><!-- end master -->
+</body>
+</html>
+
Property changes on: trunk/Master/texmf-dist/doc/lualatex/novel/novel-documentation.html
___________________________________________________________________
Added: svn:eol-style
## -0,0 +1 ##
+native
\ No newline at end of property
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/novel.pdf
===================================================================
(Binary files differ)
Modified: trunk/Master/texmf-dist/doc/lualatex/novel/novel.tex
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/novel.tex 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/novel.tex 2017-09-14 20:53:13 UTC (rev 45302)
@@ -3,7 +3,7 @@
%
% SOURCE CODE FOR FILE novel.pdf, the cover info
% for novel document class.
-\documentclass{novel} % v. 1.38 or later
+\documentclass{novel} % v. 1.40 or later
% Almost all settings are defaults.
\SetHeadFootStyle{3}
\SetTitle{Novel Document Class} % only footer, with page number
@@ -22,66 +22,40 @@
{\centering\textit{It was a dark and stormy night.}\par}
\end{ChapterStart}
-The \emph{novel} document class is for writers of original fiction, to be
-printed to paper, with particular attention to the requirements of
-the print-on-demand market.
+The \emph{novel} document class is for writers of original fiction, to be printed to paper, with particular attention to the requirements of the print-on-demand market. Non-color interiors and color covers are supported. Images are supported, but only as they might be used in fiction, not picture books.
-If your work is an E-book, or uses color other than gray, or is
-academic writing, then this document class is not for you. Images
-are supported, but only as they might be used in fiction; so if your
-work is a picture book, this class is not for you.
+If your work is an E-book, or uses interior color other than gray, or is academic, then this document class is not for you.
-But if you are writing a detective novel, or science fiction, or a
-collection of short stories, then read on!
+But if you are writing a detective novel, or science fiction, or a collection of short stories, then read on!
\QuickChapter{1. Features}
-Throughout, it is assumed that the purpose of your writing is a
-commercially printed book of fiction.
+Throughout, it is assumed that the purpose of your writing is a commercially printed book of fiction.
-A new \emph{novel} is pre-configured to produce a standard trade book
-size of 5.5in W x 8.5in H, with layout margins that are likely to be
-acceptable to the most widely-used print services. The file now are
-now reading is in this format. But if that is not the size or layout you
-want, then there are commands that configure just about anything,
-using standard terminology and understandable purpose. Best of
-all, the HTML documentation comes with images and examples, so
-you know what you are doing.
+A new \emph{novel} is pre-configured to produce a standard trade book size of 5.5in W x 8.5in H, with layout margins that are likely to be acceptable to the most widely-used print services. The file now are now reading is in this format. But if that is not the size or layout you want, then there are commands that configure just about anything, using standard terminology and understandable purpose. Best of all, the HTML documentation comes with images and examples, so you know what you are doing.
-Almost everything is pre-configured to “just work,” even the
-choice of fonts. The chosen compiler is LuaLaTeX, and Open Type
-fonts are loaded using fontspec technology. If you prefer to use
-a professional font, it will be easy to load and use in utf-8.
+Almost everything is pre-configured to “just work,” even the choice of fonts. The chosen compiler is LuaLaTeX, and Open Type fonts are loaded using fontspec technology. If you prefer to use a professional font, it will be easy to load and use in utf-8.
-Many standard LaTeX commands are disabled. This will be surprising
-at first. But \emph{novel} is focused on one thing only. Anything
-that might interfere with that purpose may have been tossed aside.
-So, be sure that you read the documentation! If you take an existing
-LaTeX document and just change the class to \emph{novel,} it is very
-unlikely to work as expected.
+Many standard LaTeX commands are disabled. This will be surprising at first. But \emph{novel} is focused on one thing only. Anything that might interfere with that purpose may have been tossed aside. So, be sure that you read the documentation! If you take an existing LaTeX document and just change the class to \emph{novel,} it is very unlikely to work as expected.
-Many new commands are provided. They are focused on the
-needs of print fiction writers, period. And, \emph{novel} has built-in PDF/X
-technology that exceeds the capabilities currently available via other
-LaTeX packages.
+Many new commands are provided. They are focused on the needs of print fiction writers, period. And, \emph{novel} has built-in PDF/X technology that exceeds the capabilities currently available via other LaTeX packages.
\QuickChapter{2. Complete Documentation}
-What you are reading now, is only an introduction. The complete
-documentation is in HTML format, directly written
-in HTML rather than extracted from code. There are numerous
-examples and images, too detailed to be presented as PDF.
+What you are reading now, is only an introduction. The complete documentation is in HTML format, directly written in HTML rather than extracted from code. There are numerous examples and images, too detailed to be presented as PDF.
\QuickChapter{3. License}
-The LaTeX code, and accompanying documentation, is released
-under the LateX Project Public License, version 1.3c or later.
+The LaTeX code, and accompanying documentation, is released under the LateX Project Public License, version 1.3c or later.
-The companion font \emph{NovelDeco.otf} is licensed under the SIL
-Open Font License, version 1.1.
+The companion font(s) is(are) licensed under the SIL Open Font License, version 1.1.
+
+
\QuickChapter{4. Version}
+\noindent 1.40, 2017-08-14: removed debug feature, major docs rewrite.
+
\noindent 1.38, 2017-08-15: corrected offset in cover artwork.
\noindent 1.36, 2017-08-10: minor documentation correction.
@@ -88,7 +62,7 @@
\noindent 1.34, 2017-07-31: added debug feature for maintainers.
-\noindent 1.32, 2017-07-26: minor bug fixes in docs, major bug concerning \string\textls\space in code.
+\noindent 1.32, 2017-07-26: bug fixes.
\noindent 1.2, 2017-06-06: added code for color image artwork.
@@ -102,8 +76,7 @@
\backindent\makebox[\parindent][l]{Q. }Can this document class be used for E-books?
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
-\backindent\makebox[\parindent][l]{A. }No. And, that feature will never be added, as the technology
-is inherently incompatible.
+\backindent\makebox[\parindent][l]{A. }No. And, that feature will never be added, as the technology is inherently incompatible. A word processor is your friend.
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
@@ -110,7 +83,7 @@
\backindent\makebox[\parindent][l]{Q. }Is this project still alive?
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
-\backindent\makebox[\parindent][l]{A. }Yes, and it is still in use by its originator. However, the originator would like someone else to take over long-term maintenance, because he is moving on to other things. If interested, contact CTAN and the creator (e-mail at top of novel.cls file). You will need to be familiar with LuaLaTeX, fontspec, Open Type, and the terminology of fiction writing. Lua coding not required. Until then, the originator will maintain it from time to time.
+\backindent\makebox[\parindent][l]{A. }Yes, and it is still in use by its creator. However, he would like someone else to take over long-term maintenance, because he is moving on to other things. If interested, contact CTAN and the creator (e-mail at top of novel.cls file). You will need to be familiar with LuaLaTeX, fontspec, Open Type, and the terminology of fiction writing. Lua coding not required. Until then, the original creator will maintain it from time to time.
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
@@ -117,8 +90,7 @@
\backindent\makebox[\parindent][l]{Q. }My thesis advisor told me---
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
-\backindent\makebox[\parindent][l]{A. }Stop right there. This document class is very different from
-anything used for theses and other academic publications.
+\backindent\makebox[\parindent][l]{A. }Stop right there. This document class is very different from anything used for theses and other academic publications.
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
@@ -129,16 +101,17 @@
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
-\backindent\makebox[\parindent][l]{Q. }When I woke up this morning, my head felt like a toddler had
-been pounding it in a sandbox. I rolled over and look at the mug shot
-on the wall. It was a woman in her forties with a drug habit that
-was bad, and an attitude that was even worse. She had seen better
-days, like the time I took her to the eighth grade sock hop. Then I
-got up, washed, and dragged my lonely butt down to the one-man
-detective agency that I jokingly called my means of living.
-You know what I mean?
+\backindent\makebox[\parindent][l]{Q. }Has this document class ever been used for an actual novel?
\end{adjustwidth}
\begin{adjustwidth}{\parindent}{0pt}
+\backindent\makebox[\parindent][l]{A. }Yes indeed! In August 2017 the author published a complete novel, including its cover, using this document class. Almost all of the setup used defaults. The files (textblock and cover) were submitted to a major American P.O.D. service in \lnum{PDF/X-1a:2001} format, then electronically reviewed and accepted \textit{on the first attempt.} A printed copy was in the author's hands within a week. Just like that. Took months to write, of course.
+\end{adjustwidth}
+
+\begin{adjustwidth}{\parindent}{0pt}
+\backindent\makebox[\parindent][l]{Q. }When I woke up this morning, my head felt like a toddler had been pounding it in a sandbox. I rolled over and looked at the mug shot on the wall. It was a woman in her forties with a drug habit that
+was bad, and an attitude that was even worse. She had seen better days, like the time I took her to the eighth grade sock hop. Then I got up, washed, and dragged my lonely butt down to the one-man detective agency that I jokingly called my means of living. You know what I mean?
+\end{adjustwidth}
+\begin{adjustwidth}{\parindent}{0pt}
\backindent\makebox[\parindent][l]{A. }Yeah. Stick with me, kid. This document class is for you.
\end{adjustwidth}
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,912 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a1">1. Overview</a></p>
-
-<ul>
-<li><a href="#a1.1">1.1 Description</a>
- <ul>
- <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.2">1.2.2 Beware of $, %, and Others</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>
- </ul></li><!-- end 1.2 -->
-<li><a href="#a1.3">1.3 Book Design Terminology</a>
- <ul>
- <li><a href="#a1.3.1">1.3.1 Sheet, Page, Leaf, Folio</a></li>
- <li><a href="#a1.3.2">1.3.2 Page Spread, Recto, Verso, Line Grid</a></li>
- <li><a href="#a1.3.3">1.3.3 Perfect Binding, Spine Signature</a></li>
- <li><a href="#a1.3.4">1.3.4 Gutter</a></li>
- <li><a href="#a1.3.5">1.3.5 Trim Size</a></li>
- <li><a href="#a1.3.6">1.3.6 Media Size, TrimBox</a></li>
- <li><a href="#a1.3.7">1.3.7 Setting Layout Dimensions</a></li>
- </ul></li><!-- end 1.3 -->
-<li><a href="#a1.4">1.4 Interior Organization</a>
- <ul>
- <li><a href="#a1.4.1">1.4.1 Front Matter</a></li>
- <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><a href="#a1.5">1.5 Command Summary: Preamble</a>
- <ul>
- <li><a href="#a1.5.1">1.5.1 Class Options</a><br>
- <ul>
- <li>draft, graytext, shademargins, cropmarks, cropview, closecrop, xml</li>
- </ul>
- </li>
- <li><a href="#a1.5.2">1.5.2 Metadata (File Data)</a>
- <ul>
- <li>\SetTitle, \SetAuthor, \SetSubtitle, \SetApplication, \SetProducer, \SetPDFX</li>
- </ul>
- </li>
- <li><a href="#a1.5.3">1.5.3 Page Layout</a>
- <ul>
- <li>\SetTrimSize, \SetMargins, \SetFontSize, \SetLinesPerPage, \SetHeadFootStyle, \SetHeadJump, \SetFootJump, \SetMediaSize, \SetCropmarkGap, \ReworkTrimSize, \ReworkMargins</li>
- </ul>
- </li>
- <li><a href="#a1.5.4">1.5.4 Font Setup</a>
- <ul>
- <li>\SetParentFont, \SetHeadFont, \SetChapterFont, \SetSubchFont, \SetDecoFont, \SetSansFont, \SetMonoFont, \NewFontFamily, \NewFontFace</li>
- </ul>
- </li>
- <li><a href="#a1.5.5">1.5.5 Other Configuration</a>
- <ul>
- <li>\SetRectoheadText, \SetVersoHeadText, \SetEmblems, \SetPageNumberStyle, \SetLooseHead, \SetChapterStart, \SetIndentAfterScenebreak, \SetMarkerStyle, \microtypesetup, \setmainlanguage</li>
- </ul>
- </li>
- </ul>
-</li>
-<li><a href="#a1.6">1.6 Command Summary: Document Body</a>
- <ul>
- <li><a href="#a1.6.1">1.6.1 Book Divisions</a>
- <ul>
- <li>\frontmatter, \mainmatter, \backmatter</li>
- </ul>
- </li>
- <li><a href="#a1.6.2">1.6.2 Special Pages</a>
- <ul>
- <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>
- <ul>
- <li> \QuickChapter, \scenebreak, \sceneline, \scenestars, \begin{parascale}, \begin{adjustwidth}</li>
- </ul>
- </li>
- <li><a href="#a1.6.4">1.6.4 Footnotes and Endnotes</a>
- <ul>
- <li>\footnote, \endnote, \endnotetext, \realmarker, \fakemarker</li>
- </ul>
- </li>
- <li><a href="#a1.6.5">1.6.5 Images</a>
- <ul>
- <li>\InlineImage, \BlockImage</li>
- </ul>
- </li>
- <li><a href="#a1.6.6">1.6.6 General Text Styling</a>
- <ul>
- <li>\charscale, {\somefont...}, \forceindent, \backindent, \hangindent, \acronym, \decoglyph, \squeeze, \crush, \color, \textcolor, \memo, \nfs, \nbs</li>
- </ul>
- </li>
- <li><a href="#a1.6.7">1.6.7 Some other LaTeX Commands</a>
- <ul>
- <li>A list of selected commands, not specific to this document class, that might be useful. Not comprehensive.</li>
- </ul>
- </li>
- <li><a href="#a1.6.8">1.6.8 Disabled LaTeX Commands</a>
- <ul>
- <li>In general, commands and environments pertaining to math, font sizes, theses, floats, tables, and images (other than novel's own commands) are entirely disabled.</li>
- </ul>
- </li>
- <li><a href="#a1.6.9">1.6.9 Discouraged LaTeX Commands</a>
- <ul>
- <li>A short list of commands that you should not use, because of undesired side effects in this document class.</li>
- </ul>
- </li>
- </ul>
-</li>
-</ul>
-
-<p> </p>
-</div><!-- end toc -->
-
-
-
-
-<div id="main">
-<a id="thetop"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p>1. Overview</p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><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, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<a id="a1"></a>
-<h2 style="clear:none">1. Overview</h2>
-
-<p><b>Read This:</b> The novel class has a lot of possible settings, and a command structure that differs from other document classes in many ways. So, there is a lot of documentation. But you probably do not have to read most of it.</p>
-<p>Before you panic, look at the <code>novel-example.tex</code> demonstration file. It uses mostly default settings. See how easy that can be?</p>
-
-
-<a id="a1.1"></a>
-<h3 style="clear:none">1.1 Description</h3>
-
-<p>The <code>novel</code> document class is intended for writers of original fiction, such as novels and collections of short stories. For this purpose, it provides easy-to-use settings that are pre-configured for the most common book Trim Sizes, according to publishing standards. The class uses the advanced typographic features of LuaTeX, fontspec, and microtype, and has the built-in capability to produce files compliant with PDF/X. All these capabilities are accessed via simple front-end commands that do the work for you, thereby reducing the learning curve.</p>
-
-<p>PDF/A and other formats pertaining to digital publication (e-books) are not supported, and never will be. If that is what you need, then this is the wrong document class for you.</p>
-
-<p>Bibliography, Floats, Tables, Math Mode, automatic generation of title page and table of contents... Forget them! Many of the TeX features used for academic work have reduced functionality, or are entirely disabled, in <code>novel</code> class. There is a reason for this. If you need them, find another document class. There is minimal support for page-bottom footnotes, but good support for raster (not vector) images.</p>
-
-<p>The class makes typographic choices that are best suited to <em>original</em> fiction, where you can easily resolve problematic typesetting by re-writing your own work. In particular, there is no effort to control widows and orphans.</p>
-
-<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>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><b>Word Processor:</b> I use LibreOffice for this (version 5.3 or later preferred), but you can use most other word processors.</p>
-
-<p>Write your wonderful novel using the word processor, with the same page layout that you will eventually use for TeX, and with the same font and point size. However, don't use italics or any other font effect that requires TeX code. This will give you a rough idea of how things look, and how many pages are used. You will still need to do final editing within TeX, where you will add codes for italics and other effects, and perhaps re-write paragraphs so that they look better.</p>
-
-<p>A good word processor will have a high-end spelling checker, and perhaps some grammatical checks. It can apply “smart quotes” and other character substitutions on-the-fly. If you save the result as plain text <em>with utf-8 encoding</em> then it can be used with the <code>novel</code> document class. Beware of saving plain text in Windows native encoding.</p>
-
-<p>Note that some word processors interpret two hyphens as an em-dash. In TeX, it's three hyphens. As long as the substitution is made, things will be OK.</p>
-
-<p><b>Adobe Reader:</b> 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 (different platform OK).</p>
-
-<p>The reason is that some other PDF readers will not object to problem files, but Adobe Reader will complain. Almost certainly, the recipient of your PDF will open it in a commercial program (perhaps Adobe Acrobat Pro), inspect it, and add manufacturing information at the bottom of the last blank page. It is that revised PDF file that will go to the printing machine.</p>
-
-<p>How to inspect your finished PDF: (1) In Adobe Reader, go to Edit, Preferences, Documents. Check "Save As optimizes for fast web view." Then go to Edit, Preferences, Page Display. Check "Show art, trim, and bleed boxes." Then OK. (2) Open your PDF. If its Trim Size is smaller than the full PDF page size (Media Size) you should see a light green box. This shows the Trim Size. This box does not print; it is only for visualization. However, if your Trim Size is the same as the Media Size (the normal situation) then the green box, if visible, will be all the way to the page edges. (3) Go to File, Properties, Fonts. Any font must be (subset) embedded. (4) "Save As" the same file name (or another one, if you prefer). This will optimize the file. You probably do not need to do that, but it does not hurt, and a few services expect it.</p>
-
-<p><b>ImageMagick or GraphicsMagick;</b> If your document has any images, whether grayscale interior or color cover art, then you will need more advanced image processing than most image editors (such as GIMP) can provide. See page 10 of this documentation, for detailed instructions.</p>
-
-<p><b>Text Extraction:</b> Did you lose your TeX source document after preparing the PDF? If so, you can extract its unformatted plain text (not TeX code). 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.</p>
-
-<p>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 <code>Okular</code> 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>
-
-
-<a id="a1.2"></a>
-<h3>1.2 Differences. Important! Read This!</h3>
-
-<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>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. Be sure you read that! For example, you cannot load a font with <code>\usepackage{fontname}</code> in this document class.</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>è</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>
-
-
-<a id="a1.2.2"></a>
-<h4 style="clear:both">1.2.2 Beware of $, %, and Other TeX Special Characters</h4>
-
-<p><b>Alert:</b> This was not correctly explained in earlier documentation.</p>
-
-<p><img class="floatright" src="html-resources/trdol.png" width="238" height="67" alt="dollar is math mode"> TeX has a number of special characters. If you type them in a document, they will not appear as an ordinary printed character, but will do something else. These are:</p>
-
-<p class="code"><code>$ % # _ ^ & ~ \ { }</code> and sometimes <code>[ ]</code></p>
-
-<p>In most cases, an incorrect usage will provide an error message that can be easily deciphered. However, the dollar sign and percent symbol are tricky. Incorrect use of the dollar sign may either place your text in math mode (not your intent) or produce a baffling error message that points to an innocent package. The percent symbol normally produces no error, since it is a comment character. But then, whatever text follows on that line will be missing from your PDF.</p>
-
-<p>Special characters, other than the backslash, are escaped by placing a backslash in front, thus: <code>\$</code> for the dollar sign, <code>\%</code> for percent. If you must print a backslash, <code>\string\</code> does it.</p>
-
-<p>To avoid unforeseen problems, you should review your document in a text editor, prior to compiling. Search for any instances of special characters, particularly dollar and percent. Backslash them as needed.</p>
-
-
-<a id="a1.2.3"></a>
-<h4>1.2.3 Standard text size commands are disabled</h4>
-
-<p>Would you like to size text, using command such as <code>\small</code> or <code>\LARGE</code>? Bah! They will be ignored. Write these commands, and the text will appear at its usual size, just as if the commands did not exist.</p>
-<p>There is a reason for this behavior, related to the need for constant line spacing. Thus, <code>novel</code> provides its own capability to size text, using different commands. Read about it, on <a href="noveldocs-07-text-size-style.html">Page 7</a>.</p>
-
-
-<a id="a1.2.4"></a>
-<h4>1.2.4 Images must be raster png or jpg</h4>
-
-<p>You read that correctly. Sometimes fiction uses images, especially for the title page and chapter titles. With <code>novel</code>, do not use vector formats such as <code>eps</code>, <code>svg</code>, or <code>pdf</code> images. Use raster images in <code>png</code> or <code>jpg</code> format.</p>
-<p>There is a reason for this, explained on Page 9, where the use of images is discussed in detail. Be sure to read it, as <code>novel</code> has its own way to place images, in a way that is most likely to work well with fiction.</p>
-
-
-<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>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>
-
-
-<a id="a1.2.6"></a>
-<h4>1.2.6 Think for yourself</h4>
-
-<p>When LaTeX processes a document on a paragraph-by-paragraph basis, it chooses the layout that has the least total "penalty." Penalties are assessed based on factors such as word spacing, inter-line spacing, hyphenation, widows, and orphans. You may choose the value of each penalty.</p>
-
-<p>With <code>novel</code>, inter-line spacing is fixed. No plus-or-minus. Hyphens are allowed, but strongly penalized. A reasonable amount of altered word spacing is allowed, and the built-in <code>microtype</code> package allows reasonable changes to letter spacing and the letters themselves. These choices achieve a high level of visual appeal and readability for flowing text.</p>
-
-<p>However, there is little penalty for widows or orphans. When you process a document with <code>novel</code> you are likely to find widows and orphans on many pages. This choice was made for several reasons. First, attention to widows and orphans would reduce the effectiveness of the other, more imprtant, layout penalties. Second, fiction often has numerous short paragraphs (especially with dialogue), and it is very difficult for software to deal with all of them. Third, it's your book... Rewrite it!</p>
-
-<p>If TeX isn't formatting paragraphs in an attractive manner, then rewrite your work. It's that simple.</p>
-
-
-<a id="a1.3"></a>
-<h3>1.3 Book Design and Terminology</h3>
-
-<p>If you are preparing a PDF for the print-on-demand (P.O.D.) market, and I assume you are, then you need to understand how terms are used in the <code>novel</code> document class (and LaTeX in general). The reason is that most authors in P.O.D. use an ordinary word processor, particularly MS Word. For that reason, many print services, and most online user forums, refer to the terminology and settings of MS Word, rather than to the meanings in traditional book publishing. In the case of images, Photoshop settings are often described. And, the more advanced authors may be using InDesign. Yes, there are authors using LaTeX and GIMP (I am among them), but they are not the ones who make the most noise. And, if you visit web sites and forums devoted to LaTeX, they primarily address the concerns of academic writers, particularly mathematicians, because that is the target user base for LaTeX.</p>
-
-<p>Here, I will present a brief overview of what key terms mean. In some cases, I will also describe how the same terms mean different things, to those who use other software. Pay attention!</p>
-
-
-<a id="a1.3.1"></a>
-<h4>1.3.1 Sheet, Page, Leaf, Folio</h4>
-
-<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>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>
-
-<p>Caution, The term "folio" has several different meanings, even in the narrow field of book publishing. It may refer to folded paper, as mentioned above. Or it may refer to a particular sheet size of paper ("foolscap"). Or, it may simply refer to the number printed on a page. This last use of "folio" will be discussed in the context of headers and footers.</p>
-
-
-<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>
-
-
-<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>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>
-
-
-<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>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>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>
-
-<p><b>Margins</b> are required on all four edges of the page. They do not have to be the same width. Generally the margin at the spine edge (inside margin) is wider. The above illustration shows a typical recto page on a layout with header and footer. The margins have been shaded gray in the picture (but, not in the book).</p>
-
-<p>Normally, your TeX document will be compiled to a PDF that is electronically at the exact Trim Size. And normally, print services want it to be that way. When you view your PDF, the text will shift from side to side as you move through the pages, due to the slightly increased margin at the spine edge. Note that in the above image, the spine margin (at its left) is a little larger than the outside margin (at its right).</p>
-
-
-<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>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>
-<p>Caution: If you are following someone else's instructions about setting margins, the odds are that the instructions apply to MS Word or maybe InDesign, not to TeX. In those other programs, the margin settings may include the wasted area beyond the Trim Size, because they are referring to margins <em>within the program</em> rather than the physical margins <em>of your book</em>.</p>
-
-
-<a id="a1.3.7"></a>
-<h4>1.3.7 Setting Layout Dimensions</h4>
-
-<p>Now that you know what the terms mean, how do you set them? This is described in detail on Page 4.</p>
-<p>In <code>novel</code> class, everything is pre-configured according to "likely" layout, for the specified book Trim Size. And, if you don't choose the Trim Size, the popular 5.5"W x 8.5"H size will be chosen for you.</p>
-
-
-
-<a id="a1.4"></a>
-<h3>1.4 Interior Organization</h3>
-
-<p>Now let us examine how a book is structured from front to back, in terms of internal organization of its content.</p>
-
-
-<a id="a1.4.1"></a>
-<h4>1.4.1 Front Matter</h4>
-
-<p>Roughly speaking, front matter identifies and describes the book, but is not the story itself.</p>
-<p>There is some wiggle room regarding what constitutes the story. In a genre where the book is supposed to be a lost manuscript written by someone else, or the translation of a (nonexistent) ancient book, the author may have introductory material describing how the book was discovered or translated. Of course, that is also a fictional part of the story. But the author may choose to place such an introduction in front matter, pretending that it is a factual description. Or, in any genre, a real or imaginary map of the locale may be in front matter, if it improves the book's overall appearance.</p>
-<p>Front matter begins with the <code>\frontmatter</code> command, which should be the first thing in the body of your document. This command sets the page numbering to lowercase roman. Most or all of the front matter page numbers will not appear in print, but they will appear in lowercase roman when viewed with most PDF readers.</p>
-<p>Front matter often contains only blank pages and "display" pages that stand by themselves. For each such page, use <code>\thispagestyle{empty}</code> to ensure that the page has no heading or printed page number.</p>
-<p>If you ever need to "drop folio," commands for that purpose are described on <a href="noveldocs-06-header-footer.html#a6.2.2">Page 6</a>. If you need a Table of Contents, see <a href="noveldocs-09-chapters-displays.html#a9.3">Page 9</a>. Note that the standard TeX methods do not work in <code>novel</code>.</p>
-<p><b>Page i.</b> As a matter of tradition, the very first page (i) recto, is the Half Title. This page contains only the book's title (not even subtitle). It may be stylized or in the form of an image, but is less prominent than the subsequent full title.</p>
-<p><b>Page ii.</b> The following page (ii) verso, is most often blank. Sometimes, a list of books by the same author can be placed here. Or, if the book is part of a series of related books, that can be mentioned. However, be aware that your print and distribution service may not allow such a list, unless they also carry all of the works listed. Another possibility is an illustration (professional artwork, not clip art). If your story has a map, and you don't know where else to put it, then the map can go here.</p>
-<p><b>Page iii.</b> The next page (iii) recto, is the Full Title Page. This contains the title (preferably decorative image), subtitle if any, author's name, and publisher's imprint (if any). Note that in the self-pbulishing market, your print and distribution service is not the publisher, <em>you are</em>. Some authors take the trouble to establish a publishing business name and logo. If so, put it at the bottom of this page. Your service <em>might</em> permit you to write something such as "Available from CremateSparks and Other Booksellers," as long as it does not imply that they are the publisher or sole distributor. The contract you have with them will say what you may or may not do.</p>
-<p><b>Page iv.</b> Next (iv) verso is the Copyright Page. It contains a number of elements. Look at other books for models. Special note: Do not use a "copyleft" notice, even if you are feeling generous.</p>
-
-<p><b>Page v.</b> If your book has a Dedication, it must appear on page (v) recto. Not all books have one. Nowadays, dedications are best put on a web site, where you can delete or change them with circumstances. Although there are some famous authors who write silly dedications, you are not famous, so don't do it.<p>
-<p>Consider using a generic dedication, if you feel that one is necessary. For example, if your book is combat fiction, you might write "To our Armed Forces." If it is a murder mystery, "To all those who wish that crimes could be solved so easily."
-
-<p>If you do not have a Dedication, then place a Table of Contents on Page (v), if your book has one. Not all books do. In fiction, a Table of Contents is most often used when chapters are distinctive, with their own chapter titles.</p>
-
-<p>Proceed to whatever else ought to go in front matter. But what if there is nothing else? This is quite possible in fiction. You don't always need a Dedication or Table of Contents, and you probably do not need a Preface or Introduction. It is bad practice to go directly from the Copyright page to the beginning of the story, because the page spread (legalese at left, story at right) looks awkward and unprofessional. So, what can you put on page (v) as a filler?</p>
-<p>Epigraph to the rescue! A book doesn't need one, but they look good. An epigraph is a short quotation from someone else's book or sayings, which sets the tone or theme of your own book. It can also imply that your book is in that genre. Copyright law applies, so be sure that the quotation is Public Domain. Permission from an author may not be good enough, since many authors transferred copyright to someone else. You can also use a fictional epigraph, from a book that does not exist. For example, if your book is sword-and-sorcery, you might provide an "Incantation from the Grimoire of Doh-Beer." In desperation, you can pick something from your own book. Keep it short.</p>
-
-<p><b>Page vi.</b> If you have nothing else in front matter, then page (vi) verso is blank. Then the following recto is page (1), the beginning of your story.</p>
-
-<p>When there is more to front matter, consult references on book design, to see what goes where.</p>
-
-
-
-
-
-<a id="a1.4.2"></a>
-<h4>1.4.2 Main Matter</h4>
-
-<p>The <code>\mainmatter</code> command marks the beginning of your story. It goes at the top of a recto page, immediately following the <code>\clearpage</code> commands that ends the front matter.</p>
-<p><code>\mainmatter</code> changes page numbering to arabic, and sets its count to 1. It also remembers the past-used page number in front matter, for possible later use.</p>
-<p>The question is: Where does main matter actually begin?</p>
-<p>Traditionally, main matter is the beginning of the story text. Non-text items, such as maps, are placed in front matter unless they are introduced later in the story.</p>
-<p>If the front matter is long (no particular length), then it is customary to place another Half Title recto page separating front matter from the story. Then, this second Half Title is page 1, its verso 2 is blank, and the text of the story actually starts on page 3. Or, if the story is broken into distinct Parts (not just chapters), then the cover for Part One would be page 1, its verso 2 blank, and again the story would begin on page 3.</p>
-<p>One genre is the "recently discovered manuscript" or "translation from ancient writings" tale. There is usually an introduction to the story from the fictional archaeologist, discoverer, or translator. Even though the introduction is fiction by a fictional person, it is customary to include it in front matter, just as if it were real. But it could be placed as the start of the story in main matter, instead.</p>
-<p>If you need footnotes and/or endnotes, they can be done. See <a href="noveldocs-09-chapters-displays.html#a9.7">Page 9</a>. But be aware that <code>novel</code> has only minimal provisions for such things, and will not automatically compile them as an addendum.</p>
-<p>In <code>novel</code>, you do not mark new chapters using a <code>\chapter</code> command. Instead you use special commands, specifically created to meet the needs of fiction. These are described on <a href="noveldocs-09-chapters-displays.html#a9.5">Page 9</a>.</p>
-<p>If your book has distinct parts (say, it is two novelettes in one), you should separate them with their own internal "cover" pages (recto), followed by a verso that is often blank, then the start of the part-story on the next recto. There is no particular <code>novel</code> command for this purpose. You have to design those pages yourself.</p>
-
-
-<a id="a1.4.3"></a>
-<h4>1.4.3 Back Matter</h4>
-
-<p>Fiction almost never needs back matter. Closing remarks by the author, or by a fictional character who introduced the story, can be treated as just another form of chapter. Even endnotes (which are themselves fictional) are treated as a continuation of main matter.</p>
-<p>If you wish to provide a separator, you can use one of four commands, immediately following <code>\clearpage</code>:</p>
-
-<p><code>\backmatter</code> is a do-nothing command. It merely informs you that what follows is considered back matter, in case someone is looking into your TeX code. Page numbers continue as arabic.</p>
-
-<p><code>\backmatter*</code> (with asterisk) puts page numbers in lowercase roman, continued from where the front matter left off.</p>
-
-<p><code>\Backmatter</code> (capital B) uses uppercase Roman, beginning at I.</p>
-
-<p><code>\Backmatter*</code> (capital B, asterisk) uses uppercase Roman, continued from where the front matter left off.</p>
-
-<p>In <code>novel</code>, you cannot automatically construct a bibliography or index, they way you can do it with other TeX document classes.</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<a id="a1.5"></a>
-<h3>1.5 Command Summary: Preamble</h3>
-
-<p style="clear:none;">Here is a list of commands created by <code>novel</code> class, plus a few of the many <code>LaTeX</code> commands that are likely to be most useful in fiction. Commands are sorted according to where they would be used.</p>
-
-<p style="clear:none;">Do not let the many Preamble settings intimidate you. All of them are pre-configured with default values that were carefully chosen for use in fiction. You may not need to write many settings.</p>
-
-<p style="clear:none;">Since <code>novel</code> is specifically intended for fiction, such as novels and collections of short stories, it does not implement many of the commands familiar to academic writers. In some cases, where such commands would interfere with <code>novel</code> commands, the academic commands have been entirely disabled.</p>
-
-
-<a id="a1.5.1"></a>
-<h4>1.5.1 Preamble: Class Options</h4>
-
-<p>These commands are further explained on <a href="noveldocs-02-class-options.html">Page 2</a>.</p>
-
-<p>Unlike other document classes, <code>novel</code> does not use class options to set layout dimensions or font point size.</p>
-
-<pre class="noindentcmd">draft</pre>
-<p>Sets draft mode. Marks horizontal overflow. Enables some other options.</p>
-
-<pre class="noindentcmd">graytext</pre>
-<p>Allows text in gray, not just pure K black.</p>
-
-<pre class="noindentcmd">shademargins</pre>
-<p>Only in draft mode. Applies gray background in page margins.</p>
-
-<pre class="noindentcmd">cropmarks</pre>
-<p>Adds basic cropmarks. Do not use unless required!</p>
-
-<pre class="noindentcmd">cropview</pre>
-<p>Only in draft mode. Removes excess area surrounding TrimBox.</p>
-
-<pre class="noindentcmd">closecrop</pre>
-<p>Only in draft mode. Crops to just clear the live text area.</p>
-
-<pre class="noindentcmd">xml</pre>
-<p>Exports XMP Metadata as an xml file.</p>
-
-
-<a id="a1.5.2"></a>
-<h4>1.5.2 Preamble: Metadata (File Data)</h4>
-
-<p>These commands are further explained on <a href="noveldocs-03-metadata-pdfx.html">Page 3</a>.</p>
-
-<p>Metadata can be seen by PDF viewers. Some of it can only be seen by professional software. The data identifies your file and describes some of its properties. In the case of PDF/X, choosing a compliance standard will also affect how LaTeX compiles your document.</p>
-<p>You may <em>not</em> apply styling to metadata!</p>
-
-<pre class="noindentcmd">\SetTitle{<em>title of your book</em>}</pre>
-<p>Default: empty</p>
-<p>The value of this setting is available as <code>\thetitle</code> everywhere.</p>
-
-<pre class="noindentcmd">\SetSubtitle{<em>subtitle of your book, if any</em>}</pre>
-<p>Default: empty</p>
-<p>The value of this setting is available as <code>\thesubtitle</code> everywhere.</p>
-
-<pre class="noindentcmd">\SetAuthor{<em>author of your book</em>}</pre>
-<p>Default: empty</p>
-<p>The value of this setting is available as <code>\theauthor</code> everywhere.</p>
-
-<pre class="noindentcmd">\SetPDFX[<em>embed-icc or no-embed</em>]{<em>compliance standard</em>}{<em>output intent</em>}</pre>
-<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>
-<p>Default: an identifying string, automatically inserted by TeX.</p>
-
-<pre class="noindentcmd">Advanced:<br>\SetProducer{<em>software that compiled the PDF</em>}</pre>
-<p>Default: an identifying string, automatically inserted by TeX.</p>
-
-
-<a id="a1.5.3"></a>
-<h4>1.5.3 Preamble: Layout</h4>
-
-<p>These commands are further explained on <a href="noveldocs-04-layout.html">Page 4</a>.</p>
-
-<p>The <code>novel</code> class provides improved alternatives to papersize, offset, and other layout commands used by other document classes. These commands have been carefully chosen to do what you need to do.<p>
-
-<pre class="noindentcmd">\SetTrimSize{width}{height}</pre>
-<p>Default: <code>{5.5in}{8.5in}</code></p>
-<p>Fundamental! This is the finished size of your book.</p>
-
-<pre class="noindentcmd">\SetMargins{top}{outside}{bottom}{inside}</pre>
-<p>Default: <code>{0.5in}{0.5in}{0.5in}{0.75in}</code></p>
-<p>Relative to Trim Size. Inside means the spine edge.</p>
-
-<pre class="noindentcmd">\SetHeadFootStyle{number}</pre>
-<p>Default: <code>1</code> (header, but no footer)</p>
-<p>Chooses whether header, footer, or both. Also chooses the general content of headers/footers. Available choices are pre-defined styles, labeled by number.</p>
-
-<pre class="noindentcmd">\SetHeadJump{number}</pre>
-<p>Default: <code>1.5</code> (corresponds to 1.5 baseline skip)</p>
-<p>Controls gap between header and main text, if style uses header.</p>
-
-<pre class="noindentcmd">\SetFootJump{number}</pre>
-<p>Default: <code>1.5</code> (corresponds to 1.5 baseline skip)</p>
-<p>Controls gap between main text and footer, if style uses footer.</p>
-
-<pre class="noindentcmd">\SetFontSize{<em>size</em>}</pre>
-<p>Default: <code>11.4pt</code></p>
-<p>Sets the normal font size. May be measured in <code>pt</code> or <code>bp</code>, decimals allowed.</p>
-
-<pre class="noindentcmd">\SetLinesPerPage{<em>integer</em>}</pre>
-<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>
-<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>
-<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>
-<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>
-<p>For emergency use only.</p>
-<p>Re-sizes an already-finished layout.</p>
-
-
-<a id="a1.5.4"></a>
-<h4>1.5.4 Preamble: Choosing Fonts</h4>
-
-<p>These commands are further explained on <a href="noveldocs-05-fonts.html">Page 5</a>.</p>
-
-<p>In <code>novel</code>, you will be using Open Type fonts loaded with features by the <code>fontspec</code> package. This permits much more flexibility than can be achieved using ancient <code>TeX</code> font methods. In particular, you never need <code>\usepackage{<em>fontname</em>}</code>, because available Open Type fonts can be loaded without LaTeX support files. If you are not already familiar with <code>LuaLaTeX</code> and <code>fontspec</code> with Open Type fonts, then forget <em>everything</em> you ever learned about <code>TeX</code> fonts, and start fresh.</p>
-<p><code>TeX</code> ligatures, such as subtituting <code>“</code> for <code>``</code>, are always enabled. Kerning (Open Type feature <code>kern</code>) is always enabled. Standard ligatures (Open Type feature <code>liga</code>) is enabled for fonts described in this section, including new fonts that you define. However, <code>liga</code> is <em>not</em> enabled by default for specialty fonts that will be described in later sections.</p>
-
-<pre class="noindentcmd">\SetParentFont[features]{font family}</pre>
-<p>Default: <code>Libertinus Serif</code></p>
-<p>Alternate: <code>Linux Libertine O</code></p>
-<p>Emergency Last Choice: <code>Latin Modern Roman</code></p>
-<p>If you permit the default or alternate font family to be chosen automatically, then the Semibold weights will be used in place of Bold. This is not automatically done for any others, becuase most font families do not have Semibold.</p>
-
-<pre class="noindentcmd">\SetHeadFont[features]{font family}</pre>
-<p>Default: <code>[Numbers=Lining, Scale=0.92]{<em>based on parent font</em>}</code></p>
-<p>Used in each element of headers and footers, unless overridden by other font commands.</p>
-
-<pre class="noindentcmd">\SetChapterFont[features]{font family}</pre>
-<p>Default: <code>[Numbers=Lining, Scale=1.6]{<em>based on parent font</em>}</code></p>
-<p>Used in <code>\ChapterTitle{}</code> command</p>
-
-<pre class="noindentcmd">\SetSubchFont[features]{font family}</pre>
-<p>Default: <code>[Numbers=Lining, Scale=1.2]{<em>based on parent font</em>}</code></p>
-<p>Used in <code>\ChapterSubtitle{}</code> command.</p>
-
-<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>
-<p>Default: <code>Libertinus Sans</code></p>
-<p>Alternate: <code>Linux Biolinum O</code></p>
-<p>Emergency Last Choice: <code>Latin Modern Sans</code></p>
-<p>Rarely used in fiction.</p>
-
-<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>Emergency Last Choice: <code>Latin Modern Mono</code></p>
-<p>Rarely used in fiction.</p>
-
-<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>
-
-
-<a id="a1.5.5"></a>
-<h4>1.5.5 Preamble: Other Configuration</h4>
-
-<p>These commands are further explained in file <a href="noveldocs-06-otherconfiguration.html">noveldocs-06-otherconfiguration.html</a>.</p>
-
-<pre class="noindentcmd">\SetRectoHeadText{<em>text</em>}</pre>
-<p>Default: Adjusted title, in small caps</p>
-<p>The text appears in recto 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">\SetVersoHeadText{<em>text</em>}</pre>
-<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>
-<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>
-<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>
-<p>Default: <code>50</code></p>
-<p>Tweaks tracking of header text, 0 to 200.</p>
-
-<pre class="noindentcmd">\SetChapterStart{<em>choice</em>}</pre>
-<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>
-<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>
-<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>
-<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>
-<p>Default: <code>english</code></p>
-<p>Several commands from the <code>polyglossia</code> package may be used for language choices.</p>
-
-
-
-<a id="a1.6"></a>
-<h3>1.6 Document Body</h3>
-
-<p>These commands are further explained in file <a href="noveldocs-07-documentbody.html">noveldocs-07-documentbody.html</a>.</p>
-
-<p>Note that standard font size commands, such as \small and \Large, are disabled.</p>
-
-
-<a id="a1.6.1"></a>
-<h4>1.6.1 Book Divisions</h4>
-
-<pre class="noindentcmd">\frontmatter</pre>
-<p>Page numbering (if shown) is lowercase roman. This division contains title page, copyright page, and usually several other pages that are not the story itself.</p>
-
-<pre class="noindentcmd2">\mainmatter</pre>
-<p>Page numbering re-starts at 1, and is arabic. This division contains the story itself.</p>
-
-<pre class="noindentcmd2">\backmatter, \backmatter*, \Backmatter, \Backmatter*</pre>
-<p>Backmatter typically contains things such as critical notes, bibliography, and appendix. Its use is very rare in fiction, because "fictional backmatter" (fake commentary, for example) is generally regarded as mainmatter. If you need to use backmatter, these commands provide a variety of options regarding page numbering.</p>
-
-
-<a id="a1.6.2"></a>
-<h4>1.6.2 Special Pages</h4>
-
-
-<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>
-
-<pre class="noindentcmd">\begin{toc} <em>...</em> \end{toc}</pre>
-<p>Specifically designed for a Table of Contents in fiction.</p>
-
-<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{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>
-<p>Used for chapter titles. One line only. May be used more than once.</p>
-
-<pre class="noindentcmd">\ChapterSubtitle{<em>text</em>}</pre>
-<p>Used for chapter subtitles. One line only. May be used more than once.</p>
-
-<pre class="noindentcmd">\ChapterDeco[]{<em>deco code</em>}</pre>
-<p>Used for chapter decorations. One line only. May be used more than once.</p>
-
-<pre class="noindentcmd">\QuickChapter[<em>dash size</em>]{<em>chapter title</em>}</pre>
-<p>Insertwo two blank lines, places the chapter title in the gap using subch font, followed on the same line with an optional, variable-length em dash.</p>
-
-<pre class="noindentcmd">\thispagestyle{<em>choose</em>}</pre>
-<p>Changes whether header/footer appears, for just the current page. This <code>fancyhdr</code> command is re-defined to accept a greater variety of pre-defined styles.</p>
-
-<pre class="noindentcmd">\FirstLine{<em>text</em>}</pre>
-<p>From the <code>magaz</code> package. Places first line of text in small caps. See also <code>\charscale \hangindent</code> commands.</p>
-
-<pre class="noindentcmd">\clearpage</pre>
-<p>Standard LaTeX command for a new full page. In <code>novel</code> you must do it yourself. For a blank page, use <code>\clearpage\thispagestyle{empty}\null</code>.</p>
-
-
-<a id="a1.6.3"></a>
-<h4>1.6.3 Block-Level Breaks and Styling</h4>
-
-<pre class="noindentcmd">\scenebreak</pre>
-<pre class="noindentcmd2">\sceneline</pre>
-<pre class="noindentcmd2">\scenestars</pre>
-<p>Skips a line. The gap will include nothing, a short line, or some asterisks.</p>
-
-<pre class="noindentcmd">\begin{parascale}[<em>scale</em>]...\end{parascale}</pre>
-<p>For an entire paragraph of scaled text. Will disobey line grid. See also <code>\charscale</code> command.</p>
-
-<pre class="noindentcmd">\begin{adjustwidth}{<em>left</em>}{<em>right</em>} <em>...</em> \end{adjustwidth}</pre>
-<p>General-purpose environment for block indenting text, at left and/or right.</p>
-
-
-<a id="a1.6.4"></a>
-<h4>1.6.4 Footnotes and Endnotes</h4>
-
-<pre class="noindentcmd">\footnote[<em>option</em>]{<em>note text</em>}</pre>
-<p>Creates a footnote at the bottom of the page.</p>
-
-<pre class="noindentcmd">\endnote</pre>
-<p>Places an endnote marker. See also <code>\memo</code> command.</p>
-
-<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>
-<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>
-<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>
-<p>Places an image as a block element, in its own space. May share the space with accompanying text.</p>
-
-
-<a id="a1.6.6"></a>
-<h4>1.6.6 General Text Styling</h4>
-
-<p>Note that standard LaTeX font size commands, such as <code>\small</code> and <code>\Large</code>, have no effect in <code>novel</code> class. This is because those commands would conflict with the emphasis on maintaining a constant baseline grid.</p>
-
-<pre class="noindentcmd">\charscale[<em>scale,x,y</em>]{<em>text</em>}</pre>
-<p>Versatile. Scales the text (at most one line), and moves it anywhere, even overlying. See also <code>parascale</code> environment.</p>
-
-<pre class="noindentcmd">{\somefontcommand <em>text</em>}</pre>
-<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>
-<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>
-<p>Place the text to the left of the command insertion point. Sometimes used to move an opening quoation mark, at the start of chapter or lines of poetry.</p>
-
-<pre class="noindentcmd">\acronym{<em>text</em>}</pre>
-<p>Requires NovelDeco font. Caps become "medium" caps, between regular and small.<p>
-
-<pre class="noindentcmd">\decoglyph{}</pre>
-<p>Selects a decorative glyph from the decofont. Glyphs are chosen from a code table. The decorative glyphs in this font (not including its ordinary characters) are shown in file <code>NovelDeco-glyphs.pdf</code>, which can be found in these docs in the <code>extras</code> folder.</p>
-
-<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>
-<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>
-<p>Ignores its argument, which does not print.</p>
-
-<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>
-
-
-<a id="a1.6.7"></a>
-<h4>1.6.7 Some Other LaTeX Commands</h4>
-
-<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>
-
-<pre class="noindentcmd">\allsmcp{<em>text</em>}</pre>
-<p>Both uppercase and lowercase to small caps.</p>
-
-<pre class="noindentcmd">\sups{<em>text</em>}</pre>
-<p>Superscripts. Result depends on whether marker style is real or fake.</p>
-
-<pre class="noindentcmd">\subs{<em>text</em>}</pre>
-<p>Subscripts (scientific inferiors). Result depends on whether marker style is real or fake.</p>
-
-<pre class="noindentcmd">\null</pre>
-<p>Inserts a blank line. Use <code>\clearpage\thispagestyle{empty}\null</code> to create a blank page.</p>
-
-<pre class="noindentcmd">\mbox{<em>text</em>}</pre>
-<p>Puts its contents in a box. Useful for preventing hyphenation.</p>
-
-<pre class="noindentcmd">\makebox[<em>width</em>][<em>alignment</em>]{<em>text</em>}</pre>
-<p>Boxes its contents at defined width and alignment. Useful for horizontal control of contents.</p>
-
-<pre class="noindentcmd">\hspace{<em>length</em>}</pre>
-<p>Creates a horizontal space. Sometimes requires <code>\strut</code> in front.</p>
-
-<pre class="noindentcmd">\vspace{<em>length</em>}</pre>
-<p>Creates a vertical space. Use only with caution, to avoid disturbing baseline grid.</p>
-
-<pre class="noindentcmd">\kern<em>length</em></pre>
-<p>Tweaks the kerning between characters.</p>
-
-<pre class="noindentcmd">\strut</pre>
-<p>Sometimes used to ensure that a line of text maintains its proper height.</p>
-
-<pre class="noindentcmd">\smash{<em>text</em>}</pre>
-<p>The smashed text may overlie other text.</p>
-
-<pre class="noindentcmd">{\centering <em>text</em>\par}</pre>
-<p>Use instead of <code>center</code> environment.</p>
-
-<pre class="noindentcmd">\hfill</pre>
-<p>Inserts as much horizontal space as needed (generally, preceding right-aligned text).</p>
-
-<pre class="noindentcmd">\vfill</pre>
-<p>Inserts as much vertical space as needed (generally, to force text downward on page).</p>
-
-<pre class="noindentcmd">\linebreak</pre>
-<p>Maintains justification of line break. Use with caution.</p>
-
-<pre class="noindentcmd">\enlargethispage{<em>usually -\nbs</em>}</pre>
-<p>Changes height of textblock for one page. Use with caution. Argument typically <code>-\nbs</code>.</p>
-
-<pre class="noindentcmd">\bigemdash[<em>voffset,thickness</em>]</pre>
-<p>Fills a a box with a simulated emdash of variable width.</p>
-
-
-<a id="a1.6.8"></a>
-<h4>1.6.8 Disabled LaTeX Commands</h4>
-
-<p>These commands are disabled or ineffective. Depending on the command, it may silently do nothing, or simply echo its argument, or generate a Warning or Error. Some of these commands are part of standard LaTeX document classes, but others are part of widely-used packages.</p>
-<p>There are other commands that <em>should</em> be disabled, but it is difficult to keep track of all of them. This list only includes some popular commands.</p>
-
-<pre class="noindentcmd">\small \LARGE and other font sizes</pre>
-<p>You may use <code>\charscale</code> or the <code>parascale</code> environment.</p>
-
-<pre class="noindentcmd">\textls</pre>
-<p>For loose tracking, use <code>{\addfontfeature{LetterSpace=<em>number</em>}text}</code> instead.</p>
-
-<pre class="noindentcmd">\includegraphics</pre>
-<p>Use <code>\InsertImage</code> or <code>\BlockImage</code> instead.</p>
-
-<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>
-<p>This ain't no stinking thesis. LaTeX "academic layout" commands don't work.</p>
-
-
-<a id="a1.6.9"></a>
-<h4>1.6.9 Discouraged LaTeX Commands</h4>
-
-<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>
-<p>Perhaps the <code>adjustwidth</code> environment will sui your needs.</p>
-
-<pre class="noindentcmd">center environment</pre>
-<p>You may use <code>{\centering...\par}</code>. In many cases, you can use the center environment, but you must pay attention regarding possible stray space above or below it.</p>
-
-<pre class="noindentcmd">\raisebox</pre>
-<p>You may use <code>\charscale</code> instead.</p>
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-02-class-options.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,194 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a2">2. Document Class Options</a></p>
-
-<ul>
- <li><a href="#a2.1">2.1 draft</a></li>
- <li><a href="#a2.2">2.2 graytext</a></li>
- <li><a href="#a2.3">2.3 shademargins</a></li>
- <li><a href="#a2.4">2.4 cropmarks</a></li>
- <li><a href="#a2.5">2.5 cropview</a></li>
- <li><a href="#a2.6">2.6 closecrop</a></li>
- <li><a href="#a2.7">2.7 xml</a></li>
- <li><a href="#a2.8">2.8 debug</a></li>
- <li><a href="#a2.9">2.9 unblock</a></li>
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p>2. Class Options</p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><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, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<a id="a2"></a>
-<h2 style="clear:none">2. Document Class Options</h2>
-
-
-<p>As with other LaTeX classes, <code>novel</code> is called this way:</p>
-<p><code>\documentclass[options]{novel}</code></p>
-
-<p>As with other document classes, <code>novel</code> chooses a default paper size, and font size, if you do not make the choice. But there, the similarity ends. The default paper size in <code>novel</code> is 5.5" wide by 8.5" high, which is a popular book Trim Size for softcover fiction in the US, and close to the Demy Octavo (C novel) British size. And, the default font size is not an integer point size!</p>
-
-<p>In fact, you <em>cannot</em> set either the paper size or font size in the class options. You set them via other commands, in the Preamble. The commands are explained on other pages of this documentation.</p>
-
-<p>Still, there are a number of class options. As usual, options must be enclosed in braces and be separated by commas.</p>
-
-
-
-<a id="a2.1"></a>
-<h4>2.1 draft</h4>
-
-<p>The word DRAFT will appear at the upper left of each page.</p>
-
-<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>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>
-
-<p>In draft mode, PDF/X compliance is turned off, no matter what you specify.</p>
-
-
-<a id="a2.2"></a>
-<h4>2.2 graytext</h4>
-
-<p>The <code>novel</code> document class is intended for black/white book interiors. Normally, any color command, even gray, will be ignored, and the text will be rendered black. This does not affect images.</p>
-
-<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>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>
-
-<p>With this option enabled, you may place light-shaded text (even white) over a darker background, but this is not recommended. Even though the resulting PDF meets standards, it may not produce an acceptable result when printed, particularly if the text is small. It is better to place dark over light.</p>
-
-
-<a id="a2.3"></a>
-<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>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>
-
-
-
-
-
-
-<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>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 class="code"><code>\SetCropmarkGap{<em>length</em>}</code></p>
-
-<p>The cropmark gap is the distance between the Trim Box and where the crop lines begin. The purpose of the gap is so that the marks do not show on the trimmed paper, if the cut is a little bit off. In all cases, the far end of the cropmarks is 0.5in from the Trim Area. The gap is marked G in this diagram. The length must be least 0pt, and is more typically 0.125in or 0.250in. The default is 0.125in. </p>
-
-<p>If your Trim is placed off-center in the Media, then only one pair of cropmarks will be visible.</p>
-
-
-<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>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>
-
-<p>The accompanying image is the <code>cropview</code> display of the same page that was used to illustrate the <code>cropmarks</code> command. However, you do not need to have cropmarks.</p>
-
-
-<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>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>
-
-
-<a id="a2.7"></a>
-<h4>2.7 xml</h4>
-
-<p>If you request your PDF to comply with PDF/X standards, it will automatically include XMP Metadata that can be seen as document properties in some (mostly professional) PDF reader software. The <code>xml</code> option exports this data with an xml header added, so that it can be independently viewed in software such as a browser.</p>
-
-<p>This option is only for your information; the exported xml file is not necessary. Whether or not you choose this option will not affect the structure or content of your PDF. If you set PDF/X compliance to <code>off</code>, then there will be no exported xml file.</p>
-
-<p>The exported file will be named <code>jobname-XMPasXML.xml</code>, where <code>jobname</code> is the file name of your *.tex document. If you wish to obtain the XMP packet, without the xml header, you can easily do that with a Unicode-compatible text editor. The necessary editing is obvious.</p>
-
-
-<a id="a2.8"></a>
-<h4>2.8 debug (primarily for developer use)</h4>
-
-<p>The <code>novel</code> class has an additional debugging feature. It is primarily intended for developers, but may be helpful to some ordinary users. Do not use this option if your document compiles, because it will clutter the log file with many messages that you do not need.</p>
-
-<p>The use of the <code>debug</code> option is described on documentation page 11.</p>
-
-
-<a id="a2.9"></a>
-<h4>2.9 unblock (primarily for developer use)</h4>
-
-<p>A number of LaTeX packages are known to be incompatible with <code>novel</code>, because "the way those packages do things" conflicts with "the way novel does things." If you attempt to load one of those packages, then the results you get may not be in agreement with the formats and styles described in this documentation, because the other package over-rides some of novel's own macros.</p>
-
-<p>Therefore, at the end of your Preamble, <code>novel</code> reviews the loaded packages, and throws an error message if you included any of them via <code>\usepackage</code> or <code>\RequirePackage</code>. That also applies if you call some other package that chain-loads one of the forbidden packages.</p>
-
-<p>The odds that you will need a forbidden package are small, because they generally pertain to layout for mathematical and academic papers (tables, floats, equations, diagrams, etc.).</p>
-
-<p>If you specify document class option <code>unblock</code> then the list of forbidden packages will be disregarded by <code>novel</code>. Use at your own risk! This option is really intended for the convenience of developers, rather than ordinary users.</p>
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-03-metadata-pdfx.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,295 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a3">3. Metadata, File Data, PDF/X</a></p>
-
-<ul>
-<li><a href="#a3.1">3.1 Definitions of Terms</a>
- <ul>
- <li><a href="#a3.1.1">3.1.1 ISBN Metadata</a></li>
- <li><a href="#a3.1.2">3.1.2 Printed Metadata</a></li>
- <li><a href="#a3.1.3">3.1.3 File (PDF) Data</a></li>
- </ul></li><!-- end 3.1 -->
-<li><a href="#a3.2">3.2 Rules for File Data</a>
- <ul>
- <li><a href="#a3.2.1">3.2.1 Required, Prohibited?</a></li>
- <li><a href="#a3.2.2">3.2.2 Latin-1?</a></li>
- <li><a href="#a3.2.3">3.2.3 TeX Escapes</a></li>
- <li><a href="#a3.2.4">3.2.4 Forbidden Characters</a></li>
- </ul></li><!-- end 3.2 -->
-<li><a href="#a3.3">3.3 File Data Commands</a>
- <ul>
- <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>
- <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>
- <ul>
- <li><a href="#a3.4.1">3.4.1 Compliance Standards</a></li>
- <li><a href="#a3.4.2">3.4.2 Output Intents</a></li>
- <li><a href="#a3.4.3">3.4.3 Built-IN OI Codes</a></li>
- <li><a href="#a3.4.4">3.4.4 Other Output Intents</a></li>
- <li><a href="#a3.4.5">3.4.5 Embed *.icc or Not?</a></li>
- <li><a href="#a3.4.6">3.4.6 Finding *.icc Files</a></li>
- </ul></li><!-- end 3.4 -->
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p>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-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>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-<a id="a3"></a>
-<h2 style="clear:none">3. Metadata, File Data, and PDF/X</h2>
-
-<p>The commands described on this page are used only in the Preamble. </p>
-
-<p>These commands write non-printing information to the PDF file. Some of the information is used to identify and classify the file. Other information is read by the printer, to assist it with printing choices.</p>
-
-<p>Unfortunately, some of the terms have slightly different meaning, depending on whether they are used in the context of printing, book distribution, or E-books. To avoid confusion <em>within this documentation</em> I will use different terms when they mean different things. When you are communicating with your printing and distribution service, take care to ensure that your understanding of terminology is what they really mean.</p>
-
-
-<a id="a3.1"></a>
-<h3 style="clear:none">3.1 Definition of Terms</h3>
-
-<p>This section is more detailed than it needs to be, because my review of various online forums (unrelated to TeX) shows a lot of user confusion.</p>
-
-
-<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>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>
-
-<p>Note: The ISBN refers to your <em>printed book</em>, not to the PDF file. You are not selling copies of the PDF.</p>
-
-
-<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>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>
-
-<p>Some print services may object to artwork that is too fancy, on the grounds that it is difficult to discern the title and author. Although this is very unlikely, it is better to ask before committing resources.</p>
-
-
-<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>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>
-
-
-<a id="a3.2"></a>
-<h3>3.2 Rules for File Data</h3>
-
-<p>File Data must conform to several specifications, in terms of what you may or may not write. Some of the limitations are imposed by the book distribution industry, which stores information in its databases a certain way.</p>
-
-
-<a id="a3.2.1"></a>
-<h4>3.2.1 Required, Prohibited, Optional?</h4>
-
-<p>If PDF/X compliance is required, then you <em>must</em> at least set the title in File Data, using the <code>\SetTitle{}</code> command. Note that this title is not styled in any way.</p>
-
-<p>Some print services require a minimum amount of file data, particularly title and author, which must match the printed and ISBN metadata for these fields. Other services may require that the book's ISBN number, with something like <code>_text</code> added, be used in place of the title (remember that underscore is a special character in LaTeX). Yet other services (for myserious reasons) may require that most or all File Data be omitted! You will have to communicate with your service, and determine their requirements.</p>
-
-<p>Caution: Whether or not you must omit File Data, be sure that any included images are stripped of their own metadata. The procedure is described on <a href="noveldocs-08-images.html#a8.2.2">Page 8</a> of this documentation.</p>
-
-<p>Many print services do not care about File Data, one way or the other. Your PDF is passed through production according to its file name, not its internals. In such a case, assume that title and author are required.</p>
-
-
-<a id="a3.2.2"></a>
-<h4>3.2.2 Limited to Latin-1?</h4>
-
-<p>At least in the USA, your print service may require that File Data be limited to characters in the Latin-1 set. This is because their production and distribution software uses Latin-1 for the database. Note that Latin-1 does not include curly quotes or em dash. You will still be using utf-8 encoding in your document files, but your choice of characters is restricted.</p>
-
-<p>If it were not for the database limitation to Latin-1, you could give your book a Greek or Cyrillic title, because <code>novel</code> can do it, and so can the PDF.</p>
-
-<p>You can still use any printable Unicode character in the text of your book, as long as you use fonts with those characters. In <code>novel</code> there is no <code>\maketitle</code> command, so you may (and should) apply styling to the printed title, even though the File Data title cannot be styled.</p>
-
-
-<a id="a3.2.3"></a>
-<h4>3.2.3 TeX escapes</h4>
-
-<p>In File Data, you must obey the same TeX rules that apply everywhere: Certain characters have special meaning, and must be preceded by a backslash, if you wish to use them as ordinary characters. These are:</p>
-
-<p><code># $ % & _ { }</code> (hash, dollar, percent, ampersand, underscore, left and right curly brackets)</p>
-
-<p>Example: The title <em>Doing 9% & Gone</em> is coded: <code>\SetTitle{Doing 9\% \& Gone}</code></p>
-
-<p>The above characters are rarely needed in File Data. Sometimes they must be spelled out, in order to agree with your book's ISBN Metadata. For example, you may need to write "and" rather than the ampersand.</p>
-
-
-<a id="a3.2.4"></a>
-<h4>3.2.4 Forbidden Characters</h4>
-
-<p>• Do not use the backslash <code>\</code> except to escape the above-listed characters.</p>
-
-<p>• Do not use the tilde <code>~</code> or the circumflex <code>^</code>.</p>
-
-<p>• Do not use TeX code, such as <code>\`e</code> for e with grave; instead paste è directly from a character map.</p>
-
-<p>• Do not use styling, such as {\small text}.</p>
-
-<p>You should not need any kind of quotation marks in File Data. But if you do, use ordinary straight quotes, and ensure that your TeX editor does not automatically substitute curly quotes or TeX code as you type it. Use a straight apostrophe if needed, and ensure that a curly apostrophe is not automatically substituted in your TeX editor. Do not use <code>`</code> or <code>``</code> for left quotes. Do not use two apostrophes for a double quote. Do not use endash or emdash (and do not type multiple hyphens).</p>
-
-
-<a id="a3.3"></a>
-<h3>3.3 File Data Commands</h3>
-
-<p>Now that you understand what File Data means, and how it may be written, you can use commands to write it.</p>
-
-
-<a id="a3.3.1"></a>
-<h4>3.3.1 \SetTitle{}</h4>
-
-<p>If you do not use the <code>\SetTitle{}</code> command, or leave it empty or blank, then the resulting PDF cannot comply with PDF/X standards. In very rare cases, that is desirable. Note that this information is not automatically transferred to your book's title page. It will be used as default in certain page heading styles, but you can over-ride it. The information can be retrieved as <code>\theTitle</code> anywhere in your document.</p>
-
-
-<a id="a3.3.2"></a>
-<h4>3.3.2 \SetAuthor{}</h4>
-
-<p>This information is not automatically transferred to your book's title page. It will be used as default in certain page heading styles, but you can over-ride it. The information can be retrieved as <code>\theAuthor</code> anywhere in your document.</p>
-
-
-<a id="a3.3.3"></a>
-<h4>3.3.3 \SetSubtitle{}</h4>
-
-<p>There is no file data for subtitle! The only reason for using this command is if you wish to later retrieve the information as <code>\theSubtitle</code> in your document.</p>
-
-
-<a id="a3.3.4"></a>
-<h4>3.3.4 Advanced: \SetApplication{} and \SetProducer{}</h4>
-
-<p>The Application, also known as CreatorTool, is the program used to create your source document. Text editors, word processors, and page layout programs are the most common Applications (not particular to TeX). The PDF Producer is the program that converts the source document to PDF. In many cases, the Producer is a back-end, directly linked to the Application.</p>
-
-<p>These details are automatically created when you compile your document, without any input from you. However, if you have the need to provide a custom text string for the Application or Producer, these commands will do it.</p>
-
-
-<a id="a3.4"></a>
-<h3>3.4 \SetPDFX[<em>output intent</em>]{<em>compliance standard</em>} and starred version</h3>
-
-<p>Commercial printers are very likely to require PDF/X compliance. This ensures that your PDF meets a variety of criteria, by containing those things it must contain, and omitting those things it must not contain. Most perfectly valid PDF files are <em>not</em> PDF/X compliant, simply because they are not intended for commercial printing.</p>
-
-<p>If the <code>\SetPDFX</code> command is not used, it is <code>off</code> by default. Note that a non-compliant file is not a defective file! It complies with PDF standards, but not PDF/X standards. Some print services insist on PDF/X, and others don't care as long as the fonts are embedded (which they always are).</p>
-
-
-<a id="a3.4.1"></a>
-<h4>3.4.1 Compliance Standard</h4>
-
-<p>The following choices are available:</p>
-<p><code>X-1a:2001</code></p>
-<p><code>X-1a:2003</code></p>
-<p><code>X-3:2002</code></p>
-<p><code>X-3:2003</code></p>
-<p><code>off</code></p>
-
-<p>The first of these is the one that is most widely accepted in commercial printing. Anything meeting <code>X-1a:2001</code> necessarily meets the other standards. If your book involved complicated color artwork, then the correct choice might be crucial. But for a black and white book block, <code>X-1a:2001</code> is the preferred choice unless your print service says otherwise.</p>
-
-
-<a id="a3.4.2"></a>
-<h4>3.4.2 Output Intent</h4>
-
-<p>Unless compliance is <code>off</code>, an Output Intent is always required. However, <code>novel</code> treats this as an optional argument, because it will automatically use <code>CGATSTR001</code> as default Output Intent. Technically the name is CGATS TR 001 (with spaces), and it is known as "US Web Coated SWOP v2" in the U.S.A., where it is the most commonly-accepted Output Intent standard.</p>
-
-<p>Output Intent informs the printer that you "intend" your PDF to be printed according to certain printer capabilities. If you took the trouble to soft-proof your PDF on a color-controlled monitor using color managed software, and if the printer's capabilities actually correspond to the intent, then you can expect that the printed result will closely match what you expected. This is very important in commercial color printing, but nearly irrelevant for a black and white book block. Nevertheless, an Output Intent is required to meet PDF/X compliance.</p>
-
-
-<a id="a3.4.3"></a>
-<h4>3.4.3 Built-in Output Intent Codes</h4>
-
-<p>There are three pre-defined choices:</p>
-<p><code>CGATSTR001</code> (default)</p>
-<p><code>FOGRA39</code></p>
-<p><code>JC200103</code></p>
-<p>The first of these, more properly named "CGATS TR 001" with spaces, is also known as "US Web Coated SWOP v2" in the USA, and is the most commonly-used American print standard for this kind of book. The second is widely used in Europe, the third in Japan.</p>
-
-
-<a id="a3.4.4"></a>
-<h4>3.4.4 Other Output Intents</h4>
-
-<p>If you are required to use an Output Intent that is not one of the above three, then you have to code it yourself. Have a look at the three pre-configured Output Intents (files novel-CGATSTR001.clo, novel-FOGRA39.clo, and -novel-JC200103.clo). Instructions are inside the files. There are several places where you can find the necessary data; the most comprehensive is at www.color.org.</p>
-<p>In essence: If you create a custom Output Intent file named <em>novel-MyFunkyPrinter.clo</em>, then you request <code>MyFunkyPrinter</code> (without the preceding novel- or the .clo extension) as Output Intent, and that file will be loaded.</p>
-
-
-<a id="a3.4.5"></a>
-<h4>3.4.5 Whether or Not to Embed *.icc</h4>
-
-<p>Each Output Intent has a corresponding color profile, in the form of a file with extension <code>*.icc</code>. You usually do not need it. In fact, unless your print service specifically asks you to embed the file, don't do it. When you use <code>\SetPDFX</code> in its un-starred form, the *.icc file will not be embedded.</p>
-
-<p>If your print service demands that you embed the *.icc color profile, then use <code>\SetPDFX*</code> (with the asterisk).</p>
-
-<p>Repeat: Do not embed the *.icc color profile unless specifically requested by your print service, for a non-color book block.</p>
-
-<p>If your printer requests "US Web Coated SWOP v2" and, as usual, requests that you <em>not</em> embed the corresponding *.icc color profile, then some software will read the Output Intent as "CGATS TR 001" instead of "US Web Coated SWOP v2". This is compliant. But not everyone knows this.</p>
-
-
-<a id="a3.4.6"></a>
-<h4>3.4.6 Where to Find *.icc Files</h4>
-
-<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> [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>
-<p>You want printer profiles, usually CMYK. Don't worry about the files being "for Windows," as they are actually cross-platform.</p>
-<p>If your system has the necessary <code>*.icc</code> file for your Output Intent, but <code>novel</code> cannot find it, then copy the file to the same folder as your TeX document.</p>
-<p>Again: Do not embed the file unless the printer requests it.</p>
-
-
-
-
-
-
-</div><!-- end main -->
-
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-04-layout.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,379 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a4">4. Book Size and Page Layout</a></p>
-
-<ul>
-
- <li><a href="#a4.1">4.1 Book Design Terminology</a>
- <ul>
- <li><a href="#a4.1.1">4.1.1 Sheet, Page, Leaf, Folio</a></li>
- <li><a href="#a4.1.2">4.1.2 Spread, Recto, Verso, Line Grid</a></li>
- <li><a href="#a4.1.3">4.1.3 Perfect Binding, Spine, Signature</a></li>
- <li><a href="#a4.1.4">4.1.4 Gutter</a></li>
- <li><a href="#a4.1.5">4.1.5 Trim Size, Margins, Live Area</a></li>
- <li><a href="#a4.1.6">4.1.6 Media Size, TrimBox</a></li>
- <li><a href="#a4.1.7">4.1.7 Arrrgh... Word Processors</a></li>
- </ul>
- </li><!-- end 4.1 -->
-
-
- <li><a href="#a4.2">4.2 Layout Commands</a>
- <ul>
- <li><a href="#a4.2.1">4.2.1 \SetTrimSize{}{}</a></li>
- <li><a href="#a4.2.2">4.2.2 \SetMargins{}{}{}{}</a></li>
- <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.7">4.2.7 \SetMediaSize[]{}{}</a></li>
- <li><a href="#a4.2.8">4.2.8 \SetCropmarkGap{}</a></li>
- </ul>
- </li><!-- end 4.2 -->
-
-
- <li><a href="#a4.3">4.3 Emergency Clinic: Rework</a>
- <ul>
- <li><a href="#a4.3.1">4.3.1 \ReworkTrimSize{}{}</a></li>
- <li><a href="#a4.3.2">4.3.2 \ReworkMargins{}{}{}{}</a></li>
- <li><a href="#a4.3.3">4.3.3 Example of Rework</a></li>
- <li><a href="#a4.3.4">4.3.4 Limitations of Rework</a></li>
- </ul>
- </li><!-- end 4.3 -->
-
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p>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-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>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<a id="a4"></a>
-<h2 style="clear:none">4. Book Size and Page Layout</h2>
-
-<p><b>Overview</b></p>
-
-<p>There are many layout settings available, but you do not have to use them all. In fact, you may not need to use any of them! Your <code>novel</code> is pre-configured with settings that will often be suitable for the 5.5"W x 8.5"H Trim Size that is widely used in the American softcover fiction market.</p>
-
-<p>If you choose a different Trim Size, then some of the other defaults will be tweaked, so that your starting point is reasonable for the requested size.</p>
-
-<p>This page begins with a review of phyysical book design, then continues to the <code>novel</code> commands that set the dimensions.</p>
-
-
-
-<a id="a4.1"></a>
-<h3>4.1 Book Design Terminology</h3>
-
-<p>If you are preparing a PDF for the print-on-demand (P.O.D.) market, and I assume you are, then you need to understand how terms are used in the <code>novel</code> document class (and LaTeX in general). Sadly, most authors in P.O.D. use an ordinary word processor, particularly MS Word. For that reason, many print services, and most online user forums, refer to the terminology and settings of MS Word, rather than to the meanings in traditional book publishing. In the case of images, Photoshop settings are often described. And, the more advanced authors may be using InDesign. Yes, there are authors using LaTeX and GIMP (I am among them), but they are not the ones who make the most noise. If you visit web sites and forums devoted to LaTeX, they primarily address the concerns of academic writers, particularly mathematicians, because that is the target user base for LaTeX.</p>
-
-<p>Here, I will present a brief overview of what key terms mean. In some cases, I will also describe how the same terms mean different things, to those who use other software. Pay attention!</p>
-
-
-<a id="a4.1.1"></a>
-<h4>4.1.1 Sheet, Page, Leaf, Folio, Imposition</h4>
-
-<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>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>
-
-<p>Caution, The term "folio" has several different meanings, even in the narrow field of book publishing. It may refer to folded paper, as mentioned above. Or it may refer to a particular sheet size of paper ("foolscap"). Or, it may simply refer to the number printed on a page. This last use of "folio" will be discussed in the context of headers and footers.</p>
-
-
-<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>
-
-
-<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>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>
-
-
-<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>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>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>
-
-<p><b>Margins</b> are required on all four edges of the page. They do not have to be the same width. Generally the margin at the spine edge (inside margin) is wider.</p>
-<p>The accompanying illustration shows a typical recto page, on a layout with header and footer. The margins have been shaded gray in the picture (but, not in the book). The inside (spine) margin is at the left of this page. In the case of fiction, where there are no marginal notes, it is typically the case that the inside margin is the widest. But this is not a rule for all books. All that is required is that each margin be "wide enough" for the printing process.</p>
-
-<p>Keep in mind that the print services are not used to seeing books with exotic margins (such as bottom margin twice the size of top margin). They may think that there is a mistake in your PDF, or in the print job, if you do that.</p>
-
-<p>The header and footer, along with the textblock, are in the <b>live area</b> bounded by the margins.</p>
-
-<p>Normally, your TeX document will be compiled to a PDF that is electronically at the exact Trim Size. And normally, print services want it to be that way. When you view your PDF, the text will shift from side to side as you move through the pages, due to the slightly increased margin at the spine edge.</p>
-
-
-<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>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>
-
-
-<a id="a4.1.7"></a>
-<h4>4.1.7 Arrrgh... Word Processors</h4>
-
-<p>Alas, it seems to be the case that in the print-on-demand market, most PDF files come straight from MS Word or some other word processor. The authors have little understanding of the technology, so the print services provide them with instructions that specifically pertain to a word processor. It gets worse: If you communicate with the print service, your question may be answered by someone who has never used any software other than MS Word, and does not know much beyond how to make menu choices in that program (which are different for each new version of the software, of course). Or, a more informed advisor might know InDesign.</p>
-<p>In such a case, for a 5.5" x 8.5" book Trim Size with 0.5" margins at top, outside, and bottom, and 0.75" at the spine edge, you might be offered advice like this: <em>On page size 8.5" x 11" with mirror-margins layout, set the top and bottom margins to 1.75", the outside margin to 2", and the inside margin to 2.25".</em> That advice means: Media Size 8.5" x 11". Unspecified Trim Size, but the printer knows you want 5.5" x 8.5" because you signed up for it; someone at the receiving end will add that instruction to your PDF file. The MS Word "margins" are the actual TeX book margins <em>plus</em> the trimmed-away paper that surrounds the Trim Size.</p>
-<p>So, be alert. And remember that even if you are reading advice on a TeX-oriented forum, the advice is likely to pertain to some other document class. The way that dimensions are set in <code>novel</code> may not be the same as the way they are set in other classes.</p>
-
-
-
-<a id="a4.2"></a>
-<h3>4.2 Layout Commands</h3>
-
-<p>Now that you understand how the terms are used, you are ready to use <code>novel</code> layout commands.</p>
-
-<p>Remember that everything is pre-configured, specifically for the purpose of fiction. You only need to write a layout command if you don't like the defaults.</p>
-
-
-
-<a id="a4.2.1"></a>
-<h4 style="clear:none">4.2.1 \SetTrimSize{<em>width</em>}{<em>height</em>}</h4>
-
-<p>Command <code>\SetTrimSize{}{}</code> sets the size of your book. Both values must be written, using units such as <code>in</code> or <code>mm</code>. If you do not use this command, the default Trim Size will be the widely-used 5.5in wide x 8.5in high.</p>
-
-<p>This setting is most crucial. Unless your book is very exceptional, its Trim Size will be one of several standard sizes available from the print service. Among those sizes, only one or two will be "standard" for your genre.</p>
-
-<p>Do not request a <em>mass-market paperback</em> size unless you really, truly, know what you are doing. Since you are not a major writer for a major publishing house, you don't know; so, don't do it.</p>
-
-<p>In the U.S.A., a Trim Size of 5.5"W x 8.5"H is widely used for print-on-demand fiction, with a slightly smaller size being a second choice. The larger 6"W x 9"H is more often used for non-fiction. If you also intend to have a hardcover edition, then that may affect your choice for softcover as well (but see the <code>\Rework</code> commands, below). Be aware that in your market, hardcover books are not like the ones you see in the library, which use a more expensive binding method.</p>
-
-
-<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>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>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>
-
-
-<a id="a4.2.3"></a>
-<h4>4.2.3 \SetFontSize{<em>length</em>}</h4>
-
-<p>In the <code>novel</code> document class, you do not set point size as a class option. Instead you use <code>\SetFontSize</code> in the Preamble.</p>
-<p>The size may be any units TeX understands, including decimal values. So, <code>11.8bp</code> and <code>12.1pt</code> are acceptable. This is because you will be using scalable, Open Type and TrueType fonts throughout your document. They do not need TeX metrics.<p>
-<p>If you insist on using ancient TeX fonts, then you may need to specify a convenient integer font size such as 11pt or 12pt. But why? Forget those fonts! Welcome to the Twenty-First Century.</p>
-<p>The minimum normal font size is 8pt, and the maximum is 18bp. On a local basis, text may be larger or smaller than this.</p>
-
-
-<a id="a4.2.4"></a>
-<h4>4.2.4 \SetLinesPerPage{<em>integer</em>}</h4>
-
-<p>Lines per page refers only to the textblock, and does <em>not</em> include header/footer. Lines are not stretched to fill short pages.</p>
-
-<p>By default, a suitable number of lines per page are set, based on other dimemsions. You can change the default with this command. Any non-integer will be rounded. There is no direct command to set the <em>leading</em>, also known as line-to-line spacing or <em>baselineskip</em>. Instead, is is calculated from the textblock height and number of lines.</p>
-
-<p>If the calculated leading is less than 1.2x the font size, an error will result. It is difficult for TeX to honor all layout settings with such a small leading, which would normally be unacceptable for fiction in any case. If the calculated leading is at least 1.2x the font size, but less than 1.25x the font size, then the log file will have an Alert message, suggesting that you should consider using fewer lines per page. If the leading exceeds 1.4x the font size, then the log will have an Alert, suggesting more lines per page. The Alert messages are friendly; you do not necessarily have to do anything.</p>
-
-
-<a id="a4.2.5"></a>
-<h4>4.2.5 \SetHeadFootStyle{<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>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>\SetHeadFootStyle</code> to choose the closest available style, then use <code>fancyhdr</code> commands for your custom style. The reason is that <code>\SetHeadFootStyle</code> tells the layout engine how much space it needs to reserve.</p>
-
-
-<a id="a4.2.6"></a>
-<h4>4.2.6 \SetHeadJump{<em>number</em>} and \SetFootJump{<em>number</em>}</h4>
-
-<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>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>
-
-<p>The maximum is 3, minimum 1. The two jumps do not need to be identical. If your layout does not have a header and/or footer, then the corresponding setting does not matter.</p>
-
-<p>Don't worry about <em>headheight</em>. Whether you like it or not, headers (if used) will have only one line, and footers (if used) will have only one line. The necessary heights are calculated automatically.</p>
-
-
-<a id="a4.2.7"></a>
-<h4>4.2.7 Advanced: \SetMediaSize[<em>alignment</em>]{<em>width</em>}{<em>height</em>}</h4>
-
-<p>Normally, the book Trim Size will also set the same size for the PDF pages. What you see is what you get.</p>
-
-<p>Some print services prefer that the Trim Size be floated in a standard paper size, such as US Letter or A4. That's not a technical necessity, but "the way things are done around here." If you must do that, use the <code>\SetMediaSize</code> command.</p>
-
-<p>The width and height must be specified with units, such as <code>in</code> or <code>mm</code>. If the optional <em>alignment</em> is not specified, then The Trim Size will be centered horizontally and vertically in the Media Size. That is the preferred method.</p>
-
-<p>If you write <code>edge</code> for the optional alignment, then the Trim Size will be off-center in the Media Size. Do not do this unless your print service specifically wants it that way. If you are making a hand-made book with a home printer, then this option might be convenient.</p>
-
-<p>Note that margins are measured relative to the Trim Size, not the Media Size. The extra white space between Trim Size and Media Size is just that: extra white space, unrelated to the margins of your book.</p>
-
-<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 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>
-
-
-<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>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>
-
-<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>
-<p>But if you re-size the book and don't knock the margins down, then the text width and height won't be the same. Your text doesn't fit the way it used to. All your lines re-flow, the page breaks are different, and all that work you put into getting just the right appearance must be re-done.</p>
-<p><em>Oh, nooooo ...</em></p></div>
-
-<p>Relax. Here is all you need to do: add <code>\ReworkTrimSize{5.06in}{7.81in}</code>. That's it. Your existing margins will be preserved. The font size, and line skip, will be cleverly re-scaled to fit the new dimensions. Paragraphs and pagination are the same as before.</p>
-
-<p>There are two Rework commands available. One changes the Trim Size without changing the margins. The other changes the margins without changing the Trim Size. If you wish to change both Trim Size and margins, you may use both commands.</p>
-
-
-<a id="a4.3.1"></a>
-<h4>4.3.1 \ReworkTrimSize{<em>width</em>}{<em>height</em>}</h4>
-
-<p>This command changes the <em>existing</em> Trim Size. If you do not use the <code>\SetTrimSize</code> command, then the existing Trim Size is the default. But if you do use <code>\SetTrimSize</code>, then you must leave that command as-is, and place <code>\ReworkTrimSize</code> later in the Preamble.</p>
-<p>If you used <code>\SetMediaSize</code>, you may leave that command as-is, or change it if you wish; the Trim Size does not care.</p>
-
-
-<a id="a4.3.2"></a>
-<h4>4.3.2 \ReworkMargins{<em>top</em>}{<em>outside</em>}{<em>bottom</em>}{<em>inside</em>}</h4>
-
-<p>This command changes the <em>existing</em> margins. If you do not use the <code>\SetMargins</code> command, then the existing margins are the defaults. But if you do use <code>\SetMargins</code>, then you must leave that command as-is, and place <code>\ReworkMargins</code> later in the Preamble.</p>
-
-
-<a id="a4.3.3"></a>
-<h4>4.3.3 Example of Rework</h4>
-
-<p>Here is an example of the Rework commands in use. When the layout is reworked, the font size and (if necessary) baseline skip is scaled to fit the new dimensions, in a way that preserves the original paragraphs and pagination. This is done in a single pass: The method simultaneously works and re-works the layout.</p>
-<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>
-\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>Result 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>
-<h4>4.3.4 Limitations of Rework</h4>
-
-<p>• The technique has been tested, but it might not always work. Be sure to inspect the result carefully.</p>
-
-<p>• If you use Rework to make a radical size change, then the resulting font size or line skip might be unattractive.</p>
-
-<p>• If the reworked pages have one less line than expected (or one more), this is due to roundoff in the calculations. It can usually be fixed by adding or substracting as little as <code>0.001\nbs</code> from the top or bottom rework margin.</p>
-
-<p>• 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> Good: <code>\hspace{0.5em}</code><br>
-Bad: <code>\kern1pt</code> Good: <code>\kern.08em</code><br>
-Bad: <code>\vspace{0.5in}</code> Good: <code>\vspace{2.4\nbs}</code>
-</p>
-
-<p>• When you use <code>\Rework</code>, images are <em>not</em> scaled. Thus, they will have a different relationship to the surrounding text than they did before. In many cases, this is not a problem. However, an un-scaled image may disrupt the flow of text, or the number of lines in a page, or overlap text that was previously cleared. Look in the log file for an Alert message, which suggests an appropriate image scale, depending on how an image was placed. Problem areas can often be fixed be scaling the related image(s) in an external graphics program (see <a href="noveldocs-08-images.html#a8.3.3">Page 8</a>) then re-compiling with the scaled image(s).</p>
-<p>• Note that you may see the Alert whether or not there are problem images, so scaling images will not make the Alert go away. It is a friendly message.</p>
-
-
-<div style="clear:both"></div>
-
-
-
-
-
-
-
-
-
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-05-fonts.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,631 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a5">5. Fonts</a></p>
-
-
-<ul>
-
-<li><a href="#a5.1">5.1 Parent Font and Descendants</a>
- <ul>
- <li><a href="#a5.1.1">5.1.1 Map of Font Positions</a></li>
- <li><a href="#a5.1.2">5.1.2 Text Font</a></li>
- <li><a href="#a5.1.3">5.1.3 Chapter Font</a></li>
- <li><a href="#a5.1.4">5.1.4 Subch Font</a></li>
- <li><a href="#a5.1.5">5.1.5 Head Font</a></li>
- </ul>
-</li><!-- end 5.1 -->
-
-<li><a href="#a5.2">5.2 Other Pre-Defined Fonts</a>
- <ul>
- <li><a href="#a5.2.1">5.2.1 Sans and Mono Fonts</a></li>
- <li><a href="#a5.2.2">5.2.2 Math Font: Forget It</a></li>
- <li><a href="#a5.2.3">5.2.3 Deco Font</a></li>
- </ul>
-</li><!-- end 5.1 -->
-
-<li><a href="#a5.3">5.3 Defining New Fonts</a></li>
-
-<li><a href="#a5.4">5.4 Font Customization Syntax</a>
- <ul>
- <li><a href="#a5.4.1">5.4.1 Font Family vs. File Name</a></li>
- <li><a href="#a5.4.2">5.4.2 Set/New by Family/Filename</a></li>
- <li><a href="#a5.4.3">5.4.3 Open Type Features</a><br>
- <span style="visibility:hidden">5.4.3 </span>kerning, ligatures, numbers,<br>
- <span style="visibility:hidden">5.4.3 </span>letters, and many others</li>
- <li><a href="#a5.4.4">5.4.4 Scale Pseudo-Feature</a></li>
- <li><a href="#a5.4.5">5.4.5 Color and Opacity</a></li>
- <li><a href="#a5.4.6">5.4.6 \CreateFeature{}{}</a></li>
- <li><a href="#a5.4.7">5.4.7 Local Feature Changes</a></li>
- </ul>
-</li><!-- end 5.4 -->
-
-<li><a href="#a5.5">5.5 Shopping for Fonts</a>
- <ul>
- <li><a href="#a5.5.1">5.5.1 Licensing Issues</a></li>
- <li><a href="#a5.5.2">5.5.2 Technical Issues</a></li>
- <li><a href="#a5.5.3">5.5.3 Appearance Issues</a></li>
- </ul>
-</li><!-- end 5.5 -->
-
-</ul>
-
-
-
-
-<p> </p>
-
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="a5"></a>
-
-
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p>5. Choosing Fonts</p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><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, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<h2 style="clear:none">5. Fonts</h2>
-
-<p>This page describes how to choose fonts and font features, and how to apply fonts within your document.</p>
-
-<p>If you are looking for information about how to specify the main text point size, see <a href="noveldocs-04-layout.html#a4.2.3">Page 4</a>.</p>
-
-<p>If you are looking for information about how to change the size of text within the body of your document, or about how to style text (such as italics), then see <a href="noveldocs-07-text-size-style.html">Page 7</a>.</p>
-
-<p><b>EEEK!</b> If you are like me, you <em>first</em> try to do something the way you did it before, then when it fails, you <em>finally</em> read the instructions. So, before you came to this page, you tried these things, and none of them worked:</p>
-
-<p class="code"><code>
-\usepackage{somefont} % FAILS!<br>
-\renewcommand\rmdefault{smf} \normalfont % FAILS!<br>
-\setmainfont{Some Font} % FAILS!
-</code></p>
-
-<p><b>DON'T PANIC.</b> In <code>novel</code>, the essential fonts are specified with different code. Fortunately, they are all pre-configured. If you accept the carefully-chosen defaults, then you do not need to worry about fonts. You do not even need to specify the font families. Sit back and relax.</p>
-
-<p>Or, you can do something like this, if you have the font license. Then let <code>novel</code> do the rest:</p>
-
-<p class="code"><code>\SetParentFont{Adobe Garamond Pro} % WORKS!</code></p>
-
-<p><b>It's that simple.</b> But TeX being what it is, there are complicated ways to customize things. The rest of this page shows you how to do it. You will be using Open Type fonts, or perhaps TrueType fonts. Forget the old Type 1 fonts.</p>
-
-
-<a id="a5.1"></a>
-<h3>5.1 The Parent Font and Descendants</h3>
-
-<p>In <code>novel</code>, you do not directly set the default font, or the main font, or the roman font, or whatever. Instead, you set the parent font. The command:</p>
-
-<p class="code"><code>\SetParentFont[optional,features]{Font Family}</code></p>
-
-<p>The parent font, or <em>parentfont</em>, is the ancestor of several other fonts, wich will use the same font family unless you manually set them to something else:</p>
-
-<p class="centerimg"><img src="html-resources/font-tree.png" width="600" height="150" alt="parent and descendant fonts"></p>
-
-<p>The <em>parentfont</em> has TeX ligatures and kerning, applied by default. All of the descendant fonts will also have TeX ligatures and kerning. (Note: TeX ligatures allow you to type <code>``</code> to get “ and so forth.)</p>
-
-<p>If you specify any optional features for the <em>parentfont</em>, they will automatically be applied to descendants: <em>textfont</em>, <em>chapterfont</em>, <em>subchfont</em>, and <em>headfont</em>.</p>
-
-<p>If you do not set the <em>parentfont</em> yourself, then the following will be used as default, in order of priority: <em>Libertinus Serif</em>, <em>Linux Libertine O</em>, <em>Latin Modern Roman</em>.
-
-<p>The <em>Libertinus Serif</em> fonts are well-suited to fiction. If in doubt, use them. They can be downloaded as TeX <code>libertinus</code> package, but do not write <code>\usepackage{libertinus}</code> in your Preamble. Those fonts are a more up-to-date fork of the <em>Linux Libertine O</em> fonts, which are in the <code>libertine</code> package. Alas, even though <em>Latin Modern Roman</em> is a fine font, its style and weight are not well-suited to fiction; the only reason they are a last-choice default, is because just about every TeX system has them.</p>
-
-<p style="font-size:small">Note: In class version 1.0.10 and earlier, the <em>parentfont</em> was known as the <em>masterfont</em>, and the <em>textfont</em> was known as the <em>mainfont</em>. For backwards compatibility, both will work.</p>
-
-
-
-<a id="a5.1.1"></a>
-<h4>5.1.1 Map of Font Positions</h4>
-
-<p>The <em>parentfont</em> is not directly used, anywhere in your document. Instead, its descendants are specialized for use in different situations. Here is a typical page spread, using some of the pre-configured choices for chapters and headings:</p>
-
-<p class="centerimg"><img src="html-resources/fonts-in-use.png" width="532" height="408" alt="fonts in use"></p>
-
-<p>If you use the <code>novel</code> pre-configured style commands, then the correct font will automatically be applied. That is the recommended, no-brainer method. If instead you choose to write your own custom styles, then you will also need to specify the fonts; but this allows you more TeX coding flexibility.</p>
-
-
-
-<a id="a5.1.2"></a>
-<h4>5.1.2 The Text Font</h4>
-
-<p>The text font, or <em>textfont</em>, is the default main font used used for ordinary, flowing text. It uses the <em>parentfont</em>, with added features: common ligatures, and oldstyle numbers.</p>
-
-<p>Common ligatures (the Open Type <em>liga</em> feature) are such things as replacing f<span style="position:relative; left:2px">f</span> with the single character ff. Oldstyle numbers are designed to blend with surrounding text. Not every font has these features; if they are missing, then whatever the font actually has, is used instead.</p>
-
-<p>Normally, you do not need to call the <em>textfont</em> explicity, because it is the default for ordinary text. But in the event that you have a small passage in <em>textfont</em>, within a passage in some other font, you can do this:</p>
-
-<p class="code"><code>{\textfont <em>text</em>}</code></p>
-
-<p>Note that <code>{\textfont <em>text</em>}</code> and <code>{\rmfamily <em>text</em>}</code> mean the same thing.</p>
-
-<p>You do not set the <em>textfont</em> itself. It inherits from the <em>parentfont</em>.</p>
-
-
-
-
-<a id="a5.1.3"></a>
-<h4>5.1.3 The Chapter Title Font</h4>
-
-<p>The <code>novel</code> command <code>\ChapterTitle{<em>text</em>}</code> automatically styles its text in the <em>chapterfont</em>.</p>
-
-<p>If you write custom code for chapter titles, then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
-
-<p class="code"><code>{\chapterfont <em>text</em>}</code></p>
-
-<p>You may customize the <em>chapterfont</em>:</p>
-
-<p class="code"><code>\SetChapterFont[optional,features]{Font Family} % Note command case!</code></p>
-
-<p>If you do not use the above command to customize the <em>chapterfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 1.6 scale.</p>
-
-
-
-<a id="a5.1.4"></a>
-<h4>5.1.4 The Chapter Subtitle Font</h4>
-
-<p>The <code>novel</code> commands <code>\ChapterSubtitle{<em>text</em>}</code> and <code>\QuickChapter{<em>text</em>}</code> automatically style their text in the <em>subchfont</em>.</p>
-
-<p>If you write custom code for chapter subtitles or quick chapters, then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
-
-<p class="code"><code>{\subchfont <em>text</em>}</code></p>
-
-<p>You may customize the subchfont:</p>
-
-<p class="code"><code>\SetSubchFont[optional,features]{Font Family} % Note command case!</code></p>
-
-<p>If you do not use the above command to customize the <em>subchfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 1.2 scale.</p>
-
-
-
-<a id="a5.1.5"></a>
-<h4>5.1.5 The Header/Footer Font</h4>
-
-<p>The <code>novel</code> pre-configured header/footer layouts automatically style their text in the <em>headfont</em>.
-
-<p>If you write a customer header/footer layout (using <code>fancyhdr</code> syntax), then whether or not you use this font is your choice. It is not automatic. If you wish to use it:</p>
-
-<p class="code"><code>{\headfont <em>text</em>}</code></p>
-
-<p>You may customize the headfont:</p>
-
-<p class="code"><code>\SetHeadFont[optional,features]{Font Family} % Note command case!</code></p>
-
-<p>If you do not use the above command to customize the <em>headfont</em>, then by default it will be the <em>parentfont</em> with added features: Lining numbers, and 0.92 scale.</p>
-
-
-
-
-
-<a id="a5.2"></a>
-<h3>5.2 Other Pre-Defined Fonts</h3>
-
-<p>There are also a few pre-defined font commands that are "unrelated to" the <em>parentfont</em>.</p>
-
-
-<a id="a5.2.1"></a>
-<h4>5.2.1 Sans and Mono Fonts</h4>
-
-<p>You probably do not need a sans-serif or monospaced font in a work of fiction. The most prominent exception might be headers/footers, where the use of a light sans-serif font is fashionable. But in that case, set the <em>headfont</em> to the desired sans-serif font, instead of inheriting from <em>parentfont</em>.</p>
-
-<p>The <code>novel</code> class does not have its own commands for setting or using sans-serif or monospaced fonts. If you wish, you may use ordinary <code>fontspec</code> syntax to set them:</p>
-
-<p class="code"><code>
-\setsansfont[optional,features]{Font Family}<br>
-\setmonofont[optional,features]{Font Family}
-</code></p>
-
-<p>Then, you may use them with ordinary LaTeX commands:</p>
-
-<p class="code"><code>
-{\sffamily <em>sans-serif text</em>}<br>
-{\ttfamily <em>monospaced text</em>}
-</code></p>
-
-<p>If you do not set these fonts, then the defaults are: <em>Libertinus Sans</em>, or <em>Linux Biolinum O</em>, or <em>Latin Modern Sans</em> for the sans-serif font; <em>Libertinus Mono</em>, or <em>Linux Libertine Mono O</em>, or <em>Latin Modern Mono</em> for the monospaced font.</p>
-
-
-
-<a id="a5.2.2"></a>
-<h4>5.2.2 Math Font: Forget It!</h4>
-
-<p>The <code>novel</code> class is not set up to do math. Seriously.</p>
-
-<p>Nevertheless, TeX being what it is, there is a behind-the-secene choice of a math font, which (hopefully) your document will never use. The code automatically looks for <em>Libertinus Math,</em> or <em>Asana-Math</em>, or <em>Latin Modern Math</em>.</p>
-
-<p>Otherwise, there is no special command for choosing a math font, and no special command for using it. Proof left to student.</p>
-
-
-
-<a id="a5.2.3"></a>
-<h4>5.2.3 The Deco Font</h4>
-
-<p>The <code>novel</code> class ships with its own custom font, <em>NovelDeco.otf</em>. This Open Type font is specifically designed to provide a number of decorative glyphs, and some other characters. It is <em>not</em> a general-purpose font, and can <em>not</em> be replaced by any other font, except by a modified version of <em>NovelDeco</em>.</p>
-
-<p>The <em>decofont</em> is automatically configured. You do not need to set it. However, if you use a font editor to create a modified version, then your modification must have a different font name (to avoid confusion with the original). In such a rare case, you may point to your modified font like this:</p>
-
-<p class="code"><code>\SetDecoFont[optional,features]{YourDecoFont}</code></p>
-
-<p>The <em>decofont</em> is automatically called by other commands, such as <code>\decoglyph{}</code> and <code>\acronym{}</code>. Normally you do not request <em>decofont</em> directly. But if you wish to do so:</p>
-
-<p class="code"><code>{\decofont <em>text</em>}</code></p>
-
-<p>The decorative glyphs in this font (not including its ordinary characters) are shown in file <code>NovelDeco-glyphs.pdf</code>, which can be found in these docs in the <code>extras</code> folder.</p>
-
-
-
-
-<a id="a5.3"></a>
-<h3>5.3 Defining New Fonts</h3>
-
-<p>You can define new font commands. The syntax depends on whether the new font is part of a family (where you might have bold and italic variants), or just a single file (no variants). If part of a family, use <code>\NewFontFamily</code>. If alone, use <code>\NewFontFace</code>.</p>
-
-<p>Note that if you define a font <em>family</em> when you should have just defined a font <em>face</em>, there will be complaints in the log file, because the font loaded cannot find the (nonexistent) other members of the family. But the document will compile. On the other hand, if you define a font <em>face</em> when you should have defined a font <em>family</em>, then commands for bold or italic will have no effect, since the other family members were not loaded. Again, the document will compile.</p>
-
-<p>The <code>\NewFontFamily</code> command (or <code>\NewFontFace</code>) takes three arguments: First, the name of the new font command is required. Second, font features are optional. Third, the font name is required.</p>
-
-<p style="margin-top:16px"><b>Example:</b> Suppose your work is science fiction, and one if its characters is a talking robot. You wish to depict its utterances in a robotic-looking font, which will be called using a new <code>\robovoice</code> command. You shop around, and find that the <em>Orbitron</em> font suits your purpose, except that it is too large compared to your <em>textfont</em>. So, you scale it.</p>
-
-<p>In the Preamble, you define the new font command:</p>
-
-<p class="code"><code>\NewFontFace\robovoice[Scale=0.8]{Orbitron} % not part of a family</code></p>
-
-<p>After some experimentation, you realize that the <code>\robovoice</code> letters need to be spread apart a bit. This is accomplished using the standard LaTeX <code>\textls</code> command.</p>
-
-<p>In the document body:</p>
-
-<p class="code"><code>
-``Want some oil?'' asked Captain Withens.\par<br>
-\textls{\robovoice ``Is it Gamma-42 Special oil?''} asked the robot.\par<br>
-``No, I got it on sale at Cosmo-Mart.''\par<br>
-\textls{\robovoice ``Forget it. I'm an oil gourmet.''}\par
-</code></p>
-
-<p>The result:</p>
-
-<p class="centerimg"><img src="html-resources/human-robot-talk.png" width="483" height="127" alt="conversation, human-robot"></p>
-
-<p>Caution: If you are using a new font within body text (as above), then it is a bad idea to use Scale greater than 1.0. Reason: An excessively tall font will cause lines to spread apart.</p>
-
-
-<p style="margin-top:16px"><img class="floatright" src="html-resources/fluffy-conspiracy.png" width="265" height="409" alt="the fluffy conspiracy"> <b>Example:</b> Suppose that you wish to style the title of your book, in a font that is not used for other things such as chapter titles. You purchase a license for the <em>Bernhard Modern Std</em> fonts, in Regular and Italic.</p>
-
-<p>In the Preamble:</p>
-
-<p class="code"><code>\NewFontFamily\booktitlefont{Bernhard Modern Std}</code></p>
-
-<p>The title page, using <code>\charscale</code> for size:</p>
-
-<p class="code"><code>
-\thispagestyle{empty}<br>
-\vspace*{7\nbs}<br>
-\begin{center}<br>
-\charscale[3]{\booktitlefont The \textit{Fluffy} Conspiracy}\par<br>
-\vspace{6\nbs}<br>
-\charscale[2]{Priscilla Milde}\par<br>
-\vfill<br>
-Nonexistent Publications • Portland, Oregon\par<br>
-\end{center}
-</code></p>
-
-<p style="clear:both; margin-top:16px; font-size:small">Note: Command \NewFontFamily is identical to \newfontfamily, and command \NewFontFace is identical to \newfontface.</p>
-
-
-
-
-<a id="a5.4"></a>
-<h3>5.4 Font Customization Syntax</h3>
-
-<p>You will be using <code>fontspec</code> syntax to select your own fonts. Much of what follows is a digested portion of the full <code>fontspec</code> documentation. There are many more features, and ways to use them, than will be described below.</p>
-
-
-
-<a id="a5.4.1"></a>
-<h4>5.4.1 Font (Family) Name vs. Font File Name</h4>
-
-<p>A <em>font file</em> is an individual file, with its own <em>file name</em>, including file extension. For example, libertinusserif-regular.otf and libertinusserif-italic.otf are two different font files. This much is obvious.</p>
-
-<p>A <em>font family name</em>, often merely called <em>font name</em>, refers to one or more font files that are variations of the same basic font. Some fonts are so unique that the family consists of just one file. For example, the NovelDeco font family consists of the one file NovelDeco.otf. Typically, a font family has four files, consisting of Regular, Italic, Bold, and BoldItalic variants. Even though there are four font files, there is a single font family name. Many font families have more than four files, including Semibold and Light weights, and Condensed tracking. It is up to the font designer to decide whether a Condensed variation of the "Bubble Turble" font should be treated as a member of the "Burble Turble" family, or as a separate "Burble Turble Condensed" family.</p>
-
-<p>The font (family) name can be learned by opening font files in your system font viewer. Currently, the Windows 10 font viewer uses "Font name" and the Ubuntu font viewer puts the font name in more prominent type. A font (family) name may contain more than one word, with or without spaces, and may contain a general classification such as <em>serif</em>, <em>sans</em>, or <em>mono</em>, because those are actually different families. But it will not contain words such as <em>regular</em>, <em>medium</em>, <em>semibold</em>, <em>bold</em>, or <em>italic</em>; those are for individual members of the same family. Within TeX, some of the older PostScript fonts have been re-worked as newer TrueType and Open Type fonts. The family names are slightly different, so pay attention.</p>
-
-
-<p class="centerimg">
-<img src="html-resources/win10libser.png" width="268" height="184" alt="Windows 10 font viewer">
-<img src="html-resources/ublibser.png" width="431" height="176" alt="Ubuntu font viewer">
-</p>
-
-
-
-<a id="a5.4.2"></a>
-<h4>5.4.2 Set/New by Font Name vs. File Name</h4>
-
-<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>Preamble:</p>
-<p class="code" style="clear:both"><code>\NewFontFamily\rway{Raleway}</code></p>
-<p>Document Body:</p>
-<p class="code"><code>{\rway I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
-
-
-<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>Preamble:</p>
-<p class="code" style="clear:both"><code>\NewFontFamily\rwayi{Raleway-Regular-Italic.otf}</code></p>
-<p>Document Body:</p>
-<p class="code"><code>{\rwayi I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
-
-
-<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>Preamble:</p>
-<p class="code" style="clear:both"><code>\NewFontFamily\frankenfont[% note the % at linebreaks<br>
- ItalicFont=BaskervilleF-Italic.otf,%<br>
- BoldFont=libertinusserif-semibold.otf,%<br>
- BoldItalicFont=texgyrepagella-bolditalic.otf,%<br>
-]{Raleway-Medium.otf}</code></p>
-
-<p>Document Body:</p>
-<p class="code"><code>{\frankenfont I came, \textbf{I saw}, \emph{I conquered}, \textsc{I left}.}</code></p>
-
-
-<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>
- ItalicFont=Raleway-Light-Italic.otf,%<br>
- BoldFont=Raleway-Medium.otf,%<br>
- 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>
-
-
-<a id="a5.4.3"></a>
-<h4>5.4.3 Open Type Features</h4>
-
-<p>Features are variations, contained within a single font file. In the bad old days, when you wanted true small caps, you had to load a separate font file that had them (and did not have ordinary lowercase letters). Now, if an Open Type font file has the "smcp" feature, you obtain the small caps from within the same file, by asking for them. Requests for the feature may be made on-the-fly, or pre-loaded for global use.</p>
-
-<p>Here are several of the most frequently-used features, relevant to fiction writing. There are many more, and most fonts have only a few of them. Even when a font has a feature, it may be limited to some portion of the characters. For example, it is common for small caps to be available only for Latin-1 letters, even though the font also contains Greek and Cyrillic. To put this another way: The availability of a feature does not tell you its breadth of coverage. Unless the font has documentation showing coverage of its features, the only way to find out is to create and print a test page.</p>
-
-
-<table class="preconf">
-<caption>
-Some Frequently-Used Open Type Features
-</caption>
-<thead>
-<tr>
-<th>Description</th>
-<th>Open Type code </th>
-<th>fontspec code</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td><p>kerning</p></td>
-<td><p>kern</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: textfont, 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>
-</tr>
-<tr>
-<td><p>lowercase letters to small caps</p></td>
-<td><p>smcp</p></td>
-<td><p>Letters=SmallCaps</p></td>
-</tr>
-<tr>
-<td><p>uppercase letters to small caps</p></td>
-<td><p>c2sc</p></td>
-<td><p>Letters=UppercaseSmallCaps</p></td>
-</tr>
-<tr>
-<td><p>lining numerals</p></td>
-<td><p>lnum</p></td>
-<td><p>Numbers=Lining</p></td>
-</tr>
-<tr>
-<td><p>oldstyle numerals</p></td>
-<td><p>onum</p></td>
-<td><p>Numbers=OldStyle<br><em>enabled: textfont, sansfont</em></p></td>
-</tr>
-</tbody>
-</table>
-
-<p>• Kerning is the automatic adjustment of spacing between letters, so that they fit together nicely. Common ligatures are substitutions, such as a combined <code>ff</code> character for two consecutive <code>f</code> characters. It is up to the font designer to determine which ligatures, if any, are common.</p>
-
-<p>• TeX ligatures (such as replacing <code>``</code> with <code>“</code> and <code>---</code> with <code>—</code>) are not actually an Open Type feature, but they are treated that way by the software. All of these are enabled by default. The <code>fontspec</code> manual explains how to disable them, if necessary.</p>
-
-<p>• 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>• 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>• 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>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>• 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>• 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>
-
-
-<a id="a5.4.4"></a>
-<h4>5.4.4 Scale as Pseudo-Feature</h4>
-
-<p>Although it is not an Open Type feature, <code>Scale=<em>number</em></code> may be written like a feature. <code>Scale</code> globally adjusts the size of the font, relative to what it would otherwise be. If a local font size command is also applied, then the result is the compounded value.</p>
-<p>If the font will be mingled with other fonts in the same place, Scale can tweak a font so that it does not stand out. If Scale does not exceed 1, then the baselineskip will not be affected. Over 1 risks spreading lines to accomodate the extra size; this should not be done for fonts that will appear in the flowing main text. But over 1 is acceptable for display fonts that do not wrap lines and do not mingle with main text.</p>
-<p>Example: <em>Orbitron</em> is a special-purpose font with a mechanical or futuristic look. Its characters are much larger and heavier than would be found in book fonts. If I wish to mingle Orbitron with ordinary text, I might load the font like this:</p>
-
-<p class="code"><code>\NewFontFace\orbitron[Scale=0.6]{Orbitron} % Preamble</code></p>
-
-<p>Then in the document body, I could use it like this, where I have added <code>\textls</code> to spread the letters by a tiny bit:</p>
-
-<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>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>
-
-
-<a id="a5.4.5"></a>
-<h4>5.4.5 Color and Opacity</h4>
-
-<p>Even though the <code>fontspec</code> syntax allows you to set <code>Color</code> and <code>Opacity</code> as pseudo-features when you define a font, <em>the novel class blocks these features.</em> If you attempt to set them as features in a font definition, an error will result. The same applies if you attempt to add them, using <code>\addfontfeature</code>. However, you can still make use of grayscale using ordinary, local color commands.</p>
-<p>When you use the <code>graytext</code> class option, you may write text in grayscale, using commands from the included <code>xcolor</code> package. You should only do this for text that is in special locations. For example, if you begin each chapter with a number that is very large, you might wish to make that number gray, so that it does not overpower the main text.</p>
-<p>To avoid possible conflicts, the color specification should be chosen from a limited list of names. In order from dark to light: black, blue, violet, darkgray, purple, red, teal, olive, magenta, gray, brown, green, orange, cyan, lightgray, lime, pink, yellow, white. They will all be rendered in <em>shades of gray</em> (of course, black and white will be themselves). You may also choose from this more convenient list: black, gray1, gray2, gray3, gray4, gray5, gray6, gray7, gray8, gray9, white.</p>
-<p>If <code>graytext</code> is not chosen as class option, then any color (even white) will be rendered as black.</p>
-
-
-
-<a id="a5.4.6"></a>
-<h4>5.4.6 \CreateFeature{<em>code</em>}{<em>substitutions</em>}</h4>
-
-<p>Once in a while, a font has a glyph that you would like to use, but it is not included in any of the font's Open Type feature sets. So, how to you grab that particular glyph? For example: One well-known font has a glyph named <em>emdash.alt</em>, which is not as long as the font's ordinary <em>emdash</em> glyph, and looks better in text. Unfortunately, <em>emdash.alt</em> is not in any of the font's style sets. Without some trickery, only a program such as InDesign can grab that glyph.</p>
-<p>Thanks to the included <code>fontspec</code> 2016 update, <code>novel</code> has the necessary trickery. Command <code>\CreateFeature</code> creates a fake Open Type feature code, and assigns your list of substitutions to that code. Use comma-separated entries if there are multiple substitutions. For the case in question:</p>
-
-<p class="code"><code>\CreateFeature{myem}{emdash=emdash.alt}</code></p>
-
-<p>The code <code>myem</code> was randomly chosen as something that is not already defined among Open Type feature codes. Once specified, the fake feature may be used in any font definition, such as this:</p>
-
-<p class="code"><code>\SetMasterFont[RawFeature=+myem]{Adobe Garamond Pro}</code></p>
-
-<p>Of course, the fake feature has no effect if the font does not have the substitution character.</p>
-
-<p>This technique may be used for more complicated features, but that is beyond the scope of this documentation. See the <code>fontspec</code> manual if you need to do more.</p>
-
-
-<a id="a5.4.7"></a>
-<h4>5.4.7 Local Modifications to Open Type Features</h4>
-
-<p>If you specify a particular Open Type feature, it will be generally used for that font command. So if you define a new font command with <code>Letters=SmallCaps</code> as a feature (and if the font actually has them), then small caps will be used for that font, whether or not you locally request them with a command such as <code>\textsc</code>.</p>
-
-<p>Often, you can add (or sometimes remove) features on a local basis. For example, suppose that you defined the font without using is <code>ss03</code> style set. You can locally add that feature to some text, using a command that looks like this:</p>
-
-<p class="code"><code>{\addfontfeature{<em>which feature</em>} <em>applied to this text</em>}</code></p>
-
-<p>The above code assumes that you are already using the font in that location. You cannot apply <code>ss03</code> from one font to an entirely different font!</p>
-
-<p>See the <code>fontspec</code> documentation for details of <code>\addfontfeature</code>.</p>
-
-<p>As an alternative to changing features locally, you can define different font commands to call the same underlying font, but with different features.</p>
-
-<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>
-Some text {\baskf\addfontfeature{Numbers=Monospaced} hello 123} is here.
-</code></p>
-
-
-
-
-<a id="a5.5"></a>
-<h3>5.5 Shopping for Fonts</h3>
-
-<p>Many TeX fonts are only available in older Type 1 format (PostScript) or even as bitmap metafonts. Do not use them.</p>
-
-<p>In some other cases, a TeX font package provides both the older format, and a newer Open Type (*.otf or *.ttf) format. The different formats will have different font names. Sometimes the difference is very slight. Carefully look at the font name for the Open Type format. Remember that most on-line discussions will refer to the older fonts, simply because they have been around longer.</p>
-
-<p>Do not attempt to load a font by the <code>\RequirePackage</code> or <code>\usepackage</code> commands. Instead, if you choose to use fonts other than the defaults, load them via the font setting commands described on this page.</p>
-
-<p>Update: Now, if you attempt to load a font the wrong way, you will get an error message.</p>
-
-
-<a id="a5.5.1"></a>
-<h4>5.5.1 Licensing Issues</h4>
-
-<p>Presumably, you are writing your novel for commercial value, and do not intend to give anything away for free. For that reason, avoid fonts licensed under the GPL (GNU Public License) unless it has the <em>font exception</em> clause. Some TeX fonts are licensed under GPL, so watch out.</p>
-
-<p>Beware of fonts "free for personal use" from download sites. Your commercial application is not "personal use." Of course, if you like the font, you may purchase its commercial license.</p>
-
-<p>Also beware of fonts generically labeled as "freeware" with no particular designer name. If you don't know who created the font, then how do you know that it can be given away for free? Even if there is a designer name, some of them had second thoughts about "freeware." They intended the fonts to be free only if you give your own work away for free. But they didn't mention it. Maybe they have no legal recourse, but you don't want them making anonymous negative reviews of your book.</p>
-
-<p>You have numerous fonts already installed in your operating system, and perhaps others that came bundled with a particular application. If you intend to use those fonts, carefully read their licenses. It is often the case that fonts bundled with an application may <em>only</em> be used for documents created within, or processed by, that application.</p>
-
-<p>Always look for a Copyright notice, which can be identified with a particular person or organization. Copyright is good! It means that someone is claiming authorship of the font software. Only the Copyright owner has the right to give the font away for free, or license it to you after payment (often through an intermediary).</p>
-
-<p>If you prefer free fonts, the most widely accepted license is the <em>SIL Open Font License</em>. This allows you to use the font for commercial purposes, embed it in PDF, modify it to suit your needs (if you change the font name), and even re-distribute the modifications.</p>
-
-
-<a id="a5.5.2"></a>
-<h4>5.5.2 Technical Issues</h4>
-
-<p>Many fonts have technical errors, even among professional fonts. Some of the errors are so minor that they are not worth fixing. This is particularly true for glyphs that are missing extrema.</p>
-
-<p>However, beware of fonts that are based on traced artwork. The late 1990s had an explosion of amateur dingbat and decorative fonts produced this way, by scanning images from old books and digitizing the scan. The resulting vector glyphs rarely meet standards, and often are quite awful. The problem is that when a commercial printer renders your PDF to print, the printer's software is very different from what you have on your home computer. A technically erroneous glyph might look OK at home, but be rejected commercially.</p>
-
-<p>If you have the knowledge, you can open a font in font editor software (such as FontForge) and ask it for validation. Missing extrema are rarely a problem, even if a lot of them are missing. Self-intersecting glyphs are not a problem if the the glyph is composed of two elements stuck together, such as Ç composed of C with separate cedilla. However, a self-intersecting glyph may be a problem if its lines criss-cross each other. Open paths, and outer paths drawn the wrong way, are often a problem. If the errors are confined to glyphs that you will not be using, then it can pass.</p>
-
-
-<a id="a5.5.3"></a>
-<h4>5.5.3 Appearance Issues</h4>
-
-<p>There are general expectations for book fonts, in terms of character sizes and shapes, and weights. Many of the widely-used TeX fonts, including Latin Modern, are unacceptable in fiction for this reason. The most commonly-used font in word processors, Times New Roman, is only marginally acceptable for fiction, and only because it is so often used by amateur writers who don't know how to change the font (but write books advising you to change your lifestyle).</p>
-
-<p>The best way to assess a font is to print it to paper. Computer screens rarely show details, except at large magnification. Depending on whom you ask for an opinion, fiction is most easily read when there are about 60 to 66 characters (including spaces) per line. To evaluate a font for the main text, print out some paragraphs about 4" to 4.25" wide, and scale the font's point size so that you get an average number of characters per line in that range. Be sure to do that: Adobe Garamond Pro at 12pt, Libertinus Serif at 11.4pt, and Libre Caslon Text at 9.6pt (!) provide about the same number of characters per line of text. At the proper point size, some fonts will look too dark, and others will look too light.</p>
-
-<p>Things to look for: Are the lowercase letters too tall? If they are, then it is hard for readers in many Western languages to find where sentences start, by looking for capital letters. Also, there is less white space between lines, which makes the text appear dense and harder to read. Is the shape of the characters so natural that you don't notice them? That's good! It is your writing, not the font, that is to be noticed. Remember that some fonts are designed for use at large size, in posters; such fonts tend to look mechanical in fiction. Other fonts are designed for computer screens; the letters will be too widely-spaced in fiction. Nearly all modern fonts have decent kerning and important ligatures, so that's not usually a decisive factor.</p>
-
-<p>The prevailing rule: If you notice the font, it's wrong.</p>
-
-
-
-
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-06-header-footer.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,319 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a6">6. Headers and Footers</a></p>
-
-<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.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>
- <li><a href="#a6.1.5">6.1.5 \SetHeadFont[]{}</a></li>
- <li><a href="#a6.1.6">6.1.6 \SetLooseHead{}</a></li>
- <li><a href="#a6.1.7">6.1.7 \SetChapterDisplay{}</a></li>
- </ul>
- </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.2">6.2.2 \thispagestyle{}</a>
- </ul>
- </li><!-- end 6.2 -->
-
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-
-<a id="a6"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p>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>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<h2 style="clear:none;">6. Headers and Footers</h2>
-
-<p><b>Overview:</b> The <code>novel</code> class has a default header style. If you like it, then you do not have to use any of the configuration commands. So, before studying these commands, do a test document that uses the defaults.</p>
-
-<p>You may choose among several pre-configured header/footer styles. Then, you may change the appearance, content, and position. If none of it works for you, then you may define your own headers/footers using <code>fancyhdr</code> syntax. However, just about every style used in fictional works can be obtained using the pre-configured styles and adjustments.</p>
-
-<p>Individual pages, such as title, copyright, and new chapters, can have the header/footer style changed locally, on a per-page basis.</p>
-
-
-
-
-<a id="a6.1"></a>
-<h3 style="clear:none;">6.1 Global Header/Footer Settings, only in Preamble.</h3>
-
-<p>These commands determine whether your book will have headers and/or footers, and set the default style that is used for nearly all pages of the text. Per-page exceptions, such as for blank pages, title, copyright, and new chapters, are performed using the local settings commands.</p>
-
-
-
-<a id="a6.1.1"></a>
-<h4>6.1.1 <code>\SetHeadJump{<em>number</em>}</code>, <code>\SetFootJump{<em>number</em>}</code></h4>
-<p>These two commands control the separation between the header/footer and the main text. Since they pertain to page layout, rather than style, their usage is described on <a href="noveldocs-04-layout.html#a4.2.6">Page 4</a>.</p>
-
-
-
-
-<a id="a6.1.2"></a>
-<h4>6.1.2 <code>\SetHeadFootStyle{<em>number</em>}</code></h4>
-<p>Command <code>\SetHeadFootStyle{<em>number</em>}</code> chooses among several pre-configured header/footer styles, numbered 1 through 6. The default is style 1. The internals of the configuration can then be changed using a variety of commands.</p>
-<p>Some styles support an optional "emblem", which applies a decoration near the page number.</p>
-<p>Style 0 means neither header nor footer. Not practical for fiction, but it exists.</p>
-
-<p> </p>
-
-<img class="floatright" src="html-resources/headfoot1.png" width="276" height="219" alt="style 1" title="style 1">
-<pre style="padding-left:16px">
-<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>
-<em>This is the default for the novel document class.</em></p>
-
-<div style="clear:both"></div>
-
-<img class="floatright" src="html-resources/headfoot2.png" width="276" height="219" alt="style 2" title="style 2">
-<pre style="padding-left:16px">
-<b>\SetHeadFootStyle{2}</b></pre>
-<p>Only Footer.<br>
-Page number at outside (left verso, right recto).<br>
-Optional emblem adjacent to page number.</p>
-
-<div style="clear:both"></div>
-
-<img class="floatright" src="html-resources/headfoot3.png" width="276" height="219" alt="style 3" title="style 3">
-<pre style="padding-left:16px">
-<b>\SetHeadFootStyle{3}</b></pre>
-<p>Only Footer.<br>
-Page number centered.<br>
-Disregards emblem, if coded.</p>
-
-<div style="clear:both"></div>
-
-<img class="floatright" src="html-resources/headfoot4.png" width="276" height="219" alt="style 4" title="style 4">
-<pre style="padding-left:16px">
-<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>
-Default author verso, title recto.</p>
-
-<div style="clear:both"></div>
-
-<img class="floatright" src="html-resources/headfoot5.png" width="276" height="219" alt="style 5" title="style 5">
-<pre style="padding-left:16px">
-<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>
-Default author verso, title recto.</p>
-
-<div style="clear:both"></div>
-
-<img class="floatright" src="html-resources/headfoot6.png" width="276" height="219" alt="style 6" title="style 6">
-<pre style="padding-left:16px">
-<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>
-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>
-<p>• In the Preamble, use one of the above <code>\SetHeadFootStyle{<em>integer</em>}</code> to pick a starting point, in terms of whether or not there is a header and/or footer. <em>This is required, so that the layout engine knows how to calculate space.</em> After that, write the <code>fancyhdr</code> code for your custom header/footer in the Preamble. It will over-ride the numerical style in terms of appearance, but occupy the same space.</p>
-<p>• You cannot use a header or footer with more than one line. No exceptions.</p>
-<p>• See the file <code>novel-HeadFootStyles.sty</code> for how it is done in the pre-configured styles. In the file, the relevant portion follows <em>Look here for the pre-defined styles, for use as models.</em></p>
-<p>• Particularly note that your own style will not automatically use the headfont, or loose tracking, unless you include the necessary code in your own definition. Do not use the <code>\textls</code> command.</p>
-<p>• No cheating! If you choose a numerical style that does not have a header, then do not attempt to write a custom style that includes a header. Same with footer. Also, if you you choose a numerical style with both header and footer, then you cannot only customize one of them; you must customize both.</p>
-
-
-
-<a id="a6.1.3"></a>
-<h4>6.1.3 <code>\SetEmblems{<em>verso</em>}{<em>recto</em>}</code></h4>
-<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">• 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">• 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>• 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>
-{\InlineImage[0pt,b]{spy.png}}
-</code></p>
-
-<p>• At the small size of an emblem, it is difficult to use detailed artwork. A black/white image at 600dpi will print similarly to a font dingbat. Grayscale at 300dpi will probably not be satisfactory unless the emblem is a single shade of gray. For the above example, a character from the "Fontawesome" font was converted to a png image at mid-gray. It is less distracting than a black character from the font, but hard to discern. Note that there is no "gray ink" for directly writing text in gray.</p>
-<p>• Ask your print service whether the presence of a small image in each page header will affect production costs. Probably not, but if there is a different per-page charge when pages have an image... Oops!</p>
-<p>• The layout calculation does not care whether emblems intrude into the margins. You will have to inspect your PDF to determine whether a header emblem is too tall, or a footer emblem too deep, for the allowed top and bottm margin clearance. Class option <code>shademargins</code> (in draft mode only) is helpful.</p>
-
-
-<a id="a6.1.4"></a>
-<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>
-\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>
-
-
-<a id="a6.1.5"></a>
-<h4>6.1.5 <code>\SetHeadFont[<em>features</em>]{<em>font</em>}</code></h4>
-
-<p>This setting is described on <a href="noveldocs-05-fonts.html#a5.3.2">Page 5</a>, among other fonts.</p>
-
-
-<a id="a6.1.6"></a>
-<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>Note: Do not use the <code>\textls</code> command. It is disabled in this class.</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>
-<p>The looseness applies to inter-letter spacing, but not to inter-word spacing. To increase inter-word spacing, use extra code such as <code>\,</code> (which is a LaTeX thin space) as needed.</p>
-
-
-<a id="a6.1.7"></a>
-<h4>6.1.7 <code>\SetChapterDisplay{<em>choice</em>}</code></h4>
-<p>This command is only applied if you begin new chapters with the <code>ChapterDisplay</code> environment. You may pick one of the <code>thispagestyle</code> choices, described in the next section. For example:</p>
-<p class="code"><code>\SetChapterDisplay{dropfolioinside}</code></p>
-<p>Then, that choice will be applied to each page using <code>ChapterDisplay</code>, without you having to write <code>\thispagestyle</code> each time.</p>
-<p>The default is <code>footer</code>. This allows a ChapterDisplay page to show its footer (only if it has one), but not header.</p>
-<p>If you use this command, you may still over-ride it on a particular page, by using <code>\thispagestyle{<em>choice</em>}</code> <em>before</em> <code>\begin{ChapterDisplay}</code>.</p>
-
-
-
-<a id="a6.2"></a>
-<h3>6.2 Local Header/Footer Settings, in Document Body</h3>
-
-<p>These commands are used when a page header/footer style is an exception to the general rule. Examples are blank pages, titles, copyright, and new chapters. You can also dynamically change the header text.</p>
-
-<a id="a6.2.1"></a>
-<h4>6.2.1 <code>\SetVersoHeadText{<em>text</em>}</code><code>\SetRectoHeadText{<em>text</em>}</code></h4>
-<p>If you are using style <code>1</code>, <code>4</code>, <code>5</code>, or <code>6</code>, the header text can be dynamically changed from page to page. This feature is useful if your wish to include chapter titles in the header. It is also useful if your work is a collection of stories with different titles, perhaps by different authors. But before you use this feature, speak with your print service! Many print-on-demand services will insist that the content of headers must not vary from place to place, because different headers may be confused with portions of different books, during the assembly process.</p>
-<p class="code"><code>\SetVersoHeadText{New Verso Head}</code><br><code>\SetRectoHeadText{New Recto Head}</code></p>
-<p>These two commands may be used at any time, in the Preamble or document body. When a command is used, it stores its argument in <code>\versoheadtext</code> or <code>\rectoheadtext</code>. In turn, the current value of <code>\versoheadtext</code> or <code>\rectoheadtext</code> is immediately used for the header, and will remain in effect until changed again by <code>\SetVersoHeadText</code> or <code>\SetRectoHeadText</code>.<p>
-<p>If you do not use these commands in the Preamble, then at the beginning of the document body they will be automatically set to the author (verso) and the title (recto). However, you may find that the inter-word space is closer than you would like.<p>
-<p>For improved inter-word space, use <code>\,</code> (the LaTeX thin space) in addition to ordinary space. You may use as many as you need.</p>
-<p>You may use ordinary LaTeX styling commands for the text:</p>
-<p class="code"><code>\SetRectoHeadText{The \,\emph{Bad \,Boy} \,Chronicles}</code></p>
-<p>The most popular styling uses lowercase to small caps:</p>
-<p class="code"><code>\SetRectoHeadText{\smcp{The \,Danton \,Code}}</code></p>
-<p>• Avoid bold. Avoid underline. Really. Don't do it. No, no, no!</p>
-<p>• With novel version 1.32, you are no longer required to use tilde instead of space.</p>
-
-
-<a id="a6.2.2"></a>
-<h4>6.2.2 <code>\thispagestyle{<em>choice</em>}</code></h4>
-<p>When you choose a style with header, then space is allocated above the text block, where the header will be placed. That space will be allocated whether or not the header is full or empty. The same applies to the footer. This allocation is global, and cannot be changed in your document body. All standard books work this way, not just with TeX.</p>
-<p>However, on a per-page basis you can change whether or not a header or footer has visible content. This is routinely done for blank pages, title page, copyright page, and some others. It is also the norm for pages that begin a new chapter.</p>
-<p>• The word "folio" has several meanings: It may refer to a particular paper size, or to a folded piece of paper at any size, or simply to a page number. Below, "folio" means page number.</p>
-<p>• When you use the <code>\thispagestyle</code> command, your choice is applied only to the one page on which the command is written. It is best to use this command at or towards the top of the affected page. If the page uses the <code>ChapterDisplay</code> environment, and you use <code>\thispagestyle</code>, then you <em>must</em> place <code>\thispagestyle</code> before <code>\begin{ChapterDisplay}</code>.</p>
-<p>• The following choices are allowed: <code>fancy</code>, <code>empty</code>, <code>footer</code>, <code>forcenumber</code>, <code>dropfoliobeneath</code>, and <code>dropfolioinside</code>.</p>
-<p>For compatibility reasons, <code>plain</code> and <code>fancyplain</code> are also allowed, and have the same effect as <code>footer</code>.</p>
-
-
-<pre>
-<b>\thispagestyle{fancy}</b></pre>
-<p>This applies the default (fancy) page style, so it is not normally needed. Only use this command to over-ride some other <code>\thispagestyle</code> command, or to over-ride the <code>\SetChapterDisplay</code> setting.</p>
-
-
-<pre>
-<b>\thispagestyle{empty}</b></pre>
-<p>Header and footer are both blank.</p>
-
-
-<pre>
-<b>\thispagestyle{footer}</b></pre>
-<p>Ignored if the style has no footer. If it does, then the usual footer appears. Header, if any, is blank.</p>
-<p>This command is an alias for <code>fancyplain</code>. It is like the <code>plain</code> style, except that the footer (which is presumed to contain the page number) is fully styled. But unlike <code>plain</code>, the <code>footer</code> style does <em>not</em> cause a page number to appear when no footer exists. If that is what you need, then use either style <code>dropfoliobeneath</code> or <code>dropfolioinside</code>, depending on whether you have extra room in the bottom margin.</p>
-
-
-<pre>
-<b>\thispagestyle{forcenumber}</b></pre>
-<p>If the style has a footer, then it appears as usual, and the header (if any) is blank. If the style has a header but no footer, then the outside portion of the header (which is presumed to contain the page number and emblem) appears, but the text portion of the header is blank.</p>
-<p>The <code>forcenumber</code> choice is non-standard. Use it only if you must have a page number, and no other choice is suitable.</p>
-
-
-<pre>
-<b>\thispagestyle{dropfoliobeneath}</b></pre>
-<p>The header (if any) is blank. If there is a footer, then it appears as usual. But if there is no footer, this command creates a one-page fake footer, which contains the centered page number. The fake footer is located where the next line of text would be, if the textblock were one line longer than its actual value.</p>
-<p>• For the fake footer to be acceptable in print, the bottom margin must be wider than the minimum amount required by your print service. For example, suppose that the minimum bottom margin is 0.5in, but you set the bottom margin to 0.75in. That gives you 0.25in wiggle room, into which the fake footer will probably fit, because typical baselineskip is 0.2in to 0.25in.</p>
-<p>• The document class does not know whether or not you have extra space available in the bottom margin. It is your responsibility to know.</p>
-
-
-<pre>
-<b>\thispagestyle{dropfolioinside}</b></pre>
-<p>The header (if any) is blank. If there is a footer, then it appears as usual. But if there is no footer, this commands temporarily reduces the number of lines per page by one line. At the bottom, where the last line of text would normally be, the page number is centered. Thus, there is no intrusion into the bottom margin.</p>
-<p>This command may only be used following the <code>\clearpage</code> command. Thus, it may be used at the start of new chapters, or on pages (such as copyright page) that do not flow from a previous page. If you use it elsewhere, the print will have incorrect layout, but there will be no error or warning, since the compiler is not sure what you are trying to do.</p>
-<p>If used on a page with <code>ChapterDisplay</code> environment, you must place <code>\thispagestyle{dropfolioinside}</code> <em>before</em> you begin <code>ChapterDisplay</code>. The display block has a disposable blank line at its top, which is removed when <code>dropfolioinside</code> is used (instead of removing a line from the following text block).</p>
-
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-07-text-size-style.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,403 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a7">7. Text Sizes, Styling, and Position</a></p>
-
-<ul>
-
- <li><a href="#a7.1">7.1 Text Sizes</a>
- <ul>
- <li><a href="#a7.1.1">7.1.1 Standard Sizes: Disabled!</a></li>
- <li><a href="#a7.1.2">7.1.2 \charscale[]{}</a></li>
- <li><a href="#a7.1.3">7.1.3 Environment: parascale</a></li>
- <li><a href="#a7.1.4">7.1.4 Open Type Scale</a></li>
- </ul>
- </li><!-- end 7.1 -->
-
- <li><a href="#a7.2">7.2 General Styling</a>
- <ul>
- <li><a href="#a7.2.1">7.2.1 Italics and Emphasis</a></li>
- <li><a href="#a7.2.2">7.2.2 Bold and Semibold</a></li>
- <li><a href="#a7.2.3">7.2.3 Underlining</a></li>
- <li><a href="#a7.2.4">7.2.4 Small Caps, Acronyms</a></li>
- <li><a href="#a7.2.5">7.2.5 Tighter Tracking</a></li>
- <li><a href="#a7.2.6">7.2.6 Local Font Selection</a></li>
- <li><a href="#a7.2.7">7.2.7 Changing Font Features</a></li>
- <li><a href="#a7.2.8">7.2.8 Text Color (grayscale)</a></li>
- </ul>
- </li><!-- end 7.2 -->
- <li><a href="#a7.3">7.3 Positioning and Alignment</a>
- <ul>
- <li><a href="#a7.3.1">7.3.1 What not to use!</a></li>
- <li><a href="#a7.3.2">7.3.2 Some Useful Commands</a></li>
- </ul>
- </li><!-- end 7.3 -->
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-
-
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p>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>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<a id="a7"></a>
-<h2 style="clear:none;">7. Text Sizes and Styling</h2>
-
-<p>This page describes how to change the size of text, how to style text (such as italics), and how to move it around. It also describes some miscellaneous commands that are intended to modify text.</p>
-<p>If you are looking for information about how to choose the main text point size, see <a href="noveldocs-04-layout.html#a4.2.3">Page 4</a>, because it is considered to be among the layout settings. If you are looking for information about how to choose fonts and font features, see <a href="noveldocs-05-fonts.html">Page 5</a>.</p>
-<p>There is no direct setting for normal baselineskip; it is automatically calculated from the size of the textblock and lines per page.</p>
-
-
-<a id="a7.1"></a>
-<h3>7.1 Text Sizes</h3>
-
-<p>Be sure to read through this. In <code>novel</code>, standard TeX font size commands are disabled. There are new commands that address the limited needs for font sizing, in the context of fiction. These new commands are primarily for local adjustments of a few characters, or for display pages that are outside the main flow of text.</p>
-
-
-<a id="a7.1.1"></a>
-<h4>7.1.1 Surprise! Traditional TeX Font Size Commands Are Disabled.</h4>
-
-<p>Ah, the simplicity of TeX font size commands, such as <code>\small</code> and <code>\LARGE</code>. But in <code>novel</code>, they don't work. If you write <code>{\LARGE text}</code>, then the incuded text appear at normal size. This is by design.</p>
-
-<p>Why? In <code>novel</code>, the focus is on maintaining a constant baselineskip, so that facing pages have text aligned. This is impossible with the standard TeX commands. In particular, commands to increase font size will change the baselineskip, whether you like it or not, even if you try to code for a constant baselineskip. That's just the way TeX works.</p>
-
-<p>The one exception is that footnotes will appear with smaller than normal size and skip. But this is done automatically. You cannot manipulate it with a size command.</p>
-
-<p>Fortunately, there are not a lot of occasions where fiction needs to change font size. In <code>novel</code>, there are new commands to address each situation.</p>
-
-
-<a id="a7.1.2"></a>
-<h4>7.1.2 \charscale[<em>scale,hoffset,voffset</em>]{<em>text</em>}, \charscale*[<em>scale,hoffset,voffset</em>]{<em>text</em>}</h4>
-
-<p>The <code>\charscale</code> command may be used for a short amount of text, where there is no line break. The command will throw an error if the included text has <code>\\</code> or <code>\par</code> or any other command that breaks the line. You may not place an image in <code>\charscale</code>.</p>
-
-<p>This command is built into some other <code>novel</code> commands, such as <code>\ChapterTitle</code>.</p>
-
-<p>When used without the option, <code>\charscale</code> echoes the included text. However, the text gains the magical ability to extend above or below the normal line of text, without pushing apart the baselines. This is useful if the text has some unusual character that is extraordinarily tall or deep.</p>
-
-<p>Using the option, you may uniformly scale the text by any amount, and displace it horizontally and vertically. The text can overlie other text, or any previously-placed image.</p>
-
-<p>With the unstarred command, the scaled width of the text will occupy horizontal space, even if the text is displaced far away. But with the starred command, the text does not occupy any horizontal space.</p>
-
-<p>The single optional argument may include up to three comma-separated values. The first value is a number, indicating the scale. If a second argument is used, it is the length of horizontal offset (positive is right). If a third number is used, it is the length of the vertical offset (positive is up). Remember that if all you want to do is scale the text, without positioning it, then you only need to provide the scale.</p>
-
-<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>
-Bada \charscale[1.25]{Bang} Bam\par
-</code></p>
-
-<p>In the result (above right), notice how the starred command leaves no gap where the word Boom would have been. The unstarred command leaves a gap where the word Bang would have been located. In each case, the baseline grid is maintained.</p>
-
-<p>The most practical application of <code>\charscale</code> is styling the first character of chapter text. Drop capitals are out of fashion, but enlarged capitals (rising above the baseline) are in fashion. Example, also using the <code>\FirstLine</code> command (from package <code>magaz</code>, included with <code>novel</code>:</p>
-
-<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>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>
-
-
-<a id="a7.1.3"></a>
-<h4>7.1.3 <code>\begin{parascale}[<em>scale</em>] ... \end{parascale}</code></h4>
-
-<p>The <code>parascale</code> environment is used on a paragraph basis. More than one paragraph may be included. The scale is applied to the font size and to the baselineskip within.</p>
-
-<p>Since the text within <code>parascale</code> generally will not occupy an integral number of normal baselineskips, the following text will be off-grid. This may not be a problem, if <code>parascale</code> is used in places where maintaining the grid does not matter (such as on a title page or copyright page).</p>
-
-<p>• If <code>parascale</code> is used within body text, then it will be necessary to restore the line grid for the following text. This cannot be done automatically; you will have to make a preliminary run, look at the results, and adjust accordingly.</p>
-
-<p>For example, suppose you use <code>\begin{parascale}[0.92]...text...\end{parascale}</code>. The preliminary run shows that the included text occupies 7 lines. The following baseline will then be 7x(1–0.92)=0.56 normal baselineskip too high. This can be fixed by adding <code>\vspace{0.56\nbs}</code>. For best appearance, the <code>\vspace</code> should be split above and below the <code>parascale</code> environment, but not nessarily in half.</p>
-
-<p>• If <code>parascale</code> crosses to the next page, then you will need to make vertical adjustment for each page independently. For example, if a 7-line <code>parascale</code> has 3 lines at the bottom of a page, followed by 4 lines on the following page, then you need to restore only a 4 line deficit on the following page.</p>
-
-<p>• Within <code>parascale</code> you may need to manually indent paragraphs, or remove indents if necessary.</p>
-
-
-<a id="a7.1.4"></a>
-<h4>7.1.4 Open Type Scale (fontspec)</h4>
-
-<p>If you will be using a font in a way that it will <em>always</em> be at a size different from the normal font size, you may use the <code>Scale</code> feature when you first define the font. This is defined by the <code>fontspec</code> package, which is automatically loaded with <code>novel</code>. See <a href="noveldocs-05-fonts.html#a5.2.4">Page 5</a> for details.</p>
-<p>A scaled font can be used anywhere. It is not limited to a single line, and it will maintain the line grid at scales not exceeding 1. However, scaled text may disturb the line grid if its scale is more than 1.</p>
-
-
-<a id="a7.2"></a>
-<h3>7.2 General Styling</h3>
-
-<p>Many of these commands are directly from LaTeX, and are mentioned here because they are frequently used. Other commands are specific to <code>novel</code>.</p>
-
-
-<a id="a7.2.1"></a>
-<h4>7.2.1 Italics and Emphasis</h4>
-
-<p><code><b>\textit{<em>text</em>}</b></code> puts the text in italics, provided that the font family has an Italic font. If it does not have an Italic font, then the letters will remain normal, <em>not</em> fake slanted.</p>
-<p>If the italicized text leans too far into the following space, try adding <code>\/</code> (back and forward slashes) just before closing the braces.</p>
-<p><code><b>\emph{<em>text</em>}</b></code> changes regular text to italics, and italic text to regular. You may nest <code>\emph</code> commands. Many writers opine that this is the preferred way to specify Italics.</p>
-
-
-<a id="a7.2.2"></a>
-<h4>7.2.2 Bold, Semibold, etc.</h4>
-
-<p><code><b>\textbf{<em>text</em>}</b></code> puts the text in whatever font you specified as the Bold font, when you defined the currently-used font family.</p>
-<p>If the font family has no Bold font, then it will <em>not</em> be faked.</p>
-<p>The default main font used by <code>novel</code>, namely <code>Libertinus Serif</code>, has both Bold and Semibold weights. Given this choice, <code>novel</code> explicitly calls for the Semibold weight. If you intend to use a font such as Adobe Garamond Pro, which also has a Semibold weight, then you can request it instead of Bold when you define the font family. This is discussed on <a href="noveldocs-05-fonts.html#a5.2.2">Page 5.</a></p>
-<p>What if you want both Bold and Semibold, or maybe even a Light weight? Only one can be assigned to <code>\textbf</code> when you define the font. For the others, use <code>\NewFontFace</code> to assign the desired weight to its own font command, which you will use (but inside the braces) instead of <code>\textbf</code>.</p>
-<p>Actually, you should not be using Bold in fiction. It <em>might</em> be the case that this weight is useful for titles, but you ought to consider a fancy-looking font for that purpose, rather than mere Bold. Or, make the letters big and bold, but balance the effect by using gray.</p>
-
-
-<a id="a7.2.3"></a>
-<h4>7.2.3 Underlining</h4>
-
-<p>Underlining is inappropriate for fiction. Don't do it. Besides, there are some issues regarding line grid and appearance, which are not a problem in academic works, but are noticeable in fiction.</p>
-
-
-<a id="a7.2.4"></a>
-<h4>7.2.4 Small Caps and Acronyms</h4>
-
-<p><code><b>\textsc{<em>text</em>}</b></code> converts lowercase letters to small caps, leaving uppercase unchanged. The font's <code>smcp</code> Open Type feature will be used. But if the font does not have <code>smcp</code>, it will <em>not</em> be faked.</p>
-<p><code><b>\smcp{<em>text</em>}</b></code> is an alias for <code>\textsc{<em>text</em>}</code>.</p>
-<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>• 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>• 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>
-\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">
-<code>
-The NATO alliance...\par<br>
-The \acronym{NATO} alliance...\par<br>
-The \allsmcp{NATO} alliance...\par
-</code></p>
-
-<p>Whether or not to use the <code>\acronym</code> command, is up to you. Since its letters are drawn from the NovelDeco font, rather than your main font, there may be some stylistic differences.</p>
-
-
-<a id="a7.2.5"></a>
-<h4>7.2.5 Local Tracking Adjustment</h4>
-
-<p><code><b>\squeeze{<em>text</em>}</b></code> narrows the text by one percent.</p>
-<p><code><b>\crush{<em>text</em>}</b></code> narrows the text by two percent.</p>
-
-<p>These commands are for emergency use only. They temporarily apply a horizontal scale to the letters, so that they are very slightly narrower than usual. Inter-word spacing is not necessarily changed (it can even grow larger), because spacing is calculated during paragraph layout. The enclosed text may span paragraphs.</p>
-<p>The commands do not compound. That is, placing one crush inside another will not narrow the text by four percent. But any adjustments made by <code>microtype</code> will still apply, and may compound with these commands.</p>
-<p>The only application for these commands is when a paragraph does not quite fit where you would like it to be. For example: Perhaps one short word, or part of a word, dangles to an extra line. Try <code>\squeeze</code> first, then <code>\crush</code>, for all or most of the paragraph. These do not always produce a useful effect, since the actual paragraph layout depends on other factors. But <em>if you are lucky,</em> then the paragraph re-flows to a better layout.</p>
-<p>If the commands do not help, then be sure to remove them, or the effect will be worse.</p>
-
-
-<a id="a7.2.6"></a>
-<h4>7.2.6 Local Font Selection</h4>
-
-<p><code><b>{\<em>fontcode</em> <em>text</em>}</b></code> where <code>fontcode</code> is a previously-defined font command.</p>
-
-<p>You locally change the font in use, by calling its font command. For example, <code>\subchfont</code> is a built-in command, automatically used in certain macros. You can use it yourself:</p>
-
-<p class="code"><code>{\subchfont <em>text</em>} % Note that the braces go on the outside.</code></p>
-
-<p>Likewise, if you used <code>\NewFontFamily</code> or <code>\NewFontFace</code> to define your own font, giving it the command name <code>\mynewfont</code>, then you would use it like this:</p>
-
-<p class="code"><code>{\mynewfont <em>text</em>} % Again, the braces go on the outside.</code></p>
-
-
-<a id="a7.2.7"></a>
-<h4>7.2.7 Local Feature Changes</h4>
-
-<p><code><b>{\addfontfeature{<em>feature</em>} <em>text</em>}</b></code> for changing Open Type features.</p>
-
-<p>If a font is already defined, you can locally add one or more features. For example, suppose that you defined <code>\mynewfont</code> without using its Open Type feature <code>ss03</code> (we will assume that the font actually has this feature). In a particular place, you wish to activate <code>ss03</code>. The code looks like this:</p>
-
-<p class="code"><code>{\mynewfont\addfontfeature{RawFeature=+ss03} <em>text</em>}</code> % Note + sign. Braces outside.</p>
-
-<p>That limits the scope of the feature to the included group, in TeX terminology.</p>
-<p>You can modify features used by any defined font, whether you defined it yourself or it is one of the <code>novel</code> built-in font commands. You can add more than one feature. If the requested feature does not exist in the font, then your request will be ignored.</p>
-
-<p>What about removing a feature that is already present in the font definition? Suppose you defined <code>\mynewfont</code> so that <code>Numbers=OldStyle</code> is used. On a local basis, can you change the style of numbers? Usually, yes. You could use <code>Numbers=Lining</code> to over-ride the feature. Sometimes it depends on how you chose the features, as a matter of syntax. See the <code>fontspec</code> documentation.</p>
-
-
-
-<a id="a7.2.8"></a>
-<h4>7.2.8 Color Text (actually, grayscale)</h4>
-
-<p><code><b>graytext</b></code> class option must be used, or any color command will be ignored, and its included text will be rendered in black (even if the requested color is white). Images are unaffected.</p>
-
-<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>
-\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>
-\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>
-
-<p>• The following color names are accepted, and will be converted to some shade of gray (from dark to light): black, blue, violet, darkgray, purple, red, teal, olive, magenta, gray, brown, green, orange, cyan, lightgray, lime, pink, yellow, white.</p>
-<p>The above names are often not helpful, so <code>novel</code> also allows you to use these: black, gray1, gray2, gray3, gray4, gray5, gray6, gray7, gray8, gray9, white. The scale is not uniform (gray5 is not 50 percent gray), but the values are usefully spaced.</p>
-<p>Other names "known to dvips," such as <code>Apricot</code>, do not work. An error will result.</p>
-
-<p>• To specify color by scale, follow the color command with <code>[gray]{<em>scale</em>}</code>, where the scale is a number between 0 (black) and 1 (white). Example: <code> \color[gray]{0.63}</code>.</p>
-
-<p>• If you use <code>xcolor</code> syntax to request an rgb color, it will be converted to 1-channel grayscale.</p>
-<p>• Absolutely no transparency!</p>
-
-
-<a id="a7.3"></a>
-<h3>7.3 Positioning and Alignment</h3>
-
-<p>By now, you should be prepared to read this: In <code>novel</code> there are new ways to position or align text, and some of the standard TeX methods are discouraged or disabled.</p>
-
-
-<a id="a7.3.1"></a>
-<h4>7.3.1 What to Avoid</h4>
-
-<p>• The <code>\raisebox</code> command does not play well with novel. It can be used, but there is the great risk of disturbing the line grid. Use <code>\charscale</code> instead.</p>
-
-<p>• If you must use the <code>\vspace{}</code> command (or its relative, <code>\vskip</code>) be sure to measure the space in units of <code>\nbs</code> (normal baseline skip).</p>
-
-<p>• Avoid <code>minipage</code> and <code>parbox</code>. These commands are likely to disrupt the line grid. When that happens, restoring the grid is your own responsibility. You may find the <code>adjustwidth</code> environment to be a useful alternative.</p>
-
-<p>• Do not use the <code>center</code> environment. You may use <code>{\centering ... \par}</code> instead. The <code>\center</code> environment causes the text to go off-grid. That's not a problem on some stand-alone pages where you don't care about the grid, but it is ugly in the middle or running text.</p>
-
-<p>• Avoid positioning via the <code>textblock</code> or <code>textblock*</code> environments (package <code>textpos</code>). Actually, novel uses <code>textblock*</code> internally. But if not handled with more care than usual, positioned text can disrupt the baseline and position of surrounding text. You may use <code>\charscale</code> to position small amounts of text safely, but not on a paragraph basis. Images have built-in positioning arguments, which may also be useful for positioned text.</p>
-
-<p>• Do not use floats. If you try, then <code>novel</code> may intercept them with a nasty message.</p>
-
-<p>• Do not use tables. Nasty message will result. But <code>novel</code> has its own provision for a Table of Contents, and the code may be used for other purposes as well. See <a href="noveldocs-09-chapters-displays.html#a9.3">Page 9</a>.</p>
-
-<p>• If you use images, then use only the image commands provided by novel: <code>\InlineImage</code> and <code>\BlockImage</code>. See <a href="noveldocs-08-images.html">Page 8</a><p>
-
-<p>• There is no built-in provision for a two-column environment. However, you can place text alongside an image. See <a href="noveldocs-08-images.html#a8.4.4">Page 8</a>.</p>
-
-
-
-<a id="a7.3.2"></a>
-<h4>7.3.2 Some Useful Commands</h4>
-
-<p>This is not a complete list. It merely addresses a few situations that you are likely to encounter, without the need for elaborate code, and without loading additional packages.</p>
-
-<p style="margin-top:10pt"><code><b>\begin{adjustwidth}{<em>left</em>}{<em>right</em>}</b> ... <b>\end{adjustwidth}</b></code></p>
-
-<p>This environment, from the included <code>changepage</code> package, is the most useful way to create block indents. The included text may have multiple paragraphs and span pages. The left and right arguments are lengths, being the amount to <em>increase</em> the respective margins from their normal values.</p>
-
-
-<p style="margin-top:10pt"><code><b>\phantom{<em>text</em>}</b></code></p>
-
-<p>Does not print the text, but leaves a horizontal gap as if the text were there.</p>
-
-
-<p style="margin-top:10pt"><code><b>\mbox{<em>text</em>}</b></code></p>
-
-<p>Prevents a specific word from being hyphenated, or to ensure that two consecitive words always appear on the same line. The box will not be broken across lines. However, it may overhang the margin, which is undesirable.</p>
-
-
-<p style="margin-top:10pt"><code><b>\makebox[<em>width</em>][<em>alignment</em>]{<em>text</em>}</b></code></p>
-
-<p>Puts the text in a box of fixed width (usually much larger than the text's own width) and aligns it left, center, or right in the box. If using this across the full textwidth, be sure to precede it with <code>\noindent</code> to prevent offset.</p>
-
-
-<p style="margin-top:10pt"><code><b>\hspace{<em>length</em>}</b></code></p>
-
-<p>Creates a horizontal space.</p>
-
-
-<p style="margin-top:10pt"><code><b>\strut</b></code></p>
-
-<p>Places an invisible box with no width, which has the height and depth of the font. Sometimes used as a placeholder.</p>
-
-
-<p style="margin-top:10pt"><code><b>\indent, \noindent, \forceindent, \backindent</b></code></p>
-
-<p>Commands <code>\indent</code> and <code>\noindent</code> have their ordinary TeX meaning. Sometimes, the action of other macros will remove an indent that should be there, or add an indent that should not be there. If writing <code>\indent</code> and <code>\noindent</code> do not fix the problems, use <code>\forceindent</code> and <code>\backindent</code> as more forceful solutions.</p>
-
-
-<p style="margin-top:10pt"><code><b>\hfill</b></code></p>
-
-<p>Pushes the following text to the right end of the line. Actual effect depends on what precedes and follows.</p>
-
-
-<p style="margin-top:10pt"><code><b>\vfill</b></code></p>
-
-<p>Pushes the following text to the bottom of the page. Actual effect depends on paragraph organization.</p>
-
-
-<p style="margin-top:10pt"><code><b>\kern</b></code></p>
-
-<p>Tweaks the spacing between consecutive letters. A tricky command, as it is always used without braces, and makes the surrounding text illegible in your source code. If you use it, the units of length should always be em, rather than pt. Example:</p>
-
-<p class="code"><code>It wa\kern-.02ems a da\kern.03emrk and stormy ni\kern-.004emght.</code></p>
-
-<p>The <code>\kern</code> command is not useful for globally changing kern values. Its most useful application is inserting just enough tweak so that the layout engine formats a paragraph with different line breaks.</p>
-
-
-<p style="margin-top:10pt"><code><b>\bigemdash[<em>yoffset,thickness</em>]</b></code></p>
-
-<p>Simulates a "big emdash" of variable length. Horizontal width is from command to end of line marked by <code>\par</code>, or limited by a fixed width such as created by <code>\makebox</code>. If placed in other situations, the line may be missing or too long.</p>
-<p>The line's normal position is at the typical height of an emdash, which is slightly above half the height of lowercase x. Its normal width is typical of an emdash width. Thus, the line is like an extended emdash.</p>
-<p>You can tweak the line using its optional argument. The first value tweaks the vertical position by a scale factor, where 1 equals its normal position (so that 0.9 places it a little lower). The second argument, if used, is separated from the first by a comma. It tweaks the line thickness by a scale factor (so that 0.9 makes it a little thinner).</p>
-<p>Since <code>\bigemdash</code> allows an optional argument, but no mandatory argument, you may not immediately follow it with text. If it is boxed, then first close the box; otherwise, end the paragraph.</p>
-
-
-<p style="margin-top:10pt"><code><b>\straightquote \straightdblquote</b></code></p>
-
-<p>New in version 1.38: These insert the single quote (apostrophe), and double quote, as ASCII straight characters, without TeX automatically substituting the curly characters.</p>
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-08-images.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,376 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a8">8. Images</a></p>
-
-<ul>
-<li><a href="#a8.1">8.1 Use Raster Images</a></li>
-<li><a href="#a8.2">8.2 Use Flattened png or jpg</a>
- <ul>
- <li><a href="#a8.2.1">8.2.1 Saving the Resolution</a></li>
- <li><a href="#a8.2.2">8.2.2 Removing Private Metadata</a></li>
- </ul></li><!-- end 8.2 -->
-<li><a href="#a8.3">8.3 Line Art vs. Grayscale</a>
- <ul>
- <li><a href="#a8.3.1">8.3.1 Line Art in GIMP</a></li>
- <li><a href="#a8.3.2">8.3.2 Grayscale in GIMP</a></li>
- <li><a href="#a8.3.3">8.3.3 Scaling After \rework</a></li>
- </ul></li><!-- end 8.3 -->
-<li><a href="#a8.4">8.4 Placing Images</a>
- <ul>
- <li><a href="#a8.4.1">8.4.1 \charscale</a></li>
- <li><a href="#a8.4.2">8.4.2 \InlineImage</a></li>
- <li><a href="#a8.4.3">8.4.3 Text Over \InlineImage</a></li>
- <li><a href="#a8.4.4">8.4.4 \BlockImage</a></li>
- <li><a href="#a8.4.5">8.4.5 \BlockImage and Text</a></li>
- </ul></li><!-- end 8.4 -->
-</ul>
-
-<p> </p>
-
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p>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>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-<a id="a8"></a>
-<h2 style="clear:none">8. Images</h2>
-
-<p>If you intend to place a lot of images in your document, or if you need to have text wrap around floating images, then the <code>novel</code> document class is not well-suited to your purpose. This is because the methods of formatting, and the emphasis on maintaining a constant baseline skip, sometimes interfere with the behavior you expect from other document classes.</p>
-
-<p>Yet you can place the occasional image. Most fiction does use imagery on the title page, and sometimes at chapter starts. Some stories include a map, or an image of ancient writing. In a detective novel, we might get a glimpse at handwritten evidence. The <code>novel</code> class has its own commands for easily dealing with these situations.</p>
-
-<p>Like it or not, you are restricted to <code>png</code> and <code>jpg</code> raster images. No vector artwork. No included <code>eps</code> or <code>pdf</code>. Forget about <code>pgf</code> and <code>TikZ</code>. Although you can "cheat" the <code>novel</code> commands, and circumvent the restrictions, don't do it. The restrictions are intentional. The reasons are explained below.</p>
-
-
-
-<a id="a8.1"></a>
-<h3>8.1 Use Raster Images</h3>
-
-<p>Place raster images, not vector images, in your document.</p>
-
-<p>You may think that the above sentence is a mistake. Haven't you been told that vector artwork is always preferable to rasterized artwork, because vector artwork is scalable? The part about being scalable is true. But if you do not need scalability, vector artwork is worse.</p>
-
-<p>How so? A PDF file can incorporate vector artwork, and if properly done it will meet commercial printing standards. <em>Sadly, it is often not properly done.</em> When vector artwork has technical errors, as it often does, then the appearance will depend on which software is used to view the image. The fact that it is within a PDF does not always help.</p>
-
-<p>When you design a vector image, or perhaps acquire one, you approve its appearance based on what you see on your computer. The odds are good that someone else, on a different computer, will be using the same software and thus see the same result. However, that is not true of the software built into commercial printing machines. That software may interpret ambiguous vector instructions in a different way than you expected.</p>
-
-<p>A good example is on pages 232-234 of the Adobe PDF 1.7 Reference. That's an enormous file, full of technical information. You don't need to read it. But Adobe provides an example of a vector drawing in the form of a five-pointed star, made with one continuous line that crosses itself. There are two possible rules for deciding whether the central pentagon should be filled or not. They produce different results. Adobe chooses a particular rule, and so should all compliant software. But is all software compliant? Without reading the Adobe spec, there is no particular reason to prefer one rule over the other. And, that's a simple example. Many vector drawings are very convoluted, in ways that make the artist's intent difficult to interpret.</p>
-
-<p>You normally do not need to scale images. Your finished work will be viewed at fixed size on the printed page, not at variable size in a PDF reader. So, scalability is not an advantage. Your image is placed on paper at its exact size and resolution. You are in complete control. If it is purely black/white line art, its detail will be about the same whether it was placed as vector or raster. If it is grayscale, it is subject to halftoning, which reduces the resolution in any case.</p>
-
-<p>Do not attempt to place an image by including a PDF within your TeX file. The reason is that the included PDF may carry its own File Data, which will differ from the File Data of the main PDF. There's nothing you can do about that, and commercial printers don't like it. So, don't do it. Indeed, <code>novel</code> may ban it!</p>
-
-
-
-<a id="a8.2"></a>
-<h3>8.2 Use Flattened png or jpg Image Format</h3>
-
-<p>The <code>novel</code> image-handling commands require the <code>png</code> or <code>jpg</code> formats, exclusively. If you already have a raster image in another format, such as <code>tif</code>, you must convert it. If you have a vector image, such as <code>eps</code> or <code>svg</code> format, you must rasterize it. This must all be done in an external graphics program, such as GIMP or Inkscape. It cannot be done from within TeX.</p>
-
-<p>Both <code>jpg</code> and <code>png</code> images can store their resolution internally. When you export images from a graphics program, be sure that the resolution is stored. This may or may not be an option that you need to check.</p>
-
-<p>With <code>png</code>, the image must be flattened (no transparency). Be sure to flatten the image before you export it to <code>png</code>. With <code>jpg</code>, the exported image is always flattened.</p>
-
-<p>When using grayscale, be sure to convert the image to true grayscale, which has only one color channel. In GIMP, this is achieved with the Image > Mode menu. Note that an RGB or CMYK image "that only uses grays" is <em>not</em> the same thing, since these have three or four color channels!</p>
-
-<p>When using pure black/white (png only), you can get there with GIMP's Image > Mode > Indexed menu.</p>
-
-<p>Note that within the finished PDF file, images are stored in an internal format which differs from your input. If your image is in the wrong format, or contains transparency, it will not be detected by TeX.</p>
-
-
-
-<a id="a8.2.1"></a>
-<h4>8.2.1 Saving the Resolution</h4>
-
-<p>Image resolution is measured in dots per inch (dpi). In a graphics program, it may be called pixels per inch (ppi). And, if the software was written in Europe or Asia, it may be measured in pixels per centimetre!</p>
-
-<p>When you prepare an image in a graphics program, you must first ensure that it is at the correct resolution. Most U.S. print services require 300dpi for grayscale images, 600dpi for black/white line art. Then, it is a simple matter of multiplying the image dimensions (in inches) by the resolution, to get the image dimensions in pixels.</p>
-
-<p>Example: A grayscale image that will print at 1.25" wide by 1.5" high, must be 375 pixels wide by 450 pixels high, at 300dpi. If the original image is at different dimensions, it must be cropped and scaled to the correct size. However, it is not enough to finish the image at 375x450 pixels. You must specifically set the resolution to 300dpi. If you fail to set the resolution correctly, then the image will not appear at its correct size in your PDF.</p>
-
-<p>In GIMP, you can use the Image > Scale Image dialog box to ensure that the image is at the proper size and resolution. When you change any of the settings, others may change in response. Be sure that all settings are satisfactory.</p>
-
-<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>
-
-
-<a id="a8.2.2"></a>
-<h4>8.2.2 Removing Private Metadata</h4>
-
-<p>Your image may contain "private metadata" that records how the image was created, especially if it was converted from a digital photograph. It may also contain color profile data that is inappropriate for a grayscale or black/white image. Commercial printing standards prefer that such private metadata be removed from images; the PDF File Data should speak for everything, not the individual images.</p>
-
-<p>The simplest way to remove private metadata is via a command-line program: Use either ImageMagick, or GraphicsMagick. These programs work on Windows, Linux, and (so I am told) OS/X. Specific code is shown in the workflow examples, below. If you ever re-work an image, you must once again remove its private data.</p>
-
-
-
-<a id="a8.3"></a>
-<h3>8.3 Line Art vs. Grayscale</h3>
-
-<p>Two kinds of images may appear in a black-and-white book: line art, and grayscale.</p>
-
-<p>Line art contains only black and white. Moreover, there cannot be any places where the black or white areas are very tiny. Most print services request that your line art be rasterized at 600dpi (dots per inch), but that does not mean you can emulate gray with an alternating pattern of black and white, repeated 300 times per inch. All it means is that the sharp transition from black areas to white areas can be resolved to about 1/600" during printing (only "about" since the ink spreads a little).</p>
-
-<p>So, if you think you can use Floyd-Steinberg dithering to convert a grayscale image to "line art," that won't work: The printer will note that it cannot resolve such fine detail, and treat it as a grayscale. The result will be worse than if you had left it as grayscale instead of dithering to black and white.</p>
-
-<p>Think in terms of how an offset press works. Look it up on the Internet. You can have a sharp boundary between black and white, but you cannot closely mingle tiny black and white areas. Actually, at low production volume, your book may be printed with a technology that can resolve very fine details. But you cannot count on that; and, if your book does sell well, you may be shocked if the print technology changes.</p>
-
-<p>A PDF file can place ordinary (vector) text atop an image. However, if the underlying image is halftoned, there is the risk that the overlying text will also be halftoned, even if it sits atop white areas of the image. Ask your print service for advice. It may be better to make the text part of the image, and anticipate halftoning by using appropriately styled text.</p>
-
-
-
-<a id="a8.3.1"></a>
-<h4>8.3.1 Workflow: Line Art in GIMP</h4>
-
-<p>To create a suitable line art image in GIMP, with post-processing in ImageMagick or GraphicsMagick, follow these instructions:</p>
-
-<p>(1) Open the image file in GIMP. If it is a vector format (such as svg or pdf), ensure that it is resolved to 600 pixels/in with anti-aliasing, and that its size is the same as your intended dimensions (measured in inches or mm). You can also use a larger size, if you intend to crop some of the periphery; or you can use a smaller size, if you intend to make it larger by adding white space.</p>
-
-<p>(2) If you need to crop to a smaller size, or add to a larger size, do it now. Image > Canvas Size, with Resize Layers All.</p>
-
-<p>(3) If you need to edit the image, by adding or removing anything, do it now.</p>
-
-<p>(4) Image > Flatten Image.</p>
-
-<p>(5) Image > Mode > Grayscale.</p>
-
-<p>(6) View > Zoom to an appropriate amount that shows the image at approximately its print size. That depends on your monitor's resolution. On my own computer, 25\% is about right. Does not need to be exact.</p>
-
-<p>(7) Colors > Threshold. If necessary, adjust the slider until the image looks best. It might be that the default 50\% works for you. If you move it to the left, then black areas will become a little narrower. If to the right, black areas will become a little thicker.</p>
-
-<p>(8) Image > Mode > Indexed > Use black and white (1-bit) palette. Remove unused colors from colormap. No dithering.</p>
-
-<p>(9) File > Export. Use png (Portable Network Graphics) extension. When the dialog box appears, ensure that "save resolution" is checked. Use the highest level of compression offered. The exported image may look poor in some image viewers, because those viewers do not read the full resolution. Not a problem. The image will look good when seen in better viewers.</p>
-
-<p>(10) Command-Line Terminal, using GraphicsMagick (or ImageMagick without the preceding <code>gm</code>):</p>
-
-<p class="code"><code>gm mogrify -strip nameofimage.png</code></p>
-
-<p>(11) Sanity check, again using GraphicsMagick (or ImageMagick without the preceding <code>gm</code>):</p>
-
-<p class="code"><code>gm identify -verbose nameofimage.png</code></p>
-
-<p>After a few moments, the Terminal will show some information. It should say that the depth is 1-bits per pixel, that the only color is gray (1 bits), that the resolution is 236.22 pixels per centimeter (which is 600dpi). The page geometry, divided by 600, will give you the image size in inches (thus, a page geometry of 900+1200+0+0 represents an image 1.5" wide x 2" high).</p>
-
-
-<a id="a8.3.2"></a>
-<h4>8.3.2 Workflow: Grayscale in GIMP</h4>
-
-<p>To produce a suitable grayscale image in GIMP, with post-processing in ImageMagick or GraphicsMagick, follow these instructions:</p>
-
-<p>(1) Open the image file in GIMP. If it is a vector format (such as svg or pdf), ensure that it is resolved to 300 pixels/in with anti-aliasing, and that its size is the same as your intended dimensions (measured in inches or mm). You can also use a larger size, if you intend to crop some of the periphery; or you can use a smaller size, if you intend to make it larger by adding white space.</p>
-
-<p>(2) If you need to crop to a smaller size, or add to a larger size, do it now. Image > Canvas Size, with Resize Layers All.</p>
-
-<p>(3) If you need to edit the image, by adding or removing anything, do it now.</p>
-
-<p>(4) Image > Flatten Image.</p>
-
-<p>(5) Image > Mode > Grayscale.</p>
-
-<p>(6) View > Zoom to an appropriate amount that shows the image at approximately its print size. That depends on your monitor's resolution. On my own computer, 25\% is about right. Does not need to be exact.</p>
-
-<p>(7) Very dark grays are hard to produce accurately, and so are very light grays. If your image relies on areas that ar nearly black and nearly white, then consider adjusting lightness and contrast so that they are not so close to black and white. GIMP's Colors > Levels might be more useful than Colors > Brightness/Contrast.</p>
-
-<p>(8) There is no transparency, but you can achieve that effect by ensuring that white areas are truly white, not light gray. Use GIMP's Select By Color Tool, with a very low threshold (perhaps 1) to choose areas that should be exactly white, then clear them.</p>
-
-<p>(9) File > Export. Use png (Portable Network Graphics) extension. When the dialog box appears, ensure that "save resolution" is checked. Use the highest level of compression offered. The exported image may look poor in some image viewers, because those viewers do not read the full resolution. Not a problem. The image will look good when seen in better viewers.</p>
-
-<p>(10) Command-Line Terminal, using GraphicsMagick (or ImageMagick without the preceding <code>gm</code>):</p>
-
-<p class="code"><code>gm mogrify -strip nameofimage.png</code></p>
-
-<p>(11) Sanity check, again using GraphicsMagick (or ImageMagick without the preceding <code>gm</code>):</p>
-
-<p class="code"><code>gm identify -verbose nameofimage.png</code></p>
-
-<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>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) <code>png: IHDR.color_type: 0 (grayscale)</code></p>
-
-<p class="code">(For jpg images) <code>JPEG-Colorspace: 1</code> and <code>JPEG-Colorspace-Name: GRAYSCALE</code></p>
-
-<p>The above codes are the only ones that matter. Even if other information claims that the image is grayscale, or lists the colors and they are all shades of gray, <em>that is not good enough</em>. When automated software reviews your PDF for compliance, it will look at the png IHDR.color_type, which must be 0, or the JPEG-Colorspace, which must be 1. Anything else fails. If the information is different, it means that you forget to change the mode to grayscale before you exported the image.</p>
-
-<p>You may ask: If the image was not really grayscale, can it be converted to grayscale using a simple command line, with ImageMagick or GraphicsMagick? The answer is yes, but don't do it that way. The reason is that there are many ways to map colors (even "gray colors") to true grayscale, and an automated conversion may produce unexpectedly light or dark results. It is better to do the conversion in a graphics program, where you can see what you are doing.</p>
-
-
-<a id="a8.3.3"></a>
-<h4>8.3.3 Workflow: Scaling the image after \Rework.</h4>
-
-<p>When you use one or both of the <code>\Rework</code> commands, the font size and/or the baselineskip will change. However, it does not scale images. In many cases, there is no problem. But in some cases, an un-scaled image will disrupt the previous flow of text or pagination. If you look in the log file, you will see an Alert message, which suggests (only suggests) appropriate values for scaling problem images, depending on whether they are placed inline or block. Then, you should re-work the image in an external image editor. When you scale the image, be sure that the revised version is at the correct resolution of 300dpi or 600dpi, or whatever is necessary.</p>
-
-<p>It is best to go back to your copy of the original artwork, before you exported it to <code>png</code> or <code>jpg</code>. But what if you do not have anything but the 1-bit or grayscale images that you created earlier? Then do this:</p>
-
-<p>(1) If the image is 1-bit, change to Color > Mode grayscale.</p>
-
-<p>(2) Use Image > Scale Image to get new dimensions, at 600 or 300 pixels per inch. Careful: Sometimes when you change size, it auto-changes resolution, or vice-versa. Click back and forth in the dialog box, to ensure that both the dimensions and resolution are correct. The default Cubic interpolation is OK.</p>
-
-<p>(3) Change View to something that puts the image at its approximate print size.</p>
-
-<p>(4) If desired, play with Filters > Enhance > Sharpen.</p>
-
-<p>(5) Image > Flatten.</p>
-
-<p>(6) If the image is to be 1-bit line art, use Colors > Threshold and Image > Mode >Indexed, as before.</p>
-
-<p>(7) Export as png, then <code>mogrify</code> the image, as before. Be sure to identify the image and look for its png IHDR.color_type or JPEG-Colorspace, as before.</p>
-
-<p>The above does not take too much time, and will provide superior results. Note that when an image is placed within text, the calculation for text positioning is different than the calculation for image positioning. It is possible (although unlikely) that a <code>\Rework</code> situation will cause an unexpected page break, due to roundoff error in the placement of the final line on a page. This can be fixed by subtracting (or, in some cases, adding) as little as <code>\vspace{-0.001\nbs}</code> before or after the re-scaled image.</p>
-
-
-
-
-<a id="a8.4"></a>
-<h3>8.4 Placing Images In Your Document</h3>
-
-<p>An image may be placed as an inline element, using the <code>\InlineImage</code> command. This allows the image to mingle with text, and even have text as an overlay.</p>
-<p><code>\BlockImage</code> places the image so that <em>subsequent</em> text will clear the bottom of the image, and be on the baseline grid. You may also <em>accompany</em> the image with text in its own block space, if you wish.</p>
-<p>If your book has a lot of images, then you should consider using a page layout program (such as Scribus) instead of TeX. That's because the best strategies for an image-intensive picture book are very different from the strategies adoped by <code>novel</code>.</p>
-<p>Beware of overlap. If images overlap each other, or overlap with text, no error will result. If text lies atop an image, the result may be desirable. All other situations are undesirable. Since TeX cannot detect such errors, you need to carefully review the result.</p>
-<p>Do not use the ordinary TeX commands, or environments, for floats or figures.</p>
-
-
-<a id="a8.4.1"></a>
-<h4>8.4.1 \charscale[<em>scale,hoffset,voffset</em>]{<em>text</em>}, \charscale*[<em>scale,hoffset,voffset</em>]{<em>text</em>}</h4>
-
-<p>The <code>\charscale</code> command pertains to text, not images. It is mentioned here because it can place text almost anywhere on a page, even overlapping other text or previously-placed images. Thus, it provides an image-like effect.</p>
-<p>The command is documented on <a href="noveldocs-07-text-size-style.html#a7.1.2">Page 7</a>.</p>
-
-
-<a id="a8.4.2"></a>
-<h4>8.4.2 \InlineImage[<em>hoffset,voffset</em>]{<em>imageFile.png or .jpg</em>} and starred version</h4>
-<p>This command places the image as an inline element, at 100% scale. The use of <code>png</code> or <code>jpg</code> images, with file extension, is required.<p>
-<p>You may offset the image horizontally or vertically. Positive direction is to the right and up. If you use one offset, then you must use both (empty brackets may be used for defaults). Any units of length may be used, but the preferred units are <code>em</code> or <code>\textwidth</code> for horizontal, and <code>em</code> or <code>\nbs</code> for vertical, because these are most compatible with the <code>\Rework</code> commands.</p>
-<p>By default, the <em>top</em> of the image is at the text baseline. If you prefer that the <em>bottom</em> of the image be at the text baseline, use voffset <code>b</code>. Example:</p>
-<p class="code"><code>\InlineImage[0pt,b]{imageFile.png}</code></p>
-<p>Thanks to the <code>calc</code> package, offsets may use \widthof{<em>text</em>} and/or \heightof{<em>text</em>} as lengths. The most useful of these is when you wish to align the top of an image at the X-height of surrounding text:</p>
-<p class="code"><code>\InlineImage[0pt,\heightof{X}]{imageFile.png}</code></p>
-<p>You may also use <code>\heightof{\Aring}</code> for the tallest accented letter normally found in Latin-1.</p>
-<p>Lengths <code>\imagewidth</code> and <code>\imageheight</code> may also be used for offsets. These lengths remain set, and can be used for other purposes (such as displacing text) until another image is placed.</p>
-<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[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>
-<p>With the un-starred command, the image occupies its natural horizontal width. That is, text following the image will (if it fits) continue from the right edge of the image. But with the starred command, the image occupies zero width. In this case, text following the image will continue from the left of the image, and overlie the image.</p>
-<p>Having text overlie the image is allowable, and can create some interesting special effects. However, such effects are rarely used in fiction. When your print service sees what you have done, they may think that it is a mistake, and flag your file. Be sure that you discuss this with your print service.</p>
-<p>If you do allow text to overlie an image, be sure that the image is very light. Repeat: <em>very light</em>. Depending on the printing technology, an image may print darker than you see on your computer screen, and that would make text hard to read. At low print volume, your print service will probably use a technology that is like an industrial-strength home inkjet printer, which can make very sharp text over images. However, if your book goes to volume production, then the technology will be different. Volume printing will use halftoned images, and the text overlay may also become halftoned, which will reduce its sharpness considerably. Once again: Discuss this with your print service!</p>
-<p>Note that an image may be placed in a way that prints some of the image in the margin. That's allowable if your margin is wider than the minimum required for printing clearance. But even if it is not allowable, there will be no complaint or warning from TeX.</p>
-<p>Do not place an image so that it approaches or goes beyond the page edge. That requires a "bleed box" which is not part of <code>novel</code> capabilities. If your book needs that kind of image handling, use a page layout program instead.</p>
-<p>Do not place images so that they overlap. Although that is allowed in the PDF, it is likely to be flagged as an error by your print service.</p>
-
-
-
-<a id="a8.4.3"></a>
-<h4>8.4.3 Text Over \InlineImage</h4>
-
-<p>As noted above, an <code>\InlineImage</code> or its starred version, can be used as the background to any subsequent text. Just as with any other text, whatever sits atop an image must be pure black. If you need text in gray, then you must integrate the rasterized text with the image in an external graphics program, instead of typing the text in your document.</p>
-
-<p>When text overlays an image, it retains its identity as vector paths, as far as the PDF is concerned. In some printing processes, particularly those for very low volume production, the result will be as sharp and dark as ordinary text. However, if your books sells well (or is being prepared to sell well), the image will be converted to halftone, and the text that lies above it may also be converted to halftone. This will reduce the sharpness of the text. It is not necessarily a problem, unless your text is very small or has fine details.</p>
-
-<p>If the text-over-image is part of a title, then the text is naturally large and dark, and will easily withstand halftoning.</p>
-
-<p>Be aware that not all print services will accept text over images. It's not that they <em>cannot</em> do it; after all, your home and office printers can easily do it. The reason they object is because the pages of your book will be handled in small volume by persons who are unfamiliar with the book. Text over an image may be flagged as a printing error or a bug in the PDF. In the advertising world, text over image is routine. But in the world of fictional novels, it is unusual. Don't imagine that they will decide what you meant to do, by reading your book. Also, very sharp image/text, at low printing volume, will not appear as sharp when the technology changes for higher volume production. They know that, but are not sure if <em>you</em> know that.</p>
-
-<p>An inline image occupies zero vertical space. If you place its top near the bottom of the textblock, then the image will happily flow into the lower margin and perhaps off the bottom of the page, without an error (but the print service will reject it). The reason that TeX does not provide an error message is quite simple: Technically, it is not an error! It is just not what you meant to do. The software cannot read your mind.</p>
-
-<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>
-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>
-
-
-
-<a id="a8.4.4"></a>
-<h4>8.4.4 \BlockImage[<em>alignment,hoffset,voffset</em>]{<em>imageFile.png or .jpg</em>}[<em>text</em>]</h4>
-
-<p>Note that <code>\BlockImage</code> has an optional argument that precedes the mandatory image file name. It has another optional argument that follows the file name. If this second option is used, there must be no space between <code>}[</code>.</p>
-
-<p>The first optional argument has up to three comma-separated values. The first is alignment: <code>l</code>, <code>c</code>, or <code>r</code> for left, center, or right. The second and third values are hoffset and voffset. Unlike the <code>\InlineImage</code> command, do not use <code>b</code> to indicate vertical position relative to the image bottom; it is always at the top with this command. The default alignment is centered, without offsets.</p>
-
-<p>An automatic calculation clears the height of the image. Subsequent text will be on grid. This is the right thing to do when the image and included text fit on a single page. But if they cannot both fit on a single page, an unusual layout will result.</p>
-
-
-<a id="a8.4.5"></a>
-<h4>8.4.5 \BlockImage and Text</h4>
-
-<p>The second optional argument of <code>\BlockImage</code>, following the image, may contain text that will accompany the image in the same block of space. The text is left-aligned like ordinary text, no matter which alignment you use for the image. The text may be in more than one paragraph, and may use <code>{\centering ...\par}</code> or <code>\begin{adjustwidth} ... \end{adjustwidth}</code> for positioning relative to the image. The text may overlie the image, using <code>\charscale</code>. You may need to use <code>\indent</code> or <code>\forceindent</code> or <code>\backindent</code> to control how the text appears. Note that you cannot "flow" text around an image in <code>novel</code> class.</p>
-
-<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>
-\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>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>
-<p>Note that I used the start of the following text as a reference point for placing CENSORED over the gnome. That is not the only way it could have been done, but it was easy to discern the necessary offset.</p>
-<p>• In general, avoid using accompanying text with an image, with the possible exception of titles and other special layouts. There is little need for it in the flowing text of a novel. If you find that you need to use it frequently, then perhaps your book would benefit from a page layout program such as Scribus, instead of TeX.</p>
-
-
-
-
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-09-chapters-displays.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,935 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<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">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<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>
- <span style="visibility:hidden">9.1 </span> including blank
- <ul>
- <li><a href="#a9.1.1">9.1.1 Half-Title</a></li>
- <li><a href="#a9.1.2">9.1.2 Frontispiece</a></li>
- <li><a href="#a9.1.3">9.1.3 Title Page</a></li>
- <li><a href="#a9.1.4">9.1.4 Copyright Page</a></li>
- <li><a href="#a9.1.5">9.1.5 Other Display Pages</a>
- <ul>
- <li><a href="#a9.1.5.1">9.1.5.1 Dedication</a></li>
- <li><a href="#a9.1.5.2">9.1.5.2 Epigraph - OBSOLETE</a></li>
- <li><a href="#a9.1.5.3">9.1.5.3 Table of Contents</a></li>
- <li><a href="#a9.1.5.4">9.1.5.4 Part Separator</a></li>
- <li><a href="#a9.1.5.5">9.1.5.5 Map or Illustration</a></li>
- </ul>
- </li>
- </ul>
- </li><!-- end 9.1 -->
-
- <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>
- <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>
- <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>
- <span style="visibility:hidden">9.3 </span>New Chapters
- <ul>
- <li><a href="#a9.4.1">9.4.1 \SetChapterStart{}</a></li>
- <li><a href="#a9.4.2">9.4.2 Environment: ChapterStart</a></li>
-
- <li><a href="#a9.4.3">9.4.3 Chapter Title Commands</a>
- <ul>
- <li><a href="#a9.4.3.1">9.4.3.1 \ChapterTitle{}</a></li>
- <li><a href="#a9.4.3.2">9.4.3.2 \ChapterSubtitle{}</a></li>
- <li><a href="#a9.4.3.3">9.4.3.3 \ChapterDeco[]{}</a></li>
- </ul>
- </li>
- <li><a href="#a9.4.4">9.4.4 ChapterStart With Image</a>
- <ul>
- <li><a href="#a9.4.4.1">9.4.4.1 Text Over Image</a></li>
- <li><a href="#a9.4.4.2">9.4.4.2 Image Includes Text</a></li>
- </ul>
- </li>
- </ul>
- </li><!-- end 9.4 -->
-
- <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>
- <ul>
- <li><a href="#a9.5.2.1">9.5.2.1 \scenebreak</a></li>
- <li><a href="#a9.5.2.2">9.5.2.2 \sceneline</a></li>
- <li><a href="#a9.5.2.3">9.5.2.3 \scenestars</a></li>
- </ul>
- </li>
- <li><a href="#a9.5.3">9.5.3 \IndentAfterScenebreak</a>
- </ul>
- </li><!-- end 9.5 -->
-
- <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</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{}{}</a></li>
- </ul>
- </li><!-- end 9.7 -->
-
-</ul>
-
-<p> </p>
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="a9"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p>9. Display, Start Pages;<br>
-<span style="visibility:hidden">9. </span>Chapters; Continued Pages;<br>
-<span style="visibility:hidden">9. </span>Footnotes, Endnotes.</p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-
-<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>
-
-<p>A <em>start page</em> is the first page of a continued section of related pages, with the same style and purpose. The important criterion is whether the section "might" continue to additional pages, not whether it actually does. Thus, a very brief Author's Note (essentially a one-page Preface) is considered to be a start page, because the author might have gone on for several pages.</p>
-
-<p>Anything other than a display page or a start page is a <em>continued page</em>.</p>
-
-
-
-<a id="a9.1"></a>
-<h3>9.1 Display Pages</h3>
-
-<p>In the book's front matter, many (perhaps all) of the pages are display pages. In fictional works, once the main matter begins, the only display pages (if any) will be part separators, maps, and blank pages.</p>
-
-<p>Display pages do not show a header or footer. At the top of the page, put this code:</p>
-
-<p class="code"><code>\thispagestyle{empty}</code></p>
-
-<p>Note that the header and/or footer is still there, and occupies its usual space. But it has no visible content. The page number does not appear in print, However, it is visible in the control panel of a PDF reader.</p>
-
-<p>Blank pages are considered to be display pages. Te create a blank page:</p>
-
-<p class="code"><code>\clearpage \thispagestyle{empty} \null \clearpage</code></p>
-
-<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. 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>
-
-
-
-<a id="a9.1.1"></a>
-<h4>9.1.1 Half-Title Page</h4>
-
-<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 <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>
-\stake\hfill{\orbitron\charscale[2]{Star Smash}}\par
-\vspace{0.4\nbs}
-<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>
-</small></code></p>
-
-<p>You can do better than that, perhaps by using a fancier font than you use for ordinary text, or even by placing the Half-Title in the form of an image.</p>
-
-
-<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>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>
-
-<p>If your Aunt Sally is a brilliant, internationally-known illustrator, and permits you (in writing, without royalties) to place one of her creations there, then that is a possibility. You might also use a photograph (reduced to grayscale), if your story is set in a real location. However, depending on location and jurisdiction, just because something is in plain public view does not necessary mean that you are free to take a photograph and use it commercially! That may even apply when it is a natural scene with no people in the picture. Here's a famous <a href="http://www.nytimes.com/1990/08/02/us/monterey-journal-trees-and-trademarks-the-disputes-run-deep.html" rel="external" target="new">example</a>, not too far from where I live.</p>
-
-<p>Something that is an integral part of the story, such as a map of its fictional locale, should not be placed as a frontispiece. Actually, with fiction you have a lot of wiggle room, so a map is possible <em>if</em> its artwork is good enough to face the title page, and you don't have a better place to put the map.</p>
-
-<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 “Books by the Same Author” here. Or, if the particular book is part of a set (“Splork Chronicles, Volume VI”) 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>
-\clearpage</small></code></p>
-
-
-<a id="a9.1.3"></a>
-<h4 style="clear:both">9.1.3 Title Page</h4>
-
-<p>The Title Page has page number <code>iii</code>, number not printed.</p>
-
-<p>With <code>novel</code>, there is no automatic construction of a Title Page, because its original artistic design is important. Nothing says “this book was written by someone who normally writes term papers instead of fiction” more than a Title Page that looks like it belongs on a term paper. Don't be afraid to use stylish fonts that differ from whatever you are using for the main text, or create the title as an image.</p>
-
-<p>If you wish to use gray text, you will need the <code>graytext</code> class option. Without it, text will always be black. But don't use the option unless you really need gray text somewhere in your book. Grayscale images will be grayscale, whether or not you choose this option:</p>
-
-<p class="code"><code>\documentclass[graytext]{novel} <span class="ap">% do not use graytext unless needed</span></code></p>
-
-<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>
-\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">
-<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
-</small></code></p>
-
-<p style="clear:both">Remember that you can also use black-and-white line art, or a grayscale image. You may find it easier to design all or part of your Title Page in a graphics program, export as <code>png</code> or <code>jpg</code>, and place the image. Be sure to read how this must be done in <code>novel</code> class, as the image requirements and commands are different from those used in other document classes.</p>
-
-
-<a id="a9.1.4"></a>
-<h4>9.1.4 Copyright Page</h4>
-
-<p>The Copyright Page will be page <code>iv</code>, number not printed. It is always the verso if the Title Page.</p>
-
-<p>This page should be styled differently from the main text. Typically, the vertical alignment leaves space at top. The final line may be at the bottom of the textblock. The text may be centered throughout (often used nowadays) or be left-aligned with ragged alignment instead of justification. The text will have one or both side margins increased, so that it does not occupy the full width of the textblock. Lines will not break with hyphenated words. All-uppercase words will be presented in small caps.</p>
-
-<p>If you have a service prepare a Cataloging-in-Print data block for you, the file will show two hyphens to mean an em dash, because that's how word processors do it. In TeX, use three dashes instead.</p>
-
-<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>
-\& <span class="ap">% when & 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>If your book is print-on-demand, then be sure to comply with requirements for stating, or not stating, the publisher and place of printing. In print-on-demend, the publisher is you, not the printer or distribution service. For books with an international market, there may be more than one nation where it is printed.</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">
-<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
-</small></code></p>
-
-<p> </p>
-
-<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">
-<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
-</small></code></p>
-
-
-
-<a id="a9.1.5"></a>
-<h4>9.1.5 Other Display Pages</h4>
-
-<p>Most fictional works do not need other display pages. However, it is bad practice to go directly from the Copyright Page (verso) to the start of your story (recto). If you do not know what else to do, have a look at the Epigraph, below.</p>
-
-<a id="a9.1.5.1"></a>
-<p class="h5"><b>9.1.5.1 Dedication:</b> A Dedication is not required. But sadly, nowadays many authors write a Dedication, which is often frivolous and detracts from the book. If you feel that you need a Dedication, why not put it on your web site? Then you can always edit or remove it, if the subject or your affection runs off with someone else.</p>
-
-<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 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
-</small></code></p>
-
-
-<a id="a9.1.5.2"></a>
-<p class="h5"><b>9.1.5.2 Epigraph: OBSOLETE</b>
-
-<p style="color:#cc0000">Sometime between March and May 2017, either I changed something in the underlying code, or TeX changed something, that caused the Epigraph command to stop functioning. I have not been able to hunt it down yet. Unless and until you have a code version 1.3 or greater (current is 1.2), do not use the Epigraph command, and remove it from any prior documents. You can emulate it using the adjustwidth environment, and some other easy code.</p>
-
-<p>Not every book has an Epigraph page, but it is a very useful way to separate the Copyright Page from the beginning of your story, when you have nothing else to put in front matter. In this case, the Epigraph appears as page <code>v</code> (recto), usually with a blank verso, and then your story begins as main matter on the following recto.</p>
-
-<p>You can also include an Epigraph, even if your front matter has more material. An Epigraph may go on a recto or verso page. So, if you have Dedication (page <code>v</code>) you may place an Epigraph on page <code>vi</code>, if you wish; but it does not have to go there. It may even go on the final front matter page, facing the beginning of your story, provided that it is particularly well-suited to setting the mood, and is not distracting.</p>
-
-<p>The purpose of an Epigraph is to set the mood for your own story. Perhaps it will give a hint of the genre, or of the theme. Or it may be pretentious, by implying that your own work can be compared to the famous work cited. Or, the Epigraph may quote from a fictional work. For example, if your story is sword-and-sorcery set in ancient China, you might quote from the imaginary <em>Grimoire of Wong Dung</em>. You may even quote from your own book: J.R.R. Tolkien's Epigraph for each book of his <em>Lord of the Rings</em> trilogy was the longer form of the ring's inscription.</p>
-
-<p>Use the <code>adjustwidth</code> environment to center the Epigraph on the page, as a block that does not occupy the full width. If you do not need the text to be justified, the <code>legalese</code> environment will provide ragged lines without hyphenation. After the text, place the source of the quotation, right-justified, and perhaps preceded by an em dash. Whether you place only the name of the person quoted, or the title of the book quoted, or something else, is a matter of formal style; see what others have done. But keep in mind that you should not use a work currently under copyright for your Epigraph. Translations of older works may be copyrighted, because the translation is sufficiently recent!</p>
-
-<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">
-<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
-</small></code></p>
-
-<p style="clear:both; margin-top:1em;">The <code>novel</code> class also provides its own <code>Epigraph</code> (not the capital E) command:</p>
-
-<p class="code"><code>\Epigraph[<em>alignment,scale,width</em>]{<em>text</em>}</code></p>
-
-<p>The optional <em>alignment</em> may be one of <code>l</code>, <code>c</code>, or <code>r</code>, which stand for left, center, right. Default is <code>c</code>. This is the horizontal alignment of the epigraph block <em>as a block</em>, not the alignment of the lines within the epigraph.<p>
-
-<p>Within the Epigraph block, alignments <code>l</code> and <code>c</code> produce left-alignment of the lines, with ragged right ends. Alignment <code>r</code> produces right-alignment of the lines, with ragged left ends.</p>
-
-<p>There is no particular width to the Epigraph block. If you write a line that is too long, it will not wrap, but will flow into the page margin. Use <code>\\</code> (not <code>\par</code>) to manually break lines.</p>
-
-<p>Exception: The final line, typically an attribution, should <em>not</em> end in <code>\\</code>. It may be without a closure. But if the final line does not end in punctuation, it may be very slightly to the right of its correct position. In this case, ending the line with <code>\par</code> tweaks it.</p>
-
-<p>In the unlikely event that you need to use the ampersand, be sure to write it as <code>\&</code> rather than as mere <code>&</code>.</p>
-
-<p>There is no provision for horizontal lines, or other styling used by academics.</p>
-
-<p>Here is an example, which will be horizontally centered on its page. For typical text size on 5.5"x8.5" Trim Size, the Epigraph will be slightly above the middle of the page, and occupy about 50% of the textblock width.</p>
-
-<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">
-<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]{<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>
-
-<p>An Epigraph like that tells you something about what to expect in the book. Actually, it tells you to expect about 350 pages of badly-written prose, interspersed with badly-written poetry. You can do better than that.</p>
-
-<p>Note that the Epigraph command may also be used inside the <code>ChapterStart</code> environment, as described farther down this page.</p>
-
-
-<a id="a9.1.5.3"></a>
-<p class="h5"><b>9.1.5.3 Table of Contents:</b> Do not place a table of contents just because you can. A table of contents is more useful when the story consists of discrete episodes with distinctive names, not just numbers. Or, if the book is a collection of short stories, a table of contents is mandatory. When a story is an “action adventure,” in which short chapters move along in rapid succession, a table of contents would be unusual.</p>
-
-<p>If you use a Table of Contents, it must be on a recto page. That would be page <code>v</code> if your book has no Dedication or Epigraph, or page <code>vii</code> if it has one or both of them.</p>
-
-<p>The Table of Contents does not include itself or anything preceding. If the front matter has textual sections such as Foreword, Preface, or Author's Intoduction, they are listed in the table (and will have lowercase roman numerals). In fiction, you might have at most one or two maps, which may be listed in the Table of Contents, rather than in a separate list of Illustrations.</p>
-
-<p>If your book has Part Separators (described lower on this page), then each Part Separator is listed in the table, but its page number is <em>not</em> provided unless the separator has a meaningful amount of text. So, <span class="apdk">“PART I. IN THE CASTLE”</span> would not have its page number listed in the table. However, <span class="apdk">“PART I. IN THE CASTLE. We begin our story in Castle McNada, where there has been an altercation between Lord Withens and Sir Nadie regarding the disposition of the gnomes.”</span> provides enough information to deserve its page number in the table. Use your discretion.</p>
-
-<p>In most fiction, the first entry in a Table of Contents will be the first chapter of the story, which will be on page 1, or in some cases, page 3.</p>
-
-<p><b>toc environment:</b> Avoid any of the table environments that come with TeX or its packages. These do not provide the most attractive presentation for fiction, without a lot of work on your part. With <code>novel</code> you have an environment defined specifically to meet the needs of fiction:</p>
-
-<p class="code"><code>\begin{toc}[<em>extra entry separation</em>]{<em>extra margins</em>} <em>...</em> \end{toc}</code></p>
-
-<p>The <code>toc</code> is not indented, and text within it is not indented.</p>
-
-<p>• The optional argument is a number. It is the portion of normal baselineskip that will be added beneath each <code>\tocitem</code> entry (see next section). Default is <code>0</code>, meaning that there is no extra skip between items, and normal baselineskip is maintained. A value greater than <code>0</code> spreads the entries, which could be attractive if there are only a few chapters and you'd like to use more space on the page. For example, a value of <code>0.25</code> means that a gap of 0.25 normal baselineskip will be added beneath each entry. A small negative value will crowd the lines together, but there is a limit (approximately <code>-0.1</code>) before the lines cannot be squeezed any tighter.</p>
-
-<p>Note that the optional argument only applies to <code>\tocitem</code> entries, not to any other text within the environment.</p>
-
-<p>• The required argument is a length, which will be the amount of extra margin added at left and right of the table (using <code>adjustwidth</code>). A value of <code>0pt</code> allows the table to occupy the full width of the textblock. A value of <code>2em</code> adds 2em to the margin on each side, so that the width of the table is 4em less than the width of the textblock.</p>
-<p>Note that it is best to specify horizontal lengths, within the textblock, in units of <code>em</code> or the proportional <code>\parindent</code> or <code>\textwidth</code>.</p>
-
-<p>Typically, the label for the <code>toc</code> will not be as bland as "Table of Contents" or even "Contents." One possibility is to use the book's title (and subtitle, if any). You can add a graphic element or a short remark, if you wish.</p>
-
-<p>In most cases, the table's title should not be placed where the first line of text would normally appear. This is because a fictional table of contents rarely fills the page, so it is more attractive to allow some space at top. Another reason is that if you use the <code>\charscale</code> command to increase the size of the topmost text, it will infringe the top margin, unless you provide at least one line of space above it. The <code>\vspace*{<em>length</em>}</code> command is best for this purpose.</p>
-
-<p><b>\tocitem:</b> The <code>\tocitem</code> command, and its starred version, are used for individual entries in the TOC environment. Do not use this command for general text that is not linked to a page number.</p>
-
-<p class="code"><code>\tocitem[<em>chapter number</em>]{<em>description</em>}{<em>page number</em>} and starred version</code></p>
-
-<p>• The optional argument is the chapter number, at most two digits. The number will be left-aligned, with a period automatically added. Following the period will be the amount of space needed to keep the following description aligned.</p>
-<p>If the optional argument is omitted (or empty), then there is no space, and the following description will align to the left of the table.</p>
-<p>If the optional argument is the tilde character <code>~</code> then no number or period is printed, but the space is occupied, so that the following description aligns as if you had entered a chapter number.</p>
-<p>• The description is usually the chapter title. If it cannot easily fit on one line, then use an additional <code>\tocitem</code>, because the text cannot be wrapped. The following example shows how this can be done.</p>
-<p>• Without the asterisk, <code>\tocitem</code> fills the area between the description and the page number with empty space. The starred <code>\tocitem*</code> command fills with a dotted line, and is very attractive.</p>
-<p>You may use ordinary style commands, such as <code>\emph{}</code>, in the entries.</p>
-
-<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">
-<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
-</code>
-</p>
-
-
-
-<a id="a9.1.5.4"></a>
-<p class="h5"><b>9.1.5.4 Part Separator:</b> A <em>Part Separator</em> is a recto page marking an abrupt change between very different portions of the book. Ordinary new chapters are <em>not</em> Part Separators. Many books have no need of Part Separators.</p>
-
-<p>One kind of Part Separator is the “Inner Half-Title”. This is a recto duplicate of the Half-Title page. It may appear in these situations: (a) You need to put something between the Copyright Page and the start of the story, but you do not want to put anything else there. (b) The front matter has a Foreword or Preface, or other material that takes up a number of pages, and you wish to provide a visual separation between the front matter and the main matter.</p>
-
-<p>The other kind of Part Separator is, as you might guess, a means to separate parts of the book. For example, if your book consists of two novellas, then each novella would have its own Part Separator, being a simplified title page for the following story. Or, if you wish to suggest an interruption in the flow of a single story, you might divide it using Part Separators. An example is each book in J.R.R. Tolkien's <em>Lord of the Rings</em> trilogy, in which each bound book is partitioned into two sub-books.</p>
-
-<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">
-<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
-</small></code></p>
-
-<p>The verso of a Part Separator is usually blank. But you could put a map there, or an Epigraph. It's up to you.</p>
-
-
-<a id="a9.1.5.5"></a>
-<p class="h5"><b>9.1.5.5 Map or Other Illustration:</b> A map, or other illustration, is simply a large image. It must be prepared at 100% scale and actual resolution, according to the detailed requirements described on that documentation page.</p>
-
-<p>Since a (fictional) map is part of the story, it belongs in main matter rather than in front matter. But where you put is is up to you.</p>
-
-<p>A map or illustration may be verso or recto.</p>
-
-
-
-
-<a id="a9.2"></a>
-<h3>9.2 Start Pages: General</h3>
-
-<p>Start pages begin a section that may continue to additional pages. The key word is "may." A section may be so brief that its start page is its only page.</p>
-
-
-<a id="a9.2.1"></a>
-<h4>9.2.1 \thispagestyle{<em>choose</em>}</h4>
-
-<p>A start page does not have a header. But if the normal page layout has a footer, then a start page will also have the footer. Thus, the page number (folio) will be printed on a start page, or not, depending on whether or not the normal layout has a footer. This is controlled by the following command:</p>
-
-<p class="code"><code>\thispagestyle{footer}</code></p>
-
-<p>The above code actually means, “footer, if normally available.” It does not create a footer that would not otherwise be present in your general book layout.</p>
-
-<p>The <code>novel</code> document class has an additional capability. On a start page, you may create a temporary footer containing just the page number. There are two ways to do that:
-
-<p class="code"><code>\thispagestyle{dropfolioinside}</code></p>
-
-<p>When you drop the folio (page number) <em>inside</em>, you reduce the height of the text block by one line, just on that page. The line that would have been the last one there, is moved to the top of the following page. However, if this command is used on a <code>ChapterStart</code> page (see below), then instead of moving that line, the space occupied by the chapter title block is reduced, so that it is not necessary to flow the line to the following page.</p>
-
-<p>Then, the page number is centered where the last line of text would have been placed.</p>
-
-<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="code"><code>\thispagestyle{dropfoliobeneath}</code></p>
-
-<p>When you drop the folio <em>beneath</em>, you do not change the height of the textblock. Instead, you place the page number centered where one additional line of text would be. Thus, the number sits within the bottom margin. This is allowable if the width of the bottom margin exceeds the minimum clearance required by the printer. However, if you do not have the excess margin, do not use this command.</p>
-
-<p>In <em>very rare cases</em>, which I have only seen in some non-fiction, the book has a header but no footer, and its start pages must show the page number (but not text) in the header. There is a command for that:</p>
-
-<p class="code"><code>\thispagestyle{forcenumber}</code></p>
-
-<p>With <em>forcenumber</em>, if a footer exists it will be used. Otherwise, the command assumes that the page number is at the outside margin of a header, and allows only that portion to print. Do not use the above command, unless you really need it.</p>
-
-
-<a id="a9.2.2"></a>
-<h4>\SetVersoHeadText{<em>new~verso~head</em>} \SetRectoHeadText{<em>new~recto~head</em>}</h4>
-
-<p>These commands only apply if you chose a header/footer style that includes text in the header. They will not throw an error if you use them with other header/footer styles; but they will have no effect.</p>
-
-<p>When your document begins, <code>novel</code> automatically places the author as verso header text, and the title as recto header text. They will appear on all pages that have a visible header (but not on pages where <code>\thispagestyle</code> blanks the header). This is the norm for many works o fiction.</p>
-
-<p>However, there are occasions when something else should appear in the header text. If your book has a Foreword, Preface, or similar section in its front matter, you do not use the author and title there. Instead, you simply place the section title (Foreword, Preface, or whatever) both verso and recto. The reasons are simple: (a) The front matter is not actually part of the story, and (b) It might have been written by someone other than the author.</p>
-
-<p>In the main matter, you might prefer that the chapter title (or story title, if short stories) appear instead of the author or book title. Or maybe something else. It is up to you, <em>but</em> be aware that some print services object to headers that change from place to place, as it creates the impression that portions of several different books are being assembled in error.</p>
-
-<p>Only use <code>\SetVersoHeadText</code> or <code>\SetRectoHeadText</code> following <code>\clearpage</code>. The effect will be applied immediately, and continue indefinitely, until the commands are re-issued.</p>
-
-<p>In the header text, use tilde rather than space to separate words. This improves the inter-word spacing. Perhaps at some future time this will not be necessary.</p>
-
-<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 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>
-<span class="ap">% Be sure to re-set the head texts now!</span>
-</small></code></p>
-
-
-
-<a id="a9.3"></a>
-<h4>9.3 Start Pages in Front Matter: Foreword, Preface, etc.</h4>
-
-<p>In most cases, a work of fiction will have no <em>start pages</em> in front matter. To put that another way, the front matter will consist entirely of <em>display pages</em>, as I have defined these terms. Example: Page i is the Half-Title; ii is blank; iii is the Title; iv is the Copyright; v is a Dedication, Epigraph, Table of Contents, Map, or duplicate Half-Title; vi is blank. That's all the front matter you need.</p>
-
-<p>However, if your book has a Foreword, Preface, Introduction, separate Acknowledgements, or similar section in front matter, then each begins with a recto start page. This is the case, even if the section is merely one page. If the section has an odd number of pages, then a blank page is inserted after it, so that the next section begins recto. Thus, if you have several sections like that, there will be several blank pages here and there, creating the impression that your book was padded. Solution: Edit!</p>
-
-<p>A potential problem arises when your book is of the “discovered lost manuscript” genre: The author pretends to be an archaeologist or professor who has discovered or translated a manuscript, or ancient inscriptions. In some cases, there may be more than one discoverer/translator involved. The author may even use his or her real name, in a fictional introduction. So, should the “archaeologist's” tale of discovery be in front matter, where it would be if it were a true academic work? Or should it belong in main matter, because it is fictional? Same with the “translator's” notes, and author's own introduction. My understanding of the <em>Chicago Manual of Style</em> (hardcover 16.ed., items 1.42, 1.46) is that it all belongs in main matter. But in established, printed fiction I have seen it both ways.</p>
-
-
-
-<a id="a9.4"></a>
-<h4>9.4 Start Pages in Main Matter: New Chapters</h4>
-
-<p>In the main matter of most books, the only start pages are new chapters. Actually, I cannot think of an exception to this. Remember that Part Separators are (usually) treated as display pages. Maps are always display pages, unless they are so small that they fit on a page with continued text.</p>
-
-<p>If your novel consists of chapters that begin on their own page, or if your book is a collection of stories, then you should use the <code>ChapterStart</code> environment to enclose the block of text (and possibly image) that starts each new chapter.</p>
-
-<p>You may place almost anything you like at the beginning of new chapters, but in reality there are only a limited number of useful things. The <code>novel</code> class has special commands for handling them, especially for the needs of fiction.</p>
-
-<p>If your book is actually a quick succession of many short chapters, then it might be better to treat them as scenes. See the scene commands, lower on this page.</p>
-
-
-<a id="a9.4.1"></a>
-<h4>9.4.1 \SetChapterStart{<em>pagestyle</em>}</h4>
-
-<p>When you use the <code>ChapterStart</code> environment, described below, it will use <code>\thispagestyle{footer}</code> by default. That is, no header will be printed on that page. If the book layout normally has a footer, it will be displayed (and thus the page number, which is in the footer, will be shown). But if there is normally no footer, no page number will be shown, so the default is equivalent to <code>\thispagestyle{empty}</code>.</p>
-
-<p>You can globally change the default behavior, with this Preamble command:</p>
-
-<p class="code"><code>\SetChapterStart{<em>some other choice of pagestyle</em>}</code></p>
-
-<p>Other choices of pagestyle are <code>dropfolioinside</code>, <code>dropfoliobeneath</code>, or very rarely <code>forcenumber</code>.</p>
-
-
-<a id="a9.4.2"></a>
-<h4>9.4.2 \begin{<em>ChapterStart</em>}[<em>lines</em>] <em>...</em> \end{<em>ChapterStart</em>}</h4>
-
-<p>The <code>ChapterStart</code> environment reserves a block of space at the top of the textblock. The same space is reserved, no matter how much or how little content you put inside. The optional argument sets the number of lines displaced by the block. Its default is 10, minimum 4.</p>
-
-<p>You will need to use <code>\clearpage</code> prior to each <code>ChapterStart</code>.</p>
-
-<p>If you put a lot of material inside <code>ChapterStart</code>, it will not push the story farther down the page. Instead, the material inside the <code>ChapterStart</code> will overflow the reserved area, and mingle with the text below. Normally this is very undesirable. However, it might be attractive, if your <code>ChapterStart</code> contains an image that you wish to dangle underneath the following text.</p>
-
-<p>For a particular chapter, if you wish to use a page style that differs from the one specified by <code>\SetChapterStart</code>, then you must put the <code>\thispageStyle</code> command <em>before</em> <code>\begin{ChapterStart}</code>.</p>
-
-<p>If you are using symbolic footnote markers, each <code>ChapterStart</code> re-sets the symbols.</p>
-
-<p>The first line of main text, following <code>ChapterStart</code>, will not be indented.</p>
-
-
-<a id="a9.4.3"></a>
-<h4>9.4.3 Pre-Styled Chapter Title Commands</h4>
-
-<p>Several commands are specifically designed for use inside the <code>ChapterStart</code> environment. If you use them anywhere else, then the text line grid will be disturbed. So, don't do that, with the possible exception of display pages where the line grid does not matter.</p>
-
-<p>Each of these commands may only be used for a single line of contents. If the contents cannot fit on a single line, then you must manually break and issue the command twice. The commands may be used in any order, may be used more than once, or not at all.</p>
-
-<a id="a9.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">
-<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>
-<p class="h5" style="clear:none"><b>9.4.3.2\ChapterSubtitle{<em>text</em>}</b> sets its text using <code>subchfont</code>. The default is the main font scaled 1.2, with lining numbers.</p>
-
-<a id="a9.4.3.3"></a>
-<p class="h5" style="clear:none"><b>9.4.3.3\ChapterDeco[<em>scale</em>]{<em>text</em>}</b> does not commit to its contents. Typically a decoration will be used, perhaps from <code>decofont</code>. The optional argument is a scale factor to be applied to the required argument. Many horizontal decorations need to be magnified.</p>
-
-<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>
-<span class="ap">% then the main text</span>
-</small></code></p>
-
-
-<a id="a9.4.4"></a>
-<h4>9.4.4 ChapterStart With Image</h4>
-
-<p>You can use an image in chapter titles. If you place an image, use one of the image commands defined by <code>novel</code> elsewhere in the documentation. Any other method is likely to push the following text off-grid.</p>
-
-<p>Be sure that you are licensed to use the image. Many clipart catalogs "for personal use only," prohibit usage in commercial books. One possible source is <a href="http://openclipart.org" rel="external" target="new">openclipart.org</a> (note the <em>.org</em>).</p>
-
-
-<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>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>
-</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>
-\end{ChapterStart}</small></code></p>
-
-
-
-<a id="a9.5"></a>
-<h3>9.5 Continued Pages</h3>
-
-<p>I define <em>continued page</em> to mean a page that has a noticeable break, but without necessarily starting another page. Thus, the <code>\clearpage</code> and <code>\thispagestyle</code> commands are not used, and it is uncommon to change header text.</p>
-
-
-<a id="a9.5.1"></a>
-<h4>9.5.1 \QuickChapter[<em>linelength</em>]{<em>chapter title</em>}</h4>
-
-<p>If your novel is the kind of story that consists of numerous short chapters in rapid succession, then you probably do not wish to begin each chapter on its own page, with a block of whitespace at the top. The <code>\QuickChapter</code> command provides an alternative to <code>ChapterStart</code>.</p>
-
-<p>The <code>\QuickChapter</code> command inserts two blank lines. In the gap, the chapter title is left-justified using <code>subchfont</code> (not <code>chapterfont</code>). It is slightly raised from the normal baseline, because this looks better; but the following text is back on-grid. The start of the following text will be un-indented.</p>
-
-<p>If the optional <code>linelength</code> is provided, then a dash will be written after the title, at the position and thickness typical of the em dash in <code>subchfont</code>. If <code>linelength</code> is specified in units of length, then that will be the length of the line. But if <code>linelength</code> is an asterisk, then the line will fill to the right margin.</p>
-
-<p>Note that this command is too obstrusive for mere scene changes within a chapter.</p>
-
-<p>Example:</p>
-
-<p class="code"><code><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>
-
-
-<a id="a9.5.2"></a>
-<h4>9.5.2 Scene Breaks</h4>
-
-<p>There are several commands dedicated to the purpose of scene breaks.</p>
-
-<a id="a9.5.2.1"></a>
-<p class="h5"><b>9.5.2.1 \scenebreak</b> inserts a one-line blank skip. The following line of text is not indented.</p>
-
-<a id="a9.5.2.2"></a>
-<p class="h5"><b>9.5.2.2 \sceneline</b> inserts a one-line skip, containing a short centered line. The following line of text is not indented.</p>
-
-<a id="a9.5.2.3"></a>
-<p class="h5"><b>9.5.2.3 \scenestars</b> inserts a one-line skip, containing three spaced, centered asterisks. The following line of text is not indented.</p>
-
-<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" >
-<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>
-Unfortunately, novelists of that era had so little to write about, or they would have chosen another family to pursue.\par
-</small></code></p>
-
-
-
-<a id="a9.5.3"></a>
-<h4>9.5.3 \IndentAfterScenebreak</h4>
-
-<p>This global command may only be used in the Preamble.</p>
-<p>Normally, text begins without a paragraph indent, at each new scene. This is standard in fiction. If you prefer that each new scene begins indented, use this command. It works with <code>\scenebreak</code>, <code>\sceneline</code>, and <code>\scenestars</code>.</p>
-
-
-
-<a id="a9.6"></a>
-<h3>9.6 Footnotes</h3>
-
-<p>This document class has <em>limited</em> support for footnotes, because footnotes are hardly ever used in original fiction. Nevertheless, they do appear on occasion.</p>
-<p>Footnotes appear at the bottom of the page where they are placed. There is no option to accumulate them to another location. Very long footnotes might straddle pages, but that situation is uncommon in fiction.</p>
-<p>If you have a lot of footnotes, consider endnotes instead. Both may be used.</p>
-
-
-<a id="a9.6.1"></a>
-<h4>9.6.1 \SetMarkers[<em>real,fake</em>]{<em>asterisk, dagger, number</em>}</h4>
-
-<p>This command is used only in the Preamble.</p>
-<p>A "marker" is a superscript or subscript, however used. Thus, a footnote or endnote is indicated by a marker in the main text (but not in the footnote or endnote itself).</p>
-<p>Most book-quality Open Type fonts have markers in style sets (sups, sinf, subs). In professional fonts, the marker glyph weights are adjusted for consisent appearance compared to ordinary glyphs. However, many free fonts do not adjust marker glyph weights, so the markers may appear too small, or too light.</p>
-<p>The option <code>real</code> (default) attempts to use the Open Type feature <em>sups</em> for superscripts, and the feature <em>sinf</em> (preferred) or <em>subs</em> (alternate) for subscripts. If the requested feature is not available, then it will be faked, by scaling/raising/lowering ordinary characters from the basefont (lining numerals will be used).</p>
-<p>Option <code>fake</code> ignores whether the Open Type features are available, and simply fakes them.</p>
-<p>Thus, you may choose whether real or fake markers look better, depending on the font you are using. What looks better in one font may not look better in another.</p>
-<p>The required argument applies only to markers created by the <code>\footnote</code> command. It does not apply to endnotes, or to manually placed superscripts and subscripts.</p>
-<p><code>asterisk</code> (default) uses symbolic footnote markers. The symbols rotate in order * † ‡ § ** †† ‡‡ §§ until reset.</p>
-<p><code>dagger</code> uses symbolic footnote markers, but without asterisks. The symbols rotate in order † ‡ § †† ‡‡ §§ until reset.</p>
-<p><code>number</code> uses numerical markers. Due to possible conflict, the log file will have a "Big Bad Warning" if you use a numerical footnote marker in a document that also has endnotes, since endnotes alays have numerical markers.</p>
-
-
-<a id="a9.6.2"></a>
-<h4>9.6.2 \realmarker \fakemarker</h4>
-
-<p>Within the body of the document, you may use <code>\realmarker</code> and <code>\fakemarker</code> to change your preference. The choice remains in effect until you change it again.</p>
-<p>The option real/fake applies wherever superscripts or subscripts are used, not just for footnotes or endnotes.</p>
-
-
-<a id="a9.6.3"></a>
-<h4>9.6.3 \footnote[<em>option</em>]{<em>text</em>}</h4>
-<p>The <code>\footnote{<em>text</em>}</code> command places a "marker" at the place where the command is written. The included text is written at the bottom of the page, beneath a short line that separates it from the main text. The footnote text is at smaller size and line skip, and has the same marker placed before it. All of this is automatic.</p>
-<p>You may, if necessary, apply some style to the footnote text. For example, if you are referring to another work, its title might be in italics.</p>
-<p>Normally, no option is used. If you use option <code>0</code> (zero) then no marker will appear in the main text, and the footnote text will appear without a marker. The count of markers is not incremented. This applies whether the markers are numbers or symbols.</p>
-<p>• Trick: If you are using footnote numbers, but wish to place a special footnote using a symbol, you can do it manually. For example:</p>
-<p class="code"><code>He blinked.*\footnote[0]{* No, he didn't.}</code></p>
-<p>• Avoid use of underlining, as it is considered bad style, due to visual distraction.</p>
-
-
-
-<a id="a9.7"></a>
-<h3>9.7 Endnotes</h3>
-
-<p>Endnotes are sometimes used in fiction, particularly for the kind of novel that pretends to be a lost manuscript, or the translation of an ancient text. The endnotes, by the fictional discoverer or translator, pretend to be an academic discussion of items in the main story. Unlike footnotes, which show quick points that must be immediately known by the reader during the story, endnotes are often a disguised chapter in themselves.</p>
-
-<p>You may use both footnotes and endnotes, if you wish. However, if endnotes are used, then footnotes must be marked by symbols, rather than by numbers, to avoid confusion. The counts for endnotes and footnotes are independent.</p>
-
-
-<a id="a9.7.1"></a>
-<h4>9.7.1 \endnote</h4>
-<p>The <code>\endnote</code> command inserts a superior number in the text. A running count of the numbers is automatically updated.</p>
-<p>The endnote numbers run continuously through the text, without reset. If you wish to reset the count (perhaps at new chapters), you have to do it manually, using <code>\ResetEndnote</code>.
-<p>When you use <code>\endnote</code> there is no provision for the actual note. If you wish to write a reminder to yourself, about why you put an endnote marker there, use <code>\memo{}</code>. The argument of <code>\memo</code> will not be printed, and will not be remembered for later use.</p>
-
-
-<a id="a9.7.2"></a>
-<h4>9.7.2 \endnotetext{<em>number</em>}{<em>text</em>}</h4>
-
-<p>The <code>\endnotetext</code> command is a simple way of styling endnotes. You do not have to use it, if you have your own method.</p>
-<p>The first argument is usually the endnote number. A period and following space will automatically be added, so that the text of the note is block-indented. You may use <code>\emph{<em>number</em>}</code> if you prefer the number to be in italics.</p>
-<p>The text must be one paragraph. Be sure to end with <code>\par</code> or equivalent.</p>
-<p>If the note needs more than one paragraph, then continue like this, with an empty note number:</p>
-<p class="code"><code>\endnotetext{}{\indent <em>text</em>}</code></p>
-<p>• In <code>novel</code>, you must create and style the page(s) with endnotes yourself! There is no provision for bibliography, and no provision for any other kind of automated styling. This is because the endnotes, being fictional, are more like the main text than any academic style. Think of the endnotes as just another chapter, but starting with something that identifies them as being endnotes.</p>
-<p>• Although <code>novel</code> provides several ways of partitioning backmatter, this is discouraged in fictional works. Normally, endnotes continue as mainmatter, with arabic page numbers.</p>
-
-
-<p>Example:</p>
-
-<p class="code">
-<code><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 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="447" height="151" alt="using endnotetext"></p>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-10-cover-art.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-10-cover-art.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-10-cover-art.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,256 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8">
-<title>Novel class documentation - Cover Artwork, CMYK 240 percent ink, PDF/X</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a10">Cover Artwork;<br>
-CMYK 240% Ink Limit;<br>
-PDF/X Compliance</a></p>
-
-<ul>
-
- <li><a href="#a10.1">10.1 Begin With PNG</a></li>
- <li><a href="#a10.2">10.2 Get Some Software</a></li>
- <li><a href="#a10.3">10.3 Convert to CMYK 240% Ink</a></li>
- <li><a href="#a10.4">10.4 Convert to PDF/X</a></li>
- <li><a href="#a10.5">10.5 Final Check</a></li>
- <li><a href="#a10.A">!0.A Appendix: The Color Gamut</a></li>
-
-</ul>
-
-<p> </p>
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="a10"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><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, Endnotes.</a></p>
-<p>10. Cover Artwork</p>
-<p><a href="noveldocs-11-debugging.html">11. Debugging</a></p>
-</div>
-
-
-
-<h2 style="clear:none">Cover Artwork, CMYK 240% Ink Limit;<br>
-PDF/X Compliance</h2>
-
-<p>This page serves a limited purpose. It is for the benefit of those who need to submit color print cover artwork in the form of a PDF/X-1a:2001 file, with the artwork as CMYK and 240% ink limit. This is the format required by some American print-on-demand services. It is also generally acceptable to others, whose requirements are less restrictive.</p>
-
-<p><b>Before you begin:</b> Do you really need to do this? Many print-on-demand services are perfectly happy to accept something such as an ordinary RGB jpeg image, as long as it has the correct size (with bleed area). They can easily process it for print production in a few moments, using professional software. If they do it, then whether or not you are surprised by the resulting colors, will depend on whether or not your original image is within the printer gamut. In other cases, the print service prefers (or insists) that you do the image print production processing yourself. Then, you get to see an emulation of the print colors <em>before</em> you submit the file, and can change your artwork if the resulting colors are disappointing.</p>
-
-<p>The <em>novel</em> document class does not provide any support for creating the original artwork, either image or text. In fact, TeX is not the best way to do that. Use a graphics program (such as the free GIMP) to do your artwork, including text. In the end, your text will be rasterized, just like any background image. For this reason, avoid using small text, and consider using a sans-serif typeface on the cover (even though there is no sans-serif in the book itself).</p>
-
-<p>DO NOT PLACE A BARCODE. If your print service requests a white rectangle where the barcode will go, then include it in your image. Almost every print service is willing to create the barcode from your ISBN, and place the barcode image into your PDF during post-processing. Some of them even demand that they do it themselves. Do-it-yourself barcodes are incompatible with the following instructions.</p>
-
-<p><b>DISCLAIMER:</b> This documentation, and its accompanying software, is offered AS-IS, WITHOUT WARRANTY EXPRESS OR IMPLIED. USE ONLY AT YOUR OWN RISK. The author is an amateur who does not profess expertise in these matters.</p>
-
-
-
-<a id="a10.1"></a>
-<h3>10.1 Begin With PNG</h3>
-
-<p>Create your artwork, including all text (but not barcode or barcode text) using whatever means you have. How you do it is not relevant. To follow these instructions, you must provide the artwork as a flattened (no transparency) PNG format image, at correct size (including bleed area) and resolution (dpi).</p>
-
-<p style="margin-top:8px"><b>Example:</b> Suppose your book is 5.5" x 8.5" softcover, a typical size for American fiction. Based on its page count and paper, you are told that the spine width must be 0.62". The required beed width, on all four sides, must be 0.125".</p>
-
-<p>Then, the image is 0.125 + 5.5 + 0.62 + 5.5 + 0.125 = 11.87in wide.</p>
-
-<p>The image is 0.125 + 8.5 + 0.125 = 8.75in high.</p>
-
-<p>At 300dpi resolution (a typical value) the image must be 11.87 x 300 = 3561 picels wide, and 8.75 x 300 = 2625 pixels high. In case of fractional pixels, round upward. The exact pixel count is important.</p>
-
-<p style="margin-top:8px"><img src="html-resources/example-adobergb.png" class="floatright" width="445" height="328" alt="example rgb image"> It is best to use the AdobeRGB1998 color workspace, or equivalent. But you can also use sRGB, or equivalent, and in many cases you will not notice much difference. It is helpful to attach (embed) the workspace color profile in your PNG image, especially if it is something other than AdobeRGB1998 or sRGB. Note that the workspace is NOT the color profile of your monitor (if you have it). If you do not attach (embed) the workspace color profile, then remember whether you were using AdobeRGB1998 or sRGB. If you make a mistake here, it is not fatal. It merely means that some colors (particularly bright greens and blue-greens) will print somewhat brighter or duller than you were expecting.</p>
-
-<p>When done, export it as a flattened PNG. An example image of this size can be found in the EXTRAS/novel-coverart-demo folder of the author's <a href="https://github.com/RobtAll/novel/" rel="external" target="new">GitHub site</a>.</p>
-
-<p>If you are provided with an image other than PNG, you have to convert it to PNG. No alternative. It is easy enough to use GIMP to convert most image formats. If you have a PDF (which is not already in the required format), GIMP can probably open it as an image. Be sure you import it with the correct resolution. Again, the pixel width and height are important.</p>
-
-<p><b>Cover Text:</b> These instructions assume that your cover text is rasterized, and is part of the image rather than vector text. In many cases your graphics program has enough text capability to do what you need.</p>
-
-<p>If you wish to use TeX to typeset the cover text, do it this way: Use TeX to create one or more PDFs of the cover text, without images. You can create several blocks of text at different pages sizes, if you wish. Open your background artwork in GIMP. Add a new transparent layer above it. Open a text PDF in GIMP. Choose resolution 300dpi, full antialiasing, grayscale or color. The opened text is now a raster image. Copy it, and paste it atop the transparent layer. Anchor it. Use Color: Color to Alpha: white to alpha filter. That removes the white area from the PDF image. Finally, move the text to where it should go. You can rotate the text 90 degrees, but do not resize it! If you would rather the text be at a different size, then either change it in TeX, or use a different resolution when you open the PDF in GIMP. Note that even when you open the PDF at a different resolution, it will still be at 300dpi when you place it over the 300dpi background image; but its size will change.</p>
-
-
-<a id="a10.2"></a>
-<h3>10.2 Get Some Software</h3>
-
-<p>You need the 238% ink limit color profile from <a href="http://www.newselfpublishing.com/TotalInkLimit.html" rel="external" target="new">Aaron Shepard</a>. This does the magic of ensuring that you comply with the 240% ink limit (the profile provides a little headroom, which seems necessary). It can also be used for softproofing, if you know how to do that. This is not the only possible profile, but it seems to me that it is the best of several available.</p>
-
-<p>You might (or might not) need the <a href="https://www.adobe.com/support/downloads/iccprofiles/iccprofiles_win.html" rel="external" target="new">Adobe icc profiles</a> (for end users). This link works for Windows or Linux (even though it says "for Windows"). I am told that there is a different link for Mac, but I don't have a Mac.</p>
-
-<p>Get GraphicsMagick or ImageMagick. On Linux, you can install it via your system package manager. On Windows, get GraphicsMagick Q16 binaries for your system (32 or 64 bit) from <a href="https://sourceforge.net/projects/graphicsmagick/files/graphicsmagick-binaries/" rel="external" target="new">SourceForge</a>. I am told that versions for Mac are available via homebrew and macports, but again, I do not have a Mac, so I cannot check that. Or, get ImageMagick Q16 for various platforms from <a href="https://www.imagemagick.org/script/download.php" rel="external" target="new">here</a>.</p>
-
-
-
-<a id="a10.3"></a>
-<h3>10.3 Convert Your Image to CMYK at 240% Ink Limit</h3>
-
-<p><img src="html-resources/example-cmyk238.png" class="floatright" width="445" height="328" alt="example cmyk238 image, back to rgb"> At right, you can see an emulation of the above cover artwork, softproofed to CMYK at 238% ink limit. It is not the CMYK file itself, but an RGB image that is supposed to help you visualize what happens during conversion. You will notice that the colors are less intense, because the original image contained colors that didn't fit the gamut of the printing process. Colors don't always change; I could have planned ahead, and selected from a palette of colors that fit within the gamut.</p>
-
-<p><b>Get ready:</b> Make a copy of the above 238% ink limit color profile, and re-name the copy as "238.icc".
-
-<p>I will call your original PNG image "yourimage.png". Put this image, the 238.icc file, and (if necessary) the AdobeRGB1998.icc file in a single working folder.</p>
-
-<p>I will also assume that the image resolution is 300dpi. If it is something else, then modify 300 to the other number, when you see it below.</p>
-
-<p style="margin-top:16px"><b>Step 1:</b> Open a Terminal (Command Prompt) and navigate to that folder.</p>
-
-<p>In the following commands, the initial "gm" calls GraphicsMagick (same code Linux and Windows). If you prefer ImageMagick, then eliminate the initial "gm" on Linux, or change the "gm" to "magick" on Windows.</p>
-
-<div class="codeblock">
-<p><code>gm convert yourimage.png embedded.icc</code></p>
-</div>
-
-<p>The above command may return the message "No color profile available" and generate a zero-byte embedded.icc file. Not a problem. Discard the zero-byte file. But if it generates a non-zero embedded.icc file, keep it.</p>
-
-<p style="margin-top:16px"><b>Step 2:</b> Next (note the file extensions):</p>
-
-<div class="codeblock">
-<p><code>gm convert -strip yourimage.png yourimage-stripped.tif</code></p>
-</div>
-
-<p style="margin-top:16px"><b>Step 3:</b> At this point, there are three possibilities:</p>
-
-<p><b>(a)</b> You have a non-zero embedded.icc file. In this case:</p>
-
-<div class="codeblock">
-<p><code>gm convert -profile embedded.icc -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
-</div>
-
-<p><b>(b)</b> No embedded.icc, but you know that the artwork was create using AdobeRGB1998 workspace, or equivalent. Then:</p>
-
-<div class="codeblock">
-<p><code>gm convert -profile AdobeRGB1998.icc -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
-</div>
-
-<p><b>(c)</b> Neither of the above. The image is probably sRGB (default), so:</p>
-
-<div class="codeblock">
-<p><code>gm convert -profile 238.icc yourimage-stripped.tif yourimage-temp.tif</code></p>
-</div>
-
-<p style="margin-top:16px"><b>Step 4:</b> Now, regardless of which possibility you used above:</p>
-
-<div class="codeblock">
-<p><code>gm mogrify -strip yourimage-temp.tif</code></p>
-</div>
-
-<p style="margin-top:16px"><b>Step 5:</b> And finally:</p>
-
-<div class="codeblock">
-<p><code>gm convert -units PixelsPerInch -density 300 -quality 100 yourimage-temp.tif yourimage-cmyk240.jpg</code></p>
-</div>
-
-<p style="margin-top:16px"><b>Step 6:</b> Now verify your work:</p>
-
-<div class="codeblock">
-<p><code>gm identify -verbose yourimage-cmyk240.jpg</code></p>
-</div>
-
-<p>The report should show that the image is CMYK, that it is at 300 pixels/inch, and that there is NO entry for "Profile-color". It will not have anything to say about ink limit, or SWOP.</p>
-
-
-
-
-<a id="a10.4"></a>
-<h3>10.4 Convert your CMYK Image to PDF/X.</h3>
-
-<p>Up to now, you did not need TeX. Now you do. Be sure that you have a working TeX installation, with the <em>novel</em> document class package.</p>
-
-<p>In folder (your TeX root)/doc/lualatex/novel/extras you will find file "novel-cover-template.tex". Place a copy in the same working folder as your image, and modify it as needed.</p>
-
-<p><code>\SetMediaSize</code> refers to the full size of the image, with units (usually in). This includes the bleed box. For the example image, <code>\SetMediaSize{11.87in}{8.75in}</code>.</p>
-
-<p><code>\SetTrimSize</code> refers to the trimmed image, without bleed. For the example image, <code>\SetTrimSize{11.62in}{8.5in}</code>.</p>
-
-<p><code>\SetPDFX[CGATSTR001]{X-1a:2001}</code> will get you "Us Web Coated SWOP v2" output intent (most common the USA), and PDF/X-1a:2001 compliance. The Output Intent *.icc color profile will NOT be embedded, because this is almost always the way that print services want it. The PDF contains a code identifying the intent, so there is no need to embed the color profile (and disadvantages to embedding it). In the unlikely event that they demand the Output Intent color profile embedded, put an asterisk on the command.</p>
-
-<p>For compliance you need to use <code>\SetTitle</code>. The title for this file might not be the title of your book, because this file isn't your book. Ask you print service what they want. Same with <code>\SetAuthor</code>.</p>
-
-<p>You can use <code>\SetApplication</code> and <code>\SetProducer</code> to change internal identifiers. Don't use these unless you have a reason.</p>
-
-<p><code>\SetCoverImage</code> is self-explanatory. Must have file extension jpg, jpeg, JPG, or JPEG. Must be CMYK. Note that TeX cannot verify whether the image is in correct color space. It will compile, even if the image is wrong. Beware!</p>
-
-<p>Do not attempt to write anything between <code>\begin{document}</code> and <code>\end{document}</code>. If you erroneously put some text there, the document will probably compile, and it may even be a valid PDF/X file. However, the resulting text color will almost surely be wrong. If so, the problem will be detected when you submit your file (wrong ink limit or color space). However, this is not a fundamental limit. It is possible to place TeX text over the image, but this documentation (as of version 1.32) does not show you how to do that.</p>
-
-<p>Compiling may take a little longer than expected. If your TeX system opens a PDF viewer automatically, the image might be missing (or partial) until a few seconds after the viewer opens. Be patient. The file size is large.</p>
-
-
-
-<a id="a10.5"></a>
-<h3>10.5 Final Check</h3>
-
-<p>Open the PDF in Adobe Reader, which does a trick that no other free software will do, to my knowledge. If your platform does not have Adobe Reader, then find a friend who has it. May be a different platform.</p>
-
-<p>In Adobe Reader, go to Edit, Preferences, Documents. Check "Save As optimizes for fast web view." Then go to Edit, Preferences, Page Display. Check "Show art, trim, and bleed boxes." Then OK.</p>
-
-<p>Open your PDF. You should see a light green box, just inside the image boundary. This shows the Trim Area. This box does not print; it is only for visualization. Go to File, Properties, Fonts. There should be no fonts listed.</p>
-
-<p>Then, "Save As" the same file name (or another one, if you prefer). This will optimize the file. You probably do not need to do that, but it does not hurt, and a few services expect it.</p>
-
-<p>There will always be some difference between color as viewed on your monitor, and color as printed. This is due to the difference between emitted light (your monitor) and reflected light (print). In professional use, the monitor will be calibrated, and operated at a specific screen brightness. The print will be viewed under lighting with a specific color temperature and illumination. Your own colors are not that critical, are they? If you have a calibrated monitor, and view the PDF and images in color-managed software, then what you see on your computer will be reasonably close to what prints. If your monitor is not calibrated, or you are not using color-managed software, then the printed cover may have its greens a bit more colorful than you were expecting. That doesn't mean there will be a greenish cast. It merely means that things such as spring leaves and shamrocks will be a bit greener (in print) than you expected.</p>
-
-<p><b>Remember the Disclaimer!</b> Your PDF file should now be ready for submission. Only "should," not "is," because this documentation and its accompanying software comes without warranty. Submit at your own risk!</p>
-
-<p>All I can say is that it "works for me." Screenshot from Adobe Acrobat Pro:</p>
-
-<p class="centerimg"><img src="html-resources/verified238.png" width="700" height="446" alt="works for me"></p>
-
-
-<a id="a10.A"></a>
-<h3>10.A Appendix: The 240% Ink Limit Color Gamut</h3>
-
-<p><img src="extras/SWOP240gamutHSV.png" class="floatright" width="225" height="265" alt="240% gamut samples"> At right are color samples in the HSV color coordinate system (as used in color picker for GIMP 2.8 software). Each sample would normally be a rectangle, with lightness as horizontal axis, and saturation as vertical axis. Note that "saturation" is a technical term, not to be confused with "chroma (colorfulness). The highest chroma would be at upper right of each rectangle. There are 36 hues, corresponding to 10 degree increments on the HSV color wheel.</p>
-
-<p>A portion of each rectangle has been whited-out. Those colors are inaccessible to the SWOP CMYK printing process with 240% ink limit. Most of the inacessible colors are at the upper left of each rectangle, where the combination of low lightness and high saturation would call for too much ink. In a few cases, the inacessible colors simply cannot be reached by standard CMYK inks.</p>
-
-<p>In general, the range of color that can be accurately portrayed on a consumer-grade laptop monitor is smaller than the range that can be printed. So, in the above image, your monitor is faking many of the colors, by showing them as closely as it can. The method of faking may depend on your computer, and on your browser. In many cases, nearby colors are also faked, so that the color error is not all in one place.</p>
-
-<p><img src="extras/SWOP240gamutHSV-monitorlimit.png" class="floatright" width="225" height="265" alt="240% gamut with monitor limit"> At right, the colors that are probably faked by your monitor have also been whited out. These tend to be in the upper portions, where the colors are too chromatic for inexpensive LCD technology. Expensive professional monitors could show more. If you look back at the first image, you will see that the faked areas seem to be in a uniform color, because your monitor cannot display the differences.</p>
-
-<p>If your cover artwork uses colors from the first image, then those RGB values can be reasonably well converted to printable CMYK at 240% ink limit. What you'll be missing are richly colored shadows.</p>
-
-<p>If you limit your cover artwork to colors in the second image, then you are much less likely to be surprised by overly colorful areas in print, which couldn't be seen that way on your monitor. On the other hand, maybe you would like to use all of the colors available in the first image, with the understanding that the printed color will be a bit surprising. It's up to you.</p>
-
-<p>You may have heard that when artwork is converted to CMYK 240%, colors tend to be "duller." Not necessarily. The second image looks much duller than the first, but that is because large areas of identically-faked color have been whited out. Those colors are still in the second image, but they only occupy a thin boundary of the remaining color.</p>
-
-<p>The full-size color sample images are in docs folder <code>extras</code>, and are named <code>SWOP240gamutHSV.png</code> and <code>SWOP240gamutHSV-monitorlimit.png</code>.</p>
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Deleted: trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-11-debugging.html
===================================================================
--- trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-11-debugging.html 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/doc/lualatex/novel/noveldocs-11-debugging.html 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,141 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8">
-<title>Novel class documentation - Debugging</title>
-<link rel="stylesheet" type="text/css" href="html-resources/novel-doc.css">
-</head>
-
-<body>
-<div id="master">
-
-
-<div id="toc">
-
-<p>Document class "novel"</p>
-
-<p><a href="#a11">11. Debugging</a></p>
-
-<ul>
- <li><a href="#a11.1">11.1 Ordinary Novel Tracking</a></li>
- <li><a href="#a11.2">11.2 Debug Novel Tracking</a></li>
- <li><a href="#a11.3">11.3 Your Own Debug Tracking</a></li>
-</ul>
-
-<p> </p>
-</div><!-- end toc -->
-
-
-
-<div id="main">
-<a id="thetop"></a>
-<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.38.</p>
-
-
-<div class="pagetopage">
-<p><b>User Guide</b></p>
-<p><a href="noveldocs-01-overview.html">1. Overview</a></p>
-<p><a href="noveldocs-02-class-options.html">2. Class Options</a></p>
-<p><a href="noveldocs-03-metadata-pdfx.html">3. Metadata, PDF/X</a></p>
-<p><a href="noveldocs-04-layout.html">4. Page Layout</a></p>
-<p><a href="noveldocs-05-fonts.html">5. Choosing Fonts</a></p>
-<p><a href="noveldocs-06-header-footer.html">6. Headers, Footers</a><br>
-<p><a href="noveldocs-07-text-size-style.html">7. Text Sizes, Styles</a></p>
-<p><a href="noveldocs-08-images.html">8. Using Images</a></p>
-<p><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, Endnotes.</a></p>
-<p><a href="noveldocs-10-cover-art.html">10. Cover Artwork</a></p>
-<p>11. Debugging</p>
-</div>
-
-
-<a id="a11"></a>
-<h2 style="clear:none">11. Debugging</h2>
-
-<p>New in version 1.34.</p>
-
-<p>The <code>debug</code> class option is primarily for developers. However, ordinary users may sometimes find it helpful. Do not use this option with a document that compiles successfully, even if it does not look the way you wanted it to look. Debuggin code does not change the PDF, but writes many additional messages to the log file, which are not necessary when the run is successful.</p>
-
-<p>The debugging information is also written to your console (terminal window or GUI application).</p>
-
-
-
-<a id="a11.1"></a>
-<h3>11.1 Ordinary Novel Tracking</h3>
-
-<p>If you look at the log file for a successful run, you will see several messages that look something like this:</p>
-
-<p class="code"><code>Novel Tracking 0.2: novel-FileData.sty loaded.</code></p>
-
-<p>That message was written to the log file at the time the compiler encountered code this code:</p>
-
-<p class="code"><code>\typeout{Novel Tracking 0.2: novel-FileData.sty loaded.}</code></p>
-
-<p>Then, you know that the compiler successfully reached that point in execution. Tracking numbers beginning with <code>0.</code> are in the <code>novel.cls</code> main file, and are written to the log whether or not you use the <code>debug</code> option. If a tracking number is missing, or out of numerical order, it merely means that your document setup has followed a particular fork in the code.</p>
-
-<p>What if the run is unsuccessful? You know it succeeded up to the point where the last tracking number (in log order, not numerical order) was written, and must have failed at some point after that.</p>
-
-
-<a id="a11.2"></a>
-<h3>11.2 Debug Novel Tracking</h3>
-
-<p>When the <code>debug</code> option is used, additional tracking codes appear in the log file. These are generated from the various subsidiary files that are part of the <code>novel</p> package. For example:</p>
-
-<p class="code"><code>Novel Tracking 3.4.1 in novel-LayoutSettings.sty.</code></p>
-
-<p>is written to the log file, when the following line of code is encountered, located in file <code>novel-LayoutSettings.sty</code>:</p>
-
-<p class="code"><code>\NDB{3.4.1 in novel-LayoutSettings.sty.}</code></p>
-
-<p>The <code>\NDB</code> macro detects whether or not you are using the <code>debug</code> option.</p>
-
-<p>So, when you see that log message, you know that the code leading to it was successfully executed.</p>
-
-<p>Keep in mind that due to forks in the logic, successive Novel Tracking messages may have code numbers all over the place, and some of them may be skipped or repeated. But more likely than not, if your document fails to compile, the error was triggered by code that soon follows the last successful Novel Tracking message, in that same file.</p>
-
-<p>The cause of an error may be any of these things:<br>
- (1) An error in novel's own code.<br>
- (2) Error in another package used by novel.<br>
- (3) Your own document code.</p>
-
-<p>The first instance is possible, but unlikely, because each update of <code>novel</code> is tested before release.</p>
-
-<p>In the second case, the offending package hopefully provides its own error message. If that package has recently been updated, then perhaps an error crept in, and will be quickly resolved when others report it.
-
-<p>The third case is up to you. Note that bad code is often not detected until the point where it is used. For example, suppose you define the following macro in your Preamble, where <code>\BADCODE</code> is undefined:</p>
-
-<p class="code"><code>\newcommand\mymonkeywrench{\BADCODE}</code></p>
-
-<p>That will not throw an error when it is parsed. If you do not use <code>\mymonkeywrench</code> anywhere, then it will not throw an error. But if you use <code>\mymonkeywrench</code> on page 214 of your novel, that's where the error will finally appear.</p>
-
-
-<a id="a11.3"></a>
-<h3>11.3 Your Own Debug Tracking</h3>
-
-<p>You can add Novel Tracking messages to your own code. You can put the messages inside macros, or simply insert them somewhere in the text.</p>
-
-<p>For example, you could do something like this, where the <code>22.5</code> is arbitrary:</p>
-
-<p class="code"><code>\newcommand\mymonkeywrench{\NDB{User 22.5 page \thepage.}\BADCODE}</code></p>
-
-<p>Then, if that macro is invoked on page 214, it will write this to the log file:</p>
-
-<p class="code"><code>Novel Tracking User 22.5 page 214.</code></p>
-
-<p>For a complicated macro, you could put Novel Tracking at its start and at its end. Then you will know whether the macro was accessed, and if it successfully completed.</p>
-
-<p>Remember that when you insert the <code>\NDB{}</code> code, you have to pay attention to white space. In some cases, you must avoid space before or after it. And, if the code is on its own line, you might need to terminate the line with a percent <code>%</code> so that the line return is not read into your document.</p>
-
-
-
-</div><!-- end main -->
-
-<div id="finish"></div>
-
-</div><!-- end master -->
-
-</body>
-</html>
-
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-CGATSTR001.clo
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-CGATSTR001.clo 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-CGATSTR001.clo 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,4 +1,4 @@
-% Typically used in the USA. Novel file version 1.38
+% Typically used in the USA. Novel file version 1.40
% The values of the arguments are public industry standards.
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-CalculateLayout.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-CalculateLayout.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-CalculateLayout.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -12,7 +12,7 @@
%%
%%
\ProvidesFile{novel-CalculateLayout.sty}%
-[2017/08/15 v1.38 LaTeX file (layout calculations)]
+[2017/09/14 v1.40 LaTeX file (layout calculations)]
%%
%%
@@ -19,8 +19,6 @@
%% This file is loaded \AtEndPreamble, which precedes \AtBeginDocument.
%%
-%% Novel Tracking messages in this file begin with 9.
-\NDB{9.0 in novel-CalculateLayout.sty.}
\newlength\normalFontSize % becomes 1em in normal text.
\newlength\normalBaselineSkip % also abbreviated as \nbs
@@ -37,7 +35,6 @@
\SetMediaSize{5.5in}{8.5in}
\fi
\fi
-\NDB{9.1 in novel-CalculateLayout.sty.}
% Default margins are based on Trim Height, if user does not set margins.
% Works for standard w/h aspect ratios, but not for exotically narrow.
\if at MarginsSet\else
@@ -72,7 +69,6 @@
} % end internal dimtest
} % end dimtest for margins.
\fi % end default margins
-\NDB{9.2 in novel-CalculateLayout.sty.}
%
% Choose default font size based on Trim Width, unless font size set by user:
\if at FontSizeSet\else
@@ -86,7 +82,6 @@
} % end internal dimtest
} % end dimtest for font size.
\fi
-\NDB{9.3 in novel-CalculateLayout.sty.}
%
% Default lines/page based on Trim Height, font size, unless LPP set by user:
\if at LinesPerPageSet\else
@@ -102,7 +97,6 @@
\FPclip{\@tempLPP}{\@tempLPP} % remove excess trailing 0.
\gdef\my at LinesPerPage{\@tempLPP}
\fi
-\NDB{9.4 in novel-CalculateLayout.sty.}
%
% Correct bottom margin for descenders, assumed to be 0.3em:
\addtolength\Old at BottomMargin{0.3\Old at FontSize}
@@ -120,7 +114,6 @@
%
%% end set default sizes and initial corrections
-\NDB{9.5 in novel-CalculateLayout.sty.}
%% OLD, NEW, CURRENT, LIVE, TEXT MACRO DEFINITIONS
@@ -180,7 +173,6 @@
%
%% End old, new... macro definitions.
-\NDB{9.6 in novel-CalculateLayout.sty.}
%% PRELIMINARY CALCULATION OF BASELINESKIP
%% -----------------------------------------------------------------------------
@@ -199,7 +191,6 @@
\if at gotFooter % allow for footer jump
\FPadd{\adj at LinesPerPage}{\adj at LinesPerPage}{\@footjump}
\fi
-\NDB{9.7 in novel-CalculateLayout.sty.}
%
% Baseline Skip is Live Height divided by adjusted number of lines.
% Thus initially, Text (with header/footer) occupies full Live Height.
@@ -221,7 +212,6 @@
%
%% End preliminary calculation of baselineskip.
-\NDB{9.8 in novel-CalculateLayout.sty.}
%% FIT CurrentTextWidth TO NewLiveWidth
@@ -235,7 +225,6 @@
%
%% end fit CurrentTextWidth to NewLiveWidth
-\NDB{9.9 in novel-CalculateLayout.sty.}
%% ADJUST CurrentBaselineSkip TO FIT NewLiveHeight
%% -----------------------------------------------------------------------------
@@ -247,7 +236,6 @@
\setlength\Current at BaselineSkip{\Current at BaselineSkipNum pt}
\FPmul{\Current at TextHeightNum}{\Current at BaselineSkipNum}{\adj at LinesPerPage}
\fi
-\NDB{9.10 in novel-CalculateLayout.sty.}
% Check if the revised skip is too small:
\FPdiv{\@ratioBLtoFS}{\Current at BaselineSkipNum}{\Current at FontSizeNum}
\FPiflt{\@ratioBLtoFS}{1.2} % Too small. Re-tweak font, text width, skip.
@@ -266,9 +254,7 @@
%
%% end adjust CurrentBaselineSkip to fit NewLiveHeight.
-\NDB{9.11 in novel-CalculateLayout.sty.}
-
%% DISTRIBUTE SIDE EXCESS
%% -----------------------------------------------------------------------------
%% The prior calculation may have shrunk CurrentTextWidth below NewLiveWidth.
@@ -280,7 +266,6 @@
%
%% end distribute side excess.
-\NDB{9.12 in novel-CalculateLayout.sty.}
%% SET TEXTWIDTH, FONT SIZE, BASELINESKIP
@@ -294,7 +279,6 @@
\@setfontsize\normalsize\normalFontSize{\normalBaselineSkip}%
\normalsize % Defined in `novel.cls'. Uses numbers, not lengths.
%
-\NDB{9.13 in novel-CalculateLayout.sty.}
\newlength\nfs % abbreviation for normal fontsize
\setlength\nfs{\normalFontSize}
\gdef\nfsnum{\strip at pt\nfs}
@@ -301,7 +285,6 @@
\newlength\nbs % abbreviation for normal baselineskip
\setlength\nbs{\normalBaselineSkip}
\gdef\nbsnum{\strip at pt\nbs} % just the numerical part
-\NDB{9.14 in novel-CalculateLayout.sty.}
%
% This document class limits range of normal point size:
\FPiflt{\Current at FontSizeNum}{8}%
@@ -327,7 +310,6 @@
\typeout{^^JClass `novel' Alert: Line spacing is allowable, but wide.^^J%
Consider more lines per page, or add header or footer.^^J}%
\fi
-\NDB{9.15 in novel-CalculateLayout.sty.}
%
\FPdiv{\Ratio at BaselineSkip}{\Current at BaselineSkipNum}{\Old at BaselineSkipNum}
\FPround{\Ratio at BaselineSkip}{\Ratio at BaselineSkip}{3}
@@ -336,7 +318,6 @@
\FPdiv{\Ratio at EM}{\Current at FontSizeNum}{\Old at FontSizeNum}
\FPround{\Ratio at EM}{\Ratio at EM}{3}
\FPclip{\Ratio at EM}{\Ratio at EM}
-\NDB{9.16 in novel-CalculateLayout.sty.}
% Alert if images scaled by \Rework:
\ifthenelse{\equal{\Ratio at EM}{1} \AND \equal{\Ratio at BaselineSkip}{1}}{}{%
\typeout{^^JClass `novel' Alert: Due to \string\Rework\space there may be^^J%
@@ -362,10 +343,8 @@
%
%% end set textwidth, font size, baselineskip
-\NDB{9.17 in novel-CalculateLayout.sty.}
-
%% BEGIN LAYOUT CALCULATIONS
%% -----------------------------------------------------------------------------
%
@@ -378,7 +357,6 @@
\setlength\headheight{0pt}
\setlength\headsep{0pt}
\fi
-\NDB{9.18 in novel-CalculateLayout.sty.}
%
% Prior to this, the following were set by user or calculated:
% \textwidth \headsep \headheight
@@ -396,9 +374,7 @@
\fi
%%
-\NDB{9.19 in novel-CalculateLayout.sty.}
-
%
% Standard TeX \hoffset and \voffset is not relative to the MediaBox, but is
% relative to 1in from the top left corner of the MediaBox. Ouch.
@@ -439,7 +415,6 @@
\fi
%%
-\NDB{9.20 in novel-CalculateLayout.sty.}
%
% \evensidemargin is at the left (outside edge) of verso pages.
@@ -457,10 +432,7 @@
\fi
%%
-\NDB{9.21 in novel-CalculateLayout.sty.}
-
-
%
% \topmargin is measured from 1in below the top of the MediaBox, to the top of
% whatever comes first (header or textblock). May be negative.
@@ -484,7 +456,6 @@
\fi
%%
-\NDB{9.22 in novel-CalculateLayout.sty.}
% Vertical position of the textblock is measured to the "top" of the first line
% of text. But that could be an X height, or an accented character height,
@@ -519,7 +490,6 @@
\fi
%%
-\NDB{9.23 in novel-CalculateLayout.sty.}
%% End layout calculations.
@@ -549,7 +519,6 @@
\fi
% End when Media Size exceeds Trim Size.
-\NDB{9.24 in novel-CalculateLayout.sty.}
% When Media Size = Trim Size, cropmarks are disabled.
% Too late for \@cropviewfalse; OK since CropBox already calculated properly.
@@ -569,7 +538,6 @@
\newlength\adj at NewLiveHeight
\setlength\adj at NewLiveHeight{\New at LiveHeight+0.3\normalFontSize}
%
-\NDB{9.25 in novel-CalculateLayout.sty.}
\gdef\@getPageXY{
\check at IsVerso % defined in novel-HeadFootStyles.sty
\if at isVerso
@@ -591,7 +559,6 @@
\setlength\Live at By{\Trim at By+\New at BottomMargin-0.3\normalFontSize}
}
%
-\NDB{9.26 in novel-CalculateLayout.sty.}
%% With class option `shademargins' (only effective in draft mode):
@@ -625,7 +592,6 @@
\fi%
\fi % end \if at shademargins
%
-\NDB{9.27 in novel-CalculateLayout.sty.}
% Labels each page with DRAFT at upper left, if in draft mode:
\if at useDraftMode
@@ -634,7 +600,6 @@
}%
\fi
%
-\NDB{9.28 in novel-CalculateLayout.sty.}
% Cropmarks (trim marks, really) are not important in this document class.
% That's because the targeted printing services generally do not want them.
@@ -694,7 +659,6 @@
%
%% end cropmarks
-\NDB{9.29 in novel-CalculateLayout.sty.}
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-ChapterScene.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-ChapterScene.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-ChapterScene.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-ChapterScene.sty}%
-[2017/08/15 v1.38 LaTeX file (chapter and scene macros)]
+[2017/09/14 v1.40 LaTeX file (chapter and scene macros)]
%%
-%% Novel Tracking messages in this file begin with 6.
-\NDB{6.0 in novel-ChapterScene.sty.}
% Class `novel' does not use \maketitle.
@@ -27,7 +25,6 @@
You must make your own title pages!^^J}%
}
%
-\NDB{6.1 in novel-ChapterScene.sty.}
%% SCENE CHANGES
@@ -57,7 +54,6 @@
\raisebox{-.3em}{*\quad\quad*\quad\quad*}\hfil\par%
}
%% end scene changes
-\NDB{6.2 in novel-ChapterScene.sty.}
%% Repair \FirstLine{} command from `magaz' package.
@@ -67,7 +63,7 @@
% and empty line to restore grid and absorb the noindent.
% Starred version uses the original \FirstLine definition, just in case
% the following paragraph has some exotic feature.
-% Thanks to user `egreg' at tex.stackexchange.com for debug assistance.
+% Thanks to user `egreg' at tex.stackexchange.com for assistance.
\let\oldFirstLine\FirstLine
\def\FirstLine{\@ifstar\FirstLineFoo\@FirstLineFoo} % improved
\def\FirstLineFoo#1{\oldFirstLine{#1}} % starred restores original def.
@@ -75,7 +71,6 @@
\oldFirstLine{#1}\par\vspace{-\nbs}\strut\par%
}
%%
-\NDB{6.3 in novel-ChapterScene.sty.}
%% ChapterStart environment.
@@ -90,7 +85,6 @@
% The argument is the number of normal baselineskips high:
\newenvironment{ChapterStart}[1][10]
{%
- \NDB{6.4.0 in novel-ChapterScene.sty.}%
\setlength\@oldparindent{\parindent}%
\global\@oldparindent=\@oldparindent%
\setlength\parindent{0pt}%
@@ -102,9 +96,7 @@
\null%
\setcounter{@linequarter}{0}%
\begin{textblock*}{\textwidth}[0,0](0pt,0pt)%
- \NDB{6.4.1 in novel-ChapterScene.sty.}%
}{% close the environment:
- \NDB{6.4.3 in novel-ChapterScene.sty.}%
\ifthenelse{%
\equal{\value{@linequarter}}{1} \OR \equal{\value{@linequarter}}{5}%
\OR \equal{\value{@linequarter}}{9} \OR \equal{\value{@linequarter}}{13}%
@@ -123,12 +115,10 @@
\setlength\parindent{\@oldparindent}%
\global\parindent=\parindent%
\nov at AfterGroup\NoIndentAfterThis% etextools and noindentafter
- \NDB{6.4.4 in novel-ChapterScene.sty.}%
}
%%
\LetLtxMacro\ChapterDisplay\ChapterStart\relax % deprecated
\LetLtxMacro\endChapterDisplay\endChapterStart\relax % deprecated
-\NDB{6.5 in novel-ChapterScene.sty.}
%
\newcommand\ChapterTitle[2][c]{% optional alignment l, c, r
\ignorespaces%
@@ -144,7 +134,6 @@
\fi%
{\@csalign\stake\smash{{\chapterfont{}#2}}\par}%
}
-\NDB{6.6 in novel-ChapterScene.sty.}
%
\newcommand\ChapterSubtitle[2][c]{% optional alignment l, c, r
\vspace{0.25\nbs}\addtocounter{@linequarter}{1}
@@ -159,7 +148,6 @@
\fi%
{\@csalign{\stake\smash{\subchfont #2}}\par}%
}
-\NDB{6.7 in novel-ChapterScene.sty.}
% In ChapterDeco, a trick is used. Instead of two optional arguments, and
% instead of using expl3 syntax to create different argument delimiters,
% the arguments for alignment and scale are passed as a single option.
@@ -190,7 +178,6 @@
}
%
%%
-\NDB{6.8 in novel-ChapterScene.sty.}
%% \Epigraph[align,scale,width]{text} OBSOLETE IN CODE VERSION 1.2
@@ -226,8 +213,41 @@
\NoIndentAfterThis%
} % end \QuickChapter
%%
-\NDB{6.9 in novel-ChapterScene.sty.}
+%% New in version 1.40: \cleartorecto and \cleartoend
+% \cleartorecto works same as \clearpage when next page is recto.
+% If next page would be verso, a blank verso is inserted,
+% so that the following material is recto.
+% \cleartoend is used at very end of book.
+% It adds a blank page. If the blank is verso, end of book.
+% But if that blank is recto, it adds a second blank page, end of book.
+% So, the book always ends with a blank verso.
+\gdef\cleartorecto{
+ \clearpage
+ \ifodd\c at page
+ \else
+ \thispagestyle{empty}
+ \null
+ \clearpage
+ \fi
+}
+\gdef\cleartoend{
+ \ifodd\c at page
+ \clearpage
+ \thispagestyle{empty}
+ \null
+ \clearpage
+ \else
+ \clearpage
+ \thispagestyle{empty}
+ \null
+ \clearpage
+ \thispagestyle{empty}
+ \null
+ \clearpage
+ \fi
+}
+%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-FOGRA39.clo
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-FOGRA39.clo 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-FOGRA39.clo 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,4 +1,4 @@
-% Typically used in Europe. Novel file version 1.38
+% Typically used in Europe. Novel file version 1.40
% The values of the arguments are public industry standards.
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-FileData.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-FileData.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-FileData.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,13 +13,10 @@
%%
%%
\ProvidesFile{novel-FileData.sty}%
-[2017/08/15 v1.38 LaTeX file (File Data settings)]
+[2017/09/14 v1.40 LaTeX file (File Data settings)]
%%
-%% Novel Tracking codes in this file begin with 2.
-\NDB{2.0 in novel-FileData.sty.}
-
%% FILE DATA (see class documentation for technical meaning of this term).
%% -----------------------------------------------------------------------------
%%
@@ -35,7 +32,6 @@
\gdef\thetitle{\@title}
\gdef\theTitle{\@title}
\title{}
-\NDB{2.1 in novel-FileData.sty.}
%
% \author{} or \SetAuthor{}
% Copied to metadata at end of preamble, unless not set or over-ridden.
@@ -47,7 +43,6 @@
\gdef\theauthor{\@author}
\gdef\theAuthor{\@author}
\author{}
-\NDB{2.2 in novel-FileData.sty.}
%
% \subtitle{} or \SetSubtitle{} (if any)
% Not copied to metadata by itself, as there is no such metadata entry.
@@ -59,7 +54,6 @@
\gdef\thesubtitle{\@subtitle}
\gdef\theSubtitle{\@subtitle}
\subtitle{}
-\NDB{2.3 in novel-FileData.sty.}
%
% \SetApplication{} (rarely used)
% Also known as CreatorTool.
@@ -68,7 +62,6 @@
% Normally leave as default, but can change if urgent.
\gdef\SetApplication#1{\gdef\@novelApplication{#1}}
\SetApplication{LaTeX with novel and microtype} % default
-\NDB{2.4 in novel-FileData.sty.}
%
% \SetProducer{} (rarely used)
% Name of the software that compiles to source to make PDF.
@@ -76,7 +69,6 @@
% Normally leave as default, but can change if urgent.
\gdef\SetProducer#1{\gdef\@novelProducer{#1}}
\SetProducer{LuaTeX with novel-pdfx and hyperref} % default
-\NDB{2.5 in novel-FileData.sty.}
%
% Although some other data fields could have been added,
% they do not pertain to fiction, especially if your book is print-on-demand.
@@ -106,7 +98,6 @@
\gdef\@OIregistry{}
\gdef\@OIprofile{}
%
-\NDB{2.6 in novel-FileData.sty.}
%%
\gdef\SetPDFX{\@ifstar\@setpdfxst\@setpdfxns}
\newcommand\@setpdfxst[2][CGATSTR001]{
@@ -113,15 +104,12 @@
\global\@noembediccfalse
\@setpdfx{#1}{#2}
}
-\NDB{2.7 in novel-FileData.sty.}
\newcommand\@setpdfxns[2][CGATSTR001]{
\global\@noembedicctrue
\@setpdfx{#1}{#2}
}
-\NDB{2.8 in novel-FileData.sty.}
%
\newcommand\@setpdfx[2]{
- \NDB{2.9.0 in novel-FileData.sty.}
\ifthenelse{\equal{#2}{off}}{
\global\pdfx at isOFFtrue
\@chosenComplianceOKtrue
@@ -162,7 +150,6 @@
\ClassError{novel}{Bad compliance argument for \string\SetPDFX}%
{Choose: off, X-1a:2001, X-1a:2003, X-3:2002, X-3:2003.^^J}%
\fi
- \NDB{2.9.1 in novel-FileData.sty.}
%
\ifpdfx at isOFF\else % Output Intent ignored if compliance is `off'.
% Grab the file that defines the output intent information:
@@ -176,7 +163,6 @@
}
\makeatother % back to usual
\fi
- \NDB{2.9.2 in novel-FileData.sty.}
} % end \@setpdfx
%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-FontDefaults.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-FontDefaults.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-FontDefaults.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,7 +13,7 @@
%%
%%
\ProvidesFile{novel-FontDefaults.sty}%
-[2017/08/15 v1.38 LaTeX file (default fonts)]
+[2017/09/14 v1.40 LaTeX file (default fonts)]
%%
@@ -21,9 +21,8 @@
%% This file is loaded \AtEndPreamble.
%%
-%% Novel Tracking messages in this file begin with 10.
-\NDB{10.0 in novel-FontDefaults.sty.}
+
%% Most TeX installations will use Latin Modern or Computer Modern
%% as default fonts. These are unsuitable for commercial fiction.
%% But `novel' class uses Libertinus as defaults.
@@ -39,7 +38,6 @@
\defaultfontfeatures[\ttfamily]{% monofont has no kerning or common ligatures
SmallCapsFeatures={Renderer=Basic},Ligatures=TeX,%
}%
-\NDB{10.1 in novel-FontDefaults.sty.}
\ifthenelse{\equal{\ttdefault}{lmtt}\OR\equal{\ttdefault}{cmtt}}{% over-ride:
\IfFontExistsTF{Libertinus Mono}{
\setmonofont[%
@@ -55,7 +53,6 @@
}
}
}{} % User \setmonofont, so leave alone.
-\NDB{10.2 in novel-FontDefaults.sty.}
%%
\defaultfontfeatures{} % reset
% Main and sans fonts: kerning, ligatures, and OldStyle numbers if available:
@@ -75,7 +72,6 @@
}
}
}{} % User \setsansfont, so leave alone.
-\NDB{10.3 in novel-FontDefaults.sty.}
%%
% At this point, if \rmdefault is something other than lmr, it means
% that the user attempted to set the main font using ordinary TeX commands,
@@ -110,13 +106,11 @@
}
}
\fi
-\NDB{10.4 in novel-FontDefaults.sty.}
% Now we are ready to set the main font:
\setmainfont[\@parentfontfeatures]{\@parentfontname}
\let\textfont\rmfamily\relax % compatibility
\let\mainfont\rmfamily\relax % compatibility
%
-\NDB{10.5 in novel-FontDefaults.sty.}
%%
\defaultfontfeatures{} % reset
% New in version 1.38, \straightquote and \straightdblquote:
@@ -128,7 +122,6 @@
SmallCapsFeatures={Renderer=Basic},Kerning=On,%
Ligatures=TeX,Ligatures=CommonOff,Numbers=Lining,%
}%
-\NDB{10.6 in novel-FontDefaults.sty.}
%% The novel-specific fonts:
\if at chapterfontset\else
\SetChapterFont[\@parentfontfeatures,Scale=1.6]{\@parentfontname}
@@ -146,7 +139,6 @@
\global\@headfontdefaulttrue
\fi
\newfontfamily\headfont[\@headfontfeatures]{\@headfontname}
-\NDB{10.7 in novel-FontDefaults.sty.}
%%
\defaultfontfeatures{} % reset
\defaultfontfeatures{% for decofont
@@ -158,7 +150,6 @@
\SetDecoFont{NovelDeco}
}{}
\fi
-\NDB{10.8 in novel-FontDefaults.sty.}
%%
\gdef\acronym#1{#1}% Re-defined below, if decofont available.
%%
@@ -206,7 +197,6 @@
%
\fi% end \if at gotdeco
%
-\NDB{10.9 in novel-FontDefaults.sty.}
%
%%
% Any other fonts will use these defaults:
@@ -231,10 +221,8 @@
\let\setdefaultlanguage\relax
\let\setotherlanguage\relax
\let\setotherlanguages\relax
-\NDB{10.10 in novel-FontDefaults.sty.}
% Now that the basic fonts are defined, we can load these packages:
\RequirePackage{polyglossia} % Instead of babel.
-\NDB{10.11 in novel-FontDefaults.sty.}
%
\ifthenelse{\equal{\@setmainlang}{}}{
\setmainlanguage{english}
@@ -259,7 +247,6 @@
\setotherlanguages[\@setotherlangsopt]{\@setotherlangs}
}
}
-\NDB{10.12 in novel-FontDefaults.sty.}
%% This provides default microtype settings, allows the user to over-ride,
% and hopefully prevents the user from choosing inappropriate settings:
\let\microtypesetup\relax % fake command no longer needed
@@ -278,7 +265,6 @@
%
%%
-\NDB{10.13 in novel-FontDefaults.sty.}
%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-Footnotes.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-Footnotes.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-Footnotes.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-Footnotes.sty}%
-[2017/08/15 v1.38 LaTeX file (commands for footnotes and endnotes)]
+[2017/09/14 v1.40 LaTeX file (commands for footnotes and endnotes)]
%%
-%% Novel Tracking codes in this file begin with 8.
-\NDB{8.0 in novel-Footnotes.sty.}
%% FOOTNOTES
@@ -50,7 +48,6 @@
\gdef\ResetFootnoteSymbol{\setcounter{@fnsymbolcount}{1}} % only symbols
\gdef\Resetendnote{\setcounter{@rnnumbercount}{1}}
%
-\NDB{8.1 in novel-Footnotes.sty.}
\newtoggle{@usenomark} % when true: no mark, no increment count
\newtoggle{@placedfootnotenumber} % true if any numerical footnote placed
%
@@ -63,7 +60,6 @@
}
\let\footnoterule\@fourem
%
-\NDB{8.2 in novel-Footnotes.sty.}
% \@makefnmark applies to the footnote marker in the flow of main text:
@@ -74,7 +70,6 @@
{\forceindent#1}%
{\forceindent\@getbotfnmark\,#1}%
} % end \@makefntext
-\NDB{8.3 in novel-Footnotes.sty.}
% Now re-define \footnote:
\newcommand\footnote[2][]{%
\ifthenelse{\equal{#1}{0}}{%
@@ -90,7 +85,6 @@
\unskip\my at oldfootnote{#2}%
\endgroup%
} % end \footnote
-\NDB{8.4 in novel-Footnotes.sty.}
%
% \@rollfnsymbol prevents running out of symbolic markers:
\gdef\@rollfnsymbol{%
@@ -99,7 +93,6 @@
\setcounter{@fnsymbolcount}{1}%
}{}%
} % end \@rollfnsymbol
-\NDB{8.5 in novel-Footnotes.sty.}
%
% \@getfnmark places a footnote marker in the running text.
% The marker depends upon whether it should be a number or a symbol.
@@ -132,7 +125,6 @@
\sups{\arabic{@fnnumbercount}}%
}%
} % end \@getfnmark
-\NDB{8.6 in novel-Footnotes.sty.}
%
% \@getbotfnmark places the marker in front of the actual footnote,
% towards the bottom of the textblock. It duplicates the marker used in
@@ -170,7 +162,6 @@
%
%% end footnotes
-\NDB{8.7 in novel-Footnotes.sty.}
%% ENDNOTES
@@ -191,7 +182,6 @@
\stepcounter{@endnotecount}\sups{\arabic{@endnotecount}}%
\long\edef\@endnotelist{\@endnotelist\space (\arabic{@endnotecount},p.\thepage)}%
}
-\NDB{8.8 in novel-Footnotes.sty.}
%%
% \endnotetext{ID}{text} where ID is (usually) the endnote number.
% If ID is other than space or tilde, it prints at left margin, followed by
@@ -207,7 +197,6 @@
}
%% end endnotes
-\NDB{8.9 in novel-Footnotes.sty.}
%% See novel.cls for the accompanying AtBeginDocument routine.
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-HeadFootStyles.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-HeadFootStyles.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-HeadFootStyles.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-HeadFootStyles.sty}%
-[2017/08/15 v1.38 LaTeX file (header and footer styles)]
+[2017/09/14 v1.40 LaTeX file (header and footer styles)]
%%
-%% Novel Tracking messages in this file begin with 5.
-\NDB{5.0 in novel-HeadFootStyles.sty.}
%% File `novel-LayoutSettings.sty' reserved space for header/footer,
@@ -42,7 +40,6 @@
%
\newtoggle{@inheadfoot} % true in header or footer
%%
-\NDB{5.1 in novel-HeadFootStyles.sty.}
%% INITIALIZE FANCYHDR
@@ -60,9 +57,7 @@
\FPdiv{\@loosehead}{\@@loosehead}{10} % change in method of using fontspec with microtype
\FPmin{\@looseheadnum}{\@loosehead}{50} % Don't want numbers too loose.
}
-\NDB{5.2 in novel-HeadFootStyles.sty.}
\SetLooseHead{50}
-\NDB{5.3 in novel-HeadFootStyles.sty.}
% Create flags to know if \fancyhead and \fancyfoot have been defined by user,
% somewhere in the Preamble. If not, then pre-defined styles based on trimsize
% will be applied \AtEndPreamble.
@@ -72,7 +67,6 @@
\@tempFancyhead[#1]{\toggletrue{@inheadfoot}{\normalsize#2}}%
}
%
-\NDB{5.4 in novel-HeadFootStyles.sty.}
\LetLtxMacro{\@tempFancyfoot}{\fancyfoot}
\renewcommand\fancyfoot[2][]{%
\@styledFootertrue%
@@ -84,7 +78,6 @@
}%
}
%
-\NDB{5.5 in novel-HeadFootStyles.sty.}
\LetLtxMacro{\@myTempTPS}{\thispagestyle}
% Re-define \thispagestyle based on layout. When style requests only the page
% number, decide what to do based on this command and whether footer is used:
@@ -92,7 +85,6 @@
%
%% See AtBeginShipout routine in novel.cls.
%
-\NDB{5.6 in novel-HeadFootStyles.sty.}
\gdef\thispagestyle#1{%
\global\@thispagestylesettrue%
\gdef\@pagestyleOK{false}%
@@ -110,7 +102,6 @@
\else \@myTempTPS{empty}%
\fi%
}{}%
- \NDB{5.6.1 in novel-HeadFootStyles.sty.}%
\ifthenelse{\equal{#1}{forcenumber}}{%
\gdef\@pagestyleOK{true}%
\if at gotFooter \@myTempTPS{fancyplain}%
@@ -118,7 +109,6 @@
\fi%
}{}%
%
- \NDB{5.6.2 in novel-HeadFootStyles.sty.}%
\ifthenelse{\equal{#1}{dropfolioinside}% after \clearpage
\OR \equal{#1}{dropfolio} \OR \equal{#1}{dropfoliolater}}{% compatibility
\gdef\@pagestyleOK{true}%
@@ -130,7 +120,6 @@
\@dropfolioinside
\fi%
}{}%
- \NDB{5.6.3 in novel-HeadFootStyles.sty.}%
% With `dropfoliobeneath` only a footer is used, if present. If no footer,
% then the styled page number is centered at one baselineskip beneath the
% ordinary bottom of the textblock. Thus, the number intrudes into the
@@ -146,7 +135,6 @@
\@dropfoliobeneath
\fi%
}{}%
- \NDB{5.6.4 in novel-HeadFootStyles.sty.}%
%%
\ifthenelse{\equal{\@pagestyleOK}{true}}{}{%
\ClassWarning{novel}{^^JPage \pagenumberstyle\space has %
@@ -153,7 +141,6 @@
\string\thispagestyle{}^^J%
but its argument is not defined. Default substituted. Better fix that.^^J}%
}%
- \NDB{5.6.5 in novel-HeadFootStyles.sty.}%
}
%
%% End initialize fancyhdr.
@@ -161,12 +148,10 @@
%% See AtBeginDocument routine in novel.cls:
%% -----------------------------------------------------------------------------
-\NDB{5.7 in novel-HeadFootStyles.sty.}
\gdef\@activateHeadFootStyles{ % called AtBeginDocument by novel.cls
% Pre-configured header/footer styles, unless user over-rode them:
% \versoheadtext is initialized to \theauthor
% \rectoheadtext is initialized to \thetitle
- \NDB{5.7.1 in novel-HeadFootStyles.sty.}%
\@ifundefined{versoheadtext}{
\NewVersoHeadText{\smcp{\StrSubstitute{\theauthor}{\space}{ \,}}}
}{}
@@ -173,7 +158,6 @@
\@ifundefined{rectoheadtext}{
\NewRectoHeadText{\smcp{\StrSubstitute{\thetitle}{\space}{ \,}}}
}{}
- \NDB{5.7.2 in novel-HeadFootStyles.sty.}%
%
% ----------------------------------------------------------------------------
% IF YOU ARE WRITING YOUR OWN HEADER/FOOTER STYLE:
@@ -251,7 +235,6 @@
\fi
}{}
%
- \NDB{5.7.1 in novel-HeadFootStyles.sty.}%
%
% END PRE-DEFINED STYLES.
% ----------------------------------------------------------------------------
@@ -284,7 +267,6 @@
%
%% end initialize fancyhdr
-\NDB{5.8 in novel-HeadFootStyles.sty.}
%% DROPFOLIO
%% -----------------------------------------------------------------------------
@@ -304,7 +286,6 @@
\setlength\temp at pgnumraise{%
\New at BottomMargin+0.5\New at MediaHeight-0.5\New at TrimHeight}%
\fi%
- \NDB{5.8.1 in novel-HeadFootStyles.sty.}%
\check at IsVerso%
\if at isVerso%
\AddToShipoutPicture*{\@getPageXY\AtPageLowerLeft{%
@@ -311,7 +292,6 @@
\hspace{\dimexpr\Trim at Lx+\New at OutsideMargin+0.5\textwidth-0.5\temp at pgnumwidth}\raisebox{%
\temp at pgnumraise}{{\headfont{\addfontfeature{LetterSpace=\@looseheadnum}\pagenumberstyle}}}}}%
\else%
- \NDB{5.8.2 in novel-HeadFootStyles.sty.}%
\AddToShipoutPicture*{\@getPageXY\AtPageLowerLeft{%
\hspace{\dimexpr\Trim at Lx+\New at InsideMargin-0.5\temp at pgnumwidth}%
\charscale[1,0.5\textwidth,\temp at pgnumraise]{%
@@ -321,7 +301,6 @@
%
\let\dropfolionow\relax % compatibility with earlier version.
%
-\NDB{5.9 in novel-HeadFootStyles.sty.}
% \@dropfoliobeneath does not change the textblock height. The styled page
% number is centered where an extra line would be, within the bottom margin.
@@ -335,7 +314,6 @@
\setlength\temp at pgnumraise{%
\New at BottomMargin-\nbs+0.5\New at MediaHeight-0.5\New at TrimHeight}%
\fi%
- \NDB{5.9.1 in novel-HeadFootStyles.sty.}%
\check at IsVerso%
\if at isVerso%
\AddToShipoutPicture*{\@getPageXY\AtPageLowerLeft{%
@@ -342,7 +320,6 @@
\hspace{\dimexpr\Trim at Lx+\New at OutsideMargin-0.5\temp at pgnumwidth}\raisebox{%
\temp at pgnumraise}{{\headfont{\addfontfeature{LetterSpace=\@looseheadnum}\pagenumberstyle}}}}}%
\else%
- \NDB{5.9.2 in novel-HeadFootStyles.sty.}%
\AddToShipoutPicture*{\@getPageXY\AtPageLowerLeft{%
\hspace{\dimexpr\Trim at Lx+\New at InsideMargin-0.5\temp at pgnumwidth}%
\charscale[1,0.5\textwidth,\temp at pgnumraise]{%
@@ -352,7 +329,6 @@
%%
%
-\NDB{5.10 in novel-HeadFootStyles.sty.}
% Content of header text (if present) can be changed at any time within
% the body, using the following commands. If not used, then
@@ -371,7 +347,6 @@
\let\SetVersoHeadText\NewVersoHeadText\relax % for convenience
\let\RenewVersoHeadText\NewVersoHeadText\relax % for convenience
%
-\NDB{5.11 in novel-HeadFootStyles.sty.}
\gdef\NewRectoHeadText#1{
\FPdiv{\@myk}{\@loosehead}{500}
\setlength\@mykem{\@myk em}
@@ -379,7 +354,6 @@
}
\let\SetRectoHeadText\NewRectoHeadText\relax % for convenience
\let\RenewRectoHeadText\NewRectoHeadText\relax % for convenience
-\NDB{5.12 in novel-HeadFootStyles.sty.}
%
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-Images.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-Images.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-Images.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-Images.sty}%
-[2017/08/15 v1.38 LaTeX file (image placement)]
+[2017/09/14 v1.40 LaTeX file (image placement)]
%%
-%% Novel Tracking messages in this file begin with 7.
-\NDB{7.0 in novel-Images.sty.}
%%
%% Be sure to read the separate documentation about how to prepare images.
@@ -81,7 +79,6 @@
{The `novel' class has its own commands for placing images. See docs.^^J%
You cannot use the \string\includegraphics\space command.}%
}
-\NDB{7.1 in novel-Images.sty.}
%
% \InlineImage can be used in body, header, footer.
% However, macros such as \imagefilename, \imagewidth, etc.
@@ -114,7 +111,6 @@
\ifthenelse{\equal{\@myilya}{} \OR \equal{\@myilya}{0}}{%
\def\@myily{0pt}}{\def\@myily{\@myilya}%
}%
- \NDB{7.1.1 in novel-Images.sty.}%
\iftoggle{@inheadfoot}{}{\gdef\imagefilename{#3}}% for possible later use
\gdef\my at graphic{\@includegraphics[draft=false]{#3}}%
\setlength\@imagewidth{\widthof{\my at graphic}}%
@@ -122,7 +118,6 @@
\iftoggle{@inheadfoot}{}{\setlength\imagewidth{\@imagewidth}}%
\setlength\@imageheight{\heightof{\my at graphic}}%
\global\@imageheight=\@imageheight%
- \NDB{7.1.2 in novel-Images.sty.}%
\iftoggle{@inheadfoot}{}{%
\setlength\imageheight{\@imageheight}%
\global\imageheight=\imageheight%
@@ -129,7 +124,6 @@
\typeout{^^JClass~`novel'~Info:~An~image~was~placed~on~page~\thepage.^^J%
Review~layout~to~ensure~that~it~does~not~overflow~into~margins.^^J}%
}%
- \NDB{7.1.3 in novel-Images.sty.}%
%
\setlength\@imagehoffset{\@myilx}%
\IfBeginWith{\@myily}{b}{%
@@ -142,7 +136,6 @@
\setlength\@imagevoffset{-\@imageheight}%
\addtolength\@imagevoffset{\@myily}%
}%
- \NDB{7.1.4 in novel-Images.sty.}%
%
\IfBooleanTF{#1}%
% starred:
@@ -154,7 +147,6 @@
}%
}%
% unstarred:
- \NDB{7.1.5 in novel-Images.sty.}%
{%
\iftoggle{@inheadfoot}{}{\gdef\imagestarred{false}}%
\hspace{\@imagehoffset}%
@@ -167,7 +159,6 @@
%
%%
-\NDB{7.2 in novel-Images.sty.}
%% \BlockImage[alignment]{image}[text]
@@ -205,7 +196,6 @@
\ifthenelse{\equal{\@myyt}{}\OR\equal{\@myyt}{0}}{%
\def\@myy{0pt}}{\def\@myy{\@myyt}%
}
- \NDB{7.2.1 in novel-Images.sty.}%
\newdimen\@sbsheight
\ifthenelse{\equal{\@myalign}{c}\OR\equal{\@myalign}{}}{%
{\centering\strut\InlineImage*[{\@myx-0.5\imagewidth},{\@myy}]{#2}\par}
@@ -213,9 +203,8 @@
{\centering\strut #3\par}
\setbox0=\vbox{{\centering #3\par}}
}{}
- \NDB{7.2.2 in novel-Images.sty.}%
\ifthenelse{\equal{\@myalign}{r}}{%
- \noindent\InlineImage*[{\textwidth-\imagewidth+\@myx},{\@myy}]{#2}\par%
+ \noindent\InlineImage[{\textwidth-\imagewidth+\@myx},{\@myy}]{#2}\par%
\vspace{-\nbs}
\begin{adjustwidth}{0pt}{\imagewidth+\parindent}%
#3\par%
@@ -226,7 +215,6 @@
\end{adjustwidth}%
}%
}{}
- \NDB{7.2.3 in novel-Images.sty.}%
\ifthenelse{\equal{\@myalign}{l}}{%
\noindent\InlineImage*[{\@myx},{\@myy}]{#2}\par%
\vspace{-\nbs}
@@ -239,7 +227,6 @@
\end{adjustwidth}%
}%
}{}
- \NDB{7.2.4 in novel-Images.sty.}%
% portion here, inspired by post from user Killian Foth,
% at stackoverflow.com, license CC-by-sa-3.0.
\@sbsheight=\ht0 \advance\@sbsheight by \dp0
@@ -263,7 +250,6 @@
\ExplSyntaxOff
%%
-\NDB{7.3 in novel-Images.sty.}
% Returns 1 for monochrome, 8 for grayscale (or rgb). EXPERIMENTAL.
@@ -277,7 +263,6 @@
}%
}
%
-\NDB{7.4 in novel-Images.sty.}
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-JC200103.clo
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-JC200103.clo 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-JC200103.clo 2017-09-14 20:53:13 UTC (rev 45302)
@@ -1,4 +1,4 @@
-% Typically used in Japan. Novel file version 1.38
+% Typically used in Japan. Novel file version 1.40
% The values of the arguments are public industry standards.
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-LayoutSettings.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-LayoutSettings.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-LayoutSettings.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-LayoutSettings.sty}%
-[2017/08/15 v1.38 LaTeX file (layout settings)]
+[2017/09/14 v1.40 LaTeX file (layout settings)]
%%
-% Novel Tracking codes in this file begin with 3.
-\NDB{3.0 in novel-LayoutSettings.sty.}
%% Note that nearly all layout settings are preconfigured based on Trim Size.
%% In general, these user commands may be used to over-ride the presets.
@@ -56,7 +54,6 @@
\newlength\normalxheight
\newlength\normalXheight
%%
-\NDB{3.1 in novel-LayoutSettings.sty.}
%% SIZE-RELATED COMMANDS AVAILABLE IN PREAMBLE.
@@ -72,7 +69,6 @@
%
% \SetTrimSize{}{} width and height of printed book.
\newcommand\SetTrimSize[2]{%
- \NDB{3.2.0 in novel-LayoutSettings.sty.}
\global\@TrimSizeSettrue
\ifthenelse{\dimtest{#1}{<}{2.99in}}{
\ClassError{novel}{Unacceptably small Trim Width}%
@@ -91,7 +87,6 @@
{\string\SetTrimSize\space cannot follow \string\ReworkTrimSize^^J%
and cannot follow \string\ReworkMargins.}%
\fi
- \NDB{3.2.1 in novel-LayoutSettings.sty.}
\setlength\Old at TrimWidth{#1}%
\setlength\Old at TrimHeight{#2}%
\setlength\New at TrimWidth{#1}%
@@ -102,12 +97,10 @@
\setlength\New at MediaWidth{#1}%
\setlength\New at MediaHeight{#2}%
\fi
- \NDB{3.2.3 in novel-LayoutSettings.sty.}
}
%
% Retroactively change Trim Size after layout. See documentation:
\newcommand\ReworkTrimSize[2]{%
- \NDB{3.4.0 in novel-LayoutSettings.sty.}
\if at coverart % New in version 1.2
\ClassError{novel}{Rework command cannot be used with coverart option}%
{Instead of reworking document size, you must re-do the artwork.}
@@ -122,7 +115,6 @@
Carefully review your PDF to ensure that line breaks, paragraphs,^^J%
and page breaks are where you expect them to be.^^J}%
\fi
- \NDB{3.4.1 in novel-LayoutSettings.sty.}
}
% Margins at top and bottom are relative to:
% top of header, or top of textblock if no header;
@@ -130,7 +122,6 @@
% Inside margin generally greater than outside, due to gutter.
% Standard margins command ("TOBI, or not TOBI, that is the question."):
\newcommand\SetMargins[4]{ % top, outside, bottom, inside
- \NDB{3.5.0 in novel-LayoutSettings.sty.}
\global\@MarginsSettrue
\if at ReworkMarginsSet
\ClassError{novel}{^^JCannot set Margins after reworking them}%
@@ -144,11 +135,9 @@
\setlength\New at BottomMargin{#3}
\setlength\Old at InsideMargin{#4}
\setlength\New at InsideMargin{#4}
- \NDB{3.5.1 in novel-LayoutSettings.sty.}
}
% Retroactively change margins after layout. See documentation:
\newcommand\ReworkMargins[4]{
- \NDB{3.6.0 in novel-LayoutSettings.sty.}
\if at coverart % New in version 1.2
\ClassError{novel}{Rework command cannot be used with coverart option}%
{Instead of reworking document size, you must re-do the artwork.}
@@ -163,7 +152,6 @@
Carefully review your PDF to ensure that line breaks, paragraphs,^^J%
and page breaks are where you expect them to be.^^J}%
\fi
- \NDB{3.6.1 in novel-LayoutSettings.sty.}
}
% \SetMediaSize[]{}{} such as {8.5in}{11in}.
% This command is only used when the Trim Size must be placed in a larger
@@ -176,7 +164,6 @@
%
\newif \if at offcenterTrim \@offcenterTrimfalse
\newcommand\SetMediaSize[3][center]{ % [alignment] width, height
- \NDB{3.7.0 in novel-LayoutSettings.sty.}
\ifthenelse{\equal{#1}{center} \OR \equal{#1}{edge}}{
\global\@MediaSizeSettrue
\setlength\Old at MediaWidth{#2}
@@ -190,7 +177,6 @@
\if at coverart\else % new in version 1.2
\ifthenelse{\equal{#1}{edge}}{\global\@offcenterTrimtrue}{}
\fi
- \NDB{3.7.1 in novel-LayoutSettings.sty.}
}
% \SetLinesPerPage{} limited due to fontsize and Trim Size constraints.
% There is no `rework' command, because as long as the number of lines fit,
@@ -199,7 +185,6 @@
% a reworked size cannot fit. In that case, the user's best plan is remove
% header or footer (if possible), or reduce vertical margins (if possible).
\newcommand\SetLinesPerPage[1]{
- \NDB{3.8.0 in novel-LayoutSettings.sty.}
\global\@LinesPerPageSettrue
\FPiflt{#1}{1}%
\ClassError{novel}{\string\SetLinesPerPage\ must be at least 1}%
@@ -207,7 +192,6 @@
\else\fi %
\FPround{\temp at IntegerLines}{#1}{0}
\def\my at LinesPerPage{\temp at IntegerLines}
- \NDB{3.8.1 in novel-LayoutSettings.sty.}
}
% \SetFontSize{} may be in any units, even decimals: 12.2pt, 11.5bp, etc.
% When packages load, the font size is temporarily set to 11pt at 15pt skip,
@@ -215,10 +199,8 @@
% Then the size is changed to its actual value based on this command, or on
% the defaults for Trim Size, or on the effects of \Rework.
\newcommand\SetFontSize[1]{
- \NDB{3.9.0 in novel-LayoutSettings.sty.}
\global\@FontSizeSettrue
\global\setlength\Old at FontSize{#1}
- \NDB{3.9.1 in novel-LayoutSettings.sty.}
}
%
%% End size-related commands available in Preamble.
@@ -246,7 +228,6 @@
\SetHeadJump{1.5} % default
\gdef\SetFootJump#1{\gdef\@footjump{#1}}
\SetFootJump{1.5} % default
-\NDB{3.10 in novel-LayoutSettings.sty.}
% New in version 1.2, coverart.
\if at coverart % cover art has no header or footer
\gdef\SetHeadFootStyle#1{\gdef\my at HeadFootStyle{0}}
@@ -257,13 +238,11 @@
\gdef\SetHeadFootStyle#1{\gdef\my at HeadFootStyle{#1}}
\gdef\SetHeadStyle#1{\gdef\my at HeadFootStyle{#1}} % deprecated
\fi
-\NDB{3.11 in novel-LayoutSettings.sty.}
% See docs part 7 for what these emblems do, if used:
\newcommand\SetEmblems[2]{ % verso, recto
\gdef\my at VersoEmblem{{\headfont #1}}
\gdef\my at RectoEmblem{{\headfont #2}}
}
-\NDB{3.12 in novel-LayoutSettings.sty.}
\let\SetEmblem\SetEmblems% for convenience
% If you want something fancier than \thepage:
\gdef\SetPageNumberStyle#1{\gdef\pagenumberstyle{#1}}
@@ -270,7 +249,6 @@
% See novel.cls for the accompanying AtBeginDocument routine.
-\NDB{3.13 in novel-LayoutSettings.sty.}
%
\newif \if at gotHeader
\newif \if at gotFooter
@@ -279,7 +257,6 @@
\newif \if at validHF
%
\gdef\@reserveHFspace{ % used for layout calculations
- \NDB{3.14.1 in novel-LayoutSettings.sty.}
\ifthenelse{\equal{\my at HeadFootStyle}{0}}{
\@gotHeaderfalse\@gotFooterfalse\@validHFtrue
}{}
@@ -307,13 +284,11 @@
{\string\SetHeadFootStyle\space needs choice of 0,1,2,3,4,5,6,^^J%
even if you wish to customize using fancyhdr syntax.^^J}%
\fi
- \NDB{3.14.2 in novel-LayoutSettings.sty.}
} % end \@reserveHFspace
% Each new chapter generally has its own header/footer style. This allows a
% default setting when chapters begin with ChapterStart environment:
\gdef\SetChapterStart#1{\gdef\@setchapterstart{#1}}
\SetChapterStart{footer} % default
-\NDB{3.15 in novel-LayoutSettings.sty.}
%
% See novel.cls for the accompanying AtBeginDocument routine.
%
@@ -322,7 +297,6 @@
%% New in version 1.2: cover image.
\newcommand\SetCoverImage[1]{
- \NDB{3.17.0 in novel-LayoutSettings.sty.}
\def\coverimageok{false}
\IfSubStr{#1}{jpg}{\def\coverimageok{true}}{}
\IfSubStr{#1}{jpeg}{\def\coverimageok{true}}{}
@@ -334,7 +308,6 @@
\ClassError{novel}{Cover image has wrong file extension}%
{Cover image must be jpg, JPG, jpeg, or JPEG.}
}%
- \NDB{3.17.1 in novel-LayoutSettings.sty.}
}
%%
@@ -351,7 +324,6 @@
% dagger, dbldagger, and section (when used as footnote markers)
% are always partially faked.
\newcommand\SetMarkerStyle[2][real]{
- \NDB{3.18.0 in novel-LayoutSettings.sty.}
\def\@goodfnm{no}
\ifthenelse{\equal{#2}{asterisk}}{%
\def\@goodfnm{yes}\global\toggletrue{@usesymbolmark}%
@@ -370,7 +342,6 @@
\ClassError{novel}{Bad choice for \string\SetMarkers}%
{Optional: real, fake. Required: asterisk, dagger, number.}%
}{}
- \NDB{3.18.1 in novel-LayoutSettings.sty.}
}
%
\SetMarkerStyle[real]{asterisk} % default
@@ -389,7 +360,6 @@
\SetCropmarkGap{0.125in} % default
%%
-\NDB{3.19 in novel-LayoutSettings.sty.}
%% Fake \microtypesetup until package is loaded later:
@@ -400,7 +370,6 @@
}
%%
-\NDB{3.20 in novel-LayoutSettings.sty.}
%% MISCELLANOUS SETTINGS. Mostly remove "glue". Best to leave as-is.
@@ -464,7 +433,6 @@
%
%% End miscellaneous settings.
-\NDB{3.21 in novel-LayoutSettings.sty.}
% The following might become unnecessary if fontspec adds the capability to
% disable keys. For now: Color and Opacity cannot be used as font features,
@@ -471,7 +439,6 @@
% for a black/white printed book. Alas, fontspec over-rules xcolor.
% So, this code over-rules fontspec:
\gdef\novel at checkfeatures#1{%
- \NDB{3.22.0 in novel-LayoutSettings.sty.}
\def\@featuresareok{yes}
\IfSubStr{#1}{Color}{\def\@featuresareok{no}}{}%
\IfSubStr{#1}{Colour}{\def\@featuresareok{no}}{}%
@@ -484,7 +451,6 @@
{You defined a font, or added a font feature, with Color or Opacity.^^J%
That is disallowed in `novel' class.}%
}
- \NDB{3.22.1 in novel-LayoutSettings.sty.}
}
%%
@@ -520,7 +486,6 @@
\newif \if at parentfontset
\gdef\@parentfontfeatures{}
\gdef\@parentfontname{}
-\NDB{3.23 in novel-LayoutSettings.sty.}
\DeclareDocumentCommand \SetParentFont { O{} m O{} } {% from version 1.1.
\novel at checkfeatures{#1,#3}
\gdef\@parentfontfeatures{#1,#3}
@@ -533,7 +498,6 @@
\gdef\@parentfontname{#2}
\global\@parentfontsettrue
}%
-\NDB{3.24 in novel-LayoutSettings.sty.}
%% Store settings for the chapterfont:
% The chapter font is used by the \ChapterTitle{} command.
\newif \if at chapterfontset
@@ -582,7 +546,6 @@
\global\@gotdecotrue
\newfontface\decofont[#1,#3]{#2}
}%
-\NDB{3.25 in novel-LayoutSettings.sty.}
%
\msg_set:nnnn {fontspec} {font-not-found} { % rewrites the standard message
Font~ "#1"~ cannot~ be~ found.
@@ -592,7 +555,6 @@
If~the~missing~font~is~anything~else,~then~the~missing~font~is\\
not~caused~by~`novel'~class.\\
}%
-\NDB{3.26 in novel-LayoutSettings.sty.}
%% For syntax consistency:
\cs_new_eq:NN \NewFontFamily \newfontfamily
\cs_new_eq:NN \NewFontFace \newfontface
@@ -602,7 +564,6 @@
\cs_new_eq:NN \AddFontFeatures \addfontfeatures
\cs_new_eq:NN \AddFontFeature \addfontfeatures
%%
-\NDB{3.27 in novel-LayoutSettings.sty.}
%% \CreateFontFeature{substitutions}{feature code}
% Problem: Font has one or more alternate glyphs that you would like to use,
% but they are not listed in a feature set for the font.
@@ -644,7 +605,6 @@
%%
%% end definition of parent and other fonts.
-\NDB{3.29 in novel-LayoutSettings.sty.}
%% FAKE POLYGLOSSIA COMMANDS
%% --------------------------------------------------------------------------
@@ -680,20 +640,17 @@
%
%% end fake polyglossia commands.
-\NDB{3.30 in novel-LayoutSettings.sty.}
-%% FRONTMATTER, MAINMATTER, BACKMATTER
+%% FRONTMATTER, MAINMATTER. BUT NO BACKMATTER!
%% --------------------------------------------------------------------------
%
\newif \ifWithinFrontmatter \WithinFrontmatterfalse
\newif \ifWithinMainmatter \WithinMainmatterfalse
-\newif \ifWithinBackmatter \WithinBackmatterfalse
\newcounter{frontmatterpages}
\newcounter{runningpages}
%
% See novel.cls for the AtBeginShipout routine.
%
-\NDB{3.32 in novel-LayoutSettings.sty.}
\def\frontmatter{ % starts page count and frontmatter count at 1.
\ifWithinFrontmatter
\ClassError{novel}{\string\frontmatter\ used more than once}%
@@ -701,21 +658,15 @@
\fi
\ifWithinMainmatter
\ClassError{novel}{\string\frontmatter\ cannot follow \mainmatter}%
- {In order: \string\frontmatter\ \string\mainmatter\ \string\backmatter^^J%
- but you do not need all of them.^^J}%
+ {In order: \string\frontmatter\ \string\mainmatter^^J%
+ but you do not need both of them.^^J}%
\fi
- \ifWithinBackmatter
- \ClassError{novel}{\string\frontmatter\ cannot follow \backmatter}%
- {In order: \string\frontmatter\ \string\mainmatter\ \string\backmatter^^J%
- but you do not need all of them.^^J}%
- \fi
- \WithinFrontmattertrue\WithinMainmatterfalse\WithinBackmatterfalse
+ \WithinFrontmattertrue\WithinMainmatterfalse
\clearpage
\pagenumbering{roman}
\setcounter{page}{1}
\setcounter{frontmatterpages}{1}
}
-\NDB{3.33 in novel-LayoutSettings.sty.}
%
\def\mainmatter{ % restarts page to 1, arabic numbers; freeze frontpagecount
\ifWithinMainmatter
@@ -722,94 +673,33 @@
\ClassError{novel}{\string\mainmatter\ used more than once}%
{You issued \string\mainmatter\ more than once.}%
\fi
- \ifWithinBackmatter
- \ClassError{novel}{\string\mainmatter\ cannot follow \backmatter}%
- {In order: \string\frontmatter\ \string\mainmatter\ \string\backmatter^^J%
- but you do not need all of them.^^J}%
- \fi
- \WithinFrontmatterfalse\WithinMainmattertrue\WithinBackmatterfalse
+ \WithinFrontmatterfalse\WithinMainmattertrue
\setcounter{frontmatterpages}{\value{page}}
\addtocounter{frontmatterpages}{-1}
\pagenumbering{arabic}
\setcounter{page}{1}
}
-\NDB{3.34 in novel-LayoutSettings.sty.}
%
-\def\backmatter{\@ifstar\@backmatterst\@backmatterns}
-%
-\def\@backmatterst{% continues frontmatter count w/ lowercase roman numerals
- \ifWithinBackmatter
- \ClassError{novel}{\string\backmatter\space used more than once}%
- {You issued \string\backmatter\space more than once.^^J}%
- \fi
- % If you really must go directly from front to back without main,
- % simply issue \mainmatter\backmatter together. Not advised.
- \ifWithinFrontmatter
- \ClassError{novel}{Missing \string\mainmatter}%
- {You went directly from \string\frontmatter\space to \string\backmatter^^J%
- Must have \string\mainmatter\space in between.^^J}%
- \fi
- \WithinFrontmatterfalse\WithinMainmatterfalse\WithinBackmattertrue
- \addtocounter{frontmatterpages}{1}
- \pagenumbering{roman}
- \setcounter{page}{\value{frontmatterpages}}
+\def\backmatter{\@ifstar\@backmatterst\@backmatterns} % obsolete from v. 1.40.
+\def\@backmatterst{%
+ \ClassWarning{novel}{Command \string\backmatter*\ ignored. Do not use.^^J}%
}
%
-\def\@backmatterns{ % continues mainmatter arabic numerals
- \ifWithinBackmatter
- \ClassError{novel}{\string\backmatter\space used more than once}%
- {You issued \string\backmatter\space more than once.^^J}%
- \fi
- % If you really must go directly from front to back without main,
- % simply issue \mainmatter\backmatter together. Not advised.
- \ifWithinFrontmatter
- \ClassError{novel}{Missing \string\mainmatter}%
- {You went directly from \string\frontmatter\space to \string\backmatter^^J%
- Must have \string\mainmatter\space in between.^^J}%
- \fi
- \WithinFrontmatterfalse\WithinMainmatterfalse\WithinBackmattertrue
+\def\@backmatterns{%
+ \ClassWarning{novel}{Command \string\backmatter\ ignored. Do not use.^^J}%
}
-\NDB{3.35 in novel-LayoutSettings.sty.}
%
-\def\Backmatter{\@ifstar\@Backmatterst\@Backmatterns}
+\def\Backmatter{\@ifstar\@Backmatterst\@Backmatterns} % obsolete from v. 1.40.
%
\def\@Backmatterst{% continues frontmatter count w/ uppercase Roman numerals
- \ifWithinBackmatter
- \ClassError{novel}{\string\backmatter\space used more than once}%
- {You issued \string\backmatter\space more than once.^^J}%
- \fi
- % If you really must go directly from front to back without main,
- % simply issue \mainmatter\backmatter together. Not advised.
- \ifWithinFrontmatter
- \ClassError{novel}{Missing \string\mainmatter}%
- {You went directly from \string\frontmatter\space to \string\backmatter^^J%
- Must have \string\mainmatter\space in between.^^J}%
- \fi
- \WithinFrontmatterfalse\WithinMainmatterfalse\WithinBackmattertrue
- \addtocounter{frontmatterpages}{1}
- \pagenumbering{Roman}
- \setcounter{page}{\value{frontmatterpages}}
+ \ClassWarning{novel}{Command \string\Backmatter*\ ignored. Do not use.^^J}%
}
%
-\def\@Backmatterns{ % restarts page count with uppercase Roman numerals
- \ifWithinBackmatter
- \ClassError{novel}{\string\backmatter\ used more than once}%
- {You issued \string\backmatter\ more than once.^^J}%
- \fi
- % If you really must go directly from front to back without main,
- % simply issue \mainmatter\backmatter together. Not advised.
- \ifWithinFrontmatter
- \ClassError{novel}{Missing \string\mainmatter}%
- {You went directly from \string\frontmatter\space to \string\backmatter^^J%
- Must have \string\mainmatter\space in between.^^J}%
- \fi
- \WithinFrontmatterfalse\WithinMainmatterfalse\WithinBackmattertrue
- \pagenumbering{Roman}
- \setcounter{page}{1}
+\def\@Backmatterns{%
+ \ClassWarning{novel}{Command \string\Backmatter\ ignored. Do not use.^^J}%
}
%
-%% end frontmatter, mainmatter, backmatter.
-\NDB{3.36 in novel-LayoutSettings.sty.}
+%% end frontmatter, mainmatter. No backmatter!
%% DISABLE OR NEUTRALIZE SOME STANDARD LATEX COMMANDS
@@ -855,7 +745,6 @@
\long\gdef\listoffigures\@nodocommand{listoffigures}
%
%% end disable or neutralize.
-\NDB{3.37 in novel-LayoutSettings.sty.}
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-TextMacros.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-TextMacros.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-TextMacros.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -13,11 +13,9 @@
%%
%%
\ProvidesFile{novel-TextMacros.sty}%
-[2017/08/15 v1.38 LaTeX file (text macros usable within document body)]
+[2017/09/14 v1.40 LaTeX file (text macros usable within document body)]
%%
-%% Novel Tracking messages in this file begin with 4.
-\NDB{4.0 in novel-TextMacros.sty.}
%% This file contains commands that are usable within the document body,
%% for styling and otherwise manipulating text.
@@ -39,7 +37,7 @@
% \DecoChapterTitle{}{}, \SideDecoChapterTitle{}, ModernChapterTitle[]{}{} -- See novel-ChapterScene.sty.
% {\chapterfont text} and other pre-defined font selection commands -- See novel-LayoutSettings.sty.
% \decoglyph{} and \acronym{} -- See novel-FontDefaults.sty.
-% \frontmatter, \mainmatter, \backmatter and variations -- See novel-LayoutSettings.sty.
+% \frontmatter, \mainmatter -- See novel-LayoutSettings.sty.
% \footnote[]{}, \endnote, \endnotetext[]{} -- See novel-Footnotes.sty.
% \thispagestyle{choice} and \dropfolio -- See novel-HeadFootStyles.sty.
% \NewVersoHeadText{}, \NewRectoHeadText{} Also \Set and \Renew forms. -- See novel-HeadFootStyles.sty.
@@ -141,7 +139,6 @@
% Useful when you wish to put a note to yourself in the *.tex document.
% Not the same as % comment, because anything after the braces will print.
\long\gdef\memo#1{}
-\NDB{4.1 in novel-TextMacros.sty.}
%
\gdef\stake{\rule{0pt}{1pt}} % placeholder
%
@@ -148,7 +145,6 @@
% \forceindent and \backindent perform or remove indent, using \hspace{}.
% Rationale: Sometimes \indent and \noindent are neutralized by another command.
\newlength\forceparlength % holds default value, even when \parindent changed
-\NDB{4.2 in novel-TextMacros.sty.}
% See novel.cls for accompanying AtBeginDocument routine.
@@ -172,7 +168,6 @@
}
%
\ExplSyntaxOff
-\NDB{4.4 in novel-TextMacros.sty.}
%
\let\textsc\smcp\relax % unified
\let\oldscshape\scshape\relax % in case needed later
@@ -190,7 +185,6 @@
%% Just in case `xcolor' re-defines its internals, to prevent code bomb:
\ProvideDocumentCommand\@declaredcolor { m } {}
\ProvideDocumentCommand\@undeclaredcolor { o m } {}
-\NDB{4.5 in novel-TextMacros.sty.}
%%
\if at graytext % and the usual colors, including black and white.
\definecolor[named]{gray1}{gray}{0.15} % ten percent gray, etc.
@@ -211,7 +205,6 @@
\ifthenelse{\equal{#2}{hingledingle}}{\@declaredcolor{white}}{}% hingledingle is internal alias for white
}
\fi
-\NDB{4.6 in novel-TextMacros.sty.}
%%
@@ -233,7 +226,6 @@
\expandafter\aftergroup\csname nov at ettl@fterGroup\the\nov at ettl@fter\endcsname%
}
% End code from `etextools`.
-\NDB{4.7 in novel-TextMacros.sty.}
@@ -251,7 +243,6 @@
#2%
\fi%
}
-\NDB{4.8 in novel-TextMacros.sty.}
%% \bigemdash inspired by code by RTBarnard at stackoverflow.com, CC-by-sa-3.0:
% Allows a rule of variable length to fill available space at its right.
% There must be a "right-hand limit" imposed by something, such as by enclosing
@@ -277,7 +268,6 @@
{\leaders\hbox{\rule[\@myraise ex]{1pt}{\@mythick em}}\hfill\stake}%
}
%%
-\NDB{4.9 in novel-TextMacros.sty.}
%%
% \charscale[scale,x,y]{text} and starred version
@@ -325,7 +315,6 @@
}
\ExplSyntaxOff
%%
-\NDB{4.10 in novel-TextMacros.sty.}
@@ -357,7 +346,6 @@
\FPround{\my at tempDetailsSkipNum}{\my at tempDetailsSkipNum}{2}%
\fontsize{\my at tempDetailsFontNum pt}{\my at tempDetailsSkipNum pt}\selectfont}%
{\endgroup}
-\NDB{4.11 in novel-TextMacros.sty.}
%
%%
% Environment toc (alternative table of contents):
@@ -376,7 +364,6 @@
}{%
\endgroup\end{adjustwidth}\par%
}%
-\NDB{4.12 in novel-TextMacros.sty.}
%% \tocitem[number]{description}{page} provides a one-line table entry in toc.
% optional number might be chapter number. Can use ~ to offset.
% unstarred: distance between description and page is not decorated.
@@ -394,7 +381,6 @@
\dotfill%
\,#3\par\vspace{\@tocskip}%
}%
-\NDB{4.13 in novel-TextMacros.sty.}
%
\newcommand\@tocitemns[3][]{%
\ifthenelse{\equal{#1}{}}{}{%
@@ -408,7 +394,6 @@
\hfill%
#3\par\vspace{\@tocskip}%
}%
-\NDB{4.14 in novel-TextMacros.sty.}
%% end toc and \tocitem.
%%
%% legalese environment. Certain info, such as Copyright page, customarily is
@@ -427,7 +412,6 @@
\setlength\@temphangl{\widthof{#1}}%
\stake\hspace{-\@temphangl}#1%
}
-\NDB{4.15 in novel-TextMacros.sty.}
%%
% \showlength[decimal places]{length}{units}
% Returns the length as a string with the units, but does not change the length.
@@ -455,7 +439,6 @@
\temp at lengthnum#3%
}
%% end \showlength
-\NDB{4.16 in novel-TextMacros.sty.}
%% \squeeze{} and \crush{} slightly shrink the horizonal dimension of the
@@ -489,7 +472,6 @@
\gdef\realmarker{\toggletrue{@realmarker}} % anywhere in text
\gdef\fakemarker{\togglefalse{@realmarker}} % anywhere in text
%%
-\NDB{4.17 in novel-TextMacros.sty.}
\ExplSyntaxOn
%
\DeclareDocumentCommand \sups { m }
@@ -507,7 +489,6 @@
}%
}% end \sups
%
-\NDB{4.18 in novel-TextMacros.sty.}
\DeclareDocumentCommand \subs { m }
{%
\iftoggle{@realmarker}{%
@@ -535,7 +516,6 @@
\gdef\specialblankline{\null} % deprecated
%%
-\NDB{4.19 in novel-TextMacros.sty.}
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-glyphtounicode.tex
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-glyphtounicode.tex 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-glyphtounicode.tex 2017-09-14 20:53:13 UTC (rev 45302)
@@ -14,7 +14,7 @@
%%
%%
\ProvidesFile{novel-gyphtounicode.tex}%
-[2017/08/15 v1.38 LaTeX file (additional glyph to unicode)]
+[2017/09/14 v1.40 LaTeX file (additional glyph to unicode)]
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-microtype.cfg
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-microtype.cfg 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-microtype.cfg 2017-09-14 20:53:13 UTC (rev 45302)
@@ -18,8 +18,8 @@
%% ------------------------------------------------------------------------
%%
\NeedsTeXFormat{LaTeX2e}
-\ProvidesFile{novel-microtype.cfg}
- [2017/08/15 v1.38 LaTeX file (microtype configuration file for novel class)]
+\ProvidesFile{novel-microtype.cfg}%
+[2017/09/14 v1.40 LaTeX file (microtype configuration file for novel class)]
%%% -----------------------------------------------------------------------
%%% FONT SETS
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-pdfx.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-pdfx.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-pdfx.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -23,8 +23,8 @@
%% -----------------------------------------------------------------------------
%%
\NeedsTeXFormat{LaTeX2e}
-\ProvidesFile{novel-pdfx.sty}
- [2017/08/15 v1.38 LaTeX file (PDF/X support for novel class)]
+\ProvidesFile{novel-pdfx.sty}%
+[2017/09/14 v1.40 LaTeX file (PDF/X support for novel class)]
% This package supports, and is part of, class `novel'.
% No support for anything but LuaLaTeX.
@@ -33,8 +33,6 @@
%% This file is loaded \AtEndPreamble.
%%
-%% Novel Tracking messages in this file begin with 11.
-\NDB{11.0 in novel-pdfx.sty.}
%
@@ -45,7 +43,6 @@
pdfpagelabels=true,pageanchor=false,pdfstartview=}
%
\RequirePackage[\pdfx at pdfX@opts at luatex]{hyperref}
-\NDB{11.1 in novel-pdfx.sty.}
%
\hypersetup{pdfencoding=auto}
\expandafter\ifx\csname KV at Hyp@psdextra\endcsname\relax\else
@@ -52,7 +49,6 @@
\hypersetup{psdextra}
\fi
\Hy at bookmarksfalse
-\NDB{11.2 in novel-pdfx.sty.}
%
\newif \if at gottitle \@gottitlefalse % refers to PDF File Data
% Was \title{} called prior to this step? If so:
@@ -66,7 +62,6 @@
before using \string\SetPDFX.^^J}
\fi
\fi
-\NDB{11.3 in novel-pdfx.sty.}
%
\if at gottitle\else
\ClassWarning{novel}{Your file has been compiled without standard^^J %
@@ -82,7 +77,6 @@
\edef\pdfcreationdate{\pdfcreationdate}%
\let\pdfx at mdfivesum\pdf at mdfivesum
%
-\NDB{11.4 in novel-pdfx.sty.}
@@ -111,7 +105,6 @@
\FPmul{\my at THnum}{\my at THnum}{0.99626401}
\FPround{\my at THnum}{\my at THnum}{3}
%
-\NDB{11.5 in novel-pdfx.sty.}
\FPsub{\my at TWorigin}{\my at MWnum}{\my at TWnum}
\FPmul{\my at TWorigin}{\my at TWorigin}{0.5}
\FPround{\my at TWorigin}{\my at TWorigin}{3}
@@ -128,7 +121,6 @@
\FPclip{\my at THorigin}{\my at THorigin}
\FPclip{\my at THcorner}{\my at THcorner}
%
-\NDB{11.6 in novel-pdfx.sty.}
\newcommand\novel at CropBox{%
\if at cropview%
/CropBox[\my at TWorigin\space\my at THorigin\space\my at TWcorner\space\my at THcorner]%
@@ -136,12 +128,10 @@
/CropBox[0\space0\space\my at MWnum\space\my at MHnum]%
\fi%
}
-\NDB{11.7 in novel-pdfx.sty.}
%
\newcommand\novel at TrimBox{%
/TrimBox[\my at TWorigin\space\my at THorigin\space\my at TWcorner\space\my at THcorner]%
}
-\NDB{11.8 in novel-pdfx.sty.}
%
% New in version 1.2: BleedBox, only for cover art. Same size as MediaBox.
\newcommand\novel at BleedBox{%
@@ -149,7 +139,6 @@
/BleedBox[0\space0\space\my at MWnum\space\my at MHnum]%
\else\fi%
}
-\NDB{11.9 in novel-pdfx.sty.}
%
\begingroup\edef\next{%
\endgroup\pdfpageattr{\novel at CropBox^^J\novel at BleedBox^^J\novel at TrimBox}}\next
@@ -156,7 +145,6 @@
%
%% End calculate and specify TrimBox.
-\NDB{11.10 in novel-pdfx.sty.}
%% DISABLE HYPERLINKS AND BOOKMARKS
@@ -193,7 +181,6 @@
}{}
%% End disable hyperlinks and bookmarks.
-\NDB{11.11 in novel-pdfx.sty.}
%% GENERAL PDF INTERNAL METADATA PREPARATION
@@ -205,7 +192,6 @@
%
%% End general PDF in internal metadata preparation.
-\NDB{11.12 in novel-pdfx.sty.}
%% PREPARATION OF XMP METADATA
@@ -230,7 +216,6 @@
\def\pad at cxxviii{\pad at lxiv\pad at lxiv}
\def\pad at cclvi{\pad at cxxviii\pad at cxxviii}
\def\pad at dxii{\pad at cclvi\pad at cclvi}
-\NDB{11.13 in novel-pdfx.sty.}
%
% Frankly, I am not sure if all this rigamarole is necessary, but it works!
% Here, portions of XMP code are prepared. Later, they will be inserted
@@ -254,13 +239,11 @@
\pad at vi</dc:creator>^^J
}
}
-\NDB{11.14 in novel-pdfx.sty.}
%
\def\@documentID{uuid:\xmp at docid}
\def\@instanceID{uuid:\xmp at instid}
%
\def\@pdfVersion{1.\the\pdfminorversion}
-\NDB{11.15 in novel-pdfx.sty.}
%
\ifpdfx at isOFF
\gdef\@verconfString{}%
@@ -272,7 +255,6 @@
\fi
}
\fi
-\NDB{11.16 in novel-pdfx.sty.}
%
\ifpdfx at isOFF
\gdef\@pdfidString{}%
@@ -281,7 +263,6 @@
\pad at vi<pdfxid:GTS_PDFXVersion>\@PDFXversion</pdfxid:GTS_PDFXVersion>^^J
}
\fi
-\NDB{11.17 in novel-pdfx.sty.}
%
\ifthenelse{\equal{\@novelApplication}{} \OR \equal{\@novelApplication}{ }}{
\gdef\@applicationString{}%
@@ -294,7 +275,6 @@
}{
\gdef\@producerString{\pad at vi<pdf:Producer>\@novelProducer</pdf:Producer>^^J}%
}
-\NDB{11.18 in novel-pdfx.sty.}
%
% Calculation of Dates and Times, which must be in a specific format.
% Each time you process to PDF, the current date/time is used,
@@ -344,7 +324,6 @@
%
%% End Prepare XMP metadata.
-\NDB{11.19 in novel-pdfx.sty.}
%% WRITE THE XMP METADATA, UNLESS PDF/X IS OFF OR NO TITLE
@@ -384,7 +363,6 @@
%
%% End write the XMP metadata.
-\NDB{11.20 in novel-pdfx.sty.}
%% PREPARE PDF /INFO METADATA
@@ -413,7 +391,6 @@
\endgroup
\fi
}
-\NDB{11.21 in novel-pdfx.sty.}
% Now, massage the metadata:
\@infotopdfstring{\@infotitle}{\@title}
\@infotopdfstring{\@infoauthor}{\@author}
@@ -428,7 +405,6 @@
%
%% End prepare PDF /Info.
-\NDB{11.22 in novel-pdfx.sty.}
%% WRITE THE OUTPUT INTENT, UNLESS PDFX IS OFF.
@@ -490,7 +466,6 @@
%
%% End write the output intent.
-\NDB{11.23 in novel-pdfx.sty.}
%% DISABLE HYPERREF OPTIONS
@@ -508,7 +483,6 @@
%
%% End disable hyperref options.
-\NDB{11.24 in novel-pdfx.sty.}
%% PREPARE PDF/Info
@@ -544,7 +518,6 @@
%
%% End prepare PDF/Info.
-\NDB{11.25 in novel-pdfx.sty.}
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel-xmppacket.sty
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel-xmppacket.sty 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel-xmppacket.sty 2017-09-14 20:53:13 UTC (rev 45302)
@@ -22,7 +22,7 @@
%%
%%
\ProvidesFile{novel-xmppacket.sty}%
-[2017/08/15 v1.38 LaTeX file (novel XMP packet template)]
+[2017/09/14 v1.40 LaTeX file (novel XMP packet template)]
%%
Modified: trunk/Master/texmf-dist/tex/lualatex/novel/novel.cls
===================================================================
--- trunk/Master/texmf-dist/tex/lualatex/novel/novel.cls 2017-09-14 17:38:58 UTC (rev 45301)
+++ trunk/Master/texmf-dist/tex/lualatex/novel/novel.cls 2017-09-14 20:53:13 UTC (rev 45302)
@@ -17,14 +17,16 @@
%%
\NeedsTeXFormat{LaTeX2e}[1995/12/01]
% Actually needs LuaLaTeX, at least version 0.95 from TeXLive 2016.
-\ProvidesClass{novel}[2017/08/15 v1.38 LaTeX document class]
+\ProvidesClass{novel}[2017/09/14 v1.40 LaTeX document class]
%%
+%% Version 1.40: removed `debug' option (was not useful). Major docs rewrite.
+
%% Version 1.38: corrected offset in cover artwork; some docs modified.
%% Version 1.36: minor documentation correction.
-%% Version 1.34: Added debug class option and related code.
+%% Version 1.34: Added debug class option and related code. [Later removed.]
%% Version 1.32 includes a minor documentation fix, and a major bug fix
%% concerning looose text tracking. The bug occasionally appeared when
@@ -59,12 +61,7 @@
%% custom font, NovelDeco.otf, is used for special purposes.
%%
-%% From version 1.34, novel has a debug system. See documentation pg. 11.
-%% Some messages appear in log file, whether or not debug option used.
-%% Other messages only appear with debug option.
-\typeout{Novel Tracking 0.0: Begin loading novel.cls file.}
-
%% REQUIRE LUATEX and do some preliminary setup.
%% -----------------------------------------------------------------------------
%% These are not user settings.
@@ -127,7 +124,7 @@
%% -----------------------------------------------------------------------------
% Allowed option list:
% draft xml shademargins graytext greytext cropmarks cropview closecrop
-% coverart debug
+% coverart unblock
% Yes, I realize that this could have been done another way:
\gdef\@mycol{\@classoptionslist}
\StrDel{\@mycol}{ }[\@mycol]
@@ -141,11 +138,13 @@
\StrDel{\@mycol}{cropview}[\@mycol]
\StrDel{\@mycol}{closecrop}[\@mycol]
\StrDel{\@mycol}{coverart}[\@mycol]
-\StrDel{\@mycol}{debug}[\@mycol]
+\StrDel{\@mycol}{debug}[\@mycol] % obsolete
+\StrDel{\@mycol}{unblock}[\@mycol]
%
\ifthenelse{\equal{\@mycol}{}}{}{
\ClassWarning{novel}{Unrecognized class option: \@mycol^^J%
The unrecognized option was ignored!^^J%
+ If `debug' it is obsolete from v.1.40.^^J%
Note that font point size and document size^^J%
are not novel class options. See documentation.}%
}
@@ -214,11 +213,6 @@
\DeclareOption{coverart}{
\@coverarttrue
}
-% New in version 1.34: debug option. See documentation page 11.
-\newif \if at noveldebug
-\DeclareOption{debug}{
- \@noveldebugtrue
-}
% New in version 1.34: unblock option, for developer use only.
% Normally, a number of packages known to be incompatible with this document class
% are blocked from loading. If the user tries to get them via \usepackage
@@ -259,15 +253,7 @@
\fi
%% end class options
-\typeout{Novel Tracking 0.0: Class options processed.}
-% \NDB is used in various other files, part of novel class.
-% It may also be used in the TeX document.
-% If debug option, this prints a message to log file.
-% Example usage: \NDB{your message goes here}
-\gdef\NDB#1{\if at noveldebug\typeout{Novel Tracking #1}\fi}
-
-
%% Activate xcolor, adjustbox, and eso-pic:
%% -----------------------------------------------------------------------------
% The final book must be monochrome (black and white only) for all text
@@ -311,7 +297,6 @@
%
%% end temporary normal point size and baselineskip
-\typeout{Novel Tracking 0.1: Additional packages loaded.}
%% Define commands used for File Data, including PDF/X Settings.
%% -----------------------------------------------------------------------------
@@ -319,7 +304,6 @@
%% and in XMP. This class does not write it to the Catalog.
%% Defines commands such as \title{}, not necessarily the same as other TeX.
\RequirePackage{novel-FileData}
-\typeout{Novel Tracking 0.2: novel-FileData.sty loaded.}
%
%%
@@ -329,7 +313,6 @@
%% Define commands that over-ride the class option pre-configured settings.
%% Variety of miscellaneous layout settings such as \parsep, \parindent, etc.
\RequirePackage{novel-LayoutSettings}
-\typeout{Novel Tracking 0.3: novel-LayoutSettings.sty loaded.}
%
%%
@@ -339,19 +322,14 @@
%%
% Macros for use in document body:
\RequirePackage{novel-TextMacros} % part of novel class
-\typeout{Novel Tracking 0.4: novel-TextMacros.sty loaded.}
% Standard `fancyhdr' header footer styles:
\RequirePackage{novel-HeadFootStyles} % part of novel class
-\typeout{Novel Tracking 0.5: novel-HeadFootStyles.sty loaded.}
% Chapter and Scene styles:
\RequirePackage{novel-ChapterScene}
-\typeout{Novel Tracking 0.6: novel-ChapterScene.sty loaded.}
% Image placement:
\RequirePackage{novel-Images} % part of novel class
-\typeout{Novel Tracking 0.7: novel-Images.sty loaded.}
% Footnotes and endnotes:
\RequirePackage{novel-Footnotes} % part of novel class
-\typeout{Novel Tracking 0.8: novel-Footnotes.sty loaded.}
%%
@@ -359,17 +337,12 @@
%% -----------------------------------------------------------------------------
%
\AtEndPreamble{
- \typeout{Novel Tracking 1.AEP.E: Entered AtEndPreamble routine in novel.cls.}
\RequirePackage{novel-CalculateLayout}
- \typeout{Novel Tracking 1.9: novel-CalculateLayout.sty loaded.}
\RequirePackage{novel-FontDefaults}
- \typeout{Novel Tracking 1.10: novel-FontDefaults.sty loaded.}
\renewcommand\textls[2][]{#2%
\typeout{Class `novel' Alert: \string\textls\space ignored on pg \thepage.}%
} % nullifies this microtype command (problems)
- \RequirePackage{novel-pdfx}
- \typeout{Novel Tracking 1.11: novel-pdfx.sty loaded.}
- \typeout{Novel Tracking 1.AEP.X: Exiting AtEndPreamble routine in novel.cls.}
+ \RequirePackage{novel-pdfx}%
}
%%
@@ -378,7 +351,6 @@
%% -----------------------------------------------------------------------------
%
\AtBeginDocument{ %
- \typeout{Novel Tracking 1.ABD.E: Entering AtBeginDocument routine in novel.cls.}
\defaultfontfeatures{} % reset
% Any other fonts will use these defaults:
\defaultfontfeatures{%
@@ -385,7 +357,6 @@
SmallCapsFeatures={Renderer=Basic},Kerning=On,%
Ligatures=TeX,%
}%
- \NDB{1.ABD.1 in novel.cls.}
%
% Find some useful measurements:
\gdef\@normalxheight{\heightof{x}}
@@ -394,7 +365,6 @@
\gdef\@normalXheight{\heightof{X}}
\setlength\normalXheight{\@normalXheight}
\global\normalXheight=\normalXheight
- \NDB{1.ABD.2 in novel.cls.}
% Activate user choice of whether or not to indent after scenebreak commands:
\if at indentAfterScenebreak\else
\NoIndentAfterCmd{\scenebreak}
@@ -401,7 +371,6 @@
\NoIndentAfterCmd{\sceneline}
\NoIndentAfterCmd{\scenestars}
\fi
- \NDB{1.ABD.3 in novel.cls.}
%
\@activateHeadFootStyles % in file `novel-HeadFootStyles.sty'
\@novelPDFinfo % in file `novel-pdfx.sty'.
@@ -410,7 +379,6 @@
\let\title\relax
\let\author\relax
\let\subtitle\relax
- \NDB{1.ABD.4 in novel.cls.}
% Dealing with known incompatible packages:
\if at novelunblock
\gdef\sorry at no#1{} % let them be used
@@ -424,7 +392,6 @@
}{}%
}
\fi
- \NDB{1.ABD.5 in novel.cls.}
%
\sorry at no{pdfx}
\sorry at no{xmpincl}
@@ -454,13 +421,12 @@
\sorry at no{engord}
\sorry at no{endnotes}
%%
- \NDB{1.ABD.6 in novel.cls.}
+
%%
%% Pertains to novel-LayoutSettings.sty:
\ifcsname pagenumberstyle\endcsname\else
\SetPageNumberStyle{\thepage}
\fi
- \NDB{1.ABD.7 in novel.cls.}
%
\def\@setchapterstartOK{false}%
\ifthenelse{\equal{\@setchapterstart}{empty}}{%
@@ -494,7 +460,6 @@
\ClassError{novel}{\string\SetChapterStart\space bad argument}%
{\string\SetChapterStart\space only allows certain choices.^^J}%
}%
- \NDB{1.ABD.8 in novel.cls.}
%%
%% Pertains to novel-TextMacros.sty:
\setlength\forceparlength{\parindent}
@@ -501,7 +466,6 @@
\global\forceparlength=\forceparlength
\gdef\forceindent{\ifvmode\else\unskip\fi\stake\hspace{\forceparlength}}
\gdef\backindent{\ifvmode\else\unskip\fi\hspace{-\forceparlength}}
- \NDB{1.ABD.9 in novel.cls.}
%%
%% Pertains to novel-footnotes.sty:
\gdef\SetFootnoteMarker#1{%
@@ -510,7 +474,6 @@
}
% Must wait for \nbs to be calculated:
\setlength\footnotesep{0.8\nbs}
- \NDB{1.ABD.10 in novel.cls.}
% Must wait for main font and its size to be active:
\newlength\@hoaring
\setlength\@hoaring{\heightof{Å}}
@@ -539,13 +502,10 @@
\addtolength\@tweight{-0.2\@tweight}%
\addtolength\@tweight{-\@hoaring}%
\global\@tweight=\@tweight%
- \NDB{1.ABD.11 in novel.cls.}
% Must wait to see how \SetFootnoteMarker was used:
\ifthenelse{\equal{\@myfnsymbols}{*}}{\setcounter{@maxfnsymbol}{8}}{}
\ifthenelse{\equal{\@myfnsymbols}{†}}{\setcounter{@maxfnsymbol}{6}}{}
- \NDB{1.ABD.12 in novel.cls.}
%%
- \typeout{Novel Tracking 1.ABD.X: Exiting AtBeginDocument in novel.cls.}
}
%%
@@ -552,7 +512,6 @@
%% New in version 1.2, coverart option. See docs page 10.
\AfterEndPreamble{
- \typeout{Novel Tracking 1.FEP.E: Entered AfterEndPreamble in novel.cls.}
\if at coverart
\AddToShipoutPictureBG{%
\AtPageUpperLeft{%
@@ -561,7 +520,6 @@
}
\null% without this, page has no "content"
\fi
- \typeout{Novel Tracking 1.FEP.X: Exiting AfterEndPreamble in novel.cls.}
}
%%
@@ -568,11 +526,9 @@
%% AtBeginShipout occurs at the completion of each page layout, in document body.
\AtBeginShipout{%
- \NDB{1.ABS.E: Entered AtBeginShipout, page \thepage, in novel.cls.}%
\gdef\@fnafter{}% Pertains to some standard LaTeX footnote code.
\stepcounter{runningpages}%
\global\@thispagestylesetfalse%
- \NDB{1.ABS.X: Exiting AtBeginShipout, page \thepage, in novel.cls.}%
}
%%
More information about the tex-live-commits
mailing list