Component Approved Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
master GPL-2.0 1% 0 0 0 0 0 0 0
Glossary yast-printer GPL-2.0 0 0 0 0 0 0 0

Overview

Project website github.com/yast/yast-printer
Project maintainers User avatar ancorgonzalezsosa
Language Chinese (Taiwan) (zh_TW)
Language code zh_TW
Text direction Left to right
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 463 8,935 57,142
Approved 1% 3 14% 1,297 14% 8,496
Waiting for review 99% 460 85% 7,638 85% 48,646
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
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

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>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://username:password@workgroup/server/printer<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-address/queue<br>
<b></b>CUPS 伺服器<br>
一般而言，不應設定本地列印佇列來存取
CUPS 伺服器上的遠端佇列，而應在
<b>透過網路列印</b>對話方塊中進行設定。
除非您確定必須設定本地列印佇列
才能存取 CUPS 伺服器上的遠端佇列時，才應如此。<br>
IPP 是在伺服器上執行的 CUPS 的原生通訊協定。
IPP 的正式 IANA 連接埠為 631。
相符的裝置 URI 為：<br>
ipp://ip-address:631/printers/queue<br>
</p>
2 years ago
User avatar graceyu

Translation approved
<p>
<b><big>Percent Encoding</big></b><br>
The issue is complicated.
It is recommended to avoid reserved characters and spaces
for component values in URIs if the values are under your control
(e.g. you cannot avoid it when you must specify such characters
in values for an URI to access a remote print queue
but the remote print queue is not under your control).
Whenever possible use only so called 'unreserved characters'.
Unreserved characters are uppercase and lowercase letters,
decimal digits, hyphen, period, underscore, and tilde.
Even hyphen, period, tilde, and case sensitivity
could cause special issues in special cases
(e.g. only letters, digits, and underscore are known to work
for a CUPS print queue name and case is not significant there).
Therefore it is best to use only lowercase letters, digits,
and underscore for all values in all URIs if possible.<br>
Reserved characters and space characters in the value of a component
must be percent-encoded (also known as URL encoding).<br>
When an input field in the dialog is intended to enter
only a single value for a single component of the URI
(e.g. separated input fields for username and password),
you must enter spaces and reserved characters literally
(i.e. non-percent-encoded).
For such input fields all spaces and reserved characters
will be automatically percent-encoded.
For example if a password is actually 'Foo%20Bar' (non-percent-encoded),
it must be entered literally in the password input field in the dialog.
The automated percent-encoding results 'Foo%2520Bar' which is how
the value of the password component is actually stored in the URI.<br>
In contrast when an input field in the dialog is intended to enter
more that a single value for a single component of the URI
(e.g. a single input field for all optional parameters
like 'option1=value1&amp;option2=value2&amp;option3=value3'
or a single input field to enter the whole URI),
you must enter spaces and reserved characters percent-encoded
because an automated percent-encoding is no longer possible.
Assume in an optional parameter 'option=value'
the value would be 'this&amp;that' so that the whole
optional parameter would be 'option=this&amp;that' (literally).
But a literal '&amp;' character denotes
the separation of different optional parameters
so that 'option=this&amp;that' in an URI means
a first optional parameter 'option=this' and
a second optional parameter which is only 'that'.
Therefore a single optional parameter 'option=this&amp;that'
must be entered percent-encoded as 'option=this%26that'<br>
Input fields which require percent-encoded input
are denoted by a '[percent-encoded]' hint.<br>
Listing of characters and their percent encoding:<br>
space ' ' is percent encoded as %20<br>
exclamation mark ! is percent encoded as %21<br>
number sign # is percent encoded as %23<br>
Dollar sign $ is percent encoded as %24<br>
percentage % is percent encoded as %25<br>
ampersand &amp; is percent encoded as %26<br>
apostrophe / single quotation mark ' is percent encoded as %27<br>
left parenthesis ( is percent encoded as %28<br>
right parenthesis ) is percent encoded as %29<br>
asterisk * is percent encoded as %2A<br>
plus sign + is percent encoded as %2B<br>
comma , is percent encoded as %2C<br>
slash / is percent encoded as %2F<br>
colon : is percent encoded as %3A<br>
semicolon ; is percent encoded as %3B<br>
equals sign = is percent encoded as %3D<br>
question mark ? is percent encoded as %3F<br>
at sign @ is percent encoded as %40<br>
left bracket [ is percent encoded as %5B<br>
right bracket ] is percent encoded as %5D<br>
For details see 'Uniform Resource Identifier (URI): Generic Syntax' at<br>
http://tools.ietf.org/html/rfc3986
</p>
<p>
<b><big>百分比編碼</big></b><br>
該問題比較複雜。
如果 URI 中的元件值受您的控制，
建議您避免對這些值使用保留字元和空格
(例如，當必須在 URI 的值中指定這種字元
才能存取遠端列印佇列，而遠端列印佇列不受
您控制的情況下，您就無法避免使用它)。
應盡可能地使用所謂的 “非保留字元”。
非保留字元是大寫和小寫字母、十進位數字、
連字號、句點、底線和波狀符號。
在特殊情況下，即使是連字號、句點、波狀符號
和區分大小寫也會導致特殊問題
(例如，我們已經知道，對於 CUPS 列印佇列名稱，
只能輸入字母、數字和底線，而大小寫並不重要)。
因此，對於所有 URI 中的所有值，在可能的情況下，
最好是只使用小寫字母、數字和底線。<br>
元件值中的保留字元和空格字元必須進行
百分比編碼 (又稱為 URL 編碼)。<br>
如果只能在對話方塊的輸入欄位中
輸入單個 URI 元件的單個值
(例如，使用者名稱和密碼的單個輸入欄位)，
則必須輸入文字形式的空格和保留字元
(即未進行百分比編碼)。
對於這種輸入欄位，所有空格和
保留字元將自動進行百分比編碼。
例如，如果密碼實際上是 ”“Foo%20Bar” (未進行百分比編碼)，
則必須在對話方塊的密碼輸入欄位中輸入文字形式的密碼。
而真正在 URI 中儲存的密碼元件值則是
其自動進行過百分比編碼的結果 “Foo%2520Bar”。<br>
反之，如果要在對話方塊的輸入欄位中輸入
單個 URI 元件的多個值
(例如，要在單個輸入欄位中輸入所有選擇性參數，如
“option1=value1&amp;option2=value2&amp;option3=value3”，
或者要在單個輸入欄位中輸入完整的 URI)，
則必須輸入經過百分比編碼的空格和保留字元，
因為此時不再能夠自動進行百分比編碼。
假設在選擇性參數 “option=value” 中，
value 是 “this&amp;that”，那麼，整個
選擇性參數應該是 “option=this&amp;that” (文字形式)。
但是，”&amp;” 文字字元表示
不同選擇性參數的分隔字元，也就是說，
URI 中的 “option=this&amp;that” 表示
第一個選擇性參數為 “option=this”，第二個
選擇性參數僅為 “that”。
因此，對於單個選擇性參數 “option=this&amp;that”，
必須輸入百分比編碼的 “option=this%26that”<br>
要求輸入百分比編碼值的輸入欄位
帶有 “[百分比編碼]” 提示。<br>
字元及其百分比編碼的清單：<br>
空格 “ “ 的百分比編碼為 %20<br>
感歎號 ! 的百分比編碼為 %21<br>
編號符號 # 的百分比編碼為 %23<br>
貨幣符號 $ 的百分比編碼為 %24<br>
百分比符號 % 的百分比編碼為 %25<br>
與號 &amp; 的百分比編碼為 %26<br>
單引號 ' 的百分比編碼為 %27<br>
左圓括弧 ( 的百分比編碼為 %28<br>
左圓括弧 ) 的百分比編碼為 %29<br>
星號 * 的百分比編碼為 %2A<br>
加號 + 的百分比編碼為 %2B<br>
逗號 , 的百分比編碼為 %2C<br>
斜線 / 的百分比編碼為 %2F<br>
冒號 : 的百分比編碼為 %3A<br>
分號 ; 的百分比編碼為 %3B<br>
等號 = 的百分比編碼為 %3D<br>
問號 ? 的百分比編碼為 %3F<br>
@ 符號的百分比編碼為 %40<br>
左方括號 [ 的百分比編碼為 %5B<br>
右方括號 ] 的百分比編碼為 %5D<br>
如需詳細資料，請參閱 “資源識別字串 (URI)：通用語法”，網址為：<br>
http://tools.ietf.org/html/rfc3986
</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" 存取 HP 印表機或多功能事務機，
必須安裝 RPM 套件 hplip。
該套件提供 HP 的列印和掃描軟體 HPLIP。<br>
相反，系統不會能自動偵測到透過藍芽連接的裝置，
因此必須以手動方式指定裝置 URI。
範例裝置 URI：<br>
bluetooth://1A2B3C4D5E6F<br>
若要透過藍芽存取裝置，必須安裝 RPM 套件 bluez-cups。
該套件提供真正實際將資料傳送至蓝到藍芽印表機的 CUPS
後端「 後端
bluetooth」。
</p>
2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
User avatar None

Source string changed
<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>
2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po” file was changed. 2 years ago
Browse all changes for this language