[brailleblaster] Re: Space, new-line, and index checking

  • From: Keith Creasy <kcreasy@xxxxxxx>
  • To: "brailleblaster@xxxxxxxxxxxxx" <brailleblaster@xxxxxxxxxxxxx>
  • Date: Wed, 10 Jul 2013 15:50:56 +0000

John.

OK, I don't know if it only needs to be while debugging but that would be OK. 
Right now we are dealing with just such instances and they should never happen. 
It'll be easier to fix if we know exactly when and where they are happening 
since finding them by hand is tedious and unreliable.




Keith Creasy
Software Developer
American Printing House for the Blind
KCreasy@xxxxxxx
Phone: 502.895.2405
Skype: keith537


-----Original Message-----
From: brailleblaster-bounce@xxxxxxxxxxxxx 
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
Sent: Wednesday, July 10, 2013 10:38 AM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Space, new-line, and index checking

Keith,

I'll have to think about this. It should probably be something that can be 
turned on with a configuration setting. There is already a debug seting that 
could be used.

John

On Wed, Jul 10, 2013 at 01:46:26PM +0000, Keith Creasy wrote:
> John.
> 
> I think we need to be loging an error or warning any time the number of 
> values in the index attribute does not match the number of braille characters 
> in the <brl> element. This should never actually happen by definition, right? 
> Who, what component, can do this? I thought LibLouisUTDML could put it in the 
> log as an error or warning, not fatal but if this happens we need to know and 
> try to correct it.
> 
> 
> 
> Keith Creasy
> Software Developer
> American Printing House for the Blind
> KCreasy@xxxxxxx
> Phone: 502.895.2405
> Skype: keith537
> 

--
John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc.
http://www.abilitiessoft.com
Madison, Wisconsin USA
Developing software for people with disabilities

Other related posts:

  1. Home
  2. brailleblaster
  3. Archive
  4. 07-2013