One more thing. You might notice that some of the words in the bad file looks the same as the translated word. That is because this is a text file. If you try one of the words that are in this file in lou_allround you will see that the words definetly are bad they have hex numbers in them. Ken From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Sunday, October 20, 2013 1:50 PM To: liblouis-liblouisxml@xxxxxxxxxxxxx Subject: [liblouis-liblouisxml] Re: en-us-g2.ctb back translation issues. Oh the format of the bad.txt file attached is <Word> <back translated word> <forward translated word> Ken From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx<mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry Sent: Sunday, October 20, 2013 1:47 PM To: liblouis-liblouisxml@xxxxxxxxxxxxx<mailto:liblouis-liblouisxml@xxxxxxxxxxxxx> Subject: [liblouis-liblouisxml] en-us-g2.ctb back translation issues. I wanted to see how well liblouis does on the Ubuntu dictionary found at /usr/share/dict/words I wrote the attached script to run lou_translate on all 99,000 + words. The first thing I found out is liblouis slows down which makes no since except maybe the shared library has some memory problems. I will e looking into that. With that said it also failed to forward translate and backward translate 650 words out of the 99,000+ words. I have attached the 650 words in a file called bad.txt and the script called back_trans.sh if anyone else wants to run it. This is only using en-us-g2.ctb maybe we should do the same thing with other tables to make sure everything is working correctly. Ken