[brailleblaster] Re: Important Next Step: Locking semantic action or style for specific elements in a specific document

  • From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Thu, 18 Jul 2013 13:29:13 -0500

That sounds good. The file should begin with "newentries no" and end 
with "include nimas.sem" .Actually, you can specify "newentries no" in 
nimas.cfg, so you never have to worry about it.

John

On Thu, Jul 18, 2013 at 05:48:17PM +0000, Keith Creasy wrote:
> Yes, I thought about using "locked" braille. Another approach I thought of is 
> allowing BrailleBlaster to create an extended .sem file that is stored in the 
> document file set. It might have entries like:
> 
> no strong,id,strong_0002
> 
> that would override the settings in the default .sem file. We'd have to add 
> code to BrailleBlaster that would look for and use that .sem file if it 
> existed.
> 
> I liked it because it didn't require us to "lock" the entire brl element. We 
> can ad an id attribute if the element doesn't already have one.
> 
> -----Original Message-----
> From: brailleblaster-bounce@xxxxxxxxxxxxx 
> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
> Sent: Thursday, July 18, 2013 1:37 PM
> To: brailleblaster@xxxxxxxxxxxxx
> Subject: [brailleblaster] Re: Important Next Step: Locking semantic action or 
> style for specific elements in a specific document
> 
> I think that maybe it is time to implement "locked" Braille. To simplify 
> things at the beginning, if anything is changed in Braille the whole L<Lbrl> 
> element should be locked, that is, the atribute class="locked" 
> should be aded to it. liblouisutdml would then treat this <brl> element as 
> something to be inserted verbatim into the translation, except that <newline> 
> and <newpage> elements might be adjusted to maintain proper formatting.
> 
> John
> 
> On Thu, Jul 18, 2013 at 04:15:32PM +0000, Keith Creasy wrote:
> > All.
> > 
> > This needs some thought and discussion particularly among the developers. I 
> > really knew it would be one of the first things users asked about, and 
> > indeed it is. Let me start with the use-case:
> > 
> > A braille transcriber opens a NIMAS document using BrailleBlaster. The 
> > document contains a lot of <strong> elements which are, according to the 
> > nimas.sem file bolded in braille.The transcriber realises that the 
> > publisher used <strong> a lot more than would be desired or useful in 
> > braille so she wants to remove the bold symbols from the braille for 
> > specific <strong> or sections of the book containing <strong> elements. How 
> > do we implement this in BrailleBlaster or LibLouisUTDML?
> > 
> > 
> > This might apply to other elements as well, such as a heading, emphasis, or 
> > a particular list. We are basically talking about making exceptions to the 
> > base semantic attribute for a specific element or group of elements  for a 
> > specific document and making this easy to do from the GUI.
> > 
> > 
> > Brandon and I talked about possibilities but I don't want to share them 
> > until others have had a chance to think about it.
> > 
> > Thanks.
> > 
> > Keith
> > 
> > 
> > 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
> 
> 

-- 
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: