Translation status

463 Strings 100%
Browse Translate
8,935 Words 100%
57,142 Characters 100%

Strings status

Strings Words Characters
463 8,935 57,142
All strings Browse Translate Zen
11 2,658 16,929
Approved strings Browse Translate Zen
463 8,935 57,142
Translated strings Browse Translate Zen
452 6,277 40,213
Strings waiting for review Browse Translate Zen
2 575 3,776
Translated strings with dismissed checks Browse Translate Zen

Overview

Project website github.com/yast/yast-printer
Project maintainers User avatar ancorgonzalezsosa
Translation license GNU General Public License v2.0 only
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Translations are reviewed by dedicated reviewers.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@github.com:yast/yast-translations.git
Repository branch master
Last remote commit New POT for text domain 'installation'. 9a9a9b5d0c
YaST Jenkins authored 2 weeks ago
Last commit in Weblate Translated using Weblate (Portuguese) a50be99cf8
User avatar RodrigoMacedodb46493176b3407b authored 2 weeks ago
Weblate repository https://l10n.opensuse.org/git/yast-base/master/
File mask po/printer/*.po
Translation file Download po/printer/zh_CN.po
Last change Feb. 16, 2022, 6:19 a.m.
Last change made by Grace Yu
Language Chinese (China) (zh_CN)
Language code zh_CN
Text direction Left to right
Number of plurals 1
Plural type None
Plurals
Plural formula 0
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 463 8,935 57,142
Approved 2% 11 29% 2,658 29% 16,929
Waiting for review 97% 452 70% 6,277 70% 40,213
Translated 100% 463 100% 8,935 100% 57,142
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
JanFebMarAprMayJunJulAugSepOctNovDec

Quick numbers

8,935
Hosted words
463
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar graceyu

Translation approved
<p>
<b><big>Print Queue Overview</big></b><br>
A printer device is not used directly but via a print queue.<br>
When various applications submit print jobs simultaneously,
these jobs are put in a queue and are sent one after the other to the printer
device.<br>
It is possible to have several different print queues for the same printer
device.
For example a second queue with a monochrome-only driver for a color device
or a PostScript queue and a queue with a PCL driver for a PostScript+PCL printer.
</p>
<p>
<b><big>打印队列概述</big></b><br>
打印机设备不能直接使用，而需要通过打印队列来使用。<br>
当有多个应用程序同时提交打印作业时，
这些作业会列入队列，然后逐个发送到打印机
设备。<br>
同一个打印机设备可以有若干个不同的打印队列。例如，
一个彩色设备可以有一个使用黑白驱动程序的二级队列，或者
一个 PostScript+PCL 打印机可以有一个 PostScript 队列和一个
使用 PCL 驱动程序的队列。 </p>
2 years ago
User avatar graceyu

Translation approved
<p>
Regarding firewall:<br>
A firewall is used to protect running server processes
(in this case the CUPS server process 'cupsd')
on your host against unwanted access via network.<br>
Printing via network happens in a trusted internal network
(nobody lets arbitrary users from whatever external network
print on his printer) and usually the users need
physical printer access to get their paper output.<br>
By default the SuSEfirewall lets any network traffic pass
via a network interface which belongs to the 'internal zone'
because this zone is trusted by default.<br>
It does not make sense to do printing in a trusted internal network
with a network interface which belongs to the untrusted 'external zone'
(the latter is the default setting for network interfaces to be safe).
Do not disable firewall protection for CUPS
(i.e. for IPP which uses TCP port 631 and UDP port 631)
for the untrusted 'external zone'.<br>
To make printers accessible in a trusted internal network
and be protected by the firewall against unwanted access
from any external network (in particular from the Internet),
assign the network interface which belongs to the internal network
to the internal zone of the firewall.
Use the YaST Firewall setup module to do this fundamental setup
to gain security plus usefulness in your network and
sharing printers in a trusted internal network
will work without any further firewall setup.<br>
For details see the openSUSE support database
article 'CUPS and SANE Firewall settings' at<br>
http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings
</p>
<p>
防火墙相关：<br>
防火墙用来保护在您的主机上运行的服务器进程
（本例中是 CUPS 服务器进程“ "cupsd”"）
不受无谓的网络访问。<br>
网络打印发生在可信的内部网络中
（没人会让外部网络的任意用户在他的打印机上
打印），
通常，用户需要能够接触
物理的打印机来取回他们打印的纸张。<br>
SuSEfirewall 默认允许任何来自属于“ "内部区域”"
的网络接口的网络流量通过，
因为此区域默认是可信的。<br>
通过属于不可信的“外部区域”的网络接口
在可信内部网络打印是不安全的（出于安全考虑，
网络接口默认属于外部区域）。
请不要禁用 CUPS 的针对不可信的“ "外部区域”"
的防火墙保护（例如 IPP 使用的 TCP 端口 631
和 UDP 端口 631）。<br>
要在可信的内部网络使用打印机，
且保护其不受任何外部网络的无谓访问
（尤其是因特网访问），
请向防火墙的内部区域指派
属于内部网络的网络接口。
可以使用 YaST 防火墙设置模块来完成此基础设置，
以实现网络中的安全和易用。
在可信的内部网络分享打印机
将不需要额外的防火墙设置。<br>
详情请见 openSUSE 支持数据库文章
《CUPS 和 SANE 的防火墙设置》，网址为：<br>
http://zh.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
If you can access remote CUPS servers for printing
but those servers do not publish their printer information via network
or when you cannot accept incoming information about published printers
(e.g. because you must have firewall protection for the network zone
in which printers are published), you can request printer information
from CUPS servers (provided the CUPS servers allow your access).<br>
For each CUPS server which is requested, a cups-polld process
is launched by the CUPS daemon process (cupsd) on your host.
By default each cups-polld polls a remote CUPS server
every 30 seconds for printer information.
</p>
<p>
如果您可以访问远程 CUPS 服务器来打印，
但这些服务器没有通过网络发布它们的打印机信息，
或者当您不能接受有关发布打印机的进站信息时
（例如您的防火墙屏蔽了打印机发布到的网络区域），
您可以从 CUPS 服务器请求打印机信息（假设 CUPS 服务器允许您访问）。<br>
您主机上的 CUPS 守护程序进程 (cupsd) 会为
每个被请求的 CUPS 服务器启动一个 cups-polld 进程。
默认情况下，每个 cups-polld 每隔 30 秒
向远程 CUPS 服务器轮询一次打印机信息。
</p>
2 years ago
User avatar graceyu

Translation approved
<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>Windows (R) or Samba (SMB/CIFS)</b><br>
To access a SMB printer share, the RPM package samba-client must be installed.
The package provides the CUPS backend 'smb' which is a link to
the <tt>/usr/bin/smbspool</tt> program which actually sends the data
to a SMB printer share.<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.
Have in mind that spaces and special characters in those values
must be percent-encoded (see above).<br>
By default CUPS runs backends (here smbspool) as user 'lp'.
When printing in an Active Directory (R) environment (AD)
the user 'lp' is not allowed to print in this environment
so that the traditional way to print via smbspool as user 'lp'
would not work.<br>
For printing in an AD environment additionally
the RPM package samba-krb-printing must be installed.
In this case the CUPS backend 'smb' link
is changed to <tt>/usr/bin/get_printing_ticket</tt>
which is a wrapper to run smbspool as the original user
who submitted a particular print job.
When the Kerberos protocol is used for authentication
in an AD environment, a user gets a ticket granting ticket (TGT)
via the display manager during login at the Gnome or KDE desktop.
When smbspool is run as the original user who submitted
a particular print job, it can access the TGT of this user
and use it to pass the printing data to the SMB printer share
even in an AD environment with Kerberos authentication.
In this case neither a fixed user name nor a fixed password
has to be specified for authentication.
A precondition is that get_printing_ticket runs on the same host
where the user who submitted a particular print job is logged in.
This means that it must be set up on the workstation
for the particular user who will submit such print jobs
and the user's workstation must send its printing data
directly to the SMB printer share in the AD environment.
In particular it does not work on a separated CUPS server machine
where users who submit print jobs are not logged in.<br>
For the traditional way a matching full device URI is:<br>
smb://username:password@workgroup/server/printer<br>
For example 'John Doe' with password '@home!' may use something like
the following device URI to access a 'Fun Printer 1000+' share:<br>
smb://John%20Doe:%40home%21@MYGROUP/homeserver/Fun%20Printer%201000%2B<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>
'Windows' and 'Active Directory' are registered trademarks
of Microsoft Corporation in the United States and/or other countries.<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>
</p>
<p>
<b><big>用于通过打印服务器计算机打印的设备 URI</big></b><br>
与打印服务器盒相反，打印服务器计算机
表示一台会提供打印服务的真实计算机。<br>
访问是通过各种不同的网络协议来进行的。
请咨询网络管理员了解您的特定网络中提供了哪种
打印服务器计算机：<br>
<b>Windows (R) 或 Samba (SMB/CIFS)</b><br>
要访问 SMB 打印机共享，必须安装 RPM 包 samba-client。
该包提供了 CUPS 后端“smb” "smb"，它链接到 <tt>/usr/bin/smbspool</tt> 程序，
后者是将数据发送到
SMB 打印机共享的实际执行者。<br>
访问它需要服务器名称和打印机共享名称，
也可能需要工作组名称。
此外，可能还需要提供用户名和口令，以获取访问权。
请记住，这些值中的空格和特殊字符
必须经过百分号编码（见上方）。<br>
默认情况下，CUPS 以用户“lp” "lp" 的身份运行后端（此处为 smbspool）。
在 Active Directory (R) 环境中打印时，
不允许用户“lp” "lp" 在此环境中打印，
因此，以用户“lp” "lp" 身份通过 smbspool 打印的传统方法
行不通。<br>
要在 AD 环境中打印，必须另外安装
RPM 包 samba-krb-printing。
如此，CUPS 后端“smb” "smb" 链接
会变成 <tt>/usr/bin/get_printing_ticket</tt>，
这是一个以提交特定打印作业的原始用户身份运行 smbspool 的
封装程序。
如果在 AD 环境中使用 Kerberos 协议
进行身份验证，用户在登录 Gnome 或 KDE 桌面期间，
将通过显示管理器获取票据授予票据 (TGT)。
如果以提交特定打印作业的原始用户身份
运行 smbspool，smbspool 该程序将可以访问此用户的 TGT，
并使用该 TGT 来向 SMB 打印机共享传递打印数据，
即使是在使用 Kerberos 身份验证的 AD 环境中也是如此。
如此，就不需要指定固定的用户名或固定的口令
进行身份验证，
前提条件是 get_printing_ticket 要在提交特定打印作业的
用户所登录的那台主机上运行。
这意味着，必须在用户将要提交此类
打印作业的的工作站上
安装该包，并且该用户的工作站必须将其打印数据
直接发送到 AD 环境中的 SMB 打印机共享。
具体而言，在提交打印作业的用户没有登录的另一台 CUPS 服务器计算机上，
这种方法将不起作用。<br>
对于传统方法，匹配的完整设备 URI 为：<br>
smb://用户名:口令@工作站/服务器/打印机<br>
例如，口令为“ "@home!”的用户“" 的用户 "John Doe”" 可以使用类似于下面的
设备 URI 来访问“ "Fun Printer 1000+”" 共享：<br>
smb://John%20Doe:%40home%21@MYGROUP/homeserver/Fun%20Printer%201000%2B<br>
有关<b>更多信息</b>，请参见 <tt>man smbspool</tt> 和<br>
http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share<br>
“"Windows”和“" 和 "Active Directory”" 是 Microsoft Corporation 在
美国和/或其他国家/地区的注册商标。<br>
<b>传统 UNIX 服务器 (LPR)</b><br>
行式打印机守护程序 (LPD) 在传统 UNIX 服务器上运行，
并提供一个或多个 LPD 队列。
访问它需要 IP 地址和 LPD 队列名。
匹配的设备 URI 为：<br>
lpd://IP 地址/队列<br>
<b>CUPS 服务器</b><br>
通常情况下，不应设置本地打印队列
来访问 CUPS 服务器上的远程队列，而应在
<b>通过网络打印</b>对话框中进行设置。
除非您确定必须设置本地打印队列
才能访问 CUPS 服务器上的远程队列时才应如此。<br>
IPP 是在服务器上运行的 CUPS 的本机协议。
IPP 的官方 IANA 端口为 631。
匹配的设备 URI 为：<br>
ipp://IP 地址:631/打印机/队列<br>
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
<b><big>Device URIs for Directly Connected Devices</big></b><br>
Devices which are connected via USB
are autodetected and the appropriate device URI is autogenerated.
For example:<br>
usb://ACME/Fun%20Printer?serial=A1B2C3<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.<br>
To access a HP printer or all-in-one device via the backend 'hp',
the RPM package hplip must be installed.
The package provides HP's printing and scanning software HPLIP.<br>
In contrast devices which are connected via bluetooth
are not autodetected so that the device URI must be manually specified.
Example device URI:<br>
bluetooth://1A2B3C4D5E6F<br>
To access a device via bluetooth, the RPM package bluez-cups must be installed.
The package provides the CUPS backend 'bluetooth' which actually sends the data
to a bluetooth printer.
</p>
<p>
<b><big>直连设备的设备 URI</big</b><br>
系统会自动检测到通过 USB 连接的设备，并自动 生成合适的设备 URI。
例如：<br>
usb://ACME/Fun%20Printer?serial=A1B2C3<br>
hp:/usb/HP_LaserJet?serial=1234<br>
通常只有自动生成的设备 URI 才能用。
当系统没有自动检测到设备时，通常无法
与设备建立通信和发送数据到设备。<br>
要通过后端 "hp" 访问 HP 打印机或多合一设备，
必须安装 RPM 软件包 hplip。
该软件包提供了 HP 的打印和扫描软件 HPLIP。<br>
相反，系统不能自动检测到通过蓝牙连接的设备，
因此必须手动指定设备 URI。
示例设备 URI：<br>
bluetooth://1A2B3C4D5E6F<br>
要通过蓝牙访问设备，必须安装 RPM 软件包 bluez-cups。
该软件包提供了将数据发送到蓝牙打印机的 CUPS 后端
"bluetooth"。
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
The <b>driver</b> determines that the right data is produced for the
specific printer model.<br>
If a wrong driver is assigned, wrong data is sent to the printer
which results bad looking printout, chaotic printout, or no printout at all.<br>
You can either select another driver and modify its driver option settings later
or keep the currently used driver and modify its driver option settings now.<br>
Some driver option settings must match to your particular printer.
For example the default paper size setting of the driver
must match to the paper which is actually loaded in your printer.<br>
For other driver option settings you can choose what you like.
For example any choice of the available printing resolutions
should work for the particular driver.
Nevertheless it may happen that your particular printer fails to print
with high resolution. For example when you have a laser printer
which has insufficient built-in memory to process high resolution pages.<br>
When you exchange the currently used driver by another one,
you must first apply this change to the print queue
so that the new driver is used for the queue
(i.e. you must finish this dialog as a first step)
and then in a second step you can adjust all driver options
by using this dialog again.<br>
Initially the input field for the driver search string is preset
with the description of the currently used driver when the connection was not changed.
This results usually only one single driver which matches
so that you would have to enter a less specific driver search string
to get also other drivers or you use the 'Find More' button.
If no driver matches, it does not mean that there is no driver available.
Therefore you can enter whatever you like as driver search string
and search through all available driver descriptions.
</p>
<p>
<b>驱动程序</b>决定了指定型号的打印机
可以输出的正确数据。<br>
如果指派了错误的驱动程序，会将错误的数据发送到打印机，
这将导致难看、混乱的打印输出，或完全没有打印输出。<br>
您可以选择另一款驱动程序并稍后修改它的驱动程序 选项设置，
也可以保留当前使用的驱动程序并立即修 改它的驱动程序选项设置。<br>
有些驱动程序选项设置必须与您的打印机匹配。
例如，驱动程序的默认纸张大小设置必须与
您打印机中实际装入的纸张匹配。<br>
对于其他驱动程序选项，您可以根据自己的喜好选择。
例如，任何可用打印分辨率都能够用于该驱动程序。
除非您的驱动程序在高分辨率下不能打印。
例如，镭射打印机的内置内存不足以
处理高分辨率的页面。<br>
当您将当前使用的驱动程序更换为另一个驱动程序时，
必须先将此更改应用于打印队列，
以对此队列使用新驱动程序
（例如，作为第一步，您必须完成此对话框），
然后在第二步，您可以再次使用
此对话框调整所有驱动程序选项。<br>
当连接没有更改时，驱动程序搜索字符串输入字段
初始预设为当前使用的驱动程序的描述。
此结果通常是一个匹配的驱动程序，
要获取其他驱动程序，您必须输入一个更宽泛的 驱动程序
搜索字符串，或者使用 “查找更多” 按钮。
如果没有匹配的驱动程序，也不意味着没有驱动程序可用。
因此，您可以输入您需要的字符串作为驱动程序搜索 字符串，
搜索所有可用驱动程序描述。
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
The <b>connection</b> determines how data is sent to the printer device.<br>
If a wrong connection is selected, no data can be sent to the device
so that there cannot be any printout.<br>
If a printer device is accessible via more than one connection type,
it is shown for each connection type.<br>
In particular HP devices are often accessible both via the 'usb:/...'
and the 'hp:/...' connection.
The latter is provided by the HP driver package 'hplip'.
For plain printing, both kinds of connections should work, but for anything else
(e.g. device status via 'hp-toolbox' or scanning with a HP all-in-one device)
the 'hp:/...' connection must be used.<br>
When you exchange the currently used connection with another one,
the input field for the driver search string is preset
with the autodetected model name of the new selected connection.
The drivers for which the driver description matches the model name
are shown by default.<br>
If driver descriptions match the autodetected model name
and if all matching driver descriptions seem to belong to the same model,
the driver descriptions are sorted so that the most reasonable driver
should be listed topmost (but still below the currently used driver).
On the other hand, it does not necessarily mean that this driver is
a reasonable driver for your particular needs.
The topmost listed driver may not work at all for your particular
printer model. The automated driver selection
compares strings (the autodetected model name and the driver
descriptions) so the result can only be a best-guess proposal
how to set up your particular printer model.<br>
Therefore check if the currently preselected values make sense.
Feel free to play around and modify the settings
to what you know works best for your printer.<br>
If no driver description matches the autodetected model name, it does
not necessarily mean that there is no driver available for the model.
Often the model name in the driver descriptions
is different from the autodetected model name.
Therefore you can enter whatever you like as driver search string
and search through all available driver descriptions.
</p>
<p>
<b>连接</b>决定数据发送到打印机设备的方式。<br>
如果选择了一个错误连接，任何数据都无法发送到设备，
因此就不会有任何打印输出。<br>
如果一个打印机设备可以通过多种连接类型访问，
对于每个连接类型，它都会显示出来。<br>
尤其是 HP 设备，往往既可以通过“ "usb:/...”"
也可以通过“ "hp:/...”" 连接访问。
后者是由 HP 驱动程序包“ "hplip”" 提供的。
对于一般打印，可以选择这两种连接中的任何一种，但对于一些特殊任务
（例如通过“ "hp-toolbox”" 获取设备状态或使用 HP 多功能一体机扫描），
就必须使用“ "hp:/...”" 连接。<br>
当您将当前使用的连接更换为另一个连接时，
驱动程序搜索字符串的输入字段将预设为
通过新选择的连接自动检测到的型号名称。
默认会显示驱动程序描述与型号名称匹配的
驱动程序。<br>
如果驱动程序描述与自动检测到的型号名称匹配，
并且所有匹配的驱动程序描述都属于同一个型号，
驱动程序描述会按如下方式排序：
最适合的驱动程序列在最上方（但在当前使用的驱动程序下面）。
另一方面，这并不意味着此驱动程序就一定是能满足
您特殊需要的最佳驱动程序。
列在最上方的驱动程序
或许在您的特定打印机型号上完全不能用。
系统是根据比较字符串
（自动检测到的型号名称与驱动程序描述）
来自动选择驱动程序的，
因此结果只是如何设置
您的特定打印机型号的最佳猜想的建议。<br>
因此，请检查当前预先选中的值是否合适，
如果您知道您的打印机使用哪种驱动程序最合适，
也可以视情况修改设置。<br>
如果没有与自动检测到的型号名称匹配的驱动程序描述，
这也不意味着没有该型号的驱动程序可用。
通常只是因为驱动程序描述中的型号名称
和自动检测到的型号名称不同。
因此，您可以输入您需要的驱动程序搜索字符串，
搜索所有可用驱动程序描述。
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
One of the print queues may be set to be <b>used by default</b>.<br>
Application programs should use such a system default print queue
if no other print queue was specified by the user.
But there is no such thing as the 'one and only' default queue.
Beside a system default queue any user can maintain his own
default queue setting and furthermore any application program
may implement its own particular way of default queue setting
(e.g. the application may remember the previously used queue).<br>
For details see the openSUSE support database
article 'Print Settings with CUPS' at<br>
http://en.opensuse.org/SDB:Print_Settings_with_CUPS
</p>
<p>
其中一个打印队列必须设置为<b>默认使用</b>。<br>
应用程序应该在用户没有指定
其他打印队列时使用系统默认打印队列。
但是没有类似“唯一” "唯一" 的默认队列。
除了系统默认队列之外，任何用户
都可以维护自己的默认队列设置，
任何应用程序也可以实施自己的特殊默认队列设置
（例如，应用程序可以记住上一次使用的队列）。<br>
详情请见 openSUSE 支持数据库文章《使用 CUPS 的打印设置》， 网址为：<br>
http://zhen.opensuse.org/SDB:Print_Settings_with_CUPS
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
<b><big>Set Up a New Queue for a Printer Device</big></b><br>
A printer device is not used directly but via a print queue.<br>
When various application programs submit print jobs simultaneously,
the jobs queue up and are sent one after the other to the printer device.<br>
It is possible to have several different print queues for the same printer device.
Usually several print queues are needed when several different printer drivers
should be used for the same printer device.
For example a second queue with a monochrome-only driver
to enforce black-only printout on a color device
or a PostScript queue and a queue with a PCL driver for a PostScript+PCL printer
because printing via the PCL driver is usually faster (but with less quality).
</p>
<p>
<b><big>为打印机设备设置一个新队列</big></b><br>
打印机设备不能直接使用，而需要通过打印队列来使用。<br>
当有多个应用程序同时提交打印作业时，
这些作业会列入队列，然后逐个发送到打印机设备。<br>
同一个打印机设备可以有若干个不同的打印队列。
通常，当同一个打印机设备使用了若干个不同的
打印机驱动程序时，就需要数个不同的打印队列。
例如，彩色设备上要有一个使用黑白驱动程序的二级队列
来强制进行黑白输出，
或者，PostScript+PCL 打印机要有 一个 PostScript 队列和一个使用 PCL 驱动程序的队列，
因为 通过 PCL 驱动程序打印通常更快（但质量会降低）。 </p>
2 years ago
User avatar graceyu

Translation approved
<p>
<b><big>Using Remote Queues:</big></b><br>
Remote queues exist on other hosts in the network,
therefore they cannot be changed on this host.<br>
The remote queues listed here are known on this host.
Usually they can be used directly by applications
so there is no need to set up a local queue for a printer
that is already available via a remote queue.<br>
</p>
<p>
<b><big>使用远程队列：</big></b><br>
远程队列存在于网络中的其他主机上，
因此在此主机上无法更改他们。<br>
此处列出的远程打印队列是此主机上已知的队列。
通常它们可以被应用程序直接使用， 因此不需要再为
一个可通过远程队列使用的打印机 设置一个本地队列。<br> </p>
2 years ago
Browse all translation changes