[Printing-architecture] snmp - average-toner-coverage per page
jsmeix at suse.de
Wed May 4 13:53:06 UTC 2016
On May 4 12:49 Predut, Marius wrote (excerpt):
>> 4. Get the PostScript stream while print job filtering
>> and analyze it.
>> Newer Ghostscript versions provide the Ghostscript
>> devices ink_cov and inkcov that output ink coverage:
>> $ gs -q -dNOPAUSE -dBATCH -sDEVICE=ink_cov \
>> -sOutputFile=/tmp/ink_cov.out \
>> $ cat /tmp/ink_cov.out
>> 5.33833 5.95657 6.71122 4.25845 CMYK OK
> Thank you so much for this solution!
> The ink_cov/ inkcov is can be ip address?
Perhaps this is no solution for your use case.
I do not understand the meaning of "ip address" here.
Do you perhaps ask if this can be used to query a
network printer device from remote (via its IP address)
for its ink coverage of a particular printed page?
You cannot do that with Ghostscript.
To use Ghostscript this way you need to run it on a computer.
Ghostscript is a PostScript (and PDF) interpreter.
Ghostscript input is PostScript or PDF and its output is
what a particular so called "Ghostscript device" produces.
Usually Ghostscript devices produce other printer languages
like PCL or Ghostscript devices produce various kind of
raster data like JPEG or CUPS raster data.
But there are also special Ghostscript devices that
output special stuff like the ink coverage.
This means it only works when you have PostScript or PDF
as input and you must be able to run Ghostscript with
that PostScript or PDF input to get its ink coverage.
When you print that PostScript or PDF on a printer device
the actual ink/toner consumption of the printer device could
be noticeable different compared to the ink coverage report
of Ghostscript because the printer device may do its own
way how much of what ink/toner it puts on the paper.
Think about a toner-saving printing mode where the
printer device puts less ink/toner on the paper
compared to what Ghostscript had reported
a high-quality photo printing mode where the
printer device puts more ink/toner on the paper
compared to what Ghostscript had reported.
For example to get real photo quality deep black
for 0 0 0 RGB (i.e. 100% black) the printer device
in CMYK mode may put 100% K plus additionally 15% C
and 15% M on the paper but Ghostscript would report
only the 100% K component because in its PostScript
input there is neither 15% C nor 15% M (there is
only 0 0 0 RGB which translates into 100% K).
SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard,
Graham Norton - HRB 21284 (AG Nuernberg)
More information about the Printing-architecture