1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
|
<!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.36.</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>
|
