Attachment 24896 Details for Bug 42473 – file.diff

[patch] file.diff

file.diff (text/plain), 17.68 KB, created by Christian Brueffer on 2002-09-06 11:30:02 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Christian Brueffer

Created: 2002-09-06 11:30:02 UTC

Size: 17.68 KB

patch

obsolete

>--- book.sgml.fixes	Thu Sep  5 07:42:09 2002
>+++ book.sgml.whitespace	Thu Sep  5 16:07:45 2002
>@@ -75,7 +75,7 @@
> 	applications, and demand for it rapidly increased across the
> 	corporation.  Large, high-capacity laser printers designed for office
> 	printing appeared on the scene.  Printing went from 150 to 300 to
>-	600dpi for the common desktop laser printer.</para>
>+	600 dpi for the common desktop laser printer.</para>
> 
>       <para>Today organizational network printing is complex, and printers
> 	themselves are more complicated.  Most organizations find that sharing
>@@ -179,9 +179,9 @@
> 	  user.  Although a single company holding control over a standard can
> 	  guarantee compliance, it does significantly raise the cost of the
> 	  printer.  As a result, PostScript has not met with much success in
>-	  the lower-end laser and inkjet Windows printing market, despite the fact
>-	  that Adobe distributes PostScript software operating system drivers
>-	  for free.</para>
>+	  the lower-end laser and inkjet Windows printing market, despite the
>+	  fact that Adobe distributes PostScript software operating system
>+	  drivers for free.</para>
> 
> 	<para>One issue that is a concern when networking PostScript printers
> 	  is the selection of banner page, (also known as header page, or
>@@ -605,7 +605,7 @@
> 	    first defined by Intel and Microsoft and later used by IBM and
> 	    Microsoft.</para>
> 
>-	  <para>The LPD protocol is defined in RFC1179. This network protocol
>+	  <para>The LPD protocol is defined in RFC1179.  This network protocol
> 	    is the standard print protocol used on all UNIX systems.  LPD
> 	    client implementations exist for all Windows operating systems and
> 	    DOS.  Microsoft has written LPD for the Windows NT versions, the
>@@ -1190,7 +1190,7 @@
> 	    <para>If the printer is PostScript and cannot print ASCII, make
> 	      sure that the "No banner page control flag" is checked to turn
> 	      off banner pages.  Accessible under Port settings, this flag is
>-	      overridden if the <filename>/etc/printcap</filename>file
>+	      overridden if the <filename>/etc/printcap</filename> file
> 	      specifies no banner pages.</para>
> 	  </step>
> 
>@@ -1201,7 +1201,7 @@
> 	      called with the <option>-c</option> option.  This is equivalent
> 	      to the local invocation of <filename>/usr/bin/lpr -l</filename>.
> 	      With the flag checked, the code is F, (formatted) meaning that
>-	      the <literal>if</literal>filter gets called without the
>+	      the <literal>if</literal> filter gets called without the
> 	      <option>-c</option> option.  This is equivalent to the default
> 	      invocation <filename>/usr/bin/lpr</filename>.  (This is also an
> 	      issue under Windows NT, which retypes the print job to text if
>@@ -1273,7 +1273,8 @@
> 
> 	  <step>
> 	    <para>In the Installed Network Software window, "Microsoft TCP/IP
>-	      Printing" should be listed as well as "TCP/IP Protocol". If it is, stop here; otherwise continue.</para>
>+	      Printing" should be listed as well as "TCP/IP Protocol". If it
>+	      is, stop here; otherwise continue.</para>
> 	  </step>
> 	  
> 	  <step>
>@@ -1448,7 +1449,8 @@
> 	    Q150930.  With Windows NT 3.51, and 4.0 up to service pack 1 the
> 	    change is global.  Starting with NT 4.0 Service pack 2 the change
> 	    can be applied to specific print queues, (see Knowledge Base
>-	    article ID Q168457). This registry change also works for Windows 2000.</para>
>+	    article ID Q168457). This registry change also works for
>+	    Windows 2000.</para>
> 
> 	  <para>Under Windows NT 4.0, the change is:</para>
> 
>@@ -1607,7 +1609,7 @@
>       <para>Normally, under Windows printing, virtually all graphical programs
> 	print through the Windows printer driver.  This is true even of basic
> 	programs such as Notepad.  For example, an administrator may have a
>-	DOS batch file named <filename>filename.txt</filename>containing the
>+	DOS batch file named <filename>filename.txt</filename> containing the
> 	following line:</para>
> 
>       <programlisting>echo \033&amp;k2G &gt; lpt1:</programlisting>
>@@ -1758,7 +1760,7 @@
> 	printers, as well as defined remote printers. Several programs also
> 	are used to manipulate jobs in the print spools that LPD manages, as
> 	well as the user programs to submit them from the UNIX command prompt.
>-	All of these programs use the <filename>/etc/printcap</filename>file,
>+	All of these programs use the <filename>/etc/printcap</filename> file,
> 	which is the master control file for the printing system.</para>
> 
>       <para>Back when printing was mostly text, it was common to place
>@@ -1781,19 +1783,19 @@
> 	description lines are often quite long, they are often written to span
> 	multiple lines by escaping intermediate newlines with the backslash
> 	(<literal>\</literal>) character.  The
>-	<filename>/etc/printcap</filename>file, as supplied, defines a single
>-	printer queue, <literal>lp</literal>.  The <literal>lp</literal>queue
>+	<filename>/etc/printcap</filename> file, as supplied, defines a single
>+	printer queue, <literal>lp</literal>.  The <literal>lp</literal> queue
> 	is the default queue.  Most UNIX-supplied printing utilities send
> 	print output to this queue if no printer is specified by the user.  It
> 	should be set to point to the most popular print queue with
> 	<emphasis>local</emphasis> UNIX print users, (i.e., users that have
> 	shell accounts).</para>
> 
>-      <para>The layout of <filename>/etc/printcap</filename>is covered in the
>+      <para>The layout of <filename>/etc/printcap</filename> is covered in the
> 	manual page, which is reached by running the <userinput>man
> 	  printcap</userinput> command. The stock
> 	<filename>/etc/printcap</filename> file at the line defining the spool
>-	<literal>lp</literal>shows:</para>
>+	<literal>lp</literal> shows:</para>
> 
>       <programlisting>#
> lp|local line printer:\
>@@ -1845,7 +1847,7 @@
> 	  directories <emphasis>must</emphasis> be different from each other,
> 	  or the spooler gets confused and doesen't print.</para>
> 
>-	<para>After the <filename>/etc/printcap</filename>is modified, the
>+	<para>After the <filename>/etc/printcap</filename> is modified, the
> 	  root user must create the <filename>/var/spool/output/NEC</filename>
> 	  directory and assign ownership of it to the <username>bin</username>
> 	  user, assign group ownership to <username>daemon</username>, and set
>@@ -1875,7 +1877,7 @@
> 	  <listitem>
> 	    <para>During FreeBSD installation, if the administrator knows a
> 	      lot of print jobs are going to go through the spooler,
>-	      <filename>/var</filename>should be set to a large
>+	      <filename>/var</filename> should be set to a large
> 		amount of free space.</para>
> 	  </listitem>
> 
>@@ -1902,7 +1904,7 @@
> 	
> 	<para>In addition to spools, the following other capabilities are
> 	  usually placed in a production
>-	  <filename>/etc/printcap</filename>file.</para>
>+	  <filename>/etc/printcap</filename> file.</para>
> 	
> 	<para>The entry <literal>fo</literal> prints a form feed when the
> 	  printer is opened.  It is handy for HPPCL (HP LaserJets) or other
>@@ -1947,7 +1949,7 @@
> 	<para>Hardware print server boxes, such as the HP JetDirect internal
> 	  and external cards, need some additional capabilities defined in the
> 	  <filename>/etc/printcap</filename> entry; <literal>rp</literal>, for
>-	  remote print spool, and <literal>rm</literal>for remote machine
>+	  remote print spool, and <literal>rm</literal> for remote machine
> 	  name.</para>
> 
> 	<para>The <literal>rm</literal> capability is simply the DNS or
>@@ -2018,7 +2020,7 @@
> 
> 	<para>The last two important printcap capabilities concern print
> 	  filters, <literal>if</literal> (input filter) and
>-	  <literal>of</literal> (output filter). If defined, incoming print
>+	  <literal>of</literal> (output filter).  If defined, incoming print
> 	  jobs are run through the filters that these entries point to for
> 	  further processing.</para>
> 
>@@ -2084,7 +2086,7 @@
> 	  <sect4>
> 	    <title>Output Filters</title>
> 
>-	    <para>These are specified by the <literal>of</literal>capability.
>+	    <para>These are specified by the <literal>of</literal> capability.
> 	      Output filters are much more complicated than input filters and
> 	      are hardly ever used in normal circumstances.  They also
> 	      generally require a compiled program somewhere, either directly
>@@ -2117,8 +2119,8 @@
> 
> 	  <para>If the printer is a PostScript printer, and doesn't support
> 	    standard ASCII, then dumping UNIX text to it doesn't work.  But
>-	    then, neither would dumping MS-DOS text to it. (Raw text printing
>-	    on PostScript printers is discussed later in this chapter.) Note
>+	    then, neither would dumping MS-DOS text to it.  (Raw text printing
>+	    on PostScript printers is discussed later in this chapter.)  Note
> 	    also that if the printer is connected over the network to an HP
> 	    JetDirect hardware print server, internal or external, the TEXT
> 	    queue on the hardware print automatically adds the extra Carriage
>@@ -2200,8 +2202,8 @@
> 	  <para>Although most filters are built by scripts or programs and are
> 	    added to the UNIX machine by the administrator, there is one
> 	    filter that is supplied with the FreeBSD operating system is very
>-	    useful for raw text files: the <literal>pr</literal>filter.  It is
>-	    most commonly used when printing from the UNIX command shell. The
>+	    useful for raw text files: the <literal>pr</literal> filter.  It is
>+	    most commonly used when printing from the UNIX command shell.  The
> 	    <literal>pr</literal> filter paginates and applies headers and
> 	    footers to ASCII text files.  It is automatically invoked with the
> 	    <option>-p</option> option used with the <command>lpr</command>
>@@ -2222,8 +2224,8 @@
> 	  <para>Unfortunately, the canned banner page supplied in the LPD
> 	    program prints only on a text-compatible printer.  If the attached
> 	    printer understands only PostScript and the administrator wants to
>-	    print banner pages, it is possible to install a filterinto the
>-	    <filename>/etc/printcap</filename>file to do this.</para>
>+	    print banner pages, it is possible to install a filter into the
>+	    <filename>/etc/printcap</filename> file to do this.</para>
> 
> 	  <para>The following filter is taken from the FreeBSD Handbook.  I've
> 	    slightly changed it's invocation for a couple of reasons.  First,
>@@ -2273,7 +2275,7 @@
> 
> cat &amp;&amp; exit 0</programlisting>
> 
>-	  <para>Here is the <filename>make-ps-header</filename>listing.</para>
>+	  <para>Here is the <filename>make-ps-header</filename> listing.</para>
> 
> 	  <programlisting>#!/bin/sh
> # Filename /usr/local/libexec/make-ps-header
>@@ -2407,7 +2409,7 @@
> 	  <para>The username of the submitter can be easily forged, if the job
> 	    is remotely submitted over the network from a client (practically
> 	    all jobs in a Windows client printing environment are remotely
>-	    submitted). Although some LPR clients can be set to authenticate,
>+	    submitted).  Although some LPR clients can be set to authenticate,
> 	    and the <literal>rs</literal> capability can be set to enforce
> 	    authentication, not all can, especially Windows LPR
> 	    clients.</para>
>@@ -2486,7 +2488,7 @@
> 	model name of the printer, the "Auto printer driver install" feature
> 	of Windows NT and Win95/98 is activated.  This automatically loads the
> 	correct printer driver if the user clicks on the print queue in
>-	Network Neighborhood under Windows 95 or NT 4.0. The restriction, of
>+	Network Neighborhood under Windows 95 or NT 4.0.  The restriction, of
> 	course, is that the printer model must be in the Windows client driver
> 	database.</para>
> 
>@@ -2688,7 +2690,7 @@
> 	  generic local line printer.  Since this print queue generally has a
> 	  filter placed on it to format jobs from the UNIX print queue
> 	  properly, it should not be visible on the SMB network (i.e., visible
>-	  in Network Neighborhood). The second queue,
>+	  in Network Neighborhood).  The second queue,
> 	  <literal>nec-crlf</literal>, has a filter that converts UNIX text to
> 	  text that prints without stairstepping, so it also should be hidden
> 	  from the SMB network.  The third, <literal>nec-raw</literal>, should
>@@ -2702,12 +2704,12 @@
> 	  as a set of defaults for printers that are going to be shared out.
> 	  Next, the <filename>/etc/printcap</filename> file is read to get a
> 	  list of all printers on the server.  Last, each printer is checked
>-	  for a service name in the <filename>smb.conf</filename>file that
>+	  for a service name in the <filename>smb.conf</filename> file that
> 	  contains settings that override the set of defaults.</para>
> 
> 	<para>In the listing of what resources are visible on the network,
> 	  both <literal>nec-crlf</literal> and <literal>nec-raw</literal>
>-	  print queues are visible, and <literal>lp</literal>and
>+	  print queues are visible, and <literal>lp</literal> and
> 	  <literal>nec-ps-banner</literal> is not. <literal>lp</literal> is
> 	  not visible because there is a specific entry,
> 	  <literal>[lp]</literal> in the <filename>smb.conf</filename> file
>@@ -2734,7 +2736,7 @@
> 	and Windows NT printing interoperability with NT as a print client
> 	passing jobs to the FreeBSD system.  What happens if the situation is
> 	reversed and the FreeBSD system is itself a printing client of another
>-	LPD server? This situation can arise in a mixed UNIX/NetWare or
>+	LPD server?  This situation can arise in a mixed UNIX/NetWare or
> 	UNIX/NT environment.  The administrator may elect to forgo the use of
> 	Samba, and use an NT server to provide print services.  Alternatively,
> 	the administrator may have existing DOS Novell IPX clients that they
>@@ -2755,8 +2757,8 @@
> 	remotely from an NT server that has LPR installed as a port for it's
> 	printers.</para>
> 
>-      <para>Following is a sample <filename>/etc/printcap</filename>file entry
>-	that defines a print queue named <literal>tank</literal>on the FreeBSD
>+      <para>Following is a sample <filename>/etc/printcap</filename> file entry
>+	that defines a print queue named <literal>tank</literal> on the FreeBSD
> 	system pointed to an NT LPD server queue named
> 	<literal>sherman</literal> on a NT Server named
> 	<hostid role="fqdn">big.army.mil</hostid> in the DNS.  This uses the
>@@ -2813,7 +2815,7 @@
> 	  through a filter that allows raw UNIX text sent to it to print
> 	  properly.  For example, if an HP LaserJet printer that doesn't have
> 	  PostScript is connected to the server, the
>-	  <literal>lp</literal>queue specifies in the
>+	  <literal>lp</literal> queue specifies in the
> 	  <filename>/etc/printcap</filename> file the CRLF filter listed
> 	  earlier.  On the other hand, if an Apple Laserwriter that doesn't
> 	  support ASCII is connected to the server, the
>@@ -2856,7 +2858,7 @@
> 	    queues are on and view them there.</para>
> 
> 	  <para>The UNIX shell command used to view the queue is the
>-	    <command>lpq</command> command. It is frequently run as
>+	    <command>lpq</command> command.  It is frequently run as
> 	    <userinput>lpq -a</userinput> which shows jobs in all queues.  The
> 	    following is a sample output of the command:</para>
> 
>@@ -2981,9 +2983,9 @@
> 	  <para>Just as the root user can manipulate remotely submitted jobs
> 	    in the print queue, print jobs can be remotely managed by regular
> 	    users with the LPR clients that created them. Unfortunately, some
>-	    LPR clients, such as the ACITS LPR client for Win95, don't have enough programming to be
>-	    able to do this.  Others, like the Win31 client, can manipulate
>-	    the print jobs remotely.</para>
>+	    LPR clients, such as the ACITS LPR client for Win95, don't have
>+	    enough programming to be able to do this.  Others, like the Win31
>+	    client, can manipulate the print jobs remotely.</para>
> 
> 	  <para>FreeBSD offers some level of protection against inadvertent
> 	    deletion of print jobs from remote hosts by restricting
>@@ -3022,8 +3024,8 @@
> 	<para>The Ghostscript home page is located at
> 	  <ulink url="http://www.cs.wisc.edu/~ghost/">http://www.cs.wisc.edu/~ghost/</ulink>
> 	  and contains the most current version of the program.  A prebuilt
>-	  FreeBSD binary of Ghostscript is located in the Packages section of the
>-	  FreeBSD CDROM.  This can be installed on the FreeBSD system by
>+	  FreeBSD binary of Ghostscript is located in the Packages section of
>+	  the FreeBSD CDROM.  This can be installed on the FreeBSD system by
> 	  selecting the package from the prepackaged software list that is
> 	  accessed through the <command>/stand/sysinstall</command>
> 	  installation program.  Many packaged programs on the CD depend on
>@@ -3054,7 +3056,7 @@
> 	  </step>
> 
> 	  <step>
>-	    <para>In the <filename>gs5.03</filename>directory, copy the
>+	    <para>In the <filename>gs5.03</filename> directory, copy the
> 	      <filename>lprsetup.sh</filename>,
> 	      <filename>unix-lpr.txt</filename>, and
> 	      <filename>unix-lpr.sh</filename> files to
>@@ -3091,7 +3093,7 @@
> 	  <step>
> 	    <para>If the printer that you defined in the
> 	      <filename>lprsetup.sh</filename> file is a monochrome printer,
>-	      remove the <literal>"-dBitsPerPixel=${bpp}"</literal>and
>+	      remove the <literal>"-dBitsPerPixel=${bpp}"</literal> and
> 	      <literal>"$colorspec"</literal> entries on the
> 	      <literal>gs</literal> invocation line and save the file.
> 	      Otherwise, if it is a color definition leave them in.  For
>@@ -3152,8 +3154,8 @@
>       <sect2>
> 	<title>a2ps filter</title>
> 
>-	<para>Another handy utility is the <command>a2ps</command> filter, short for
>-	  ASCII-to-PostScript.  This program takes an incoming ASCII
>+	<para>Another handy utility is the <command>a2ps</command> filter, short
>+	  for ASCII-to-PostScript.  This program takes an incoming ASCII
> 	  datastream and converts it into PostScript.  It can also print
> 	  multiple pages on a single sheet of paper by shrinking them down. It
> 	  is a useful tool for a printer that cannot interpret ASCII, such as
>--- corp-net-guide.whitespace.diff ends here ---

Actions: View | Diff

Attachments on bug 42473: 24895 | 24896