[liblouis-liblouisxml] Re: [brailleblaster] Re: UTDML re-design

From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
To: brailleblaster@xxxxxxxxxxxxx
Date: Tue, 11 Mar 2014 05:52:53 -0500
liblouisutdml is used in the Daisy pipeline also. Bookshare and some places in 
Europe are using it for production. Generally they call file2brl from whatever 
language they are using or directly from 
the command  line. It is being used on Windows and Mac as well as Linux.

John

On Tue, Mar 11, 2014 at 08:34:55AM +0000, Michael Whapples wrote:
> John it would be useful to have your input on understanding what exactly 
> is done at certain points in the LibLouisUTDML process.
> 
> Michael Whapples
> On 11/03/2014 05:36, John J. Boyer wrote:
> >I understand that a rewrite in Java would deal with the utd part of 
> >liblouisutdml, plus the configuration files and semantic-action files. utd 
> >exists mostly in the transcriber.c module, with a few bits
> >of code in other modules, such as transcribe_paragraph.c . It was intended 
> >not only as a universal tactile document markup language, but also as the 
> >basis for other enhancements, such as the
> >creation of volumes (utd2volumes.c) This module is only a stub at present. 
> >Only utd2brf is completely fleshed out. There was also  to be a table of 
> >contents module.
> >
> >I assume that the reasons for switching to Java are that much of the 
> >necessary cap0ability already exists in Java libraries, and debugging 
> >should be easier. If this course is taken I will be glad to act
> >as a consultant on what already exists and on what bugs are likely to turn 
> >up.
> >
> >John
> >
> >On Mon, Mar 10, 2014 at 05:40:46PM -0400, Keith Creasy wrote:
> >>Michael and Brandon.
> >>
> >>  
> >>
> >>After my conversation with Brandon I'd like us to spend some quality time 
> >>on
> >>Thursday trying to get a handle on just how much work it would be to shift
> >>most of the XML/UTD work from the LibLouisUTDML library to a Java library.
> >>Same question re refactoring for C++. How many hours of development time
> >>would it cost us? I'll bring my own estimate to the table. If we decide to
> >>do it then I think Michael and Brandon would be the two for the job. 
> >>Brandon
> >>is well versed on Java, XML, SWT, and what UTD actually does. Michael, you
> >>seem to have a better handle on LibLouisUTDML and how it is put together.
> >>
> >>  
> >>
> >>There are already examples of a Java API for LibLouis we can draw on. My
> >>proposal is to use LibLouis for translation of content only.
> >>
> >>  
> >>
> >>While we are doing that, should we choose to do it, Chuck and our new
> >>developer could work on issues with the current BrailleBlaster. We would 
> >>try
> >>to keep the new API as much like the old one as possible so the transition
> >>is as simple as it can be.
> >>
> >>  
> >>
> >>We wuld continue to use the basic structure of configuration and semantic
> >>actions, perhaps put in an XML form.
> >>
> >>  
> >>
> >>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
[liblouis-liblouisxml] Re: [brailleblaster] Re: UTDML re-design

Other related posts:
