Klavaro, learn to type efficiently…

Lo
I will intentionnally write this in english. The main reason is that I’m too lazy to write an install report (with bugs and so on) to the authors of this soft AND explain u and make u discover this software.
Laziness is really one of my principal feature. Let’s say it’s one of my killer-feature ;)
First I discover this soft totally by chance: a friend at the work looks at my fingers on the keyboard and say: »ouah u could type with ur 10 fingers » I said that my mother gives me ten fingers so why should I use only 3 of them to type or make anything else? She smiled and asked me if I learned that thx to a powerful soft that she could use herself to learn that so fantastic thing. I did not use any soft: my mother tells me to stick a paper with a kbd reproduction to the wall and typed looking at that sheet of paper and not my fingers or kbd. Nowadays I typed without looking at all but I must confess that it’s hard for me using the ctl or alt keys. This question makes me feel frustated about my poor typing skills. I decide to find a free software that works under windows and linux and freebsd (last but not least coz I’m currently using it!) to improve that and be more at ease with the typing difficulties: it really worth it when u use an strengh and powerful editor (vim): u could be more at ease with the keybindings. And keybindings it’s gaining time to do ur work and then going on with ur laziness style of life. It’s useful I thought too when u write code eg I should look at my kbd to write: #include and I’ve just mistyped the first bracket ;)
Time to improve that to be more efficient and not wasting my time looking at that fucking kbd instead of working :)

So I ask google and I fall on that. It was the first link and looks nice. I was too lazy to go further so go on with that stuff :)
I d/l it and try to compile it on my box which is a amd64 one with FreeBSD 6.0 on it. I read the lightweight readme and install files and start with autogen and configure. At the make moment I got an error in tutor.c:

tutor.c: In function `tutor_calc_stats':
tutor.c:671: error: `LC_NUMERIC' undeclared (first use in this function)
tutor.c:671: error: (Each undeclared identifier is reported only once
tutor.c:671: error: for each function it appears in.)
tutor.c:671: warning: passing arg 1 of `g_strdup' makes pointer from integer without a cast
*** Error code 1

Sounds bad. Look at the code (ah that’s a nice thing that looking at the code to correct it!). I just notice that one header is missing: locale.h was not include so it prevents from compile right. I add that and re-make.
New complain: exactly the same but in plot.c

plot.c: In function `plot_draw_chart':
plot.c:147: error: `LC_NUMERIC' undeclared (first use in this function)
plot.c:147: error: (Each undeclared identifier is reported only once
plot.c:147: error: for each function it appears in.)
plot.c:147: warning: passing arg 1 of `g_strdup' makes pointer from integer without a cast
*** Error code 1

I had the header reremake and got feared at the end by:

/usr/bin/ld: warning: libz.so.2, needed by /usr/local/lib/libfreetype.so, may conflict with libz.so.3
/usr/bin/ld: warning: libm.so.3, needed by /usr/local/lib/libpng.so.5, may conflict with libm.so.4

I suppose that the matter is coming from my box here I should do a ld and check my libs more carefully ;)
I install it and try to handle it. I should give u a pic from my desk. It works but I could not got it in french: see my term on the pics. Oh btw It could be great if this output could be redirect in /var/log for example (it sounds it’s there coz I’m launching it by the shell.
I try « normally » and for example I cant see message error like:
** Message: trans_read_text() --> couldn't open the data file: fr_FR_basic_intro.txt
in my logs however they are important to understand for example why I cant have it in french (I’m not very good in english and making an effort to understand etc…such a pain).
Here it is :)
If I got some time (and courage!) I will do a port for freebsd. Klavaro sounds in a good way to become a good soft but the code needs to be « polish » by some careful and riguourous hands. So an open-project which seems searching what we could call a « second souffle »