Hi Davy,
Sorry, but I haven't been doing much with the yaml tests yet. It is something I
need to look at when I have finished this round of Danish tables.
Actually, sv should be written with a letsign. In the Danish grade 2 tables, I
have the following:
word selv 234-1236
contraction sv
It is a case like the English example
word could 14-145
contraction cd
I have done it consequently with word contractions consisting of two or three
cells, even if I didn't know of any commonly used abbreviation with those
letters. You never know what people get to write (smile).
HTH Bue
Fra: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] På vegne af Davy Kager
Sendt: 30. juni 2016 10:32
Til: 'liblouis-liblouisxml@xxxxxxxxxxxxx'
Emne: [liblouis-liblouisxml] For Bue: letsign in Danish
Hi Bue (and others),
I recently noticed a small oversight in the code dealing with letsign in
forward translation. I corrected this issue (see branch dkager_letsign), but
now the tests for Danish grade 2 fail.
It appears the tests do not expect a letsign before a multi-letter contraction.
For example sv is expected to come out as ⠎⠧ but liblouis generates ⠠⠎⠧.
I checked the last stable release of liblouis, v2.6.5, and there too the
letsign is added. The YAML tests mark such cases as xfail. In v3.0 they are no
longer marked as xfail and indeed they worked because of that small oversight.
It would be very helpful if an expert can clarify what’s going on here. There
seems to be nothing in the tables to suggest that the letsign should be
suppressed in these cases.
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: <mailto:info@xxxxxxxxxx>
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 <mailto:info@xxxxxxxxxx>
info@xxxxxxxxxx) and delete the original message and possible copies.