I would quarrel with the last point. You will want a way to have the end user
add a table if needed.
Greg
On Feb 15, 2019, at 3:57 AM, Jacques Menu <imj-219@xxxxxxxxxx> wrote:
Hello James, Greg and all,
Thanks for your answers!
IIUC :
- generating UTF-8 or UTF-16 text files is OK for checking the results
and publications;
- generating BRF files is needed to have the results read on a braille
bar or embossed;
- such BRF files contain one byte per cell, and those cells should be
in grade 2, i.e. using contractions;
- the particular grade-2-cell to byte correspondance is language
dependent.
So:
- liblouis is the library I should use to obtain grade 2 cells
seamlessly;
- my tool should have a ‘-language' option to select the corresponding
grade 2 table behind the scenes;
- thus the liblouis library and needed tables should be compiled and
bundled with the tool, without a way for the end user to use other tables
than the ones supplied.
Do I miss anything?
Thanks for your help!
JM
Le 11 févr. 2019 à 17:22, Greg Kearney <gkearney@xxxxxxxxx> a écrit :
You should keep in mind however that unless your tools install liblouis
itself it is very unlikely that your users will have liblouis and all it
parts already installed. This is why tools like BrailleBlaster and NVDA have
liblouis installed as part of application and are included in the
application bundle itself.
Compiling and installing liblouis is a task well beyond the skill set of
most users.
Greg
For a description of the software, to download it and links to
project pages go to http://liblouis.org
