summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html')
-rw-r--r--Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html25
1 files changed, 20 insertions, 5 deletions
diff --git a/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html b/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
index b058bb1d1a0..523555173f4 100644
--- a/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
+++ b/Master/texmf-dist/doc/lualatex/novel/noveldocs-01-overview.html
@@ -139,7 +139,7 @@
<div id="main">
<a id="thetop"></a>
<h1>Documentation for <code>novel</code> document class</h1>
-<p>Documentation version: 1.32.</p>
+<p>Documentation version: 1.34.</p>
<div class="pagetopage">
<p><b>User Guide</b></p>
@@ -155,6 +155,7 @@
<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>
@@ -206,11 +207,25 @@
<a id="a1.1.4"></a>
<h4>1.1.4 Useful Tools</h4>
-<p>Before sending your PDF file anywhere, you should always open it in Adobe Reader, and inspect it. If you are on a system that does not have that software, then find a friend who has it. The reason is that some other PDF readers will not object to problem files, but Adobe Reader will complain.</p>
+<p><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>In commercial printing, it is not necessary that your file be "optimized for fast web view" or "linearized." Nevertheless, some services do a lot of work with e-books, and may request that printer files be optimized or linearized, out of force of habit. The free <code>qpdf</code> command-line tool, available for Linux and Windows, is your friend.</p>
+<p>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>Your PDF cannot be encrypted or password-protected for commercial printing. Only you and the printer are supposed to see it. So, it is always possible to extract the text, not as a TeX document, but as plain text. Adobe Reader probably will not do what you expect. Adobe Acrobat Pro does a good job, if you first "add tags" via its accessibility features. Otherwise, the free Okular PDF reader does a reasonable job, as does the <code>pdftotext</code> command-line program (part of <code>xpdf</code>). Be sure to request that layout be preserved. You may need to review the exported text for words that were broken by hyphenation, and re-assemble the words.</p>
+<p>A good word processor will have a high-end spelling checker, and perhaps some grammatical checks. It can apply &ldquo;smart quotes&rdquo; 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>
@@ -760,7 +775,7 @@
<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.</p>
+<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>