From 8ea9c80a6e2ab8a7012f4b22c585a156f0e5c121 Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Mon, 30 Sep 2002 21:55:17 +0000 Subject: * adding some notes on the wins failover stuff * fixing some typos after running printing.sgml through ispell (This used to be commit d20be2e868015266ef3b33f353e1c9a2e6d6b7e1) --- docs/docbook/devdoc/printing.sgml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'docs/docbook/devdoc/printing.sgml') diff --git a/docs/docbook/devdoc/printing.sgml b/docs/docbook/devdoc/printing.sgml index c95d5460b7..8259fead5f 100644 --- a/docs/docbook/devdoc/printing.sgml +++ b/docs/docbook/devdoc/printing.sgml @@ -23,7 +23,7 @@ of certain features of Windows client printing. -Printing Interface to Various Backends +Printing Interface to Various Back ends @@ -39,11 +39,11 @@ in printing.h. delete a job from the queue pause a job in the print queue result a paused print job in the queue - submit a jobn to the print queue + submit a job to the print queue -Currently there are only two printing backend implementations +Currently there are only two printing back end implementations defined. @@ -75,7 +75,7 @@ queue contents displayed to clients will be diminished as well. -The list of currently opened print queue TDB's can eb found +The list of currently opened print queue TDB's can be found be examining the list of tdb_print_db structures ( see print_db_head in printing.c ). A queue TDB is opened using the wrapper function printing.c:get_print_db_byname(). The function ensures that smbd @@ -125,7 +125,7 @@ the id reported by lpq. In order to match a 32-bit Windows jobid onto a 16-bit lanman print job -id, smbd uses an in memory TDB to match the former to a number approriate +id, smbd uses an in memory TDB to match the former to a number appropriate for old lanman clients. @@ -180,8 +180,8 @@ clients and not the actual listing from the "lpq command". The NT_DEVICEMODE stored as part of the printjob structure is used to store a pointer to a non-default DeviceMode associated with the print job. The pointer will be non-null when the client included a Device -Mode in the OpePrinterEx() call and subsequently submitted a job for -printing on that sam handle. If the client did not include a Device +Mode in the OpenPrinterEx() call and subsequently submitted a job for +printing on that same handle. If the client did not include a Device Mode in the OpenPrinterEx() request, the nt_devmode field is NULL and the job has the printer's device mode associated with it by default. -- cgit