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 |
![]() |
Translation license | GPL-2.0 master yast-printer |
22 hours 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 |
Quick numbers
and previous 30 days
Trends of last 30 days
—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
![]() Translation approved |
|
![]() Translation approved |
|
![]() Translation approved |
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
![]() Source string changed |
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
![]() Resource updated |
The “
/var/lib/weblate/vcs/yast-base/master/po/printer/zh_TW.po ” file was changed.
2 years ago
|
<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>
<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>