Whitespace-only fixes, translators please ignore.

This commit is contained in:
Warren Block 2016-01-25 22:41:17 +00:00
parent 7735d34a7e
commit b0c3d5987b
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48095

View file

@ -144,9 +144,9 @@ Starting lpd.</screen>
job, <filename>ulpt0</filename> resets the job, <filename>ulpt0</filename> resets the
<acronym>USB</acronym> port. Resetting the port can cause <acronym>USB</acronym> port. Resetting the port can cause
problems with some printers, so the problems with some printers, so the
<filename>unlpt0</filename> device is usually used instead. <filename>unlpt0</filename> device is usually used
<filename>unlpt0</filename> does not reset the USB port at instead. <filename>unlpt0</filename> does not reset the
all.</para> USB port at all.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -187,10 +187,10 @@ Starting lpd.</screen>
<para>Several communication parameters must be known to <para>Several communication parameters must be known to
communicate with a serial printer. The most important are communicate with a serial printer. The most important are
<emphasis>baud rate</emphasis> or <acronym>BPS</acronym> (Bits Per Second) and <emphasis>baud rate</emphasis> or <acronym>BPS</acronym>
<emphasis>parity</emphasis>. Values vary, but typical (Bits Per Second) and <emphasis>parity</emphasis>. Values
serial printers use a baud rate of 9600 and no vary, but typical serial printers use a baud rate of 9600
parity.</para> and no parity.</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -1042,17 +1042,17 @@ lp:
<para>All of the documents print on that single printer. When <para>All of the documents print on that single printer. When
the Sales department grows enough to need their own printer, the Sales department grows enough to need their own printer,
the alias can be removed from the shared printer entry and used the alias can be removed from the shared printer entry and
as the name of a new printer. Users in both departments used as the name of a new printer. Users in both
continue to use the same commands, but the Sales documents departments continue to use the same commands, but the Sales
are sent to the new printer.</para> documents are sent to the new printer.</para>
</sect3> </sect3>
<sect3 xml:id="printing-shared-headers"> <sect3 xml:id="printing-shared-headers">
<title>Header Pages</title> <title>Header Pages</title>
<para>It can be difficult for users to locate their documents in <para>It can be difficult for users to locate their documents
the stack of pages produced by a busy shared printer. in the stack of pages produced by a busy shared printer.
<emphasis>Header pages</emphasis> were created to solve this <emphasis>Header pages</emphasis> were created to solve this
problem. A header page with the user name and document name problem. A header page with the user name and document name
is printed before each print job. These pages are also is printed before each print job. These pages are also