Docs: CP-M1A vs CP-M1E
(Just in case thre's any confusion..)
This commit is contained in:
parent
3ccabfd64e
commit
b7560192b9
9
README
9
README
|
@ -80,7 +80,7 @@
|
|||
Mitsubishi CP-3020D/DE and CP-3020DA/DAE
|
||||
Mitsubishi CP-9000DW, CP-9500DW, and CP-9600DW-S
|
||||
Mitsubishi CP-9800DW, CP-9800DW-S, CP-9810DW, and CP-9820DW-S
|
||||
Mitsubishi CP-M1E
|
||||
Mitsubishi CP-M1A / CP-M1E
|
||||
Olmec OP900
|
||||
Shinko CHC-S2245 (aka Sinfonia S3)
|
||||
Shinko CHC-S6145-5A (aka Sinfonia CS2-c)
|
||||
|
@ -898,7 +898,7 @@
|
|||
|
||||
Work-in-progress printers:
|
||||
|
||||
Mitsubishi CP-M1E
|
||||
Mitsubishi CP-M1A / CP-M1E
|
||||
|
||||
Unsupported printers (Unknown VID/PID):
|
||||
|
||||
|
@ -912,10 +912,11 @@
|
|||
|
||||
*** VERY IMPORTANT ***
|
||||
|
||||
In order to generate usable output, the Mitsubishi CP-M1E printer
|
||||
In order to generate usable output, the Mitsubishi CP-M1 family
|
||||
requires the input data to be transformed using specific image
|
||||
processing algorithms. These are currently only implemented within
|
||||
Mitsubishi's proprietary drivers.
|
||||
Mitsubishi's proprietary drivers, and will require a substantial
|
||||
amount of effort to re-implement.
|
||||
|
||||
Valid commands:
|
||||
|
||||
|
|
|
@ -1280,7 +1280,7 @@ struct dyesub_backend mitsud90_backend = {
|
|||
|
||||
****************************************************
|
||||
|
||||
Comms Protocol for D90 & CP-M1E
|
||||
Comms Protocol for D90 & CP-M1
|
||||
|
||||
[[ ERROR STATUS ]]
|
||||
|
||||
|
|
Loading…
Reference in a new issue