From: Christian Ebner <c.ebner@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Shannon Sterz <s.sterz@proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-i18n] update Italian translations
Date: Tue, 19 Nov 2024 13:39:06 +0100 [thread overview]
Message-ID: <a3270657-03ea-404b-9d1e-b04fd1247e8c@proxmox.com> (raw)
In-Reply-To: <ee89f00e-a708-4a6b-9596-6ca09852b66e@proxmox.com>
On 11/19/24 13:30, Thomas Lamprecht wrote:
> Am 19.11.24 um 13:09 schrieb Shannon Sterz:
>>>> This is intentional since that is the description for the systemd state, not
>>>> sure if it makes to translate that in this case?
>>> Maybe, but perhaps then it makes sense to remove the english string? I
>>> mean there are more similar strings which do have a translation:
>>>
>> yeah i'm really not sure translating these states made sense... a user
>> requested this [1], but for systemd stati there isn't a good translation
>> imo. like how would you translate 'dead'? the german eqivalents of
>> 'verstorben' or 'tot' sound non-sensical. translating this less
>> literally makes it harder to understand what's going on (i.e. an enabled
>> service could not be started repeatedly due to some error) or would lead
>> to really long translations which would probably break the layout in
>> places. so really not sure if these strings should be translated...
>>
>> [1]: https://bugzilla.proxmox.com/show_bug.cgi?id=5847
>
>
> FWIW, I'm fine with not placing systemd unit states under translation, one
> would need to send patches though if they want to see that implemented.
Will send a patch to proxmox-widget-toolkit to remove the gettext for
the systemd states.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-11-19 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 11:37 Christian Ebner
2024-11-19 11:48 ` Maximiliano Sandoval
2024-11-19 11:55 ` Christian Ebner
2024-11-19 11:58 ` Maximiliano Sandoval
2024-11-19 12:05 ` Christian Ebner
2024-11-19 12:09 ` Shannon Sterz
2024-11-19 12:30 ` Thomas Lamprecht
2024-11-19 12:39 ` Christian Ebner [this message]
2024-11-19 12:01 ` Shannon Sterz
2024-11-19 12:04 ` Maximiliano Sandoval
2024-11-19 12:16 ` Christian Ebner
2024-11-19 12:33 ` Gabriel Goller
2024-11-19 12:36 ` Christian Ebner
2024-11-19 12:53 ` Gabriel Goller
-- strict thread matches above, loose matches on Subject: below --
2024-04-23 6:29 Christian Ebner
2024-02-27 17:12 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=a3270657-03ea-404b-9d1e-b04fd1247e8c@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@proxmox.com \
--cc=t.lamprecht@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