[liblouis-liblouisxml] Re: SV: Multipass opcode suggestions.
- From: Dave Mielke <dave@xxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Tue, 17 Jan 2017 08:49:55 -0500
[quoted lines by Bue Vester-Andersen on 2017/01/17 at 14:24 +0100]
I think it makes perfect sense to have a context opcode also in the backward
direction. Back-translation can be very tricky, so, I think it will be of
use. Also, it gives a nice symmetry to the system.
I'll do it. I may wait till dm/simplify-passes has been merged (assuming that
that'll actually happen) in order to avoid merge conflicts, but it'll get done.
I assume you mean that multi-pass opcodes without direction implies noback,
Yes, of course! My fingers were a little ahead of my brain. :-) That's not the
first time that that's happened.
An alternative is to make an automatic search&replace in all tables, provided
that only the name of the opcode has changed. This has already been done in
other situations, e.g. when capsign changed to capsletter.
Yes, but that leaves us with what should an unqualified multipass opcode do?
Do you know how many back translations rely on them today?
--
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
Other related posts:
