[liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Fri, 25 Oct 2013 17:44:36 +0000
That is the wrong way to look at this. I am sorry it will be a while before
something new is available if the stuff that is in service now does not work
then it still needs fixing.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John Gardner
Sent: Friday, October 25, 2013 11:11 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
I understand - I'm just looking forward now. I cannot contribute much of
anything to fixing the present liblouis, so my brain is just working on future
translators.
Be well.
John
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Friday, October 25, 2013 8:05 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
That could be done with a lexer but the point was to fix the tables that exist
not write a whole new parser. I thought liblouis would handle this.
I actually have a lexer that can pull all words out of a text file but again I
was just trying to fix table errors. The exceptions I sent as diff's will fix
the problems so this is fine for now.
ken
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John Gardner
Sent: Friday, October 25, 2013 10:59 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
Ken, my first action would be to have somebody build an efficient C routine for
looking up words in your file. I am told that this should be as fast as
applying rules. And it would do 99% of the translations on most documents.
John
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Friday, October 25, 2013 3:25 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
As I said in my last email I can put exceptions in for those two words but what
if there are more words that are not in my list of 99,000. I was just asking
if you wanted to fix the largesign opp code so that if the separation of the
words did not end up in words that are largesign for example if it didn't end
up in something like "the and" or something like that then it should not add a
space. For example if it ends up in "and antie" that obviously is not two
largsigns and should not be separated. That could be handled in the translator
and should be. I will add the two exceptions but I really think that should be
fixed in the translator.
Ken
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John J.
Boyer
Sent: Thursday, October 24, 2013 10:09 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: largesign opt code problem with en-us-g2.ctb
Try putting andante and standoff in the table with the always opcode.
Note the spelling of opcode. It is an abbreviation of operation code.
John
On Fri, Oct 25, 2013 at 12:42:11AM +0000, Ken Perry wrote:
>
> For the following words the largesign opt code is a problem. The
> problem
is if a word has two largesign words in a row in the word when it is back
translated there is a space added. See the list of words below. I could fix
this by adding the words as word opt code to cover up the problem if that is
what we want to do. I would think though the largesign should only work if the
finished back translation are complete words that are all largesign with out
extra bits if that makes since. See the words below and let me know if this is
a table fix thing or a largesign opt code fix.
>
> In the list below the first word is the word, the second is the
backtranslation, and the third is the translation.
>
> andante and ante &ante
> andante's and ante's &ante's
> andantes and antes &antes
> standoff stand off /&(f
> standoff's stand off's /&(f's
> standoffish stand offish /&(fi%
> standoffs stand offs /&(fs
--
John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com For a description of the software, to download
it and links to project pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com For a description of the software, to download
it and links to project pages go to http://www.abilitiessoft.com
For a description of the software, to download it and links to project pages go
to http://www.abilitiessoft.com
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
