I think the best way is to let us get these changes merged back into Liblouis
which we should be doing soon.
Thanks.
-----Original Message-----
From: Gregory Kearney [mailto:gkearney@xxxxxxxxx]
Sent: Friday, January 8, 2016 12:53 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx; Larry Skutchan <lskutchan@xxxxxxx>
Subject: Re: [liblouis-liblouisxml] Re: Regarding last UEB message: Some issues
outlined in the attached report fixed in 2.6.5
Larry;
While I admit I am a glutton for punishment I would like to try and build this
for MacOS X as well. Where would I get a copy of your changes?
Commonwealth Braille & Talking Book Cooperative Greg Kearney, General Manager
#320, 185-911 Yates Street Victoria, BC V8V 4Y9 CANADA
Email: info@xxxxxxxxx
U.S. Address
21908 Almaden Av.
Cupertino, CA 95014
UNITED STATES
Email: gkearney@xxxxxxxxx
On Jan 8, 2016, at 9:46 AM, Larry Skutchan <lskutchan@xxxxxxx> wrote:
All but two of the issue's in Jennifer's report work as desired in the APH
LibLouis UEB revisions still under construction. These include table
modifications, code refactoring, and a compliment of new code with expanded
capabilities including five new op codes on which rules may build.
APH's modifications to accurately support UEB are in their mature stages and
should be merged back with the main branch at a time yet to be finalized. The
next public release of LibLouis seems like the most logical time for the
release, and APH continues to devote significant resources toward the goal of
high quality UEB translation availability.
We have built binaries for Windows that let you try these along with a
Windows Send to Braille shortcut which you can download at:
http://tech.aph.org/redmine/projects/lt/wiki
Let us know.
Thanks.
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Davy
Kager
Sent: Thursday, December 17, 2015 3:27 AM
To: 'liblouis-liblouisxml@xxxxxxxxxxxxx'
<liblouis-liblouisxml@xxxxxxxxxxxxx>
Subject: [liblouis-liblouisxml] Re: Regarding last UEB message: Some
issues outlined in the attached report fixed in 2.6.5
I think ultimately we want to fix the problems with multi-pass rules. Also,
it might be a good idea to wait a little while longer to see where the UEB
patches from the APH are heading. Right now it seems there are multiple table
candidates from multiple sources. It would be nice to pick a ‘winner’ before
including in NVDA and other projects.
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Joseph Lee
Verzonden: dinsdag 15 december 2015 15:55
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Re: Regarding last UEB message: Some
issues outlined in the attached report fixed in 2.6.5
Hi,
I’ve tested the newest UEB tables (en-ueb-g*) using NVDA source code (there
is a ticket out there suggesting that we move to the newer table set, and I’d
be happy to provide a trivial patch for it (modifying the table filename), as
I wrote the initial version of the newer table set).
If NVDA does not use multipass (pass2, pass3, pass4) opcodes but understands
context (pass1) opcode, then it might be useful to use these in UEB provided
the spec gives us room for doing it (a hyphen between numbers, for example,
but there are limitations to context opcode format).
For Jamie: Should I proceed with UEB ticket patch (modifying filename and
perhaps change the UEB entry in output table in NVDA?).
Cheers,
Joseph
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Davy
Kager
Sent: Tuesday, December 15, 2015 12:53 AM
To: 'liblouis-liblouisxml@xxxxxxxxxxxxx'
<liblouis-liblouisxml@xxxxxxxxxxxxx>
Subject: [liblouis-liblouisxml] Re: Regarding last UEB message: Some
issues outlined in the attached report fixed in 2.6.5
Hi,
Note that NVDA disables multi-pass rules during translation, so chances are
your results won’t be exactly the same as if you ran lou_translate directly.
Also, I’m interested in UEB only because the new functionality Mike added to
liblouis looks very useful for Dutch as well (OK, and I also like UEB because
I’m interested in US culture, though I can’t read UEB yet).
Are you still interested in improving documentation? In reviewing the UEB
patches I realized quite a bit of the docs are out of date, ambiguous, or
missing altogether. Not just for the UEB opcodes, those are actually quite
well defined. But for example my own misinterpretation of the decpoint
opcode. Not to make a whole project out of this, but it would be good to have
a short list of sections that could be improved.
Davy
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Joseph Lee
Verzonden: dinsdag 15 december 2015 4:58
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Regarding last UEB message: Some
issues outlined in the attached report fixed in 2.6.5
Hi,
My brief testing with NVDA shows that some issues outlined in the report sent
earlier were fixed in LibLouis 2.6.5, and I’ve asked Jennifer to ask her
contacts at Bookshare about using LibLouis 2.6.5.
Thanks.
Cheers,
Joseph
DISCLAIMER:
De informatie verzonden met dit e-mail bericht is uitsluitend bestemd voor de
geadresseerde. Indien u niet de beoogde geadresseerde bent, verzoeken wij u
vriendelijk dit aan de afzender te melden (of via: info@xxxxxxxxxx) en het
origineel en eventuele kopieën te verwijderen.
The information sent in this e-mail is solely intended for the individual or
company to whom it is addressed. If you received this message in error,
please notify the sender immediately (or mail to info@xxxxxxxxxx) and delete
the original message and possible copies.
DISCLAIMER:
De informatie verzonden met dit e-mail bericht is uitsluitend bestemd voor de
geadresseerde. Indien u niet de beoogde geadresseerde bent, verzoeken wij u
vriendelijk dit aan de afzender te melden (of via: info@xxxxxxxxxx) en het
origineel en eventuele kopieën te verwijderen.
The information sent in this e-mail is solely intended for the individual or
company to whom it is addressed. If you received this message in error,
please notify the sender immediately (or mail to info@xxxxxxxxxx) and delete
the original message and possible copies.
