Author: jsmeix Date: Thu Sep 18 16:55:02 2008 New Revision: 51291 URL: http://svn.opensuse.org/viewcvs/yast?rev=51291&view=rev Log: Added an explanatory help text for the "Connection Wizard" dialog. Hopefully not too late now for the translators. Modified: trunk/printer/src/helps.ycp Modified: trunk/printer/src/helps.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/printer/src/helps.ycp?rev=51291&r1=51290&r2=51291&view=diff ============================================================================== --- trunk/printer/src/helps.ycp (original) +++ trunk/printer/src/helps.ycp Thu Sep 18 16:55:02 2008 @@ -239,26 +239,26 @@ </p>"), "connection_wizard_dialog" : -// ConnectionWizardDialog help 1/3: +// ConnectionWizardDialog help 1/6: _("<p> <b><big>Specify the Connection</big></b><br> The <b>connection</b> determines which way data is sent to the printer device.<br> If a wrong connection is used, no data can be sent to the device -so that there cannot be any printout.<br> +so that there cannot be any printout. </p>") + -// ConnectionWizardDialog help 2/3: +// ConnectionWizardDialog help 2/6: _("<p> -A connection is specified as so called <b>printer device URI</b>.<br> +<b><big>Printer Device URI</big></b><br> +A connection is specified as so called <b>device URI</b>.<br> Its first word (the so called URI scheme) specifies the kind of data-transfer, -for example 'usb', 'socket', or 'lpd'.<br> +for example 'parallel', 'usb', 'socket', 'lpd', or 'ipp'.<br> After the scheme there are more or less additional parts (separated by slash '/' characters) which specify the details -for this kind of data-transfer. +for this kind of data-transfer.<br> Finally there could be optional parameters (separated by a question mark '?') -of the form option1=value1&option2=value2&option3=value3 -</p>") + -// ConnectionWizardDialog help 3/3: -_("<p> +of the form option1=value1&option2=value2&option3=value3 so that +a full device URI could be for example:<br> +ipp://server.domain:631/printers/queuename?waitjob=false&waitprinter=false<br> Special characters must be percent-encoded (also known as URL encoding). For example a space character ' ' must be written as '%20' and a plus sign '+' must be written as '%2B'.<br> @@ -273,6 +273,139 @@ via LPD protocol with a remote LPD queue name 'lpt1' may have a device URI like:<br> lpd://192.168.100.2/lpt1 +</p>") + +// ConnectionWizardDialog help 3/6: +_("<p> +<b><big>Device URIs for Directly Connected Devices</big></b><br> +Devices which are connected via the parallel port or via USB +are autodetected and the appropriate device URI is autogenerated. +For example:<br> +parallel:/dev/lp0<br> +usb://ACME/FunPrinter<br> +hp:/usb/HP_LaserJet?serial=1234<br> +Usually only the autogenerated device URIs work. +When the device is not autodetected, there is usually no communication +with the device possible and no data can be sent to the device. +</p>") + +// ConnectionWizardDialog help 4/6: +_("<p> +<b><big>Device URIs to Access a Network Printer or a Printserver Box</big></b><br> +A printserver box is a small device with a network connection +and a USB or parallel port connection to connect the actual printer. +A network printer has such kind of device built-in. +Access happens via three different network protocols. +See the manual of your network printer or printserver box +what your particular device supports:<br> +<b>TCP Port (AppSocket/JetDirect)</b><br> +The IP address and a port number is needed to access it. +Often the port number 9100 is the right one. +It is the simplest, fastest, and generally the most reliable protocol. +The matching device URI is:<br> +socket://ip-address:port-number<br> +<b>Line Printer Daemon (LPD) Protocol</b><br> +A LPD runs on the device and provides one or more LPD queues. +The IP address and a LPD queue name is needed to access it. +Almost all network printers and printserver boxes support it. +Often an arbitrary queue name or 'LPT1' works somehow. +But using a correct LPD queue which does not somehow change +the data or add additional formfeeds or banner pages +could be essential for reliable printing. +The matching device URI is:<br> +lpd://ip-address/queue<br> +<b>Internet Printing Protocol (IPP)</b><br> +IPP is the native protocol for CUPS which runs on a real computer +but when IPP is implemented in a small printserver box, +it is often not implemented properly. Only use IPP when the vendor +actually documents official support for it. +The matching device URI is:<br> +ipp://ip-address:port-number/resource<br> +What 'port-number' and 'resource' exactly is depends totally +on the particular network printer or printserver box model.<br> +For <b>more information</b> have a look at<br> +http://www.cups.org/documentation.php/network.html +</p>") + +// ConnectionWizardDialog help 5/6: +_("<p> +<b><big>Device URIs to Print Via a Print Server Machine</big></b><br> +In contrast to a printserver box a print server machine +means a real computer which offers a print service.<br> +Access happens via various different network protocols. +Ask your network administrator what which print server machine +provides in your particular network:<br> +<b>Microsoft Windows/SAMBA (SMB/CIFS)</b><br> +A server name and a printer share name and optionally a workgroup name +is needed to access it. +Furthermore a user name and a password may be required to get access. +A matching full device URI is:<br> +smb://username:password@workgroup/server/printer<br> +For <b>more information</b> have a look at <tt>man smbspool</tt> and<br> +http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share<br> +<b>Traditional UNIX Server (LPR)</b><br> +A Line Printer Daemon (LPD) runs on a traditional UNIX server +and provides one or more LPD queues. +The IP address and a LPD queue name is needed to access it. +The matching device URI is:<br> +lpd://ip-address/queue<br> +<b>CUPS Server</b><br> +Usually you should not set up a local print queue to access +a remote queue on a CUPS server. Instead do the setup +in the <b>Print Via Network</b> dialog. +Only if you really know that you must set up a local print queue +to access a remote queue on a CUPS server proceed here.<br> +IPP is the native protocol for CUPS which runs on a server. +The official IANA port for IPP is 631. +The matching device URI is:<br> +ipp://ip-address:631/printers/queue<br> +<b>Novell Netware Print Server (IPX)</b><br> +To access print queues on a Novell Netware print server, +the RPM package ncpfs must be installed. +The package provides the CUPS backend 'novell' which runs +the <tt>nprint</tt> program which actually sends the data +to a Novell Netware print queue. +A server name and a printer queue name is needed to access it. +Furthermore a user name and a password may be required to get access. +The matching device URI is:<br> +novell://username:password@server/queue<br> +For <b>more information</b> have a look at <tt>man nprint</tt> and +the other documentation in the RPM package ncpfs. +</p>") + +// ConnectionWizardDialog help 6/6: +_("<p> +<b><big>Special Device URIs</big></b><br> +<b>Specify an Arbitrary Device URI</b> +if you know the exact right device URI for your particular case +or to modify an existing device URI in a special way.<br> +<b>Send Print Data to Other Program (pipe)</b><br> +To do this, the RPM package cups-backends must be installed. +The package provides the CUPS backend 'pipe' which runs +the program that you specified here. +The matching device URI is:<br> +pipe:/path/to/targetcommand<br> +<b>Daisy-chain Backend Error Handler (beh)</b><br> +To do this, the RPM package cups-backends must be installed. +The package provides the CUPS backend 'beh'.<br> +The backend 'beh' is a wrapper for the usual backend, +which is then called by beh. +This way beh can, depending on its configuration, +repeat the call of the backend or simply hide the error status +of the backend from being seen by the CUPS daemon. +The matching device URI is:<br> +beh:/nodisable/attempts/delay/originalDeviceURI<br> +If nodisable is '1' beh always exits successfully +so that the queue gets never disabled but on the other hand +print jobs are lost if there is an error.<br> +Attempts is the number of attempts to recall the backend +in case of an error. '0' means infinite retries.<br> +Delay is the number of seconds between two attempts +to call the beckend.<br> +The last parameter is the original URI, which the queue had before.<br> +Example:<br> +beh:/1/3/5/socket://ip-address:port-number<br> +The beh backend tries to access a network printer 3 times with 5 second delay +between the attempts. If access still fails, the queue is not disabled +and the print job is lost.<br> +For <b>more information</b> have a look at <tt>/usr/lib[64]/cups/backend/beh</tt> and<br> +http://www.linuxfoundation.org/en/OpenPrinting/Database/BackendErrorHandler<br> </p>"), "printing_via_network_dialog" : -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org