Hi all.
A meeting would be great. From the sound of it we need to get Mike, perhaps in
collaboration with a few others, to resolve the failing tests. That seems to be
the roadblock at this point. Is that correct?
Mike is out today and probably tomorrow. Let's see what he says when he gets
back in and then schedule a call later in the week just to touch base and be
sure everyone has a clear understanding of where we should go. If everyone will
give us a few optional times when they'd be available that might help. I'd
recommend Skype for the call.
One thing we talked about at length the other day is the abstraction of the
emphasis codes. This may require a little extra time as Mike probably needs to
merge that into the UEB update branch before we can merge everything back onto
the default branch. Am I understanding this correctly?
Keith
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Davy Kager
Sent: Monday, February 22, 2016 8:49 AM
To: 'liblouis-liblouisxml@xxxxxxxxxxxxx'
Subject: [liblouis-liblouisxml] Re: Analysis of regressions in ueb_update branch
I'd be up for a call once Christian is back in his office.
One more common problem I found is the lack of letter signs where the tests
specify there should be one. The other issues were summarized already by
Christian.
-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Larry Skutchan
Verzonden: maandag 22 februari 2016 14:41
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Re: Analysis of regressions in ueb_update
branch
Thanks Davey.
We are trying to understand the places where Mike's patches break other
languages, and I know he has been looking at that extensively. We have also
been talking about getting a conference call together, so we can all understand
the issues.
Thanks.
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Davy Kager
Sent: Monday, February 22, 2016 7:33 AM
To: 'liblouis-liblouisxml@xxxxxxxxxxxxx' <liblouis-liblouisxml@xxxxxxxxxxxxx>
Subject: [liblouis-liblouisxml] Re: Analysis of regressions in ueb_update branch
Thanks Larry. I understand UEB is a priority, and I would gladly look into it
if I could read UEB myself. If Mike could have a look at the regressions
reported by "make check" that would be highly appreciated. It doesn't have to
be this week, but as you said we really should work toward getting this code
integrated. For UEB it looks to perform quite well, but unfortunately it breaks
some other languages. Mike is definitely the most skilled in his own code,
hence why I asked.
-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Larry Skutchan
Verzonden: maandag 22 februari 2016 13:16
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx; 'Christian Egli'
<christian.egli@xxxxxx>
Onderwerp: [liblouis-liblouisxml] Re: Analysis of regressions in ueb_update
branch
Mike is out today and Tuesday, but APH is extremely keen on getting these UEB
changes in for the next release.
The U. S. officially switched to UEB back in January, and JAWS and NVDA, of
course, still don't do it properly.
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Davy Kager
Sent: Monday, February 22, 2016 5:19 AM
To: 'Christian Egli' <christian.egli@xxxxxx>; liblouis-liblouisxml
<liblouis-liblouisxml@xxxxxxxxxxxxx>
Subject: [liblouis-liblouisxml] Re: Analysis of regressions in ueb_update branch
In addition, tests/en-ueb-g1_harness.yaml has two failures that should be easy
to fix:
Input: '—'
Expected: '⠠⠤' (length 2)
Received: '⠐⠠⠤' (length 3)
Diff: Expected '⠠' but received '⠐' in index 0
lou_checkyaml:./yaml/en-ueb-g1_harness.yaml:4: Failure
Input: 'ÿ'
Expected: '⠰⠘⠒⠽' (length 4)
Received: '⠘⠒⠽' (length 3)
Diff: Expected '⠰' but received '⠘' in index 0
lou_checkyaml:./yaml/en-ueb-g1_harness.yaml:45: Failure
Maybe Michael Gray could shed some light on this, since he extensively updated
the table. I had a quick look but can't really pinpoint the cause.
-----Oorspronkelijk bericht-----
Van: Christian Egli [mailto:christian.egli@xxxxxx]
Verzonden: vrijdag 19 februari 2016 12:42
Aan: liblouis-liblouisxml <liblouis-liblouisxml@xxxxxxxxxxxxx>; Davy Kager
<DavyKager@xxxxxxxxxx>
Onderwerp: Analysis of regressions in ueb_update branch
Hi all, hi Davy
I did some work on the regressions in the ueb_update branch. I cleaned the
error output and unchecked the tests that were marked as expected failures
previously but now actually work (150).
There are now 15 failing (yaml) test files with 248 failing test cases.
I think that these can be classified into a couple of main classes of
issues:
- Problems with in-word capitalization
ar-ar-g1_harness has a test for 'MPower' which should apparently be
translated as '⠠⠠⠍⠏⠕⠺⠑⠗' where as it comes out as '⠠⠠⠍⠏⠠⠄⠕⠺⠑⠗'. It
appears that the end of the capitalized letters is indicated in the
received output. Maybe the expected string is actually wrong.
Similarly in ta-ta-g1_harness where 'GHz,' is expected as '⠠⠠⠛⠓⠵⠂' but
actually comes out as '⠠⠠⠛⠓⠠⠄⠵⠂'.
In en-ueb-g2-dictionary_harness.txt.bak there is a test for 'Ac' which
is expected as '⠰⠠⠁⠉' but actually comes out as '⠠⠁⠉'. I don't speak
ueb but the actual result seems more plausible to me.
- Problems with symbols in ueb
en-ueb-symbols_harness has many tests for single symbols. At the
moment I fail to see a common pattern there. For example
'"' translates to '⠐' instead of '⠠⠶'.
'`' translates to '⠈' instead of '⠨⠡'. and
'│' (BOX DRAWINGS LIGHT VERTICAL) translates to '⠄⡳⠭⠆⠢⠴⠆⠄' instead of '⠸'
- Mixed numbers and letters
da-dk-g26-dictionary_harness for example has a test for "1kg" and
expects "⠼⠁⠠⠅⠛" as a translation. However the resulting translation is
"⠼⠁⠅⠛". It appears that the indicator to indicate the end of the
number is missing.
- Capitalization and backtranslation
In one test It appears that some of backtranslation of capitalized
braille is broken. Single letter capitals are translated correctly but
stuff like '⠨⠨⠍⠧⠹⠕⠱' is not translated back to 'MVGYOSZ'. See
tests/yaml/hu-hu-g1_backward.yaml:1179
- Emphasis
fi_harness has failures in emphasis. It appears that the start
indicator is doubled and an end indicator is added for single word
emphasis where it shouldn't be (yaml/fi_harness.yaml:74). For
multiword emphasis the closing indicator seems to be added at the and
instead of at the beginning. Maybe just a problem in the table?
- Single word capitalization
no_harness seems to have a problem with a single letter capital: 'I'
is translated as '⠠⠄⠠⠊⠠⠄' instead of as '⠠⠊'. This is right after an
emphasis word
Hope that helps
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse
12, CH-8045 Zürich, Switzerland
-----
Jetzt kostenlos bestellen: Eidgenoessische und kantonale Abstimmungsunterlagen
fuer den 28. Februar zum Hoeren auf CD. Bestellungen an medienverlag@xxxxxx
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<mailto: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<mailto:info@xxxxxxxxxx>) and delete the original message and
possible copies.
���z�+��b�z����pj����0�Zv+Z��b�K-����-�� �
-�m��剹h�+(�
���z�+��b�z����pj����0�Zv+Z��b�K-����-�� �
-�m��剹h�+(�
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<mailto: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<mailto:info@xxxxxxxxxx>) and delete the original message and
possible copies.
���z�+��b�z����pj����0�Zv+Z��b�K-����-�� �
-�m��剹h�+(�
h��^���ب����(~���hv�'����֧vX���h��#y�ij
���h��i��bnZ.��+
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<mailto: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<mailto:info@xxxxxxxxxx>) and delete the original message and
possible copies.
h��^���ب����(~���hv�'����֧vX���h��#y�ij
���h��i��bnZ.��+
