As the commit bot just posted, I added a test for this behavior. I marked it as
a bug because the documentation doesn't mention any special rules for exactly
two caps. The Dutch table mentions that "opcodes for capitalisation (capsign,
begcaps and endcaps) are insufficient", so I used that output table for the
test.
My guess is that the failing tests in ta-ta-g1_harness.yaml were automatically
generated without scrutinizing the results:
- ['IAccessible2,', ⠠⠠⠊⠁⠉⠉⠑⠎⠎⠊⠃⠇⠑⠼⠃⠂]
- [MPower, ⠠⠠⠍⠏⠕⠺⠑⠗]
-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens Davy Kager
Verzonden: donderdag 31 maart 2016 15:04
Aan: 'liblouis-liblouisxml@xxxxxxxxxxxxx' <liblouis-liblouisxml@xxxxxxxxxxxxx>
Onderwerp: [liblouis-liblouisxml] Re: Rule for 2 consecutive caps in US English
braille?
It looks like there is no endcaps sign if the first two letters of a word are
capitals. But I’m not sure if this is a regression in Mike's code or if the
unit test is wrong.
-----Oorspronkelijk bericht-----
Van: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] Namens John J. Boyer
Verzonden: donderdag 31 maart 2016 14:43
Aan: liblouis-liblouisxml@xxxxxxxxxxxxx
Onderwerp: [liblouis-liblouisxml] Re: Rule for 2 consecutive caps in US English
braille?
I think the rule is that if there are two consecutive capital letters each
should be proceeded by a capital sign, as in the formula KCl
John
On Thu, Mar 31, 2016 at 11:09:09AM +0000, Davy Kager wrote:
Hello all,
Today I had another look at the regressions on the feature/ueb_update branch.
In tests/yaml/ta-ta-g1_harness.yaml I see a few tests that expect no endcaps
sign after two consecutive capital letters. For example:
- [MPower, ⠠⠠⠍⠏⠕⠺⠑⠗]
This appears to be a feature of the en-us-g1.ctb table on the master branch
(i.e. the current public release of liblouis). After applying the patches
from the APH, this rule is gone. Here is some output from lou_translate to
show the behavior:
$ tools/lou_translate tables/en-us-g1.ctb Foobar ,foobar FOobar
,,foobar FOObar ,,foo,'bar FOOBar ,,foob,'ar foOBar fo,,ob,'ar fOObar
f,,oo,'bar fOOBAr f,,ooba,'r
Compare FOobar, FOObar and fOObar. Could anyone clarify if this is a feature
or a failure?
Thanks,
Davy
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.
