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
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.3//EN">
<html><head><title>Pnmtojbig User Manual</title></head>
<body>
<h1>pnmtojbig</h1>
Updated: 28 July 2020
<br>
<a href="#index">Table Of Contents</a>
<h2>NAME</h2>
pnmtojbig - PNM to JBIG file converter
<h2 id="synopsis">SYNOPSIS</h2>
<b>pnmtojbig</b>
[<i>options</i>]
[<i>input-file</i> [<i>output-file</i>]]
<h2 id="description">DESCRIPTION</h2>
<p>This program is part of <a href="index.html">Netpbm</a>.
<p><b>pnmtojbig</b> reads a PBM or PGM image, compresses it, and
outputs the image as a JBIG bi-level image entity (BIE) file.
<p>JBIG is a highly effective lossless compression algorithm for
bi-level images (one bit per pixel), which is particularly suitable
for scanned document pages.
<p>A JBIG encoded image can be stored in several resolutions
(progressive mode). These resolution layers can be stored all in one
single BIE or they can be stored in several separate BIE files. All
resolution layers except the lowest one are stored merely as
differences to the next lower resolution layer, because this requires
less space than encoding the full image completely every time. Each
resolution layer has twice the number of horizontal and vertical
pixels than the next lower layer. JBIG files can also store several
bits per pixel as separate bitmap planes, and <b>pnmtojbig</b>
can read a PGM file and transform it into a multi-bitplane BIE.
<h2 id="options">OPTIONS</h2>
<p>In addition to the options common to all programs based on libnetpbm
(most notably <b>-quiet</b>, see <a href="index.html#commonoptions">
Common Options</a>), <b>pnmtojbig</b> recognizes the following
command line options:
<dl compact>
<dt><b>-q</b>
<dd>Encode the image in one single resolution layer (sequential
mode). This is usually the most efficient compression method. By
default, the number of resolution layers is chosen automatically such
that the lowest layer image is not larger than 640 × 480 pixels.
<dt><b>-x</b> <i>number</i>
<dd>Specify the maximal horizontal size of the lowest resolution
layer. The default is 640 pixels.
<dt><b>-y</b> <i>number</i>
<dd>Specify the maximal vertical size of the lowest resolution layer.
The default is 480 pixels.
<dt><b>-l</b> <i>number</i>
<dd>Select the lowest resolution layer that will be written to the
BIE. It is possible to store the various resolution layers of a JBIG
image in progressive mode into different BIEs. Options <b>-l</b> and
<b>-h</b> allow you to select the resolution-layer interval that will
appear in the created BIE. The lowest resolution layer has number 0
and this is also the default value. By default, <b>pnmtojbig</b>
writes all layers.
<dt><b>-h</b> <i>number</i>
<dd>Select the highest resolution layer that will be written to the
BIE. By default, <b>pnmtojbig</b> writes all layers. See also option
<b>-l</b>.
<dt><b>-b</b>
<dd>Use binary values instead of Gray code words in order to encode
pixel values in multiple bitplanes. This option has only an effect if
the input is a PGM file and if more than one bitplane is
produced. Note that the decoder has to make the same selection but
cannot determine from the BIE, whether Gray or binary code words were
used by the encoder.
<dt><b>-d</b> <i>number</i>
<dd>Specify the total number of differential resolution layers into
which the input image will be split in addition to the lowest layer.
Each additional layer reduces the size of layer 0 by 50 %. This
option overrides options <b>-x</b> and <b>-y</b>, which are usually a
more comfortable way of selecting the number of resolution layers.
<dt><b>-s</b> <i>number</i>
<dd>The JBIG algorithm splits each image into a number of horizontal
stripes. This option specifies that each stripe shall have
<i>number</i> lines in layer 0. The default value is selected so that
approximately 35 stripes will be used for the whole image.
<dt><b>-m</b> <i>number</i>
<dd>Select the maximum horizontal offset of the adaptive template pixel. The
JBIG encoder uses a number of neighbour pixels in order to get statistical a
priori knowledge of the probability, whether the next pixel will be black or
white. One single pixel out of this template of context neighbor pixels can
be moved around. Especially for dithered images it can be a significant
advantage to have one neighbor pixel which has a distance large enough to
cover the period of a dither function. By default, the adaptive template
pixel can be moved up to 8 pixels away. This encoder go up to 23 pixels,
however as decoders are only required to handle at least a distance of 16
pixels by the standard, no higher value than 16 for
<i>number</i> is recommended in order to maintain interoperability
with other JBIG implementations. The maximal vertical offset of the
adaptive template pixel is always zero.
<dt><b>-t</b> <i>number</i>
<dd>Encode only the specified number of most significant bit planes.
This option allows one to reduce the depth of an input PGM file if not all
bits per pixel are needed in the output.
<dt><b>-o</b> <i>number</i>
<dd>JBIG separates an image into several horizontal stripes,
resolution layers and planes, were each plane contains one bit per
pixel. One single stripe in one plane and layer is encoded as a data
unit called stripe data entity (SDE) inside the BIE. There are 12
different possible orders in which the SDEs can be stored inside the
BIE and <i>number</i> selects which one shall be used. The order of
the SDEs is only relevant for applications that want to decode a JBIG
file which has not yet completely arrived from e.g. a slow network
connection. For instance some applications prefer that the outermost
of the three loops (stripes, layers, planes) is over all layers so
that all data of the lowest resolution layer is transmitted first.
<p>The following values for <i>number</i> select these loop
arrangements for writing the SDEs (outermost loop first):
<dl>
<dt>0
<dd>planes, layers, stripes
<dt>2
<dd>layers, planes, stripes
<dt>3
<dd>layers, stripes, planes
<dt>4
<dd>stripes, planes, layers
<dt>5
<dd>planes, stripes, layers
<dt>6
<dd>stripes, layers, planes
</dl>
<p>All loops count starting with zero, however by adding 8 to the
above order code, the layer loop can be reversed so that it counts
down to zero and then higher resolution layers will be stored before
lower layers. Default order is 3 which writes at first all planes of
the first stripe and then completes layer 0 before continuing with the
next layer and so on.
<dt><b>-p</b> <i>number</i>
<dd>This option allows you to activate or deactivate various optional
algorithms defined in the JBIG standard. Just add the numbers of the
following options which you want to activate in order to get the
<i>number</i> value:
<dl>
<dt>4
<dd>deterministic prediction (DPON)
<dt>8
<dd>typical prediction (TPBON)
<dt>16
<dd>diff. layer typical prediction (TPDON)
<dt>64
<dd>layer 0 two-line template (LRLTWO)
</dl>
<p>Except for special applications (like communication with JBIG
subset implementations) and for debugging purposes you will normally
not want to change anything here. The default is 28, which provides
the best compression result.
<dt><b>-c</b>
<dd>The adaptive template pixel movement is determined as suggested in
annex C of the standard. By default the template change takes place
directly in the next line which is most effective. However a few
conformance test examples in the standard require the adaptive
template change to be delayed until the first line of the next stripe.
This option selects this special behavior, which is normally not
required except in order to pass some conformance test suite.
<dt><b>-v</b>
<dd>After <b>pnmtojbig</b> creates the BIE, it lists a few technical
details of the created file (verbose mode).
</dl>
<h2 id="formats">FORMATS</h2>
<p>Most of the format <b>pnmtojbig</b> creates is defined by the
JBIG standard.
<p>The standard, however, does not specify which values in the BIE mean
white and which mean black. It contains a recommendation that for a
single plane image zero mean background and one mean foreground, but
the Netpbm formats have no concept of foreground and background. And
the standard says nothing about values for multiple plane BIEs.
<p><b>pnmtojbig</b> follows Markus Kuhn's implementation of the
standard in the <b>pbmtojbg</b> program that comes with his
JBIG library: If the BIE is a single plane BIE, zero means
white and one means black. If it is a multiple plane BIE, zero means
black and the maximal value is white.
<h2 id="standards">STANDARDS</h2>
<p>This program implements the JBIG image coding algorithm as
specified in ISO/IEC 11544:1993 and ITU-T T.82(1993).
<h2 id="author">AUTHOR</h2>
<b>pnmtojbig</b> is based on the JBIG library by Markus Kuhn, part of
his <b>JBIG-KIT</b> package. The <b>pbmtojbg</b> program is part of
the <i>JBIG-KIT</i> package. The most recent version of that library
and tools set is freely available on the Internet from anonymous ftp
server <a
href="ftp://ftp.informatik.uni-erlangen.de">ftp.informatik.uni-erlangen.de</a>
in directory pub/doc/ISO/JBIG/.
<p><b>pnmtojbig</b> is part of the Netpbm package of graphics tools.
<h2 id="seealso">SEE ALSO</h2>
<b><a href="pnm.html">pnm</a></b>,
<b><a href="jbigtopnm.html">jbigtopnm</a></b>
<h2 id="license">LICENSE</h2>
<p>There was at one time concern about the need for patent licenses to
use <b>pnmtojbig</b>, but any relevant patents expired by 2012.
<hr>
<h2 id="index">Table Of Contents</h2>
<ul>
<li><a href="#synopsis">SYNOPSIS</a>
<li><a href="#description">DESCRIPTION</a>
<li><a href="#options">OPTIONS</a>
<li><a href="#formats">FORMATS</a>
<li><a href="#standards">STANDARDS</a>
<li><a href="#author">AUTHOR</a>
<li><a href="#seealso">SEE ALSO</a>
<li><a href="#license">LICENSE</a>
</ul>
</body>
</html>
|
