[liblouis-liblouisxml] Re: Difference between "format for text device" and "format for BRF"?
- From: Brandon Roller <brandon.r.roller@xxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Wed, 30 Jul 2014 14:09:12 -0400
Hey Michael,
What I had mentioned in an earlier email was when a heading was inside a
boxline. My example was a heading one which has a lnie before and after
inside a boxline. According to the transcribers, using the 2011 Format, it
would go top boxline, then blank line, then heading text, then blank line,
then bottom boxline. I was talking about whether blank lines should be
honored within the boxline. Whether a blank line should precede a top
boxline and follow a bottom boxline may be something worth looking into
before attempting to implement.
On Wed, Jul 30, 2014 at 2:03 PM, Keith Creasy <kcreasy@xxxxxxx> wrote:
> Yes, I think you have it. Also, because of what the boxline is anything
> that comes after it ends up being a block element, and probably is anyway.
>
> -----Original Message-----
> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx [mailto:
> liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples
> Sent: Wednesday, July 30, 2014 1:59 PM
> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> Subject: [liblouis-liblouisxml] Re: Difference between "format for text
> device" and "format for BRF"?
>
> I can give the idea you said a go and see how it works in practice.
>
> So just to confirm you want a newline to start the brl node representing
> the boxline, but for it to depend on the next brl node to start its own
> newline? I may have been thinking about it too hard, it may be the case
> that the content of a sidebar will always be an element such as a
> paragraph, etc which will start with a newline node.
>
> Finally can I just check where the blank lines should appear. I think
> Brandon did say at some point, going from memory it is one blank line
> before the top boxline and one after the bottom boxline. There should not
> be blank lines between the boxlines and the sidebar content. Is that
> correct?
>
> Michael Whapples
> On 30/07/2014 18:52, Keith Creasy wrote:
> > Can we talk about this on Skype? It seems simple to me but maybe I'm
> wrong somehow.
> >
> >
> > -----Original Message-----
> > From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> > [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of
> > Michael Whapples
> > Sent: Wednesday, July 30, 2014 1:51 PM
> > To: liblouis-liblouisxml@xxxxxxxxxxxxx
> > Subject: [liblouis-liblouisxml] Re: Difference between "format for text
> device" and "format for BRF"?
> >
> > Hello,
> > In fact utd2brf.c did not really need modifying to work with the boxline
> style, the issue of the characters not appearing was due to me not
> inserting them correctly into the UTD (I forgot to convert the character
> into dots).
> >
> > However we still have the outstanding issue of the placement of the
> boxlines. I think I need further explanation of how the UTD functions for
> begin and finish newline work. Also we must decide where the newline nodes
> should appear in UTD.
> >
> > Michael Whapples
> > On 30/07/2014 17:44, Keith Creasy wrote:
> >> OK, thanks John. This doesn't entirely answer the question. What is the
> real difference? Isn't BRF output for a text device?
> >>
> >> The reason, or one of the reasons, is that our boxline style is working
> in UTD and for output to a text device but not for output to BRF, which is
> what is used in the Braille Preview pane.
> >>
> >>
> >> -----Original Message-----
> >> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> >> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of John
> >> J. Boyer
> >> Sent: Wednesday, July 30, 2014 12:41 PM
> >> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> >> Subject: [liblouis-liblouisxml] Re: Difference between "format for text
> device" and "format for BRF"?
> >>
> >> formatFor textDevice produces output for embossing or reading on a
> Braille display directly. formatFor brf first produces UTDML then uses this
> to produce Braille which may contain tactile graphics. The graphics are not
> yet implemented in utd.
> >>
> >> John
> >>
> >> On Wed, Jul 30, 2014 at 12:09:27PM +0000, Keith Creasy wrote:
> >>> Can someone please explain precisely what the differences are between
> format for text device and format for BRF? Performance with some features
> differs and obviously processing goes through different channels. I'm
> assuming there is some very good reason for this.
> >>>
> >>> Keith
> >>>
> >> --
> >> 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
> > 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
>
> 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:
