[liblouis-liblouisxml] Re: liblouis as a Visual Studio project
- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx>
- To: liblouis-liblouisxml@xxxxxxxxxxxxx
- Date: Fri, 25 Mar 2011 01:39:12 -0500
Neil,
Thanks to your student. The problems you are encountering sound liike
the problems ViewPlus had in inncluding liblouis and liblouisxml in
their TSS software. We never did get around to making thsir solutions
part of the liblouis* project. They were quite simple.
liblouisutdml and the latest version of liblouis have new features for
specifying the locations of tables, semantic files, configuration files
and temporary files.
Perhaps the student could corresponnd with me directly about handling
these problems and also compiling liblouislutdml. It has Java bindings,
which means that the include path must contain jni.h and jni-md.h These
can be obtained from the include directory of your jdk.
The method used for Nemeth translation is an early one. The translation
of British maths, etc. use a more developed and intuitive method. There
is no neede to modify the Nemeth translation. I think that the only
fraction format implemented was mfrac. This can be fixed by updating the
nemeth.sem file and the liblouis tables.
I understand that the Visual Studio project files are xml. They could
easily be included in the repositories. Unfortunately, I'm not good with
Visual Studio. Perhaps, though, if you describe the changes you made in
some detail I can comment.
Thanks,
John
On Thu, Mar 24, 2011 at 05:04:13PM -0700, Neil Soiffer wrote:
> At CSUN, I told John Boyer that I would set up a MS Visual Studio project to
> for liblouis. John was going to do the real work, but ... I (actually a
> student we hired) got liblouis and liblouis to build and work under visual
> studio in windows. There were a few changes that needed to be done (eg,
> temp files were written to an "illegal" location), and we found what seem to
> be some serious bugs -- I suspect we are missing something though because I
> can't see how the code would work as is.
>
> Because I'm so uncertain of the changes, I don't want to commit them to
> repository. I do want to the work we did to be part of the project though.
> Is anyone willing to take the files and look at the changes and decide if
> they are right or not. John? Someone else? Locations of the temp files
> and the config files are probably something to be discussed.
>
> We were confused by this statement in the documentation:
> "The Nemeth Code of Braille Mathematical and Science Notation, BAUK maths
> and Marburg Maths have been implemented. the Nemeth code was the first and
> uses an implementation which is now obsolete."
>
> Is this statement out of date? Does it just mean "don't do translations to
> other braille math codes the way the Nemeth translation is done"?
>
> Also, from what little I understand of Nemeth code, it looks like we are
> getting a bad translation for linear fractions (ie, fractions that use
> <mo>/</mo> as opposed to mfrac). It only produced a single char for "/"
> instead of two chars as in the examples in the green book. Is that a sign
> we have things set up wrong, is my understanding of Nemeth code wrong, or is
> it a bug?
>
> Neil
--
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:
