[liblouis-liblouisxml] Re: correct opcode no longer recognized in version 3.1?
- From: Yuemei Sun <yuemei.sun@xxxxxxxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Mon, 8 May 2017 19:40:11 +0000
Hi, Dave,
Thank you for your quick response. I added noback before correct, and it
works!
Yuemei
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Dave Mielke
Sent: Monday, May 08, 2017 12:04 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: correct opcode no longer recognized in
version 3.1?
[quoted lines by Yuemei Sun on 2017/05/08 at 18:39 +0000]
Is the opcode “correct” still recognized in version 3.1.? I tried to
use “correct” opcode to ask liblouis to drop space before some
quotation marks (see below), but it lou_translationString() will not translate
when “correct”
is in the table. I did not have this problem with older versions of
liblouis (2.6.4).
correct "\s," ","
Starting in 3.1, it's necessary to prefix all multipass opcodes - correct being
one of those - with either nofor or noback. This is because the same multipass
opcode can't be used for both forward and backward translation. If your
"correct" is for forward translation then prefix it with "noback", and if it's
for back translation then prefix it with "nofor".
--
Dave Mielke | 2213 Fox Crescent |
http://Mielke.cc/
Phone: 1-613-726-0014 | Ottawa, Ontario |
http://Mielke.cc/bible/
EMail: Dave@xxxxxxxxx | Canada K2A 1H7 | The Bible is the very Word of God.
For a description of the software, to download it and links to
project pages go to
http://liblouis.org
��u� �*m���~�^������h�yhiحjwe�y,��k�7����z�(��m����&��謢�
Other related posts:
