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
|
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
</head>
<body>
<h1><a name="Introduction"></a>Introduction<a href="#Introduction"
class="section_anchor"></a></h1>
<p>This document contains information needed to run the command line user
interface contained in the package. Note that this software doesn't target end
users directly, but rather developers of user interfaces or braille systems.
The functionality in the user interface does not demonstrate the full
capability of the package. </p>
<h1><a name="First_Run"></a>First Run<a href="#First_Run"
class="section_anchor"></a></h1>
<p>To run the user interface, download and extract the latest release. If you
do not have Java installed on your machine, you have to download and install
that as well. </p>
<p>On the command line, navigate to the extracted folder and type: <tt>java
-jar brailleUtils-ui-1.1.0.jar</tt>. Press enter. </p>
<p>This will bring up a list of applications (or features): </p>
<ul>
<li>emboss</li>
<li>text2pef </li>
<li>pef2text </li>
<li>validate </li>
<li>split </li>
<li>merge </li>
<li>generate </li>
</ul>
<p>These are explained in detail below. To start one of them, append their name
as the first argument, for example: <tt>java -jar brailleUtils-ui-1.1.0.jar
emboss</tt> </p>
<h1><a name="Emboss"></a>Emboss<a href="#Emboss"
class="section_anchor"></a></h1>
<p>Send a PEF-file to an embosser for embossing. </p>
<p>One argument is required, and can be one of the following: </p>
<ul>
<li>path to a file </li>
<li><tt>-clear</tt> </li>
<li><tt>-setup</tt> </li>
</ul>
<p>Upon the first run, the application will ask the user for the required
setup: </p>
<ul>
<li>device </li>
<li>embosser model </li>
<li>embosser table (if applicable) </li>
<li>paper size </li>
</ul>
<p>The file will be sent directly to the embosser on subsequent runs. To change
settings, use either <tt>-setup</tt> or <tt>-clear</tt>. </p>
<h2><a name="Setup"></a>Setup<a href="#Setup" class="section_anchor"></a></h2>
<p>Setup will ask all the user to verify all settings. </p>
<h2><a name="Clear"></a>Clear<a href="#Clear" class="section_anchor"></a></h2>
<p>Clear will delete the current settings. The next time the application is
started, it runs as on the first run. </p>
<h2><a name="Device"></a>Device<a href="#Device"
class="section_anchor"></a></h2>
<p>The device is the address where the embosser can be contacted. In most cases
this should be intuitive. If your device does not show up, make sure that the
embosser is turned on. </p>
<h2><a name="Embosser_Model"></a>Embosser Model<a href="#Embosser_Model"
class="section_anchor"></a></h2>
<p>Note that the same embosser model may communicate differently depending on
firmware or hardware version. Make sure that the embosser version is correct.
</p>
<h2><a name="Embosser_Table"></a>Embosser Table<a href="#Embosser_Table"
class="section_anchor"></a></h2>
<p>Some embossers require that a table is chosen by the user for the purpose of
communication. Make sure that the table chosen in the user interface matches
the value expected by the embosser. </p>
<h2><a name="Paper_Size"></a>Paper Size<a href="#Paper_Size"
class="section_anchor"></a></h2>
<p>Verify that the paper in the embosser matches the value in the user
interface. Some embossers uses rolls of paper. In this case, select a paper
size that matches the intended paper size once cut. </p>
<h1><a name="Text_to_PEF"></a>Text to PEF<a href="#Text_to_PEF"
class="section_anchor"></a></h1>
<p>Convert a text braille file into a PEF-file. </p>
<p>Two arguments are required <i>path to input file</i> and <i>path to output
file</i>. </p>
<p>The input file should be a "braille ready" text file, i.e. broken in rows an
pages (using the form feed character), and using one unique character to
represent each braille pattern. </p>
<p>Optional arguments include: </p>
<ul>
<li>mode </li>
<li>identifier </li>
<li>date </li>
<li>author </li>
<li>title </li>
<li>language </li>
<li>duplex </li>
</ul>
<p>The options <tt>identifier</tt>, <tt>date</tt>, <tt>author</tt>,
<tt>title</tt> and <tt>language</tt> all involve setting the meta data of the
resulting file. It will not affect the contents of the file in any way. </p>
<h2><a name="Mode"></a>Mode<a href="#Mode" class="section_anchor"></a></h2>
<p>Choose a table to use when converting. Note that, if a character is
encountered in the file that isn't in the selected table, an error will occur.
The default mode is to attempt to detect. If this fail, choose between the
tables suggested in the detector failure message. </p>
<h2><a name="Duplex"></a>Duplex<a href="#Duplex"
class="section_anchor"></a></h2>
<p>Set the duplex property of the resulting file. </p>
<h1><a name="PEF_to_Text"></a>PEF to Text<a href="#PEF_to_Text"
class="section_anchor"></a></h1>
<p>Convert a PEF-file document into a text braille file. </p>
<p>Two arguments are required <i>path to input file</i> and <i>path to output
file</i>. </p>
<p>Optional arguments include: </p>
<ul>
<li>range </li>
<li>table </li>
<li>breaks </li>
<li>fallback </li>
<li>replacement </li>
</ul>
<h2><a name="Range"></a>Range<a href="#Range" class="section_anchor"></a></h2>
<p>Output a range of pages. </p>
<h2><a name="Table"></a>Table<a href="#Table" class="section_anchor"></a></h2>
<p>Set the table (character mapping) to use. </p>
<h2><a name="Breaks"></a>Breaks<a href="#Breaks"
class="section_anchor"></a></h2>
<p>Set the line break style. Most braille applications use DOS line breaks. </p>
<h2><a name="Fallback"></a>Fallback<a href="#Fallback"
class="section_anchor"></a></h2>
<p>Set the action to use if an eight dot pattern is encountered and the current
table does not support eight dot: </p>
<ul>
<li>mask </li>
<li>replace </li>
<li>remove </li>
</ul>
<h2><a name="Replacement"></a>Replacement<a href="#Replacement"
class="section_anchor"></a></h2>
<p>Set the replacement character to use if an eight dot pattern is encountered
and fallback is set to "replace". </p>
<h1><a name="Validate_a_PEF-file"></a>Validate a PEF-file<a
href="#Validate_a_PEF-file" class="section_anchor"></a></h1>
<p>Validate a PEF-file. </p>
<p>One argument is required: <i>path to input file</i> </p>
<p>Optional arguments include: </p>
<ul>
<li>mode </li>
</ul>
<h2><a name="Mode"></a>Mode<a href="#Mode" class="section_anchor"></a></h2>
<p>Set the validation mode: </p>
<ul>
<li>full </li>
<li>light </li>
</ul>
<h1><a name="Split_a_PEF-file"></a>Split a PEF-file<a href="#Split_a_PEF-file"
class="section_anchor"></a></h1>
<p>Split a PEF file into several files, one file per volume. </p>
<p>The purpose is to facilitating the use of PEF files with braille editors
that do not support multi volume files. </p>
<p>Two arguments are required: <i>path to input file</i> and <i>path to output
folder</i>. </p>
<h1><a name="Merge_several_PEF-files"></a>Merge several PEF-files<a
href="#Merge_several_PEF-files" class="section_anchor"></a></h1>
<p>Merge several PEF files into one. </p>
<p>The purpose is to facilitating the use of PEF-files with braille editors
that do not support multi volume files. </p>
<p>Three arguments are required: <i>path to input folder</i>, <i>path to output
file</i> and identifier. </p>
<p>Optional arguments include: </p>
<ul>
<li>sort </li>
</ul>
<h2><a name="Sort"></a>Sort<a href="#Sort" class="section_anchor"></a></h2>
<p>Set the sorting method to use when ordering files in the input folder. </p>
<h1><a name="Generate_a_PEF-file"></a>Generate a PEF-file<a
href="#Generate_a_PEF-file" class="section_anchor"></a></h1>
<p>Generate a random PEF-file for testing purposes. </p>
<p>One argument is required: <i>path to output file</i> </p>
<p>Optional arguments include: </p>
<ul>
<li>volumes </li>
<li>pages </li>
<li>eightdot </li>
<li>rows </li>
<li>cols </li>
<li>duplex </li>
</ul>
<h2><a name="Volumes"></a>Volumes<a href="#Volumes"
class="section_anchor"></a></h2>
<p>Set the number of volumes to generate. </p>
<h2><a name="Pages"></a>Pages<a href="#Pages" class="section_anchor"></a></h2>
<p>Set the number of pages in each volume. </p>
<h2><a name="Eight_dot"></a>Eight dot<a href="#Eight_dot"
class="section_anchor"></a></h2>
<p>Set to true to include 8-dot patterns. </p>
<h2><a name="Rows"></a>Rows<a href="#Rows" class="section_anchor"></a></h2>
<p>Set the maximum numbers of rows on a page. </p>
<h2><a name="Cols"></a>Cols<a href="#Cols" class="section_anchor"></a></h2>
<p>Set the maximum number of characters on a row. </p>
<h2><a name="Duplex"></a>Duplex<a href="#Duplex"
class="section_anchor"></a></h2>
<p>Set the duplex property. </p>
<h1><a name="Plugins"></a>Plugins<a href="#Plugins"
class="section_anchor"></a></h1>
<p>Plugins can be added by creating a directory called <i>plugins</i> in the
software folder and placing the plugin (.jar) in that folder. </p>
</body>
</html>
|
