slp/selphy_print
1
0
Fork 0
Code Issues 48 Pull requests Activity

Update the README, and add an explicitly warranty disclaimer and GPL

Browse source 
reference.
This commit is contained in:
Solomon Peachy 2014-02-11 09:53:34 -05:00
parent 784e26c9b3
commit 3eef2ba475
1 changed files with 34 additions and 31 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

65
README
View file

@ -1,8 +1,11 @@
***************************************************************************
Unified Gutenprint/CUPS Backend for various Dye-Sublimation photo printers
Unified Gutenprint/CUPS backend for various Dye-Sublimation photo printers
(c) 2007-2014 Solomon Peachy <pizza@shaftnet.org>
Copyright (c) 2007-2014 Solomon Peachy <pizza@shaftnet.org>
This free software comes with ABSOLUTELY NO WARRANTY!
Licensed under the GNU GPL, see the 'COPYING' file for more details.
The latest version can be found at
@ -50,15 +53,18 @@
special two-way handshaking in order to successfully print.
This backend can only be used in conjunction with Gutenprint 5.2.10 or
newer. Please see the Gutenprint README file for more information on
use of this backend and integration into CUPS.
newer. Please see the Gutenprint README file (section II D) for more
information on use of this backend and integration into CUPS.
Although this backend is bundled with Gutenprint, this repository is
considered the canonical upstream source where all development occurs.
As such, when compared to the current Gutenprint release, the code here
often has additional features or device support. At the same time, it may
have half-developed features that don't quite work, and have bugs that
may eat your cats while you sleep.
As such, when compared to the current Gutenprint release, the code found
here is often newer, with additional features or device support. At the
same time, it may have half-developed features that don't quite work,
with giant bugs that come out at midnight to eat your cat.
On that note, please keep in mind that this software distributed
in the hope that it will be useful, but WITHOUT ANY WARRANTY WHATSOEVER.
***************************************************************************
@ -92,24 +98,19 @@
behaivor changes based on the name used to invoke the executable.
When compiled, a set of symlinks are created, corresponding to each
of the internal backends. Alternatively you may set the BACKEND
environment variable to force a specific backend to be used:
environment variable to force a specific backend to be used. These
commands are all equivalent:
BACKEND=backend gutenprint52+usb [ arguments ]
(OR)
gutenprint52+usb -B backend [ arguments ]
(OR)
backend [ arguments ]
That said, all internal backends support these invocation options:
All backends support the following invocations:
backend [ arguments ] filename
backend [ arguments ]- < filename
somecommand | backend [ arguments ]-
backend [ arguments ]
backend [ arguments ] filename
backend [ arguments ] - < filename
somecommand | backend [ arguments ] -
The 'filename' here refers to the raw spool data generated by
Gutenprint (eg via its gimp plugin) or the Windows print-to-file
@ -122,25 +123,27 @@
simultaneously, the backend will choose the first one it finds. If you
wish to target a specific device, you may specify its serial number
in the 'DEVICE' environment variable or by passing the '-S serialnum'
argument on the command line. For example:
argument on the command line. For example, these are equivalent:
DEVICE=N782 backend filename [ arguments ]
backend -S N782 filename [ arguments ]
All backends support an additional operational mode, to test out
unknown models. To use this mode, specify the VID, PID and its
internal device type as arguments or environment variables. For example:
internal device type as arguments or environment variables:
EXTRA_VID=04a9 EXTRA_PID=3ab1 EXTRA_TYPE=7 backend filename
backend -V 04a9 -P 3ab1 -T 7 filename
The VID and PID are specified in hexidecimal, and the TYPE is
the P_XXX enumeration defined in backend_common.h. '7' corresponds to
most Canon SELPHY CP models (eg the CP520, CP820, and CP910). If
you are able to successfuly print using this technique, please let
the P_XXX enumeration defined in backend_common.h. The '7' in this
example corresponds to most Canon SELPHY CP models, and is what you
would use if you were trying to get the backend to detect an
otherwise unrecognized SELPHY CP model (eg the CP520, CP820, or CP910).
If you are able to successfuly print using this technique, please let
us know so we can add the apppriate entry to the internal database.
Finally, some backends may support additional arguments; see below:
Finally, some backends support additional arguments; see below:
***************************************************************************
BACKEND=canonselphy
@ -151,7 +154,7 @@
CP400, CP500, CP510, CP710, CP720, CP730, CP740, CP750, CP760, CP770,
CP780, CP790, CP800, CP900
Unverified/untested, but should work:
Unverified/untested, but should work: (let us know, please!)
ES20, CP-220, CP530, CP600, CP810
@ -159,7 +162,7 @@
CP520, CP820, CP910
This backend does not support additional commands
This backend does not support additional commands.
***************************************************************************
BACKEND=kodak1400
@ -228,7 +231,7 @@
Verified supported printers:
Shinko/Sinfonia CHC-S2145 (aka "S2")
Shinko CHC-S2145 (aka "Sinfonia S2")
Development was sponsored by:
@ -283,10 +286,10 @@
Verified supported printers:
Sony UP-DR150,
Sony UP-DR150
Sony UP-DR200
This backend does not support additional commands
This backend does not support additional commands.
***************************************************************************
BACKEND=mitsu70x
@ -319,7 +322,7 @@
Citizen CX-W
Citizen CY
Work-in-progress (Unknown USB IDs):
Work-in-progress printers: (USB PIDs unknown)
Citizen CW-01/OP900/CW-02/OP900II
Olmec OP900