Package: wv
Version: 1.2.4-1
Severity: minor
Running wvWare without any options gives:
wvWare 1.2.4
Usage: wvWare [OPTION...] filename.doc
[...]
Authors:
Dom Lachowicz ([EMAIL PROTECTED])
Caolan McNamara (original author)
Visit http://www.wvware.com
The page at the bottom does not longer seem to be controlled by the
authors. It should reference the sf.net page, I guess.
Also, the way the programs in the suite handle the above case
of missing command line arguments is different. Some show usage
information while others yield error messages:
$ for i in /usr/bin/wv* ; do echo $i `$i < /dev/null 2>&1 | head -1` ; done
/usr/bin/wvAbw error: '' unreadable
/usr/bin/wvCleanLatex error: '' unreadable
/usr/bin/wvConvert Usage: wvConvert [--config config.xml] [--password password]
filename.doc
/usr/bin/wvDVI error: '' unreadable
/usr/bin/wvDocBook error: '' unreadable
/usr/bin/wvHtml error: '' unreadable
/usr/bin/wvLatex error: '' unreadable
/usr/bin/wvMime Usage: /usr/bin/wvMime <word document>
/usr/bin/wvPDF error: '' unreadable
/usr/bin/wvPS error: '' unreadable
/usr/bin/wvRTF wvRTF version 1.2.4
/usr/bin/wvSummary Usage: wvSummary doc1 [... docN]
/usr/bin/wvText Usage: /usr/bin/wvText <word document> <text output file>
/usr/bin/wvVersion Usage: wvVersion filename.doc
/usr/bin/wvWare wvWare 1.2.4
/usr/bin/wvWml error: '' unreadable
As none of the programs seems to be prepared to read stdin, all could
provide usage information alike.
This is conntected to some programs outputting to stdout, while others
want input and output file specified.
That, too, could be improved to a more consitent user interface.
Last issue: The wvWare usage tells you that it is possible to generate
PDF, DVI and whatever output. But *how* to do this is explained neither
there, nor in the man page (not counting the SEE ALSO section).
What output format running 'wvWare foo.doc' will produce is also obscured.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
