OK here we are: https://goo.gl/a4w8qW
This form will collect the word or phase, the current liblouis URB translation,
the correct translation and any notes the user cares to offer. I can add
anything else anyone would want.
The Sheet itself is at: https://goo.gl/9sa7TD
Let me know if there are any issues.
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 Jun 2, 2015, at 8:09 AM, Paul Wood <paulw@xxxxxxxxxxxxxx> wrote:
Sounds good to me! Thanks Greg!
Paul
On 02/06/2015 16:02, Greg Kearney wrote:
I could set up a website to collect the errors as they are found. People
could enter the word or phase being translated. The results and what the
correct translation should be. Any notes and so on. It would all be
collected in a Google sheet for review.
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 Jun 2, 2015, at 3:02 AM, Paul Wood <paulw@xxxxxxxxxxxxxx>For a description of the software, to download it and links to
wrote:
I agree we should base on your tables Mike. But I too will want to update
as and when we come across translation errors. How is it best to do that?
Also in view of tidying up the tables, can someone please explain to me
what should be defined in chardefs and what should be defined in the g1
table?
Also I think it is suggested to use the unicode value as opposed to the
actual unicode character as the definition with the character in the
comment. Can the rationale be explained to me please as I was advised
previously to do the reverse? I personally don't mind I just don't want to
keep changing it!
I'm happy to take a share in the work, maybe as I'm not the best at table
definitions I could do the test harnesses?
Thanks
Paul
On 01/06/2015 18:24, Joseph Lee wrote:
Hi Mike,--
Before we do that, let's wait on Bert to see if we can merge master into
tables/ueb. Once we agree on which tables to use (I'd vote for yours, which
is based on work done by Ken, Mesar and I), then let's think about dividing
our work.
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 10:09 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
I will start adding my updates to the tables/ueb branch. Note that these
will be just the updates that don't need the new opcodes. How does that
sound?
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 1:00 PM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi,
Gotcha. In this case, should we keep tables/ueb and rebase it from master,
or say goodbye to that branch? If we keep it, then I think we need to
rebase
it from master from now on.
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 9:59 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
That is what I have been doing. I just put the actually character after
the
opcode instead of a description.
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 12:54 PM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi Mike,
I see. But what if a sighted researcher wanted to see the actual character
(not just the hex value and a textual description, but the actual symbol)
for which a braille representation is present? I think a better approach
would have been to put the actual symbol in parentheses to help a potential
sighted colleague get a glimpse of UEB and its braille representation
(personally, I would have wanted to see the actual symbol as part of the
comment no only to help a potential sighted contributor, but also to serve
as a small test to make sure that the actual braille representation of that
symbol is present when viewed by a screen reader user).
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 9:44 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Actually I had a request to use the hex values to make it easier to
identify
which Unicode character is being used. I put the actual character in the
comment part. It makes no difference to me.
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 12:37 PM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi Mike,
I don't know what happened to the master UEB tables, but when I merge it
into tables/ueb branch, I get major conflicts, such as incompatible entries
for accents and math symbols and others. A note of concern is use of hex
values for these symbols, which will not help future maintainers when it
comes to seeing the actual symbols. I would much prefer if the actual
symbols are present rather than their hex values for readability.
This tells me either I need to rebase from master or we need to resolve
them
as soon as possible. Or, we could say goodbye to tables/ueb in favor of
yours or the table set from master (remember that we are talking about a
potential project that'll affect lives of hundreds of braille readers and
screen reader users across the globe).
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 9:23 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
I thinking about moving the unicode definitions to the en-ueb-chardefs
table. Either that or moving them to their own file.
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 12:14 PM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi,
How would you like to reorganize the table set? Let us know if you need any
help with it.
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 9:14 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
That is no problem. I would like to however reorganize and clean up the
UEB
tables if nobody has an issue with that?
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 12:08 PM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi,
The latest commit on that branch is from last August and should be updated
(if not, we should merge it with latest master and work from there).
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 9:05 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Are your updated tables in the tables/ueb branch?
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Joseph Lee
[
joseph.lee22590@xxxxxxxxx
]
Sent: Monday, June 01, 2015 11:57 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi,
Could you try porting my tables to see if they'll work? I plan to work on
grade 1 material this summer and would like to base it from a tablet set
that looks promising (including yours).
Cheers,
Joseph
-----Original Message-----
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] On Behalf Of Michael Gray
Sent: Monday, June 1, 2015 8:53 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Sorry for the delay.
Because my tables uses the opcodes they will not work with any branches
that
have not been merged with my mrg_ueb_update branch. However, if requested
I
will create a branch with that will contain those parts of my updates that
should work with any branch.
If anyone else is working on these tables, please let me know, Some of my
changes will be extensive.
MRG
mgray@xxxxxxx
________________________________________
From:
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[
liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
] on behalf of Bert Frees
[
bertfrees@xxxxxxxxx
]
Sent: Tuesday, May 26, 2015 8:57 AM
To:
liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Status of UEB tables
Hi Paul,
OK, if you want to drop your work and wait for Michael's that fine with us.
Still, having test data for all the things you did would be really useful
anyway because like you say, they apply to Michael's table too, or any
other
implementation.
Thanks,
Bert
Paul Wood (Torch) writes:
Anyway, I'm happy to dump all my Pull Requests and wait for Michael'sFor a description of the software, to download it and links to project
merge. If it is useful I will generate the harness tests that are
being requested as these will be applicable to Michael's tables as
well and where I have seen a difference I have notified Michael,
hopefully not frustrating him too much!
From what I understand of all the work Michael has done, his code
enhancements have been essential, as well as the table enhancements to
enabling full UEB implementation. As I said previously I don't think
it's really worth just adding my Pull Requests, although it adds a few
corrections and the accented letters to have full UEB implementation
requires Michael's code and the tables go together with that.
Let me know if there is anything you still want me to do.
Cheers
Paul
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to project
pages
go to
http://liblouis.org
For a description of the software, to download it
and links to project pages go to
http://liblouis.org
For a description of the software, to download it and links to
project pages go to
http://liblouis.org
Paul Wood, Chief Technical Officer
Torch Trust
Torch House, Torch Way,
Market Harborough, Leics. LE16 9HL, UK
Direct Line: +44(0)1858 438269
Tel: +44(0)1858 438260, Fax: +44(0)1858 438275
Email:
paulw@xxxxxxxxxxxxxx
Website:
www.torchtrust.org
____________________________________________________
Chief Executive: Dr Gordon Temple
Charity No. 1095904
Privileged/Confidential Information may be contained in this message.
If you are not the intended recipient please destroy this message
and kindly notify the sender by reply email. The computer from which
this mail originates is equipped with virus screening software.
However Torch Trust cannot guarantee that the mail and its attachments
are free from virus infection.
project pages go to
http://liblouis.org
--
Paul Wood, Chief Technical Officer
Torch Trust
Torch House, Torch Way,
Market Harborough, Leics. LE16 9HL, UK
Direct Line: +44(0)1858 438269
Tel: +44(0)1858 438260, Fax: +44(0)1858 438275
Email: paulw@xxxxxxxxxxxxxx
Website: www.torchtrust.org
____________________________________________________
Chief Executive: Dr Gordon Temple
Charity No. 1095904
Privileged/Confidential Information may be contained in this message.
If you are not the intended recipient please destroy this message
and kindly notify the sender by reply email. The computer from which
this mail originates is equipped with virus screening software.
However Torch Trust cannot guarantee that the mail and its attachments
are free from virus infection.