[liblouis-liblouisxml] Re: Thoughts onn a new liblouis*
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Sat, 26 Oct 2013 10:57:27 -0500
The reason for the typeform parameter is to avoid having to edit the
input text. This was considered near the beginning and rejected. It
would also greatly complicate indexing, which is important forr editing
in BrailleBlaster and in the ViewPlus applications.
So what do you propose for solving the problems with handling the often
conflicting requirements for the placement of Braille indicators in the
various Braille codes? We need that in a few months.
John
On Sat, Oct 26, 2013 at 04:30:37PM +0100, Michael Whapples wrote:
> Depending on how much from scratch the new liblouis is to be, the
> typeform parameter may or may not be an issue.
>
> Why do we need a second array to indicate typeform? There are other ways
> of marking emphasis. As an example one can embed tags in the text to
> indicate the beginning and end of emphasis (eg. as XML does with things
> like <em>emphasised text</em>). What does a second array offer over
> these other representations, if nothing then why restrict ourselves to
> the one method of representing it?
>
> Why is something like Python, or may be LUA, not capable of handling
> typeform? Even if going with the separate typeform array, why could that
> not simply be passed into the script function along with the text?
>
> I really see no reason to create a home grown solution which everyone
> would need to learn rather than use something which exists and may be
> known to some people. Also a home grown solution would be far less
> tested and probably far less optimised than something with wider use. I
> think a home grown solution would be a mistake.
>
> Michael Whapples
> On 26/10/2013 14:26, John J. Boyer wrote:
> >Before we think of writing code we should design algorithms that meet
> >all the requirements that we know if. One use of liblouis and
> >liblouisutdml that has not been menntioned is for Braille production by
> >Braille publishing houses. Several places in Europe are already using it
> >this way, and APH here in the U.S. will be using the libraries in
> >BrailleBlaster. This use requires proper indication of emphasis and even
> >other kinds of type, such as colored type, which is frequently used now.
> >
> >Another consideration is the license and copyright. We need to free
> >ourselves of the LGPL. This probably means that we can't use any of the
> >existing code. Whether it applies to the concepts behind that code I
> >don't know. It would be good to get the opinion of someone with legal
> >experience. The license should be a permissive one, like Apache 2.0.
> >Although the software will be open source, it should be copyrighted by
> >an organization that can take action if someone violates the license.
> >
> >For liblouis, something like the current opcodes for entering simple
> >contraction rules will give the best performance. For more complex
> >situations some form of scripting language seems necessary. This was
> >first introduced in an assembly-like language used in context and
> >multipass rules. It needs to be extended to handle even more complex
> >situations, such as insertion of Braille indicators for emphasis. Such
> >indicators must be inserted in more than one place. Moreover, it must be
> >able to query the typeform parameter. I doubt that any scripting
> >language now in use can meet those requiremennts.
> >
> >liblouisutdml handles interpretation of xml and formatting. We will need
> >something like the present semantic-action files and configuration
> >files.
> >
> >Finally, work on the existing code must continue. Plans for new
> >incarnations must not distract from it.
> >
> >John
> >
>
> 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
Other related posts:
