[liblouis-liblouisxml] Re: SV: Translation problems with some tables

  • From: "Michael Whapples" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "mwhapples@xxxxxxx" for DMARC)
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Fri, 24 Jul 2015 09:30:43 +0100

As far as I know there is no definite way of determining if a table is good for back translation, I think it is try it and see how it works.

I think some of the main things for back translation in a table is adding certain rules to help with back translation. I think there is a noback opcode for instructing liblouis not to use a rule in back translation, I think there are other opcodes specifically for rules for back translation.

I am not over familiar with back translation stuff and would suggest looking at the documentation for details of these opcodes.

Michael Whapples

On 24/07/2015 01:27, Daniel Dalton wrote:

Hi Bue,
Thanks for the clarification.
Do you know how I can find out what tables don't yet support back translation? Or is it just a case of testing each one individually.
Can I assume that back translation should work for all computer Braille tables?

What is required to get the tables working with back translation? Is it just a matter of update the ctb files? How much effort is generally involved in implementing this and what's the best way to test it all works correctly?

Finally, do you know of any other projects that use liblouis for it's back translation service?

Thanks,
Daniel


On Fri, Jul 24, 2015 at 6:22 AM, Bue Vester-Andersen <bue@xxxxxxxxxxxxxxxxxx <mailto:bue@xxxxxxxxxxxxxxxxxx>> wrote:

Hi Daniel,

I think that many of the tables in liblouis have not been designed
with back-translation in mind. Probably, the reason is that they
were designed for use with a library service or in a Braille
embosser, so back-translation would not be a big issue. However, I
think it is something that we should take more seriously as
liblouis is getting more popular with both screen readers and
note-takers.

Currently, all the Danish tables have good back-translation. I am
going to do what I can over time to help improve back-translation
for other tables as well. However, I have quite a heap of projects
on my hands at the moment. So I can't make any specific promises.

Best regards Bue

*Fra:*liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
<mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx>
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
<mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx>] *På vegne af
*Daniel Dalton
*Sendt:* 23. juli 2015 15:59
*Til:* liblouis-liblouisxml@xxxxxxxxxxxxx
<mailto:liblouis-liblouisxml@xxxxxxxxxxxxx>
*Emne:* [liblouis-liblouisxml] Translation problems with some tables

Hello,

I'm writing an app that relies on loui for back translation. It
works fine with the English tables. However, having trouble with
Polish and Spanish. Firstly I do not use either of these codes, so
they are issues reported by users, but I can reproduce. They are
having trouble typing punctuation like . , ? !

For example in Polish if I do lou_translate from my console on
Linux forward translation a "." should be in Braille as ' or dot
3. If I then forward translate this ' it just returns '

In Polish when I back translate some letters like a b c through j
it would return the numbers 1 2 ... 9 and 0. I fixed this by
making the change of removing the include digits6Dots.uti and
replacing it with litdigits6Dots.uti. Not even sure if this is
correct.

Finally, when I programatically back translate with the java
wrapper I some times get back the dot number where something has
no corresponding translation. For instance if I pass dot 7 by its
own and it has no corresponding symbol in that braille table it'll
return "7". Will I just need to write my own logic to not show
this to my user?

Thanks in advance for any help with any of this.

Daniel



Other related posts: