#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: cups 1.4b2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2009-01-10 21:21-0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Translate Toolkit 1.2.1\n"

#: ./spec-browsing.html:1
msgid "CUPS Browse Protocol"
msgstr ""

#: ./spec-browsing.html:2
msgid "Programming"
msgstr ""

#: ./spec-browsing.html:3
msgid "Introduction"
msgstr ""

#: ./spec-browsing.html:4
msgid ""
"This specification describes the CUPS browsing protocol which is used for "
"printer sharing. The protocol is a UDP/IP-based broadcast service that "
"operates on IP service port 631 by default. Each broadcast packet describes "
"a single printer or class being shared."
msgstr ""

#: ./spec-browsing.html:5
msgid ""
"For simple networks with a single subnet, a CUPS system sharing a printer "
"(the <em>server</em>) will periodically broadcast that printer's "
"availability and status information to the subnet. Every other CUPS system "
"on the subnet (the <em>clients</em>) will receive the broadcast and make "
"that printer available to local users. If a client stops receiving "
"broadcasts from the server, or if the server sends a special \"deleted\" "
"broadcast message, the client will remove its copy of the printer."
msgstr ""

#: ./spec-browsing.html:6
msgid ""
"For larger networks with multiple subnets, a relay configuration can be used "
"where one or more client systems poll the server and then broadcast the "
"availability and status information for the server's shared printers to the "
"clients' local subnets."
msgstr ""

#: ./spec-browsing.html:7
msgid ""
"A key feature of CUPS printer sharing is support for <em>implicit "
"classes</em>, which are automatically-created classes for printers that are "
"shared by multiple servers. These implicit classes provide automatic load "
"balancing and fail-safe printing functionality transparently to the user."
msgstr ""

#: ./spec-browsing.html:8
msgid "Security Considerations"
msgstr ""

#: ./spec-browsing.html:9
msgid ""
"Like most discovery protocols, CUPS browse packets are not encrypted or "
"signed, so it is possible for malicious systems on a network to advertise or "
"remove printers on that network to cause denial of service or information "
"disclosure. In order to combat this, CUPS logs incoming browse packets and "
"provides access controls to limit browse packet reception to known hosts."
msgstr ""

#: ./spec-browsing.html:10
msgid "Browse Packet Format"
msgstr ""

#: ./spec-browsing.html:11
msgid ""
"Each broadcast packet is an ASCII text string of up to 1450 bytes ending "
"with a line feed (0x0a). The general format is:"
msgstr ""

#: ./spec-browsing.html:12
msgid ""
"printer-type printer-state printer-uri \"printer-location\" \"printer-info\" "
"\"printer-make-and-model\" name=value name2=value2 ..."
msgstr ""

#: ./spec-browsing.html:13
msgid ""
"Each of the fields contains the value of the corresponding IPP attribute. "
"The trailing \"name=value\" information is used to convey default job template "
"attribute values (job-sheets-default, media-default, etc.), authentication "
"requirements (auth-info-required), and additional IPP URI options that are "
"requested by the server (ipp-options)."
msgstr ""

#: ./spec-browsing.html:14
msgid "ABNF Definition"
msgstr ""

#: ./spec-browsing.html:15
msgid ""
"The following ABNF definition [RFC4234, RFC3986] defines the format of each "
"browse packet:"
msgstr ""