Hi Bert,
Thank you very much. I will look through the news file and see if there are
more obvious things to add to the documentation.
Bue
‘
Fra: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] På vegne af Bert Frees
Sendt: 9. november 2017 23:46
Til: liblouis-liblouisxml@xxxxxxxxxxxxx
Emne: [liblouis-liblouisxml] Re: Translation flags - anybody knows the details?
Finally, some more info can be found in NEWS:
* Noteworthy changes in release 1.5 (2009-01-21)
*** pass1Only mode bit
The new pass1Only mode bit will help developers of screen readers as
the cursor will stay where it is expected to.
* Noteworthy changes in release 3.1.0 (2017-03-06)
*** noUndefinedDots mode
(same description as below)
*** partialTrans mode
(same description as below)
2017-11-09 23:41 GMT+01:00 Bert Frees <bertfrees@xxxxxxxxx
<mailto:bertfrees@xxxxxxxxx> >:
Correction: partialTrans and noUndefinedDots were added in 2016, not 2014.
2017-11-09 23:38 GMT+01:00 Bert Frees <bertfrees@xxxxxxxxx
<mailto:bertfrees@xxxxxxxxx> >:
This is the information I could find:
There is this post on the mailing list that kind of explains some of the modes:
https://www.freelists.org/post/liblouis-liblouisxml/Draft-documentation-for-liblouisutdml-mode-configuration-setting
- noContractions: (not working) Do not use any contractions, even though a
table containing contractions is being used.
- comp8Dots: Unimplemented. May be replaced.
- pass1Only: Run only the main translation pass, even though correct, pass2,
pass3 and pass4 opcodes may be specified.
pass1Only was added by John in January 2009:
https://github.com/liblouis/liblouis/commit/2919b1e. See also the announcement ;
on the mailing list:
https://www.freelists.org/post/liblouis-liblouisxml/pass1Only-mode-bit-implemented.
I didn't find what exactly the purpose was, but it seems that NVDA is using it
because the outputPosition feature is broken for tables that use more than one
pass.
partialTrans was added by Jamie in October 2014:
https://github.com/liblouis/liblouis/commit/56bb717. The commit message says:
Add a partialTrans mode to specify that back-translation input should be
treated as an incomplete word.
If this mode is set, rules that apply only for complete words or at the end
of a word will not take effect. This is intended to be used when translating
input typed on a braille keyboard to provide a rough idea to the user of the
characters they are typing before the word is complete.
noUndefinedDots was also added by Jamie in October 2014: See
https://github.com/liblouis/liblouis/commit/6b0ab9c. The commit message says:
Add a noUndefinedDots mode to disable the output of dot numbers when
back-translating undefined patterns.
When backtranslating input from a braille keyboard cell by cell, it is
desirable to output characters as soon as they are produced. Similarly, when
backtranslating contracted braille, it is desirable to provide a "guess" to the
user of the characters they typed. To achieve this, liblouis needs to have the
ability to produce no text when indicators (which don't produce a character by
themselves) are not followed by another cell. This works already for indicators
liblouis knows about such as capital sign, number sign, etc., but it does not
work for indicators which are not (and cannot be) specifically defined as
indicators. For example, in UEB, dots 4 5 6 alone produces the text "\456/".
Setting the noUndefinedDots mode suppresses this dot number output.
See also issue https://github.com/liblouis/liblouis/issues/210.
2017-11-07 11:06 GMT+01:00 Bue Vester-Andersen <bue@xxxxxxxxxxxxxxxxxx
<mailto:bue@xxxxxxxxxxxxxxxxxx> >:
Hi guys,
I am updating parts of the documentation, and I was wondering about some of the
translation flags. Some of the flags are more or less documented under section
7.7 (lou_translate), but in 7.6, there is just a reference to the .h file,
which merely lists the flags without any explanation. Some of the mode flags
are currently undocumented. Can anybody help me with the following flags?
noContractions: Does this have the same effect as using the nocont opcode?
Comp8Dots: Obviously, it is something with 8 dots computer Braille, but how
does it work?
Pass1Only: It is clear what this flag does, but what is the purpose? Why was it
introduced? The flag will have no effect whatsoever on tables that only make
use of pass 1 opcodes, and with tables that do depend on multi-pass opcodes,
the flag will have a negative impact on the produced Braille. Is this flag for
debugging purposes?
noUndefinedDots: What does this flag do, and what is the purpose?
partialTrans: What does this flag do, and what is the purpose?
Hope someone can bring some light to this.
