cuneiform-linux problem

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create an entry for cuneiform-linux, using 

-l ger - f text -o  $FILE  $IMAGE; cat $FILE

as argument which will use german as recognition language, and produce a
textfile as output.
2. start the text recognition using the cuneiform engine
3. Recognition works fine, but you always get

Cuneiform for Linux 0.9.0

as first line in the recognized text.

What is the expected output? What do you see instead?
Using tesseract, a similar message is displayed in the terminal, not in the
output. Somehow the cuneiform-message seem to be misplaced; it doesn't
appear in the termnial, where it is supposed to show up.  

What version of the product are you using? On what operating system?
I use the git-version of ocrfeeder (yesterdays version), 0.6.1,  on Ubuntu
9.10, 32 bit, and Cuneiform for Linux 0.9.0.

Please provide any additional information below.

Original issue reported on code.google.com by hanksch...@googlemail.com on 5 Mar 2010 at 2:09

[GoogleCodeExporter]

Hi Hank,

I had already tested that case and I am going to write a blog post about how to 
use
Cuneiform with OCRFeeder.

Although OCRFeeder is intended to be user friendly, the cost of it being 
flexible
with the system-wide OCR engines is that users will have to know a bit of shell
scripting if they want to configure the engines.

Here are the arguments that make Cuneiform work properly on OCRFeeder:

-l ger -f text -o $FILE $IMAGE >/dev/null; cat $FILE; rm $FILE

Where  >/dev/null discards whatever standard output is returned from the 
command.
The rm $FILE here is merely because although everything is made on the /tmp
directory, this way, the temporary $FILE is removed when no longer used.

I will also add Cuneiform to the list of engines that OCRFeeder should detect 
after
being installed.

Original comment by joaquimr...@gmail.com on 5 Mar 2010 at 2:17

• Changed state: Invalid

[GoogleCodeExporter]

Hi!

Thanks! I thought something like that would solve this; I tried to use an entry 
for
the error file, but without success.  

Speaking about user friendlieness: a little more documentation would be nice... 
;-)

I'm trying to write about OCRFeeder in the german ubuntuusers-wiki, see
http://wiki.ubuntuusers.de/Baustelle/ocrfeeder, if your interested, its German 
tough,
I'm afraid...

so long
hank

Original comment by hanksch...@googlemail.com on 5 Mar 2010 at 3:59

[GoogleCodeExporter]

Hi,

Yes, I should indeed create a better documentation for it.

I'll set a Google Group for OCRFeeder so we can better discuss new features,
problems, etc.

Also, it would be great if more people could contribute to the documentation (I
prefer to focus more on the code), so if you feel like contributing, I would
appreciate that.

Best regards,

Original comment by joaquimr...@gmail.com on 5 Mar 2010 at 4:05