Package: zbar-tools
Version: 0.10+doc-7
Severity: minor
When I invoke zbarimg utility with last '--xml' parameter before the
filename, it shows some unwanted output of xml header and footer.
Example command:
$> zbarimg hello.png --xml
QR-Code:Hello, World!
<barcodes xmlns='http://zbar.sourceforge.net/2008/barcode'>
</barcodes>
scanned 1 barcode symbols from 1 images in 0.02 seconds
The lines containing <barcodes... and </barcodes> should not appear at
the output. It is reproducible with some more parameters, like
$> zbarimg --raw hello.png --xml bye.png --noxml bye.png --xml
Hello, World!
<barcodes xmlns='http://zbar.sourceforge.net/2008/barcode'>
<source href='bye.png'>
<index num='0'>
<symbol type='QR-Code' quality='1'><data><![CDATA[Bye,
World!]]></data></symbol>
</index>
</source>
</barcodes>
QR-Code:Bye, World!
<barcodes xmlns='http://zbar.sourceforge.net/2008/barcode'>
</barcodes>
scanned 3 barcode symbols from 3 images in 0.04 seconds
also generates extra strings at the end. If I add some filename as a
parameter at the end, then everything looks correctly. For example,
$> zbarimg hello.png --xml bye.png
QR-Code:Hello, World!
<barcodes xmlns='http://zbar.sourceforge.net/2008/barcode'>
<source href='bye.png'>
<index num='0'>
<symbol type='QR-Code' quality='1'><data><![CDATA[Bye,
World!]]></data></symbol>
</index>
</source>
</barcodes>
scanned 2 barcode symbols from 2 images in 0.04 seconds
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages zbar-tools depends on:
ii libc6 2.13-18
ii libjpeg8 8c-2
ii libmagickcore4 8:6.6.9.7-5
ii libmagickwand4 8:6.6.9.7-5
ii libv4l-0 0.8.5-3
ii libzbar0 0.10+doc-7
zbar-tools recommends no packages.
zbar-tools suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
