Hy Jon, I not tryed yet with file2brl, but monday I trying. I have got a question:With context level opcodes or new script language with Liblouis supports possible doing this wrong characterreplacements only with backtranslated output?
I would like following safe rules designing if this is possible:If the backtranslated output containing 1 character any place and before the 1 character not have numbersign indicator, need replacing this character in the backtranslated output with \x00e9 character.
So, need executing this rule if the 1 number is not literal digitOf course, the 211 number need right presenting the backtranslated output text, because this situation the original braille output containing #baa braille text. Or, if the original braille translated output containing #a character, backtranslated output need presenting 1 number, not \x00e9 character.
If the backtranslated output containing " character and this character not a punctuation character, need replacing this character with \x00e1 character with any place. For example, if the backtranslated text containing "m or tam"s text, both two text need replacing with \x00e1m and tam\x00e1s the backtranslated text. In the hungarian Liblouis translate function produced braille output right the normal left quotation mark is (, and right quotation mark is ) characters.
In the hu-chardefs.cti file following rules defined: punctuation " 4 QUOTATION MARK punctuation ( 236 LEFT PARENTHESIS punctuation ) 356 RIGHT PARENTHESISTo use right before and after a text with left and right quotation marks (\x0022 character) in the generated braille output, in hu1.ctb file defined following rules:
prepunc " 236 postpunc " 356If I reading normal contracted braille support with Orca for example quotation mark characters containing sentences, I see absolute right results this situation.
Attila For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com