1
1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
4
<title>printtarg</title>
5
<meta http-equiv="content-type"
6
content="text/html; charset=ISO-8859-1">
7
<meta name="author" content="Graeme Gill">
10
<h2><b>target/printtarg</b></h2>
12
Create a PostScript (PS), Embedded PostScript (EPS) or Tagged Image
13
File Format (TIFF) file containing profile test patch values, ready for
15
<h3>Usage Summary</h3>
16
<small><span style="font-family: monospace;">printtarg [options]
17
basename</span><br style="font-family: monospace;">
18
<span style="font-family: monospace;"> </span><a
19
style="font-family: monospace;" href="#v">-v</a><span
20
style="font-family: monospace;">
21
Verbose mode</span><br style="font-family: monospace;">
22
<span style="font-family: monospace;"> </span><a
23
style="font-family: monospace;" href="#i">-i 20 | 22 | 41 | 51 | SS |
24
i1 | CM</a><span style="font-family: monospace;"> Select target
26
(default DTP41)</span><br style="font-family: monospace;">
27
<span style="font-family: monospace;">
28
20 = DTP20, 22 = DTP22, 41 = DTP41, 51 = DTP51, SS = SpectroScan,<br>
4
<title>printtarg</title>
5
<meta http-equiv="content-type" content="text/html;
7
<meta name="author" content="Graeme Gill">
10
<h2><b>target/printtarg</b></h2>
12
Create a PostScript (PS), Embedded PostScript (EPS) or Tagged Image
13
File Format (TIFF) file containing profile test patch values, ready
16
<h3>Usage Summary</h3>
17
<small><span style="font-family: monospace;">printtarg [options]
18
basename</span><br style="font-family: monospace;">
19
<span style="font-family: monospace;"> </span><a
20
style="font-family: monospace;" href="#v">-v</a><span
21
style="font-family: monospace;">
23
mode</span><br style="font-family: monospace;">
24
<span style="font-family: monospace;"> </span><a
25
style="font-family: monospace;" href="#i">-i 20 | 22 | 41 | 51 |
27
i1 | CM</a><span style="font-family: monospace;"> Select target
29
(default DTP41)</span><br style="font-family: monospace;">
30
<span style="font-family: monospace;">
36
DTP22, 41 = DTP41, 51 = DTP51, SS = SpectroScan,<br>
29
37
31
i1Pro, CM = ColorMunki</span><br style="font-family: monospace;">
32
<span style="font-family: monospace;"> </span><a
33
style="font-family: monospace;" href="#a">-a scale</a><span
34
style="font-family: monospace;">
35
Scale patch and spacer size by factor (e.g. 0.857 or 1.5 etc.)<br>
36
</span></small><small><span style="font-family: monospace;"> </span><a
37
style="font-family: monospace;" href="#A">-A scale</a><span
38
style="font-family: monospace;">
39
Scale spacer size by additional factor (e.g. 0.857 or 1.5 etc.)</span></small><br
40
style="font-family: monospace;">
41
<small><span style="font-family: monospace;"></span><span
42
style="font-family: monospace;"> </span><a
43
style="font-family: monospace;" href="#h">-h</a><span
44
style="font-family: monospace;">
45
46
Use hexagon patches for SS, double density for CM</span><br
47
style="font-family: monospace;">
48
<span style="font-family: monospace;"> </span><a
49
style="font-family: monospace;" href="#r">-r</a><span
50
style="font-family: monospace;">
51
Don't randomize patch location</span><br style="font-family: monospace;">
52
<span style="font-family: monospace;"> </span><a
53
style="font-family: monospace;" href="#s">-s</a><span
54
style="font-family: monospace;">
55
Create a scan image recognition (.cht) file</span><br
56
style="font-family: monospace;">
57
<span style="font-family: monospace;"> </span><a
58
style="font-family: monospace;" href="#S">-S</a><span
59
style="font-family: monospace;">
60
Same as -s, but don't generate wide orientation strip.</span><br
61
style="font-family: monospace;">
62
<span style="font-family: monospace;"> </span><a
63
style="font-family: monospace;" href="#c">-c</a><span
64
style="font-family: monospace;">
65
Force colored spacers</span><br style="font-family: monospace;">
66
<span style="font-family: monospace;"> </span><a
67
style="font-family: monospace;" href="#b">-b</a><span
68
style="font-family: monospace;">
69
70
Force B&W spacers</span><br style="font-family: monospace;">
71
<span style="font-family: monospace;"> </span><a
72
style="font-family: monospace;" href="#n">-n</a><span
73
style="font-family: monospace;">
74
Force no spacers</span><br style="font-family: monospace;">
75
<span style="font-family: monospace;"> </span><a
76
style="font-family: monospace;" href="#f">-f</a><span
77
style="font-family: monospace;">
78
Create PostScript DeviceN Color fallback</span><br
79
style="font-family: monospace;">
80
<span style="font-family: monospace;"> </span><a
81
style="font-family: monospace;" href="#w">-w g|r|s|n</a><span
82
style="font-family: monospace;">
83
White colorspace encoding DeviceGray (def), DeviceRGB, Separation or
84
DeviceN</span><br style="font-family: monospace;">
85
<span style="font-family: monospace;"> </span><a
86
style="font-family: monospace;" href="#k">-k g|c|s|n</a><span
87
style="font-family: monospace;"> Black
88
colorspace encoding DeviceGray (def), DeviceCMYK, Separation or DeviceN</span><br
89
style="font-family: monospace;">
90
<span style="font-family: monospace;"> </span><a
91
style="font-family: monospace;" href="#e">-e</a><span
92
style="font-family: monospace;">
93
Output EPS compatible file<br>
94
<a href="#t">-t [res]</a>
95
Output 8 bit TIFF raster file, optional res DPI (default 200)<br>
96
<a href="#T">-T [res]</a>
97
Output 16 bit TIFF raster file, optional res DPI (default 200)<br>
98
</span></small><small><span style="font-family: monospace;"> <a
99
href="#C">-C</a>
100
Don't use TIFF compression</span></small><br>
101
<small><span style="font-family: monospace;"> <a href="#N">-N</a>
102
Use TIFF alpha N channels more than 4<br>
103
<a href="#Q">-Q nbits</a>
104
Quantize test values to fit in nbits<br>
105
</span></small><small style="font-family: monospace;"> <span
106
style="text-decoration: underline;">-</span><a href="#K">K
107
file.cal</a> Apply printer calibration to patch
108
values and include in .ti2<br>
109
<a href="#I">-I file.cal</a> Include
110
calibration in .ti2 (but don't apply it)<br
111
style="font-family: monospace;">
112
</small><small><span style="font-family: monospace;"></span><span
113
style="font-family: monospace;"> </span><a
114
style="font-family: monospace;" href="#R">-R rsnum</a><span
115
style="font-family: monospace;">
116
Use given random start number</span><br style="font-family: monospace;">
117
<span style="font-family: monospace;"> </span><a
118
style="font-family: monospace;" href="#x">-x pattern</a><span
119
style="font-family: monospace;"> Use
121
strip indexing pattern (Default = "A-Z, A-Z")</span><br
122
style="font-family: monospace;">
123
<span style="font-family: monospace;"> </span><a
124
style="font-family: monospace;" href="#y">-y pattern</a><span
125
style="font-family: monospace;"> Use
127
patch indexing pattern (Default = "0-9,@-9,@-9;1-999")</span><br
128
style="font-family: monospace;">
129
<span style="font-family: monospace;"> </span><a
130
style="font-family: monospace;" href="#m">-m margin</a><span
131
style="font-family: monospace;">
133
mm (default 6.0 mm)<br>
134
</span></small><small><span style="font-family: monospace;"> </span><a
135
style="font-family: monospace;" href="#M">-M margin</a><span
136
style="font-family: monospace;"> </span></small><small><span
137
style="font-family: monospace;">Set a page margin in mm and include it
138
in TIFF</span><span style="font-family: monospace;"></span></small><br>
139
<small><span style="font-family: monospace;"> <a href="#P">-P</a>
140
141
Don't limit strip length</span></small><br>
142
<small><span style="font-family: monospace;"> <a href="#L">-L</a>
143
Suppress any left paper clip border<br style="font-family: monospace;">
144
</span><span style="font-family: monospace;"> </span><a
145
style="font-family: monospace;" href="#p">-p size</a><span
146
style="font-family: monospace;">
147
Select page size from:</span><br style="font-family: monospace;">
148
<span style="font-family: monospace;">
149
A4 [210.0 x 297.0 mm]</span><br
150
style="font-family: monospace;">
151
<span style="font-family: monospace;">
152
A4R [297.0 x 210.0 mm]</span><br
153
style="font-family: monospace;">
154
<span style="font-family: monospace;">
155
A3 [297.0 x 420.0 mm] (default)</span><br
156
style="font-family: monospace;">
157
<span style="font-family: monospace;">
158
A2 [420.0 x 594.0 mm]</span><br
159
style="font-family: monospace;">
160
<span style="font-family: monospace;">
161
Letter [215.9 x 279.4 mm]</span><br
162
style="font-family: monospace;">
163
<span style="font-family: monospace;">
164
LetterR [279.4 x
165
215.9 mm]</span><br style="font-family: monospace;">
166
<span style="font-family: monospace;">
167
Legal [215.9 x 355.6 mm]</span><br
168
style="font-family: monospace;">
169
<span style="font-family: monospace;">
170
11x17 [279.4 x 431.8 mm]</span><br
171
style="font-family: monospace;">
172
<span style="font-family: monospace;"> </span><a
173
style="font-family: monospace;" href="#pp">-p WWWxHHH</a><span
174
style="font-family: monospace;"> Custom
177
</span></small><small style="font-family: monospace;"></small><br
178
style="font-family: monospace;">
179
<small><span style="font-family: monospace;"></span>
180
<span style="font-family: monospace;"></span><a
181
style="font-family: monospace;" href="#p1"><i>basename</i></a><span
182
style="font-family: monospace;">
183
Base name for input(</span><a style="font-family: monospace;"
184
href="File_Formats.html#.ti1">.ti1</a><span
185
style="font-family: monospace;">), output(</span><a
186
style="font-family: monospace;" href="File_Formats.html#.ti2">.ti2</a><span
187
style="font-family: monospace;">) and output(.ps/.eps/.tif)</span></small><br>
188
<h3>Usage Details and Discussion</h3>
189
<b> printtarg</b> is used to generate a PostScript or TIFF print file
191
device test values in a .ti1 file. It output both a PostScript/EPS/TIFF
192
file, and a .ti2 file containing the device test values together with
193
the layout information needed to identify the patch location. This
194
module can also generate the image recognition templates needed to read
195
the print targets in using a scanner.<br>
197
<a name="v"></a> The <b>-v</b> flag turns on verbose mode. Prints
198
information about how many patches there are in a row, how many patches
199
in a set, and how many pages will be generated. Good for figuring
200
out what the magic number of patches should be for a particular page
203
<a name="i"></a> The <b>-i</b> parameter should be used to tell
204
printtarg which instrument it should lay the patches out for. Each
206
slightly different requirement, and will lead to a different number of
43
ColorMunki</span><br style="font-family: monospace;">
44
<span style="font-family: monospace;"> </span><a
45
style="font-family: monospace;" href="#a">-a scale</a><span
46
style="font-family: monospace;">
52
by factor (e.g. 0.857 or 1.5 etc.)<br>
53
</span></small><small><span style="font-family: monospace;"> </span><a
54
style="font-family: monospace;" href="#A">-A scale</a><span
55
style="font-family: monospace;">
61
factor (e.g. 0.857 or 1.5 etc.)</span></small><br
62
style="font-family: monospace;">
63
<small><span style="font-family: monospace;"></span><span
64
style="font-family: monospace;"> </span><a
65
style="font-family: monospace;" href="#h">-h</a><span
66
style="font-family: monospace;">
67
208
ending up on a particular page size. For a generic type of chart, try <span
209
style="font-weight: bold;">SS</span>.<br>
211
<a name="a"></a><a name="A"></a> <span style="font-weight: bold;">-a,
212
-A: </span>Normally, <b>printtarg</b> prints test patches that
213
are the minimum size that can be reliably and accurately read by the
214
instrument. For some media, it might be desirable to use test
215
patches that are larger than this minimum (e.g. if the media has poor
216
registration, gets physically distorted in the print production
217
process, or if it has a coarse screen, and there are few samples per
218
patch), and the <span style="font-weight: bold;">-a</span> flag should
219
be given an argument greater than 1.0 to increase the patch length,
220
patch width, and spacer size between patches, if it is appropriate for
221
the type of instrument. A
222
value of 1.5 would make the patch 50% larger for instance. For the
223
strip reading instruments the patch is made longer, the strip spacing
224
remaining the same, while for XY scanning instruments, both the width
225
and height will be increased. If a value less than 1.0 is given as an
226
argument, then the patches will be made smaller. For instance, using
227
the SpectroScan instrument it is possible to reduce the test patches to
228
6mm rather than the default 7mm by supplying an argument of 0.857.
230
that this make lining up of the scan head very critical, and increases
231
the amount of bleed through from adjacent squares. For an instrument
232
that needs color spacers between patches, <span
233
style="font-weight: bold;">-a scale</span> also scales the spacer
234
length. For some situations, this may be insufficient, and the <span
235
style="font-weight: bold;"> -A scale</span> option
236
can be used to additionally scale the spacer length.<br>
238
<a name="h"></a> Normally, <b>printtarg</b> creates a regular grid of
239
test patches, but for instruments that support arbitrary X, Y
240
addressing (such as the SpectroScan). For the <span
241
style="font-weight: bold;">SpectroScan</span> it can also create a
243
regular hexagonal patches, allowing more patches to be fitted into a
244
single sheet if the <span style="font-weight: bold;">-h</span> flag
245
is used. For the <span style="font-weight: bold;">ColorMunki</span>
246
instrument, <span style="font-weight: bold;">-h</span> doubles the
247
normal number of patches is printed by halving the row width. The
248
patches are also staggered to improve the detection of a poor scan.<br>
250
<a name="r"></a> Normally, <b>printtarg</b> randomizes the patch
251
locations, which helps strip reading instruments detect patch
252
boundaries and the direction the strip was read in, as well as being
253
able to detect incorrect strips being
254
fed into strip reading instruments, and also assists in randomizing any
255
systematic printing errors introduced into the test chart due to print
256
engine unevenness, inkjet banding, or printing press ink key settings
257
etc. The <b>-r</b> flag turns this off, and lays the test squares out
258
in the order the values appear in, in the .ti1 file. Note that if you
259
turn this off you probably want to <a href="chartread.html#B">disable
260
bi-directional</a> strip reading in instruments such as the i1pro.<br>
262
<a name="s"></a> The <b>-s</b> flag does two things. One is that it
263
causes printtarg to output a chart recognition file (<a
264
href="File_Formats.html#.cht">.cht</a>) so that <a href="scanin.html">
265
scanin</a> can recognize the chart, and convert rasterized patches into
266
patch values, and the second is that is expands the size of the leading
268
of patches by 50%, to help make sure that each sheet can be oriented
269
correctly by <a href="scanin.html"> scanin</a>. <a name="S"></a>If <b>-S</b>
271
rather than <b>-s</b>, then the recognition chart will be created, but
273
leading row will be the same size as all the other rows.<br>
275
<a name="c"></a> For strip reading instruments, the contrast with the
276
spacers is important in ensuring that a reading will be successful.
277
Normally <span style="font-weight: bold;">printtarg</span> ensures
278
this by printing optimally contrasting colored spacers between each
279
measurement patch. The <b>-c</b> flag is therefore the default
280
behaviour. <a name="b"></a>If the <b>-b</b> flag is used, then
281
contrasting neutral colored
282
spacers will be used, but these generally work less reliably than
284
spacers. <a name="n"></a>The <b>-n</b> flag will cause spacers to be
286
which may still work with smaller numbers of test values when the
288
selection is randomized, but won't work successfully when a large
290
of test points is being used (>200), or when the patches are not
294
<a name="f"></a><b>-f</b>:
295
When creating a test chart for more than CMYK inks, a PostScript file
296
normally contains color settings that use the PostScript level 3
298
N" color specifications. Such color specifications have a "fallback"
300
for PostScript interpreters that don't handle Device N specifications.
302
fallback colors are normally set to a grayscale estimate of the patch
304
so that it is possible to tell if the PostScript interpreter is not
306
the Device N values correctly. <a name="f"></a>The <b>-f</b> flag,
308
the fallback color to be a color estimate of the Device N test patch
310
which is useful for diagnostic purposes.<br>
312
<a name="e"></a> The <b>-e</b> flag gives EPS output, rather than
313
PostScript, allowing the charts to be included in other applications.
314
Because EPS disallows the showpage command, multiple EPS files will
315
result for a multi-page test chart, each one having a two digit number
316
sequence in it's name, so if the input file name is <span
317
style="font-weight: bold;">chart</span>, then file <span
318
style="font-weight: bold;">chart.ti1</span> will be read, and file <span
319
style="font-weight: bold;">chart.ti2</span> written, together with <span
320
style="font-weight: bold;">chart.eps</span> if there is only one page,
321
or <span style="font-weight: bold;">chart_01.eps</span>, <span
322
style="font-weight: bold;">chart_02.eps</span>, etc. if there is more
325
<a name="t"></a><a name="T"></a><span style="font-weight: bold;">-t
326
[res], -T [res]</span> The <b>-t</b> flag gives TIFF raster output
328
PostScript, allowing the charts to be printed to systems that do not
329
accept PostScript input. Because few systems understand multi-page TIFF
330
files, multiple TIFF files will
331
result for a multi-page test chart, each one having a two digit number
332
sequence in it's name, so if the input file name is <span
333
style="font-weight: bold;">chart</span>, then file <span
334
style="font-weight: bold;">chart.ti1</span> will be read, and file <span
335
style="font-weight: bold;">chart.ti2</span> written, together with <span
336
style="font-weight: bold;">chart.eps</span> if there is only one page,
337
or <span style="font-weight: bold;">chart_01.tif</span>, <span
338
style="font-weight: bold;">chart_02.tif</span>, etc. if there is more
339
than one page. By default the resolution of the chart will be 100 Dots
340
Per Inch (DPI), but this can be changed by providing an optional DPI
341
argument after the <span style="font-weight: bold;">-t</span> or <span
342
style="font-weight: bold;">-T</span> flag. If the <span
343
style="font-weight: bold;">-t</span> flag is used, than an 8 bit per
344
component TIFF file will be created. If the <span
345
style="font-weight: bold;">-T</span> flag is used, then a 16 bit per
346
component TIFF file will be created.<br>
348
<a name="C"></a><span style="font-weight: bold;">-C:</span> Normally
349
the TIFF files created will be compressed using LZW compression to save
350
space. Some systems may not support this compression, so it can be
351
disabled by using the <span style="font-weight: bold;">-C</span> flag.<br>
353
<a name="N"></a><span style="font-weight: bold;">-N:</span> When
354
creating TIFF files with more than 4 colorants, the normal Separated
355
mode is used. Some systems don't cope well with extra colorants
356
presented in this manner, and the <span style="font-weight: bold;">-N</span>
357
flag causes all the channels greater than 4 to be labelled as "Alpha"
358
channels, which may be more palatable.<br>
360
<a name="Q"></a><span style="font-weight: bold;">-Q:</span> Normally
361
the target device values are floating point numbers that may get
362
rounded and quantized in the process of printing them or reproducing
363
them on the printing or display device. If some of this quantization
364
can be accounted for, it may improve the accuracy of the resulting
365
profile, and the <span style="font-weight: bold;">Q</span> parameter
366
allows this quantization to be specified. The parameter is the number
367
of binary digits (bits) that the device values should be quantized to.
368
In many systems the right value would be 8 bits. Note that if 8 bit TIFF<span
369
style="font-weight: bold;"></span> output is selected (<span
370
style="font-weight: bold;">-t</span>) that the values will by default
371
be quanized to 8 bits, and that if 16 bit TIFF<span
372
style="font-weight: bold;"></span> output is selected (<span
373
style="font-weight: bold;">-T</span>) that the values will by default
374
be quanized to 16 bits.<br>
376
<a name="K"></a> The <b>-K file.cal</b> parameter specifies a printer
377
calibration file created by <a href="printcal.html">printcal</a>, and
378
the supplied calibration curves will be applied to the test patch
379
values. This allows profiling of a printing system that doesn't
380
natively support calibration. The calibration curves will also be
382
the resulting .ti2 file, so that they can be passed through to .ti3
383
file and ICC profile, to allow accurate computation of ink limits.<br>
385
<a name="I"></a> The <b>-I file.cal</b> parameter specifies a printer
386
calibration file created by <a href="printcal.html">printcal</a>,
387
and the calibration curves will be
388
included in the included in
389
the resulting .ti2 file, so that they can be passed through to .ti3
391
and ICC profile, to allow accurate computation of ink limits.
392
The calibration <span style="font-weight: bold;">is not applied</span>
393
to the test patch values, but is assumed to be applied somewhere else
394
in the printing workflow when printing the profile test chart.<br>
396
<a name="R"></a> The <b>-R</b> parameter allows setting the random
397
layout seed. Normally the seed is chosen at random, but sometimes it is
398
useful to be able to generate a chart with the same layout, so a
399
specific seed can be specified this way. The seed (ID) used to generate
73
double density for CM</span><br style="font-family: monospace;">
74
<span style="font-family: monospace;"> </span><a
75
style="font-family: monospace;" href="#r">-r</a><span
76
style="font-family: monospace;">
80
location</span><br style="font-family: monospace;">
81
<span style="font-family: monospace;"> </span><a
82
style="font-family: monospace;" href="#s">-s</a><span
83
style="font-family: monospace;">
401
chart is recorded in the
402
.ti2 file, and is also in the label printed on the right hand side of
405
<a name="x"></a> The <b>-x</b> parameter allows specifying the
406
labelling sequence used for strips (e.g. the X axis of the chart). By
407
default this will be a character sequence A, B, C .. Z. AA, AB, AC ..
408
ZZ, but this can be changed by specifying an alternate labelling
409
sequence pattern. The pattern specifies the labelling sequence as
410
follows: First comes the definition of the symbols for each digit
411
location, least significant to most significant, each digit separated
412
by the ',' character. Note that space is a
413
valid character. The number of
414
definitions declares the maximum number of digits. For example, for a 2
415
digit numerical sequence: "0123456789, 123456789" would define
416
0..99 with the most significant digit suppressed when it is 0 (because
418
space rather than 0). Ranges
419
can be used for brevity: "0-9, 1-9". As a special case, the '@'
420
character can be used to instead of '0' to indicate suppression of the
421
leading zero: "0-9,@-9". Leading ' ' characters in the resulting
422
generated sequence are
423
omitted. Optionally following this and delimited by a ';'
424
character, are the definitions of valid segments of the index sequence.
425
For instance, to define the index range to be 1..19, 30..39 one could
426
use the pattern "0-9, 1-9;1-19,30-39". Of course most of the time an
427
alphabetic sequence will be wanted, to distinguish it from the
428
numerical sequence used to number the patches in a strip. For a
429
sequence A, B, C .. AA, AB, AC etc. (the default used in Argyll), the
430
following patter would be used: "A-Z, A-Z". For a some ECI2002R charts
431
that skip columns Y and Z, and use a leading numeric digits for
432
addressing strips over 26, the following might be used: "A-Z,
435
<a name="y"></a> The <b>-y</b> parameter allows specifying the
436
labelling sequence used for patches (e.g. the Y axis of the chart). By
437
default this will be a number sequence 1, 2, ..10, 11, ... 999, but
438
this can be changed by specifying an alternate labelling
439
sequence pattern. See the above description for the labelling sequence
442
<span style="font-weight: bold;">NOTE</span> that the pattern chosen
443
for the X and Y axes of the chart must be distinguishable, e.g. if they
444
are both numbers or both letters then reading the chart will fail.<br>
446
<a name="w"></a> The <b>-w</b> parameter changes how a white
447
colorspace test chart (ie. Additive Grey monochrome) will be
448
represented in the Postscript output.
449
The default is to use the DeviceGray representation (<span
450
style="font-weight: bold;">-wg</span>), but Device RGB can also be
451
used, where the R, G &B values are all set to the same value (<span
452
style="font-weight: bold;">-wr</span>), a <span
453
style="font-weight: bold;">White</span> separation color can be
454
specified (<span style="font-weight: bold;">-ws</span>), or a DeviceN <span
455
style="font-weight: bold;">White</span> color can be used (<span
456
style="font-weight: bold;">-wn</span>).<br>
458
<a name="k"></a> The <b>-k</b> parameter changes how a black
459
colorspace test chart (ie. Subtractive
460
Grey monochrome ) will be represented in the Postscript output. The
461
default is to use the
462
DeviceGray representation (<span style="font-weight: bold;">-kg</span>),
463
but Device CMYK can also be used, where the CMY values are zero, and
464
just the K channel is used (<span style="font-weight: bold;">-kc</span>),
465
a <span style="font-weight: bold;">Black</span> separation color can
466
be specified (<span style="font-weight: bold;">-ks</span>), or a
467
DeviceN <span style="font-weight: bold;">Black</span> color can be
468
used (<span style="font-weight: bold;">-kn</span>).<br>
470
<a name="m"></a> The <b>-m</b> parameter sets the page margin for all
471
sides. If parts of the test chart are not printed at the edge of a
472
sheet, the devices printable area may be smaller than the default
473
assumed by <span style="font-weight: bold;">printtarg</span>.
474
Increasing this from the default of 6 mm to 10 or 15 mm, may alleviate
475
this problem. (Note that
476
the number of patches per page may be reduced as a consequence.)
477
Decreasing the margin below 6 mm may be possible for printers that have
478
smaller or no margins, increasing the number of patches possible on
479
each page. A TIFF chart will be the size of the paper minus the margin,
481
can be placed on a page that size without cropping or inadvertent
484
<a name="M"></a> The <b>-M</b> parameter sets the page margin for all
485
sides, but for a TIFF chart will the margin will be <span
486
style="font-weight: bold;">included</span> in the raster, meaning that
487
the TIFF will have to be printed right to the edge of the paper,
488
or on paper larger than the raster size.<br>
490
<a name="P"></a> The <b>-P</b> flag disables any normal limiting of
491
strip length that would normally be imposed due to guide or instrument
492
limitations. There is still an upper limit of around 500 patches or
493
2Meters though. Note that if you generate a strip larger than the
494
instrument can cope with, it may be unable to read the strip.<br>
496
<a name="L"></a> The <b>-L</b> flag suppresses the left margin that is
497
added for instruments that have a paper holder that has a clip to hold
498
the chart in place, while it is being read. (Currently this is only the
501
<a name="p"></a> The <b>-p</b> parameter specifies the paper size. The
502
size can either be one of the default sizes, <a name="pp"></a>or can
503
be specified in millimeters. limitations of the instrument may limit
504
the maximum number of patches in a strip. For SpectroScan, a size of
505
A4 or Letter (or smaller) should be used. Useful combinations of
506
number of patches and paper size are listed <a href="targen.html#Table">here</a>.
507
The printed parts of the chart will be the size of paper minus the page
508
margin. A TIFF chart will be the size of the paper minus the margin, so
509
that it can be placed on a page that size without cropping or
510
inadvertent scaling.<br>
512
<a name="p1"></a><i>basename</i> is the base file name of the <a
513
href="File_Formats.html#.ti1">.ti1</a> file that contains the device
514
values to be put on the test chart. <b>printtarg</b> will output a <i>basename.ps</i>
515
or one or more <i>basename_NN.eps</i> or <i>basename_NN.tif </i>files
517
printed on the devices, as well as a <i>basename.ti2</i> file that
518
contains both the device test point values, and the location of the
519
corresponding patch on the test chart. If the <b>-s</b> or <b>-S</b>
520
flag was specified, then one or more <i>basename_NN.cht</i>
89
(.cht) file</span><br style="font-family: monospace;">
90
<span style="font-family: monospace;"> </span><a
91
style="font-family: monospace;" href="#S">-S</a><span
92
style="font-family: monospace;">
98
generate wide orientation strip.</span><br style="font-family:
100
<span style="font-family: monospace;"> </span><a
101
style="font-family: monospace;" href="#c">-c</a><span
102
style="font-family: monospace;">
105
spacers</span><br style="font-family: monospace;">
106
<span style="font-family: monospace;"> </span><a
107
style="font-family: monospace;" href="#b">-b</a><span
108
style="font-family: monospace;">
109
112
spacers</span><br style="font-family: monospace;">
113
<span style="font-family: monospace;"> </span><a
114
style="font-family: monospace;" href="#n">-n</a><span
115
style="font-family: monospace;">
118
spacers</span><br style="font-family: monospace;">
119
<span style="font-family: monospace;"> </span><a
120
style="font-family: monospace;" href="#f">-f</a><span
121
style="font-family: monospace;">
126
fallback</span><br style="font-family: monospace;">
127
<span style="font-family: monospace;"> </span><a
128
style="font-family: monospace;" href="#w">-w g|r|s|n</a><span
129
style="font-family: monospace;">
130
White colorspace encoding DeviceGray (def), DeviceRGB,
132
DeviceN</span><br style="font-family: monospace;">
133
<span style="font-family: monospace;"> </span><a
134
style="font-family: monospace;" href="#k">-k g|c|s|n</a><span
135
style="font-family: monospace;">
137
colorspace encoding DeviceGray (def), DeviceCMYK, Separation or
138
DeviceN</span><br style="font-family: monospace;">
139
<span style="font-family: monospace;"> </span><a
140
style="font-family: monospace;" href="#e">-e</a><span
141
style="font-family: monospace;">
146
<a href="#t">-t [res]</a>
152
file, optional res DPI (default 200)<br>
153
<a href="#T">-T [res]</a>
159
file, optional res DPI (default 200)<br>
160
</span></small><small><span style="font-family: monospace;"> <a
161
href="#C">-C</a>
165
compression</span></small><br>
166
<small><span style="font-family: monospace;"> <a href="#N">-N</a>
173
<a href="#D">-D</a>
174
Dither 8 bit TIFF values down from 16 bit<br>
175
<a href="#Q">-Q nbits</a>
182
</span></small><small style="font-family: monospace;"> <span
183
style="text-decoration: underline;">-</span><a href="#K">K
184
file.cal</a> Apply printer calibration
186
values and include in .ti2<br>
187
<a href="#I">-I file.cal</a> Include
188
calibration in .ti2 (but don't apply it)<br style="font-family:
190
</small><small><span style="font-family: monospace;"></span><span
191
style="font-family: monospace;"> </span><a
192
style="font-family: monospace;" href="#R">-R rsnum</a><span
193
style="font-family: monospace;">
198
number</span><br style="font-family: monospace;">
199
<span style="font-family: monospace;"> </span><a
200
style="font-family: monospace;" href="#x">-x pattern</a><span
201
style="font-family: monospace;">
204
strip indexing pattern (Default = "A-Z, A-Z")</span><br
205
style="font-family: monospace;">
206
<span style="font-family: monospace;"> </span><a
207
style="font-family: monospace;" href="#y">-y pattern</a><span
208
style="font-family: monospace;">
211
patch indexing pattern (Default = "0-9,@-9,@-9;1-999")</span><br
212
style="font-family: monospace;">
213
<span style="font-family: monospace;"> </span><a
214
style="font-family: monospace;" href="#m">-m margin</a><span
215
style="font-family: monospace;">
218
mm (default 6.0 mm)<br>
219
</span></small><small><span style="font-family: monospace;"> </span><a
220
style="font-family: monospace;" href="#M">-M margin</a><span
221
style="font-family: monospace;">
222
</span></small><small><span style="font-family: monospace;">Set a
223
page margin in mm and include it
224
in TIFF</span><span style="font-family: monospace;"></span></small><br>
225
<small><span style="font-family: monospace;"> <a href="#P">-P</a>
226
230
length</span></small><br>
231
<small><span style="font-family: monospace;"> <a href="#L">-L</a>
237
border<br style="font-family: monospace;">
238
</span><span style="font-family: monospace;"> </span><a
239
style="font-family: monospace;" href="#p">-p size</a><span
240
style="font-family: monospace;">
244
from:</span><br style="font-family: monospace;">
245
<span style="font-family: monospace;"></span></small><small><span
246
style="font-family: monospace;">
247
248
A4
249
[210.0 x 297.0 mm]<br>
250
251
A4R
252
[297.0 x 210.0 mm]<br>
254
255
A3
256
[297.0 x 420.0 mm] (default)<br>
257
258
259
A2
260
[420.0 x 594.0 mm]<br>
261
262
263
Letter [215.9 x 279.4 mm]<br>
264
265
LetterR [279.4 x
267
269
Legal [215.9 x 355.6
271
273
4x6 [101.6 x 152.4
275
276
11x17
277
[279.4 x 431.8 mm]<br style="font-family: monospace;">
278
</span><span style="font-family: monospace;"> </span><a
279
style="font-family: monospace;" href="#pp">-p WWWxHHH</a><span
280
style="font-family: monospace;">
284
</span></small><small style="font-family: monospace;"></small><br
285
style="font-family: monospace;">
286
<small><span style="font-family: monospace;"></span>
287
<span style="font-family: monospace;"></span><a
288
style="font-family: monospace;" href="#p1"><i>basename</i></a><span
289
style="font-family: monospace;">
293
input(</span><a style="font-family: monospace;"
294
href="File_Formats.html#.ti1">.ti1</a><span style="font-family:
295
monospace;">), output(</span><a style="font-family: monospace;"
296
href="File_Formats.html#.ti2">.ti2</a><span style="font-family:
297
monospace;">) and output(.ps/.eps/.tif)</span></small><br>
298
<h3>Usage Details and Discussion</h3>
299
<b> printtarg</b> is used to generate a PostScript or TIFF print
302
device test values in a .ti1 file. It output both a
304
file, and a .ti2 file containing the device test values together
306
the layout information needed to identify the patch location. This
307
module can also generate the image recognition templates needed to
309
the print targets in using a scanner.<br>
311
<a name="v"></a> The <b>-v</b> flag turns on verbose mode. Prints
312
information about how many patches there are in a row, how many
314
in a set, and how many pages will be generated. Good for
316
out what the magic number of patches should be for a particular page
319
<a name="i"></a> The <b>-i</b> parameter should be used to tell
320
printtarg which instrument it should lay the patches out for. Each
322
slightly different requirement, and will lead to a different number
325
ending up on a particular page size. For a generic type of chart,
326
try <span style="font-weight: bold;">SS</span>.<br>
328
<a name="a"></a><a name="A"></a> <span style="font-weight: bold;">-a,
330
</span>Normally, <b>printtarg</b> prints test patches that
331
are the minimum size that can be reliably and accurately read by the
332
instrument. For some media, it might be desirable to use test
333
patches that are larger than this minimum (e.g. if the media has
335
registration, gets physically distorted in the print production
336
process, or if it has a coarse screen, and there are few samples per
337
patch), and the <span style="font-weight: bold;">-a</span> flag
339
be given an argument greater than 1.0 to increase the patch length,
340
patch width, and spacer size between patches, if it is appropriate
342
the type of instrument. A
343
value of 1.5 would make the patch 50% larger for instance. For the
344
strip reading instruments the patch is made longer, the strip
346
remaining the same, while for XY scanning instruments, both the
348
and height will be increased. If a value less than 1.0 is given as
350
argument, then the patches will be made smaller. For instance, using
351
the SpectroScan instrument it is possible to reduce the test patches
353
6mm rather than the default 7mm by supplying an argument of 0.857.
355
that this make lining up of the scan head very critical, and
357
the amount of bleed through from adjacent squares. For an instrument
358
that needs color spacers between patches, <span style="font-weight:
359
bold;">-a scale</span> also scales the spacer
360
length. For some situations, this may be insufficient, and the <span
361
style="font-weight: bold;"> -A scale</span> option
362
can be used to additionally scale the spacer length.<br>
363
Note that the for the <span style="font-weight: bold;">DTP20</span>
364
only <span style="font-weight: bold;">-a </span>values of 1.0,
366
1.54, 1.92, 2.0 and that
367
the patch width will be made no smaller than its length.<br>
369
<a name="h"></a> Normally, <b>printtarg</b> creates a regular grid
371
test patches, but for instruments that support arbitrary X, Y
372
addressing (such as the SpectroScan). For the <span
373
style="font-weight: bold;">SpectroScan</span> it can also create a
375
regular hexagonal patches, allowing more patches to be fitted into a
376
single sheet if the <span style="font-weight: bold;">-h</span> flag
377
is used. For the <span style="font-weight: bold;">ColorMunki</span>
378
instrument, <span style="font-weight: bold;">-h</span> doubles the
379
normal number of patches is printed by halving the row width. The
380
patches are also staggered to improve the detection of a poor scan.<br>
382
<a name="r"></a> Normally, <b>printtarg</b> randomizes the patch
383
locations, which helps strip reading instruments detect patch
384
boundaries and the direction the strip was read in, as well as being
385
able to detect incorrect strips being
386
fed into strip reading instruments, and also assists in randomizing
388
systematic printing errors introduced into the test chart due to
390
engine unevenness, inkjet banding, or printing press ink key
392
etc. The <b>-r</b> flag turns this off, and lays the test squares
394
in the order the values appear in, in the .ti1 file. Note that if
396
turn this off you probably want to <a href="chartread.html#B">disable
397
bi-directional</a> strip reading in instruments such as the i1pro.<br>
399
<a name="s"></a> The <b>-s</b> flag does two things. One is that it
400
causes printtarg to output a chart recognition file (<a
401
href="File_Formats.html#.cht">.cht</a>) so that <a
403
scanin</a> can recognize the chart, and convert rasterized patches
405
patch values, and the second is that is expands the size of the
408
of patches by 50%, to help make sure that each sheet can be oriented
409
correctly by <a href="scanin.html"> scanin</a>. <a name="S"></a>If
412
rather than <b>-s</b>, then the recognition chart will be created,
415
leading row will be the same size as all the other rows.<br>
417
<a name="c"></a> For strip reading instruments, the contrast with
419
spacers is important in ensuring that a reading will be successful.
420
Normally <span style="font-weight: bold;">printtarg</span> ensures
421
this by printing optimally contrasting colored spacers between each
422
measurement patch. The <b>-c</b> flag is therefore the default
423
behaviour. <a name="b"></a>If the <b>-b</b> flag is used, then
424
contrasting neutral colored
425
spacers will be used, but these generally work less reliably than
427
spacers. <a name="n"></a>The <b>-n</b> flag will cause spacers to
430
which may still work with smaller numbers of test values when the
432
selection is randomized, but won't work successfully when a large
434
of test points is being used (>200), or when the patches are not
438
<a name="f"></a><b>-f</b>:
439
When creating a test chart for more than CMYK inks, a PostScript
441
normally contains color settings that use the PostScript level 3
443
N" color specifications. Such color specifications have a "fallback"
445
for PostScript interpreters that don't handle Device N
448
fallback colors are normally set to a grayscale estimate of the
451
so that it is possible to tell if the PostScript interpreter is not
453
the Device N values correctly. <a name="f"></a>The <b>-f</b> flag,
455
the fallback color to be a color estimate of the Device N test patch
457
which is useful for diagnostic purposes.<br>
459
<a name="e"></a> The <b>-e</b> flag gives EPS output, rather than
460
PostScript, allowing the charts to be included in other
462
Because EPS disallows the showpage command, multiple EPS files will
463
result for a multi-page test chart, each one having a two digit
465
sequence in it's name, so if the input file name is <span
466
style="font-weight: bold;">chart</span>, then file <span
467
style="font-weight: bold;">chart.ti1</span> will be read, and file
468
<span style="font-weight: bold;">chart.ti2</span> written, together
469
with <span style="font-weight: bold;">chart.eps</span> if there is
471
or <span style="font-weight: bold;">chart_01.eps</span>, <span
472
style="font-weight: bold;">chart_02.eps</span>, etc. if there is
476
<a name="t"></a><a name="T"></a><span style="font-weight: bold;">-t
477
[res], -T [res]</span> The <b>-t</b> flag gives TIFF raster
480
PostScript, allowing the charts to be printed to systems that do not
481
accept PostScript input. Because few systems understand multi-page
483
files, multiple TIFF files will
484
result for a multi-page test chart, each one having a two digit
486
sequence in it's name, so if the input file name is <span
487
style="font-weight: bold;">chart</span>, then file <span
488
style="font-weight: bold;">chart.ti1</span> will be read, and file
489
<span style="font-weight: bold;">chart.ti2</span> written, together
490
with <span style="font-weight: bold;">chart.eps</span> if there is
492
or <span style="font-weight: bold;">chart_01.tif</span>, <span
493
style="font-weight: bold;">chart_02.tif</span>, etc. if there is
495
than one page. By default the resolution of the chart will be 100
497
Per Inch (DPI), but this can be changed by providing an optional DPI
498
argument after the <span style="font-weight: bold;">-t</span> or <span
499
style="font-weight: bold;">-T</span> flag. If the <span
500
style="font-weight: bold;">-t</span> flag is used, than an 8 bit
502
component TIFF file will be created. If the <span
503
style="font-weight: bold;">-T</span> flag is used, then a 16 bit
505
component TIFF file will be created.<br>
507
<a name="C"></a><span style="font-weight: bold;">-C:</span> Normally
508
the TIFF files created will be compressed using LZW compression to
510
space. Some systems may not support this compression, so it can be
511
disabled by using the <span style="font-weight: bold;">-C</span>
514
<a name="N"></a><span style="font-weight: bold;">-N:</span> When
515
creating TIFF files with more than 4 colorants, the normal Separated
516
mode is used. Some systems don't cope well with extra colorants
517
presented in this manner, and the <span style="font-weight: bold;">-N</span>
518
flag causes all the channels greater than 4 to be labelled as
520
channels, which may be more palatable.<br>
522
<a name="D"></a><span style="font-weight: bold;">-D:</span> When
523
creating TIFF files with 8 bit output, dither the values to give
524
effective 16 bit precision. Note this is applied after any
525
quantization of the test values (see <a href="#Q">-Q</a>). Note
526
that this might interfere (i.e. give alias/moire patterns) in
527
printed output if the printer uses screening that happens to clash.
528
Note also that dithering is effectively linearly interpolating
529
between the 8 bit values using spatial averaging, and that therefore
530
the device response may also be a linear interpolation between its 8
531
bit output values, adding no effective extra precision to the device
534
<a name="Q"></a><span style="font-weight: bold;">-Q:</span> Normally
535
the target device values are floating point numbers that may get
536
rounded and quantized in the process of printing them or reproducing
537
them on the printing or display device. If some of this quantization
538
can be accounted for, it may improve the accuracy of the resulting
539
profile, and the <span style="font-weight: bold;">Q</span>
541
allows this quantization to be specified. The parameter is the
543
of binary digits (bits) that the device values should be quantized
545
In many systems the right value would be 8 bits. Note that if 8 bit
546
TIFF<span style="font-weight: bold;"></span> output is selected (<span
547
style="font-weight: bold;">-t</span>) without dithering (no <span
548
style="font-weight: bold;">-D) </span>that the values will by
550
be quantized to 8 bits, and that if 16 bit TIFF<span
551
style="font-weight: bold;"></span> output is selected (<span
552
style="font-weight: bold;">-T</span>) or 8 bit TIFF with dithering
553
(<span style="font-weight: bold;">-D) </span>that the values will
555
be quantized to 16 bits.<br>
557
<a name="K"></a> The <b>-K file.cal</b> parameter specifies a
559
calibration file created by <a href="printcal.html">printcal</a>,
561
the supplied calibration curves will be applied to the test patch
562
values. This allows profiling of a printing system that doesn't
563
natively support calibration. The calibration curves will also be
565
the resulting .ti2 file, so that they can be passed through to .ti3
566
file and ICC profile, to allow accurate computation of ink limits.<br>
568
<a name="I"></a> The <b>-I file.cal</b> parameter specifies a
570
calibration file created by <a href="printcal.html">printcal</a>,
571
and the calibration curves will be
572
included in the included in
573
the resulting .ti2 file, so that they can be passed through to .ti3
575
and ICC profile, to allow accurate computation of ink limits.
576
The calibration <span style="font-weight: bold;">is not applied</span>
577
to the test patch values, but is assumed to be applied somewhere
579
in the printing workflow when printing the profile test chart.<br>
581
<a name="R"></a> The <b>-R</b> parameter allows setting the random
582
layout seed. Normally the seed is chosen at random, but sometimes it
584
useful to be able to generate a chart with the same layout, so a
585
specific seed can be specified this way. The seed (ID) used to
588
chart is recorded in the
589
.ti2 file, and is also in the label printed on the right hand side
593
<a name="x"></a> The <b>-x</b> parameter allows specifying the
594
labelling sequence used for strips (e.g. the X axis of the chart).
596
default this will be a character sequence A, B, C .. Z. AA, AB, AC
598
ZZ, but this can be changed by specifying an alternate labelling
599
sequence pattern. The pattern specifies the labelling sequence as
600
follows: First comes the definition of the symbols for each digit
601
location, least significant to most significant, each digit
603
by the ',' character. Note that space is a
604
valid character. The number of
605
definitions declares the maximum number of digits. For example, for
607
digit numerical sequence: "0123456789, 123456789" would define
608
0..99 with the most significant digit suppressed when it is 0
611
space rather than 0). Ranges
612
can be used for brevity: "0-9, 1-9". As a special case, the '@'
613
character can be used to instead of '0' to indicate suppression of
615
leading zero: "0-9,@-9". Leading ' ' characters in the resulting
616
generated sequence are
617
omitted. Optionally following this and delimited by a ';'
618
character, are the definitions of valid segments of the index
620
For instance, to define the index range to be 1..19, 30..39 one
622
use the pattern "0-9, 1-9;1-19,30-39". Of course most of the time an
623
alphabetic sequence will be wanted, to distinguish it from the
624
numerical sequence used to number the patches in a strip. For a
625
sequence A, B, C .. AA, AB, AC etc. (the default used in Argyll),
627
following patter would be used: "A-Z, A-Z". For a some ECI2002R
629
that skip columns Y and Z, and use a leading numeric digits for
630
addressing strips over 26, the following might be used: "A-Z,
633
<a name="y"></a> The <b>-y</b> parameter allows specifying the
634
labelling sequence used for patches (e.g. the Y axis of the chart).
636
default this will be a number sequence 1, 2, ..10, 11, ... 999, but
637
this can be changed by specifying an alternate labelling
638
sequence pattern. See the above description for the labelling
642
<span style="font-weight: bold;">NOTE</span> that the pattern chosen
643
for the X and Y axes of the chart must be distinguishable, e.g. if
645
are both numbers or both letters then reading the chart will fail.<br>
647
<a name="w"></a> The <b>-w</b> parameter changes how a white
648
colorspace test chart (ie. Additive Grey monochrome) will be
649
represented in the Postscript output.
650
The default is to use the DeviceGray representation (<span
651
style="font-weight: bold;">-wg</span>), but Device RGB can also be
652
used, where the R, G &B values are all set to the same value (<span
653
style="font-weight: bold;">-wr</span>), a <span
654
style="font-weight: bold;">White</span> separation color can be
655
specified (<span style="font-weight: bold;">-ws</span>), or a
656
DeviceN <span style="font-weight: bold;">White</span> color can be
657
used (<span style="font-weight: bold;">-wn</span>).<br>
659
<a name="k"></a> The <b>-k</b> parameter changes how a black
660
colorspace test chart (ie. Subtractive
661
Grey monochrome ) will be represented in the Postscript output. The
662
default is to use the
663
DeviceGray representation (<span style="font-weight: bold;">-kg</span>),
669
be used, where the CMY values are zero, and
670
just the K channel is used (<span style="font-weight: bold;">-kc</span>),
672
<span style="font-weight: bold;">Black</span> separation color can
673
be specified (<span style="font-weight: bold;">-ks</span>), or a
674
DeviceN <span style="font-weight: bold;">Black</span> color can be
675
used (<span style="font-weight: bold;">-kn</span>).<br>
677
<a name="m"></a> The <b>-m</b> parameter sets the page margin for
679
sides. If the printer has print margins larger than the default
681
by <span style="font-weight: bold;">printtarg,</span> then critical
682
parts of the test chart may be cropped or scaled, and not printed
683
properly.<span style="font-weight: bold;"></span>
684
Increasing the margin from the default of 6 mm to 10 or 15 mm, may
686
this problem. (Note that
687
the number of patches per page may be reduced as a consequence.)
688
Decreasing the margin below 6 mm may be possible for printers that
690
smaller or no margins, increasing the number of patches possible on
691
each page. A TIFF chart raster will be the size of the paper minus
695
can be placed on a page that size without cropping or inadvertent
698
<a name="M"></a> The <b>-M</b> parameter sets the page margin for
700
sides the same as <span style="font-weight: bold;"><span
701
style="font-weight: bold;">-m</span></span>, but for a TIFF
703
margin will be <span style="font-weight: bold;">included</span> in
706
the TIFF will have to be printed right to the edge of the
708
or on paper larger than the raster size. (Having the raster be the
710
page size may be useful in certain situations.)<br>
713
<a name="P"></a> The <b>-P</b> flag disables any normal limiting of
714
strip length that would normally be imposed due to guide or
716
limitations. There is still an upper limit of around 500 patches or
717
2Meters though. Note that if you generate a strip larger than the
718
instrument can cope with, it may be unable to read the strip.<br>
720
<a name="L"></a> The <b>-L</b> flag suppresses the left margin that
722
added for instruments that have a paper holder that has a clip to
724
the chart in place, while it is being read. (Currently this is only
728
<a name="p"></a> The <b>-p</b> parameter specifies the paper size.
730
size can either be one of the default sizes, <a name="pp"></a>or
732
be specified in millimeters. Limitations of the instrument may limit
733
the maximum number of patches in a strip. For SpectroScan, a size of
734
A4 or Letter (or smaller) should be used. Useful combinations
736
number of patches and paper size are listed <a
737
href="targen.html#Table">here</a>.
742
the chart will be the size of paper minus the page
743
margin. A TIFF chart will be the size of the paper minus the margin,
745
that it can be placed on a page that size without cropping or
746
inadvertent scaling, but also see the <span style="font-weight:
750
<a name="p1"></a><i>basename</i> is the base file name of the <a
751
href="File_Formats.html#.ti1">.ti1</a> file that contains the
753
values to be put on the test chart. <b>printtarg</b> will output a
755
or one or more <i>basename_NN.eps</i> or <i>basename_NN.tif </i>files
522
will also be generated.<br>
524
<a href="http://www.ghostgum.com.au/">GSview</a> or <a
525
href="http://www.cs.wisc.edu/%7Eghost/gv/index.htm">GhostView</a> are
526
good programs to use to check what the PostScript or EPS file will look
528
without actually printing it out. Alternatively, use the TIFF raster
529
output for non-PostScript printers.<br>
762
the devices, as well as a <i>basename.ti2</i> file that
763
contains both the device test point values, and the location of the
764
corresponding patch on the test chart. If the <b>-s</b> or <b>-S</b>
765
flag was specified, then one or more <i>basename_NN.cht</i>
767
will also be generated.<br>
769
<a href="http://www.ghostgum.com.au/">GSview</a> or <a
770
href="http://www.cs.wisc.edu/%7Eghost/gv/index.htm">GhostView</a>
772
good programs to use to check what the PostScript or EPS file will
775
without actually printing it out. Alternatively, use the TIFF raster
776
output for non-PostScript printers.<br>
added
removed
doc/printtarg.html
