Translation status

1,089 Strings 100%
Browse Translate
17,901 Words 100%
168,826 Characters 100%

Strings status

Strings Words Characters
1,089 17,901 168,826
All strings Browse Translate Zen
1,089 17,901 168,826
Translated strings Browse Translate Zen
122 1,143 14,684
Strings with any failing checks Browse Translate Zen
122 1,143 14,684
Translated strings with any failing checks Browse Translate Zen
25 375 3,477
Translated strings with dismissed checks Browse Translate Zen
119 1,133 14,509
Failing check: Unchanged translation Browse Translate Zen
3 10 175
Failing check: XML markup Browse Translate Zen
5 251 2,017
Strings with comments Browse Translate Zen

Overview

Project website debian-handbook.info
Instructions for translators

https://debian-handbook.info/contribute/ Mailing list for translators: <debian-handbook-translators@lists.alioth.debian.org
Project maintainers User avatar rhertzog User avatar pere User avatar dleidert
Translation license GNU General Public License v2.0 or later
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://salsa.debian.org/hertzog/debian-handbook.git
Repository branch bullseye/main
Last remote commit Fix incorrect syntax in pt-BR translation. 02708025
Petter Reinholdtsen authored 4 months ago
Last commit in Weblate ru-RU: Translated using Weblate. 50457d68
User avatar ashed authored 2 days ago
Weblate repository https://hosted.weblate.org/git/debian-handbook/12_advanced-administration/
File mask */11_network-services.po
Translation file Download it-IT/11_network-services.po
Last change July 8, 2024, 3:09 p.m.
Last change made by None
Language Italian
Language code it
Text direction Left to right
Number of speakers 69,298,348
Number of plurals 2
Plural type One/other
Plurals Singular 1
Plural 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, …
Plural formula n != 1
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,089 17,901 168,826
Translated 100% 1,089 100% 17,901 100% 168,826
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 11% 122 6% 1,143 8% 14,684
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

249 changes 0 changes 594 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 6 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

17,901
Hosted words
1,089
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 None

Changes committed
Changes committed 4 months ago
User avatar eppesuig

Translation changed
<primary>Network File System</primary><see>NFS</see>
<primary><foreignphrase>Network File System</foreignphrase></primary><see>NFS</see>
4 months ago
User avatar eppesuig

Translation changed
<primary>Lightweight Directory Access Protocol</primary><see>LDAP</see>
<primary><foreignphrase>Lightweight Directory Access Protocol</foreignphrase></primary><see>LDAP</see>
4 months ago
User avatar eppesuig

Translation changed
<primary>Name Service Switch</primary><see>NSS</see>
<primary><foreignphrase>Name Service Switch</foreignphrase></primary><see>NSS</see>
4 months ago
User avatar eppesuig

Contributor joined
Contributor joined 4 months ago
User avatar pere

Resource updated
Parsing of the “it-IT/11_network-services.po” file was enforced. 4 months ago
User avatar pere

Resource updated
Parsing of the “it-IT/11_network-services.po” file was enforced. a year ago
User avatar Passero

Translation changed
In that scenario, since DNS blacklists never triggers a definitive rejection, it becomes reasonable to use aggressive blacklists, including those listing all dynamic IP addresses from ISP clients (such as <literal>pbl.spamhaus.org</literal> or <literal>dul.dnsbl.sorbs.net</literal>).
In talquesto scenario, poichè le blacklist DNS non innescano mai un rifiuto definitivo, diventa ragionevole l'uso di blacklist aggressive, comprese quelle che includono tutti gli indirizzi IP dinamici assegnati dai Pprovider ai loro clienti (come <literal>pbl.spamhaus.org</literal> o <literal>dul.dnsbl.sorbs.net</literal>).
a year ago
User avatar pere

Resource updated
Parsing of the “it-IT/11_network-services.po” file was enforced. a year ago
User avatar Passero

Translation changed
The first question deals with the type of setup. Only two of the proposed answers are relevant in case of an Internet-connected server, “Internet site” and “Internet with smarthost”. The former is appropriate for a server that receives incoming email and sends outgoing email directly to its recipients, and is therefore well-adapted to the Falcot Corp case. The latter is appropriate for a server receiving incoming email normally, but that sends outgoing email through an intermediate SMTP server — the “smarthost” — rather than directly to the recipient's server. This is mostly useful for individuals with a dynamic IP address, since many email servers reject messages coming straight from such an IP address. In this case, the smarthost will usually be the ISP's SMTP server, which is always configured to accept email coming from the ISP's customers and forward it appropriately. This setup (with a smarthost) is also relevant for servers that are not permanently connected to the internet, since it avoids having to manage a queue of undeliverable messages that need to be retried later.
La prima domanda riguarda la tipologia di configurazione. Solo due delle risposte proposte sono rilevanti nel caso in cui il server sia connesso ad Internet: «"Sito internet» e «" e "Sito internet con smarthost»". La prima opzione è appropriata per un server che riceve la posta in arrivo ed invia le email in uscita direttamente ai rispettivi destinatari: pertanto si adatta bene al caso della Falcot Corporation. La seconda opzione è appropriata per un server che riceve le email in arrivo normalmente ma che invia le email in uscita attraverso un server SMTP intermedio, lo «"smarthost»", anziché consegnarle direttamente al server del destinatario. Questo è particolarmente utile per chi ha con un indirizzo IP dinamico poiché molti server di posta rifiutano i messaggi che arrivano direttamente da questo tipo di indirizzo. In questo caso lo smarthost sarà generalmente il server SMTP dell'ISP che a sua volta è configurato per accettare ed inoltrare in modo appropriato le email provenienti dai clienti. Questo tipo di configurazione (con smarthost) è rilevante anche per i server che non sono costantemente connessi ad internet poiché evita di dover gestire una coda di messaggi non consegnabili da dover riprovare a inviare in seguito.
a year ago
Browse all translation changes