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 'storage'. d2b3db3100
YaST Jenkins authored 13 days ago
Last commit in Weblate Translated using Weblate (Finnish) a42621795a
User avatar TommiNieminen authored 11 days ago
Weblate repository https://l10n.opensuse.org/git/yast-base/master/
File mask po/printer/*.po
Translation file Download po/printer/ro.po
Last change May 7, 2024, 4:01 p.m.
Last change made by Coleasa Nicolae
Language Romanian
Language code ro
Text direction Left to right
Number of speakers 20,024,109
Number of plurals 3
Plural type One/few/other
Plurals One 1
Few 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Other 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, …
Plural formula n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 463 8,935 57,142
Approved 0% 0 0% 0 0% 0
Waiting for review 81% 377 50% 4,483 49% 28,370
Translated 81% 377 50% 4,483 49% 28,370
Needs editing 12% 60 44% 3,969 44% 25,696
Read-only 0% 0 0% 0 0% 0
Failing checks 7% 37 39% 3,557 40% 22,963
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 5% 26 5% 483 5% 3,076
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 4 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
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

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

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+81%
—
Contributors
—
User avatar NicolaeFericitu

Translation changed
<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 de dispozitiv pentru Imprimare printr-o Mașină Server de Imprimare</big></b><br>
În contrast cu un printserver box un server de imprimare este
un calculator real de oferă un serviciu de imprimare.<br>
Accesul se realizează prin protocoale diferite de rețea.
Întreabă administratorul de sistem pentru a afla ce mașină server de imprimare
există în rețeaua ta:<br>
<b>Microsoft Windows/SAMBA (SMB/CIFS)</b><br>
Pentru a accesa o imprimantă partajată SMB, pachetul RPM samba-client trebuie să fie instalat.
Pachetul oferă suportul 'smb' pentru CUPS care este o adresă către
programul <tt>/usr/bin/smbspool</tt> care trimite datele
către o imprimantă partajată SMB.
Un nume de server ți un nume de partajare a imprimantei și opțional grupul de lucru
este necesar pentru acces.
Și mai mult un nume de utilizator și o parolă poate fi necesar pentru a avea acces.
Ai în vedere ca spațiile și caracterele speciale în acele valori
trebuie să fie codate în procente (vezi deasupra).
Un URI complet al dispozitivului este:<br>
smb://username:password@workgroup/server/printer<br>
De exemplu 'John Doe' cu parola '@home!' poate fi ceva de genul
acestui URI de dispozitiv pentru a accesa partajul 'Fun Printer 1000+' :<br>
smb://John%20Doe:%40home%21@MYGROUP/homeserver/Fun%20Printer%201000%2B<br>
Pentru mai multe <b>informații</b> tastează <tt>man smbspool</tt> și vezi <br>
http://en.opensuse.org/SDB:Printing_via_SMB_(Samba)_Share_or_Windows_Share<br>
<b>Serverul UNIX Tradițional(LPR)</b><br>
Serviciul de Imprimare Liniar (LPD) este activ pe serverele tradiționale UNIX
și oferă una sau multe cozi LPD.
Adresa IP și numele cozii LPD este necesar pentru acces.
URI de dispozitiv este:<br>
lpd://ip-address/queue<br>
<b>CUPS Server</b><br>
În mod normal nu ar trebui să configurezi o coadă locală de imprimare
pentru a accesa cozi externe de pe un server CUPS. În schimb realizează configurarea
în meniul <b>Printare Prin Rețea</b>.
Numai dacă știi că trebuie să faci o coadă locală de imprimare
pentru a accesa o coadă de imprimare externă de un server CUPS continuați aici.<br>
IPP este protocolul nativ pentru CUPS activ pe un server.
Portul oficial IANA pentru IPP este 631.
URI de dispozitiv fiind:<br>
ipp://ip-address:631/printers/queue<br>
<b>Novell Netware Print Server (IPX)</b><br>
Pentru a accesa cozile de imprimare pe un server de imprimare Novell Netware,
pachetul RPM ncpfs trebuie să fie instalat.
Pachetul oferă suportul 'novell' pentru CUPS ce inițiază
programul <tt>nprint</tt>ce trimite datele
către o coadă de imprimare Novell Netware.
Un nume de server și un nume de coadă de imprimare este necesar pentru acces.
Și mai mult un nume de utilizator și parola pot fi necesare pentru acces.
URI de dispozitiv este:<br>
novell://username:password@server/queue<br>
Pentru <b>mai multe informații</b> vezi <tt>man nprint</tt> și
alte documente din pachetul RPM ncpfs.
</p>
7 months ago
User avatar NicolaeFericitu

Translation changed
Cannot configure local printers (no local cupsd accessible).
Nu se pot configura imprimantele locale (nici un cupsd nu esteu există cupsd local accesibil).
7 months ago
User avatar NicolaeFericitu

Translation changed
&Printer
&Im&primantă
7 months ago
User avatar NicolaeFericitu

Contributor joined
Contributor joined 7 months ago
User avatar None

Resource updated
The “/var/lib/weblate/vcs/yast-base/master/po/printer/ro.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 the parallel port or via USB
are autodetected and the appropriate device URI is autogenerated.
For example:<br>
parallel:/dev/lp0<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 serial port or bluetooth
are not autodetected so that the device URI must be manually specified.
The serial device URI parameters must comply with
what the serial port in the printer requires,
see the manual of your serial printer.
Example device URIs:<br>
serial:/dev/ttyS9?baud=9600+bits=8+parity=none+flow=soft+stop=1Example 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/ro.po” file was changed. 2 years ago
User avatar None

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

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

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