The translation is temporarily closed for contributions due to maintenance, please come back later.

Source string Read only

(itstool) path: sect2/para
Context English State
Communication between the driver and a host-based printer is often through proprietary or undocumented protocols, making them functional only on the most common operating systems.
Converting <trademark class="registered">PostScript</trademark> to Other <acronym>PDL</acronym>s
Many applications from the Ports Collection and FreeBSD utilities produce <trademark class="registered">PostScript</trademark> output. This table shows the utilities available to convert that into other common <acronym>PDL</acronym>s:
Output <acronym>PDL</acronym>s
Output <acronym>PDL</acronym>
Generated By
<acronym>PCL</acronym> or <acronym>PCL5</acronym>
<package role="port">print/ghostscript9-base</package>
<literal>-sDEVICE=ljet4</literal> for monochrome, <literal>-sDEVICE=cljet5</literal> for color
<acronym>PCLXL</acronym> or <acronym>PCL6</acronym>
<literal>-sDEVICE=pxlmono</literal> for monochrome, <literal>-sDEVICE=pxlcolor</literal> for color
<acronym>ESC/P2</acronym>
<literal>-sDEVICE=uniprint</literal>
<acronym>XQX</acronym>
<package role="port">print/foo2zjs</package>
For the easiest printing, choose a printer that supports <trademark class="registered">PostScript</trademark>. Printers that support <acronym>PCL</acronym> are the next preferred. With <package role="port">print/ghostscript9-base</package>, these printers can be used as if they understood <trademark class="registered">PostScript</trademark> natively. Printers that support <trademark class="registered">PostScript</trademark> or <acronym>PCL</acronym> directly almost always support direct printing of plain <acronym>ASCII</acronym> text files also.
Line-based printers like typical inkjets usually do not support <trademark class="registered">PostScript</trademark> or <acronym>PCL</acronym>. They often can print plain <acronym>ASCII</acronym> text files. <package role="port">print/ghostscript9-base</package> supports the <acronym>PDL</acronym>s used by some of these printers. However, printing an entire graphic-based page on these printers is often very slow due to the large amount of data to be transferred and printed.
Host-based printers are often more difficult to set up. Some cannot be used at all because of proprietary <acronym>PDL</acronym>s. Avoid these printers when possible.
Descriptions of many <acronym>PDL</acronym>s can be found at <link xlink:href="http://www.undocprint.org/formats/page_description_languages"/>. The particular <acronym>PDL</acronym> used by various models of printers can be found at <link xlink:href="http://www.openprinting.org/printers"/>.
Direct Printing
For occasional printing, files can be sent directly to a printer device without any setup. For example, a file called <filename>sample.txt</filename> can be sent to a <acronym>USB</acronym> printer:
<prompt>#</prompt> <userinput>cp sample.txt /dev/unlpt0</userinput>
Direct printing to network printers depends on the abilities of the printer, but most accept print jobs on port 9100, and <citerefentry><refentrytitle>nc</refentrytitle><manvolnum>1</manvolnum></citerefentry> can be used with them. To print the same file to a printer with the <acronym>DNS</acronym> hostname of <replaceable>netlaser</replaceable>:
<prompt>#</prompt> <userinput>nc <replaceable>netlaser</replaceable> 9100 &lt; sample.txt</userinput>
<acronym>LPD</acronym> (Line Printer Daemon)
Printing a file in the background is called <emphasis>spooling</emphasis>. A spooler allows the user to continue with other programs on the computer without waiting for the printer to slowly complete the print job.
FreeBSD includes a spooler called <citerefentry><refentrytitle>lpd</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Print jobs are submitted with <citerefentry><refentrytitle>lpr</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Initial Setup
A directory for storing print jobs is created, ownership is set, and the permissions are set to prevent other users from viewing the contents of those files:
Printers are defined in <filename>/etc/printcap</filename>. An entry for each printer includes details like a name, the port where it is attached, and various other settings. Create <filename>/etc/printcap</filename> with these contents:
lp:\ <co xml:id="printing-lpd-co-name"/>
:lp=/dev/unlpt0:\ <co xml:id="printing-lpd-co-device"/>
:sh:\ <co xml:id="printing-lpd-co-header"/>
:mx#0:\ <co xml:id="printing-lpd-co-mx"/>
:sd=/var/spool/lpd/lp:\ <co xml:id="printing-lpd-co-sd"/>
:lf=/var/log/lpd-errs: <co xml:id="printing-lpd-co-lf"/>

Loading…

No matching activity found.

Browse all component changes
User avatar dbaio

Translation comment

Build error, needs editing.

8 months ago

Things to check

Multiple failing checks

Following checks are failing:
Consecutive duplicated words: Turkish (tr_TR)
Has been translated: Turkish (tr_TR)
XML syntax: Turkish (tr_TR)

Reset

Comments

There is 1 comment for this string.

View

Source information

Source string comment
(itstool) path: sect2/para
Flags
read-only
Source string location
book.translate.xml:17529
String age
a year ago
Source string age
a year ago
Translation file
books/handbook.pot, string 2953