kopia lustrzana https://gitlab.com/sane-project/website
115 wiersze
5.9 KiB
HTML
115 wiersze
5.9 KiB
HTML
|
<!-- received="Tue Aug 24 19:14:58 1999 PDT" -->
|
|||
|
|
<!-- sent="Tue, 24 Aug 1999 21:39:26 -0400" -->
|
|||
|
|
<!-- name="Tom Martone" -->
|
|||
|
|
<!-- email="tom@martoneconsulting.com" -->
|
|||
|
|
<!-- subject="Re: SANE V2" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="SANE V2" -->
|
|||
|
|
<title>sane-devel: Re: SANE V2</title>
|
|||
|
|
<h1>Re: SANE V2</h1>
|
|||
|
|
<b>Tom Martone</b> (<a href="mailto:tom@martoneconsulting.com"><i>tom@martoneconsulting.com</i></a>)<br>
|
|||
|
|
<i>Tue, 24 Aug 1999 21:39:26 -0400</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#297">[ date ]</a><a href="index.html#297">[ thread ]</a><a href="subject.html#297">[ subject ]</a><a href="author.html#297">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0298.html">Harald Finster: "Re: microtek X6 advance and TMA"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
|
|||
|
|
<li> <b>Maybe in reply to:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0299.html">Oliver Rauch: "Re: SANE V2"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
Greetings,<br>
|
|||
|
|
<p>
|
|||
|
|
Nick Lamb wrote:<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> However, when it came to adding JBIG (which someone mentioned wanting) I</i><br>
|
|||
|
|
<i>> noticed that JBIG uses the exact same arithmetic coding stuff which was</i><br>
|
|||
|
|
<i>> patented by IBM and thus lies unused in the JPEG standards.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> At the moment I have explicitly mentioned the patented process as a no-no</i><br>
|
|||
|
|
<i>> in the JPEG frame type, which makes sense because hardly anything can</i><br>
|
|||
|
|
<i>> read JPEG streams with arithmetic encoding anyway. For JBIG we don't have</i><br>
|
|||
|
|
<i>> that option because the patented Q-coder is in the baseline standard.</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> So: A question for those writing drivers for high-speed document scanning</i><br>
|
|||
|
|
<i>> </i><br>
|
|||
|
|
<i>> Should we include a JBIG frame type anyway? If we do it will be the first</i><br>
|
|||
|
|
<i>> format for which SANE cannot include a reference implementation. The</i><br>
|
|||
|
|
<i>> advantage in supporting it anyway would be that you could potentially</i><br>
|
|||
|
|
<i>> save the JBIG image (if an interchange format exists) and import it into</i><br>
|
|||
|
|
<i>> your proprietary document management system. The disadvantage is that</i><br>
|
|||
|
|
<i>> this sets an unpleasant precedent.</i><br>
|
|||
|
|
Yes, I was the one who mentioned JBIG. I mentioned it because the newer<br>
|
|||
|
|
line of Bell+Howell scanners (4000/8000) series generate that format as<br>
|
|||
|
|
well. I do not have one of those scanners available to me at this time,<br>
|
|||
|
|
so I do not have an urgent need to send JBIG. I just thought that I'd<br>
|
|||
|
|
put it in the list of frametypes for discussion, hoping that I'd get to<br>
|
|||
|
|
expand the backed support to the newer line of scanners sometime soon.<br>
|
|||
|
|
<p>
|
|||
|
|
I also noticed the patent issue and it caused concern. But then I saw<br>
|
|||
|
|
the following (quoted from "Encyclopedia of Graphic File Formats" by<br>
|
|||
|
|
Murray and VanRyper)<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> JBIG-KIT is free software under the GNU General Public License and</i><br>
|
|||
|
|
<i>> provides complete source code and documentation. A 1992 draft copy</i><br>
|
|||
|
|
<i>> of the CCiTT T.82 Recommendation for JBIG is also currently included</i><br>
|
|||
|
|
<i>> in this distribution.</i><br>
|
|||
|
|
<p>
|
|||
|
|
When I saw this, it made me feel better, but I'm not really well versed<br>
|
|||
|
|
in the patent side of things...<br>
|
|||
|
|
<p>
|
|||
|
|
FYI, here is the web page of the author of JBIG-KIT:<br>
|
|||
|
|
<a href="http://www.cl.cam.ac.uk/~mgk25/">http://www.cl.cam.ac.uk/~mgk25/</a><br>
|
|||
|
|
<p>
|
|||
|
|
and the web page for the JBIG group:<br>
|
|||
|
|
<a href="http://www.jpeg.org/public/jbighomepage.htm">http://www.jpeg.org/public/jbighomepage.htm</a><br>
|
|||
|
|
<p>
|
|||
|
|
This is a quote from the jbigkit-1.0-announce.txt file in the author's<br>
|
|||
|
|
ftp area. <a href="ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/JBIG">ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/JBIG</a><br>
|
|||
|
|
<p>
|
|||
|
|
There's no mention of IBM or the patent issue, here.<br>
|
|||
|
|
<p>
|
|||
|
|
<i>> JBIG-KIT implements a highly effective data compression algorithm for</i><br>
|
|||
|
|
<i>> bi-level high-resolution images such as fax pages or scanned</i><br>
|
|||
|
|
<i>> documents.</i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>> JBIG-KIT provides a portable library of compression and decompression</i><br>
|
|||
|
|
<i>> functions with a documented interface that you can very easily include</i><br>
|
|||
|
|
<i>> into your image or document processing software. In addition, JBIG-KIT</i><br>
|
|||
|
|
<i>> provides ready-to-use compression and decompression programs with a</i><br>
|
|||
|
|
<i>> simple command line interface (similar to the converters found in Jef</i><br>
|
|||
|
|
<i>> Poskanzer's PBM graphics file conversion package).</i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>> JBIG-KIT implements the specification</i><br>
|
|||
|
|
<p>
|
|||
|
|
<i>> International Standard ISO/IEC 11544:1993 and ITU-T Recommendation</i><br>
|
|||
|
|
<i>> T.82(1993), "Information technology - Coded representation of picture</i><br>
|
|||
|
|
<i>> and audio information - progressive bi-level image compression",</i><br>
|
|||
|
|
<i>> <<a href="http://www.itu.ch/itudoc/itu-t/rec/t/t82_23822.html">http://www.itu.ch/itudoc/itu-t/rec/t/t82_23822.html</a>>,</i><br>
|
|||
|
|
<p>
|
|||
|
|
So could this software satisfy the reference implementation?<br>
|
|||
|
|
I don't want to start an unpleasant precedent, so if there's a problem<br>
|
|||
|
|
with JBIG, let's cross it off the list.<br>
|
|||
|
|
<p>
|
|||
|
|
Tom Martone<br>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|||
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0298.html">Harald Finster: "Re: microtek X6 advance and TMA"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
|
|||
|
|
<li> <b>Maybe in reply to:</b> <a href="0296.html">Nick Lamb: "SANE V2"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0299.html">Oliver Rauch: "Re: SANE V2"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|