gs-pcl3.ref

openmeetings组件之GS openmeetings组件之GS openmeetings组件之GS

<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook V3.1//EN">

<!-- **************************************************************************

  Some markup conventions:
  - "ghostscript" is not usually marked up.
  - Ghostscript drivers are treated as <command>s.
  - Inline PostScript code is encapsulated by <literal>...</literal>.
  - Inline options are specified without the option prefix (-s or -d) except
    when an argument follows or (in the case of optional boolean arguments)
    could follow. In the first case they are marked as "option", in the second
    case as "userinput".

  Other conventions:
  - Statements which refer to undocumented properties of ghostscript are
    accompanied by a comment containing the string VERIFIED and describing
    the ghostscript version(s) in which I've checked the statement.

*************************************************************************** -->

<refentry id="gs-pcl3">

<docinfo>
  <title>Reference page for the <application>ghostscript</application>
    device driver <command>pcl3</command></title>
  <author>
    <firstname>Martin</firstname>
    <surname>Lottermoser</surname>
  </author>
  <address>
    <street>Greifswaldstra&szlig;e 28</street>
    <postcode>38124</postcode> <city>Braunschweig</city>
    <country>Germany</country>
    <email>[e-mail]</email>
  </address>
  <copyright>
    <year>2000</year>
    <year>2001</year>
    <holder>Martin Lottermoser</holder>
  </copyright>
  <releaseinfo>$Id: gs-pcl3.ref,v 1.21 2001/08/18 17:19:29 Martin Rel $</releaseinfo>
</docinfo>

<!-- ********************************************************************** -->

<refmeta>
  <refentrytitle>GS-PCL3</refentrytitle>
  <manvolnum>1</manvolnum>
</refmeta>

<!-- ********************************************************************** -->

<refnamediv>
  <refname>pcl3</refname>
  <refpurpose>ghostscript device driver for printers <!--
    -->understanding PCL 3+</refpurpose>
</refnamediv>

<!-- ********************************************************************** -->

<refsynopsisdiv>
  <!-- According to Walsh+Muellner, "DocBook - The Definitive Guide" (1.0.2),
       the title should be generated if not given. The version of Norman Walsh's
       HTML stylesheet I'm using does not do it, docbook-to-man does.
       If one specifies a title here, docbook-to-man produces two.
       Hence both packages are wrong. -->
  <cmdsynopsis>
    <command>gs</command>
      <arg choice="plain"> -sDEVICE=pcl3</arg>
      <group rep="repeat">
	<arg><replaceable>gs_option</replaceable></arg>
	<!-- The optional argument for boolean options is omitted because
	     docbook-to-man does not produce good output for it. -->
	<arg>-dBlackLevels=<replaceable>integer</replaceable></arg>
	<arg>-dCMYLevels=<replaceable>integer</replaceable></arg>
	<arg>-sColorModel=<replaceable>model</replaceable></arg>
	<arg>-sColourModel=<replaceable>model</replaceable></arg>
	<arg>-dCompressionMethod=<replaceable>method</replaceable></arg>
	<arg>-dConfigureEveryPage</arg>
	<arg>-dCUPSAccounting</arg>
	<arg>-dCUPSMessages</arg>
	<arg>-dDepletion=<replaceable>depletion</replaceable></arg>
	<arg>-dDryTime=<replaceable>seconds</replaceable></arg>
	<arg>-sDuplexCapability=<replaceable>capability</replaceable></arg>
	<arg>-sIntensityRendering=<replaceable>method</replaceable></arg>
	<arg>-dLeadingEdge=<replaceable>edge</replaceable></arg>
	<arg>-dManualFeed</arg>
	<arg>-sMediaConfigurationFile=<replaceable>pathname</replaceable></arg>
	<arg>-dMediaPosition=<replaceable>position</replaceable></arg>
	<arg>-sMedium=<replaceable>medium</replaceable></arg>
	<arg>-dOnlyCRD</arg>
	<arg>-sPageCountFile=<replaceable>pathname</replaceable></arg>
	<arg>-sPCLInit1=<replaceable>string</replaceable></arg>
	<arg>-sPCLInit2=<replaceable>string</replaceable></arg>
	<arg>-sPJLJob=<replaceable>jobname</replaceable></arg>
	<arg>-sPJLLanguage=<replaceable>language</replaceable></arg>
	<arg>-sPrintQuality=<replaceable>quality</replaceable></arg>
	<arg>-dRasterGraphicsQuality=<replaceable>quality</replaceable></arg>
	<arg>-dSendBlackLast</arg>
	<arg>-dSendNULs=<replaceable>number</replaceable></arg>
	<arg>-dShingling=<replaceable>shingling</replaceable></arg>
	<arg>-sSubdevice=<replaceable>subdevice</replaceable></arg>
	<arg>-dTumble</arg>
	<arg>-dUseCard=<replaceable>value</replaceable></arg>
      </group>
      <arg rep="repeat"><replaceable>file</replaceable></arg>
      <!-- Actually, gs does not follow the XPG Utility Syntax Guidelines and
	you can not only mix options and files but there are also multi-token
	options. --> 
  </cmdsynopsis>
</refsynopsisdiv>

<!-- ********************************************************************** -->

<refsect1 id="DESCRIPTION"><title id="DESCRIPTIONtitle">DESCRIPTION</title>

<refsect2><title>Supported Printers</title>
<para>
The ghostscript device driver <command>pcl3</command>
(formerly called <command>hpdj</command>)
is a ghostscript backend for printers understanding
Hewlett-Packard's Printer Command Language, level 3+
("PCL 3+", also called "PCL 3 Plus").
The driver is intended to support in particular the following printer models:
<blockquote><literallayout><!-- This is a hack to get a compact list.
-->HP DeskJet
HP DeskJet Plus
HP DeskJet Portable
HP DeskJet 310
HP DeskJet 320
HP DeskJet 340
HP DeskJet 400
HP DeskJet 500
HP DeskJet 500C
HP DeskJet 510
HP DeskJet 520
HP DeskJet 540
HP DeskJet 550C
HP DeskJet 560C
HP DeskJet 600
HP DeskJet 660C
HP DeskJet 670C
HP DeskJet 680C
HP DeskJet 690C
HP DeskJet 850C
HP DeskJet 855C
HP DeskJet 870C
HP DeskJet 890C
HP DeskJet 1120C
<!-- A total of 24 printer models. --></literallayout></blockquote>

The PCL dialect called "PCL Level 3 enhanced" is apparently a not
entirely compatible modification of PCL 3+.
This driver should basically work with such printers
but you must be more careful which options you select and
you might not be able to exploit all your printer's capabilities.
</para>

<para>
The driver does <emphasis>not</emphasis> support printers understanding only
Hewlett-Packard's PPA (Printing Performance Architecture) commands.
If a printer's documentation does not say anything about its
printer command language and
you find a statement like "... is designed for Microsoft Windows" or
"DOS support through Windows only",
the printer is almost certainly a PPA printer and hence is intended
<emphasis>exclusively</emphasis>
for systems running Microsoft Windows.
(These printers are also erroneously known as "GDI printers"
because they are intended to be accessed through a manufacturer-supplied driver
via Windows' GDI interface.)
There exist ways of using a PPA printer with ghostscript,
but not through <command>pcl3</command>.
</para>

<para>
Different printer models usually implement model-specific subsets of all
PCL-3+ commands or arguments to commands.
You must therefore tell the driver by means of the
<option>Subdevice</option>
option for which model the generated PCL code is intended.
The model-dependent difference in the generated code is not great.
Apart from media specifications, resolutions and colour capabilities,
one can consider three groups of models
which are treated with significant differences:

<blockquote><variablelist>
<varlistentry>
<term>Group 1</term>
<listitem><para>DeskJet, DeskJet Plus, DeskJet 500</para></listitem>
</varlistentry>
<varlistentry>
<term>Group 2</term>
<listitem><para>DeskJet Portable, DeskJets 3<replaceable>xx</replaceable>,
400, 5<replaceable>xx</replaceable> except 500 and 540,
</para></listitem>
</varlistentry>
<varlistentry>
<term>Group 3</term>
<listitem><para>DeskJets 540, 6<replaceable>xx</replaceable>,
8<replaceable>xx</replaceable> and 1120C.</para></listitem>
</varlistentry>
</variablelist>
</blockquote>

The first two groups I call the "old Deskjets",
the third group consists of "new DeskJets".
If you have a PCL-3 printer not appearing in the list above,
the likelihood is still good that it will accept the files generated by
<command>pcl3</command>.
You can specify one of the supported subdevices in these cases
(it is sufficient to try one each from the groups just mentioned),
or use the special subdevice names
<userinput>unspecold</userinput> or <userinput>unspec</userinput>
which are treated like members of the second and the third group above,
respectively,
with all subdevice-dependent checks having been turned off.
</para>

<para>
The list of printer models for which this driver is currently known to work is:
</para>
<para>
<!-- I don't know how to achieve a compact list. -->
<blockquote><literallayout>
HP 2000C
HP 2500CM
HP DeskJet 697C
HP DeskJet 850C
HP DeskJet 970C
HP DeskJet 1100C
Xerox DocuPrint M750
</literallayout></blockquote>
</para>
<para>
Details can be found in the file <filename>reports.txt</filename> in the
<command>pcl3</command> distribution;
its latest version is available via <command>pcl3</command>'s
<ulink url="http://home.t-online.de/home/Martin.Lottermoser/pcl3.html">home
page</ulink>.
If you wish to report on the hardware compatibility for a particular
printer model,
please read the file <filename>how-to-report.txt</filename>.
</para>

<para>
Omitting models already mentioned,
previous (<command>hpdj</command>) versions of this driver were reported to
work with the following printers:
</para>
<para>
<!-- Should be a compact list. -->
<blockquote><literallayout>
HP DeskJet 340
HP DeskJet 400 (tested for Gray only)
HP DeskJet 420
HP DeskJet 500
HP DeskJet 500C (tested for Gray only)
HP DeskJet 520
HP DeskJet 540
HP DeskJet 560C
HP DeskJet 600
HP DeskJet 610C
HP DeskJet 612C		<!-- 2000-07-06 R. Thavas -->
HP DeskJet 640C		<!-- 2000-10-02 Filip Stanek -->
HP DeskJet 660C/660Cse
HP DeskJet 670C
HP DeskJet 672C
HP DeskJet 680C
HP DeskJet 690C
HP DeskJet 690C+
HP DeskJet 693C
HP DeskJet 694C
HP DeskJet 832C
HP DeskJet 855C
HP DeskJet 870Cse/870Cxi
HP DeskJet 880C
HP DeskJet 890C
HP DeskJet 895Cse/895Cxi
HP DeskJet 932C		<!-- 2000-08-19 David Murdoch -->
HP DeskJet 1120C
HP OfficeJet 350	<!-- 2000-08-09 Chris BeHanna -->
HP OfficeJet 590
HP OfficeJet 600
HP OfficeJet 625
HP OfficeJet G55	<!-- 2000-10-27 Harald Schmid -->
HP OfficeJet T45	<!-- 2000-09-02 Peter Henning -->
Lexmark 3000 Color Jetprinter
Olivetti JP792 (see the option <option>SendBlackLast</option>)
</literallayout></blockquote>
</para>

<para>
Most of the people who sent me reports did not state to which extent
<command>hpdj</command> worked for their printer model.
</para>
</refsect2>

<!--========================================================================-->

<refsect2 id="ColourModels"><title>Colour Models</title>

<para>
Ignoring photo cartridges which are not supported by <command>pcl3</command>,
DeskJet printers can be classified in four categories:
</para>
<itemizedlist>
<listitem><para>The printer has only a black ink cartridge.</para></listitem>
<listitem><para>The printer can print with either a black or a
cyan/magenta/yellow (CMY) cartridge.</para></listitem>
<listitem><para>The printer holds a CMY and a black cartridge simultaneously,
but the two groups of inks are chemically incompatible and should not be
overlayed.
(Don't worry: the printer is not going to explode if they do.
You merely get poorer results because the black ink will spread further
than it should.
This is called "ink bleeding".)</para></listitem>
<listitem><para>The printer holds a CMY and a black cartridge simultaneously
and the inks can be mixed.
(Newer HP DeskJets use such bleed-proof inks.)</para></listitem>
</itemizedlist>
<para>
This leads to four <firstterm>(process) colour models</firstterm>
for the driver:
<blockquote><variablelist>
<varlistentry>
<term>Gray</term>
<listitem><para>Print in black only.</para></listitem>
</varlistentry>
<varlistentry>