[liblouis-liblouisxml] Re: lou_translate
- From: Ken Perry <kperry@xxxxxxx>
- To: "liblouis-liblouisxml@xxxxxxxxxxxxx" <liblouis-liblouisxml@xxxxxxxxxxxxx>
- Date: Tue, 24 Jun 2014 11:34:46 +0000
Is this something you will add because this new logging api also messes up
using lou_allround. It already has a way to know the input and output buffers
but now has extra spam.
Ken
From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx
[mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Whapples
Sent: Tuesday, June 24, 2014 6:44 AM
To: liblouis-liblouisxml@xxxxxxxxxxxxx
Subject: [liblouis-liblouisxml] Re: lou_translate
OK, so the liblouis command line tools need a default callback creating for the
logging API.
However in the meantime you can redirect the logging output to a file with a
command like:
lou_translate -b en-us-g2.ctb 2>./output.log
Or if you do not want any storing of the logging output you could write it to
/dev/null
lou_translate -b en-us-g2.ctb 2>/dev/null
Michael Whapples
On 24/06/2014 11:33, Ken Perry wrote:
I was trying to do some testing and the lou_translate command spams with output
and it did not use to do this. It shows the in buff, out buff, and it shows a
message saying translating. You used to be able to turn these messages on in
lou_allround but not in lou_translate. This makes it hard to test on large
files if it spams you with all kinds of output. It used to translate a file
silently and quickly. Is there a reason this has been changed?
ken
Other related posts:
