[liblouis-liblouisxml] Re: Harness and doctests files
- From: "Vic Beckley" <vic.beckley3@xxxxxxxxx>
- To: <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Wed, 13 Jun 2012 20:08:57 -0400
Michael,
Thank you so much for this excellent information. I will try it tomorrow and
see how it goes.
Best regards from Ohio, U.S.A.,
Vic
E-mail: vic.beckley3@xxxxxxxxx
-----Original Message-----
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael
Whapples
Sent: Wednesday, June 13, 2012 6:15 PM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: Harness and doctests files
Oh yes, its much simpler to get running on Linux or a Mac, or even any
other unix based system. They tend to be GNU tools based and the make
files tend to set everything up correct. I may have made cygwin sound
harder than it is, however that has its disadvantages as any DLL made in
cygwin depends on the cygwin DLL (it certainly used to I don't know if
they have changed that yet).
So in your archlinux system, at a command shell give the following
commands (ensure SVN and nose are installed there should be packages for
these using pacman, I only do not give the names for the packages
because I am too lazy to look them up):
svn co http://liblouis.googlecode.com/svn/trunk liblouis
cd liblouis
./autogen.sh
./configure --enable-ucs4
make
and then to run the tests
make check
Whenever you want to update from SVN just do
svn update
from the liblouis directory. Don't forget then you would need to make
again, you may need to make clean to ensure no old stuff is floating around.
You could install the svn version with:
make install
might need either su command before to change to root user or you could do
sudo make install
depending on how your system is set up.
However you may not wish to install the SVN version as it may mess up
the version from pacman, if you are purely testing then make check does
not need it to be installed.
I hope this helps you get it working on Linux.
Michael Whapples
On 13/06/2012 22:57, Vic Beckley wrote:
> Michael,
>
> You make this sound very complicated, as I am sure it is. I think for me
it
> would be worth the effort to get it to work if possible since I will be
> working with creating and troubleshooting tables on a regular basis. Would
> it be any easier if I could learn to use the tools on my ArchLinux VM?
>
>
> Best regards from Ohio, U.S.A.,
>
> Vic
> E-mail: vic.beckley3@xxxxxxxxx
>
>
> -----Original Message-----
> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael
> Whapples
> Sent: Wednesday, June 13, 2012 5:44 PM
> To: liblouis-liblouisxml@xxxxxxxxxxxxx
> Subject: [liblouis-liblouisxml] Re: Harness and doctests files
>
> I am concluding for a windows user the tests are not really of any
> advantage. In short I am having trouble even making the harness run on
> windows. NOTE: I am using the windows SDK for compilation rather than
> MINGW32 and such like which ports the GNU tools to windows, I found
> those more bother than they were worth.
>
> Also I am having trouble even getting nose to install on python3 on
> windows. I don't like the setuptools/distribute stuff (that was why I
> took a time away from python as they seemed to be the dominating
> installer system) and the nose docs indicates I can download the package
> and just use the setup.py script, but that seems to try and download
> distribute and then distribute fails to install when using python3.
>
> Using python2 I do get nose installed, however when I try and run the
> runHarness.py script it complains that certain tables cannot be found.
> As I remember this was an issue with earlier versions of the harness. I
> think the issue is that the tables the tests rely on are split between
> the main liblouis tables directory and the tables directory of the tests
> directory. Running make check may set this all up for GNU tools users
> but doesn't help the windows user who might be using Microsoft tools for
> building.
>
> I certainly could look at the tables issue, I feel though it doesn't
> really need a fix in the harness but rather a better plan on where
> tables for tests should be found (IE. should tests only rely on tables
> in the tables subdirectory of the tests directory?).
>
> As for the nose issues, I am not even going near that, setuptools and
> distribute are projects I want to steer well clear of.
>
> Michael Whapples
> On 13/06/2012 22:26, Mesar Hameed wrote:
>> Hi Vic
>>
>> On Wed 13/06/12,17:10, Vic Beckley wrote:
>>> Hi all,
>>>
>>> I have seen a tremendous amount of traffic lately on the harness test
> files.
>> Yes sorry about that, hope it wasnt to irritating.
>> we kept changing bits and peaces until we finally seem to have settled :)
> for now at least.
>>
>>> I don't understand their purpose
>> The purpose is to have real input texts in a given language, and the
> matching expected (correct) braille output.
>> For example english grade 2, word "the" should contract to dots 2346
>>
>> The purpose of the harness is to have a list of input texts, single
words,
> anything to trigger a contraction rule, and its known (manually checked)
> braille.
>> Then when the harness runs we can quickly identify what words dont
> translate correctly, and how liblouis braille output is different from the
> expected.
>> This should then gives us extra knowledge to correct liblouis
> opcodes/rules.
>> It isnt something that will be used by everyday liblouis consumers, but
> more targeted towards table debugger/improver people.
>>
>>
>>
>>> and how to use them.
>> Assuming you have python, you probably also need to install the nose
> modules, in theory when you run make check it should all work.
>>> Are they of any value to me running strictly, for now, under Windows?
>> Strictly not needed, but if you are interested in making sure your tables
> are correct/complete then you may consider giving us a hand.
>> for a relatively small example you can have a look at the en-gb-g2
harness
> file
>> Note that file does both forward and backward translation, but for a
first
> step just considering forward translations is probably simplest.
>> Thanks,
>> Mesart
>> 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:
