From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>,
Gabriel Goller <g.goller@proxmox.com>,
Christian Ebner <c.ebner@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-i18n] update Italian translations
Date: Mon, 18 May 2026 13:18:28 +0200 [thread overview]
Message-ID: <5fb66de2-3cb0-4bb0-a0ac-5001d5135992@proxmox.com> (raw)
In-Reply-To: <DILRBUCTCVC0.XJ1MFTAL8DSA@proxmox.com>
Am 18.05.26 um 13:14 schrieb Shannon Sterz:
>>> #: pve-manager/www/manager6/sdn/PrefixListPanel.js:129
>>> #: pve-manager/www/manager6/sdn/PrefixListPanel.js:282
>>> -#, fuzzy
>>> msgid "No prefix list configured"
>>> -msgstr "Nessun destinatario configurato"
>>> +msgstr "Nessuna lista di prefisso configurata"
>> I think it would be better to keep the english name here:
>>
>> "Nessuna prefix list configurata"
>>
>> If not, we should at least use the plural "prefissi".
>>
> quick question since i did pretty much the same for the german
> translation (Präfixliste): should we also keep the english "prefix list"
> there. also, i assume keeping "route map" instead of trying to translate
> it, is also preferable?
>
> not sure what is commonly used in german in this context. let me know
> and i'll update the translations there. thanks!
As it's a SDN term it might be indeed better to keep it as is, but not to
strong feelings here. If we keep it, or maybe in any case, we probably
should want to add translator context to the use sites then though.
next prev parent reply other threads:[~2026-05-18 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 10:04 [PATCH proxmox-i18n] update Italian translations Christian Ebner
2026-05-18 10:59 ` applied: " Thomas Lamprecht
2026-05-18 11:10 ` Gabriel Goller
2026-05-18 11:14 ` Shannon Sterz
2026-05-18 11:18 ` Thomas Lamprecht [this message]
2026-05-18 11:37 ` Shannon Sterz
2026-05-18 11:25 ` Gabriel Goller
2026-05-18 11:22 ` Gabriel Goller
2026-05-18 11:30 ` Christian Ebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fb66de2-3cb0-4bb0-a0ac-5001d5135992@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox