Hi,
I agree with Dave. One example where the correct opcode is useful during
back-translation is words with accented letters. In many languages, foreign
letters with unusual accents are marked with a special accent mark. However,
since there is usually only one accent mark to choose from, it has to cover
many different accents with the same letter, which can be a problem during
back-translation. In these cases, the "correct" opcode can help improve
back-translation of words that use these accented letters.
The "correct" opcodes is a characters-to-characters opcode both ways, so it
should be possible to implement the test part in the same manner in both
forward and backward translation.
The same goes for pass2-3-4, which are dots-to-dots opcodes both ways.
The problem is the "context" opcode, which is characters-to-dots one way and
dots-to-characters the other way. So, it would have to work differently in
forward and backward translation. For back-translation, I would suggest
implementing the test part using the same implementation as for pass2-4.
Hope it makes sense.
Bue
-----Oprindelig meddelelse-----
Fra: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] På vegne af Dave Mielke
Sendt: 11. januar 2017 06:04
Til: liblouis-liblouisxml@xxxxxxxxxxxxx
Emne: [liblouis-liblouisxml] Corrections pass during back translation.
Someone asked if the corrections pass during back translation makes sense or
if it should be removed. My opinion is that it should be retained to deal
with cases where back translation gets it wrong.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of
God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
EMail: Dave@xxxxxxxxx | Canada K2A 1H7 | http://FamilyRadio.org/
For a description of the software, to download it and links to project pages
go to http://liblouis.org
For a description of the software, to download it and links to
project pages go to http://liblouis.org
