sane-project-website/manufacturers.html

97 wiersze
4.9 KiB
HTML
Czysty Zwykły widok Historia

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>SANE - Information for Manufacturers</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="author" content="Henning Meier-Geinitz">
<meta name="keywords" content="sane, scanner, manufacturers, programming, vendor, driver, backend">
<meta name="description" content="Information for Manufacturers">
<link href="mailto:hmg-guest@users.alioth.debian.org" rev="made">
<link rel="icon" href="favicon.ico" type="image/x-icon">
<link rel="shortcut icon" href="favicon.ico" type="image/x-icon">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<center>
<a href="http://www.sane-project.org"><img src="images/sane.png"
alt="SANE" height="117" width="346" border="0"></a>
</center>
<center>
<h1>Information for Manufacturers</h1>
</center>
<hr>
<p>
Are you a manufacturer or vendor of scanners and one of your scanners is not supported by <a
href="./">SANE</a> yet? As Linux and other Unix systems become more and more popular, many
people check for SANE support when buying scanners. A logo "Supported by SANE" or "Runs on
Linux" or similar would be nice, wouldn't it? Also an existing SANE backend would mean that
your scanner is no longer listed as <a
2005-10-03 15:35:30 +00:00
href="lists/sane-backends-cvs.html#S-UNSUPPORTED">unsupported</a> in our lists and you could add
"Linux support" to the list of features on your website.
</p>
<p>
As you are the manufacturer of the device, you have all the information necessary to write a
SANE backend (driver). That makes it much easier for you to do it than for any other
person. Most probably you only need to port your MS Windows code to SANE. You can ignore all
the graphical interface code as SANE already provides a variety of <a
href="sane-frontends.html">frontends</a> (scanning applications). You only need the code for
accessing the scanner. For details on how to write a driver see our <a
href="contrib.html">contributing page</a>.
</p>
<p>
I recommend to use the <a href="license.html">GPL + SANE exception</a> license for your
code. So it can be included in the SANE distribution and your driver will come with most Linux
distributions. Furthermore you can use the existing code for USB and SCSI access and many
helper functions so you don't need to think about the low level details. And your scanner will
be supported not just on one operating system and platform but on everything SANE runs on (see
our <a href="sane-support.html">platforms page</a>). Providing source code makes it easier for
other developers to give feedback and send patches for bugs.
</p>
<p>
If you can only release binary SANE backends that's better than nothing but still not
recommended. The SANE standard itself is public domain, so you are free to use it. But keep
in mind that you must adhere to our <a href="license.html">license</a> if you use parts of the
SANE code. Binary-only drivers mean you can't get help from us or any SANE users because
nobody can debug your code. Binary-only drivers can not be included in the official SANE
releases.
</p>
<p>
Yet another option is to publish complete programming information or the source code of the
scanner drivers for MS Windows. With this information it's much easier for a free software
developer to create a backend. Some manufacturers don't like to publish this information but
give it to selected developers only. That's possible, but the backend code will be GPL most
likely so at least part of the information will be public anyway. If you intend to publish
programming information, you may want to ask on the <a
href="mailing-lists.html">sane-devel mailing list</a> if anyone is
interested in programming a driver. But keep in mind that providing programming information is
not a guarantee that a driver will ever be written.
</p>
<p>
The most important part is communication: Please tell us what you intend to do. We are also
interested in partial information, e.g. if some scanners use the same chipset as others. That
may help to write backends for a variety of devices. Also tell us if any of the information in
our lists is missing or wrong. So please contact the <a href="mailing-lists.html">sane-devel
mailing list</a> with your information and ideas. If you don't want to subscribe to this list,
please write to Henning Meier-Geinitz (<a
href="mailto:henning@meier-geinitz.de">henning@meier-geinitz.de</a>).
</p>
<hr>
<p>
<a href="./">SANE homepage</a><br>
<a href="imprint.html">Contact</a>
</p>
<p>
<font size="-1">$Date$ $Author$</font>
</p>
</body>
</html>