[liblouis-liblouisxml] Re: Problem with all caps in en-us-g2.ctb
- From: Aaron Cannon <cannona@xxxxxxxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Wed, 23 Oct 2013 22:13:55 -0500
I haven't looked at their brf files. I'll take a look and get back to you.
Aaron
On 10/23/13, John J. Boyer <john.boyer@xxxxxxxxxxxxxxxxx> wrote:
> Bookshare has been using the current en-us-brf.dis file without
> complaint for a while, unless they changed it and didn't report the
> change. It looks like it would be a good idea for the people who handle
> tables to apply the patch.
>
> John
>
> On Wed, Oct 23, 2013 at 04:55:15PM -0500, Aaron Cannon wrote:
>> What this patch appears to do, at least based on my testing, is to
>> output Braille in the proper BRF format, which uses upper-case letters
>> for the letter symbols, and uses a few different symbols than Liblouis
>> outputs by default, such as a ^ for dots 45, instead of a ~.
>>
>> I'm basing my knowledge of the "proper BRF format" on what is output
>> by Duxbury when saving to the BRF format, and based on the format of
>> the files from the NLS WebBraille service.
>>
>> Aaron Cannon
>>
>> On 10/23/13, John J. Boyer <john.boyer@xxxxxxxxxxxxxxxxx> wrote:
>> > Aaron,
>> >
>> > Your patch adds characters such as digits and punctuation marks which
>> > do
>> > not have a case and are therefore the same in uppoer and lower case.
>> > These were not included in the curent en-us-brf.dis because they are
>> > unnecessary. Thanks fro the work, anyway. If someone wants to apply the
>> > patch it will do no harm.
>> >
>> > John
>> >
>> > On Wed, Oct 23, 2013 at 03:27:12PM -0500, Aaron Cannon wrote:
>> >> The current en-us-brf.dis doesn't use the BRF standard either. I
>> >> provided a patch that corrects this issue, but it was never merged,
>> >> either because it wasn't accepted, or because it got overlooked. I'm
>> >> not sure which.
>> >>
>> >> Anyway, I'm reattaching to this message in case anyone's interested.
>> >>
>> >> Aaron
>> >>
>> >> On 10/23/13, John J. Boyer <john.boyer@xxxxxxxxxxxxxxxxx> wrote:
>> >> > The brf standard requires letters to be in uppercase and also some
>> >> > special symbols such as \ . liblouis uses lowercase so that
>> >> > translations
>> >> > will look nice on a Braille display. Embossers accept either
>> >> > uppercase
>> >> > or lowercaase. If you want something that conforms to the strict brf
>> >> > standard use a tablelist like en-us-brf.dis,en-us-g2.ctb Bookshare
>> >> > does
>> >> > this, but I don't think it is appropriate for the Braille Plus 18.
>> >> >
>> >> > liblouis would handle capitalized letters followed by uncapitalized
>> >> > ones
>> >> > by inserting dots 6-3 The apostrrophe throws it off. A context rule
>> >> > might work. Something like:
>> >> >
>> >> > $U1-20"'"[]$l @6-3
>> >> >
>> >> > Johnn
>> >> >
>> >> > On Wed, Oct 23, 2013 at 06:23:36PM +0000, Ken Perry wrote:
>> >> >>
>> >> >>
>> >> >> I have been starting on fixing some of those problems I have found
>> >> >> in
>> >> >> en-us-g2.ctb. I now have a list of 99000 words translated by
>> >> >> duxberry
>> >> >> and
>> >> >> the same list translated by en-us-g2.ctb. A blaring problem is
>> >> >> capitalized words that end in 's. Liblouis translates the word
>> >> >> AIDS'S
>> >> >> as
>> >> >> ,,aids's where as duxberry does it as ,,AIDS,''S
>> >> >> I am a bit out of my legue on what rule will even affect that. I
>> >> >> think
>> >> >> ,'
>> >> >> is an end caps sign but how do I make liblouis do it? Also I
>> >> >> notice
>> >> >> duxberry capitalizes all letters is there a reason we don't?
>> >> >>
>> >> >> Ken
>> >> >
>> >> > --
>> >> > John J. Boyer; President, Chief Software Developer
>> >> > Abilitiessoft, Inc.
>> >> > http://www.abilitiessoft.com
>> >> > Madison, Wisconsin USA
>> >> > Developing software for people with disabilities
>> >> >
>> >> > For a description of the software, to download it and links to
>> >> > project pages go to http://www.abilitiessoft.com
>> >> >
>> >
>> >
>> >
>> > --
>> > John J. Boyer; President, Chief Software Developer
>> > Abilitiessoft, Inc.
>> > http://www.abilitiessoft.com
>> > Madison, Wisconsin USA
>> > Developing software for people with disabilities
>> >
>> > For a description of the software, to download it and links to
>> > project pages go to http://www.abilitiessoft.com
>> >
>> For a description of the software, to download it and links to
>> project pages go to http://www.abilitiessoft.com
>
> --
> John J. Boyer; President, Chief Software Developer
> Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
>
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.com
>
For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com
Other related posts:
