public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-i18n] update Italian translations
Date: Tue, 19 Nov 2024 13:04:16 +0100	[thread overview]
Message-ID: <s8omshv2ziq.fsf@proxmox.com> (raw)
In-Reply-To: <D5Q511PN24RB.3R7JPPTPCK4MS@proxmox.com>


"Shannon Sterz" <s.sterz@proxmox.com> writes:

> On Tue Nov 19, 2024 at 12:55 PM CET, Christian Ebner wrote:
>> On 11/19/24 12:48, Maximiliano Sandoval wrote:
>> >
>> > Christian Ebner <c.ebner@proxmox.com> writes:
>> >
>> >>   #: proxmox-widget-toolkit/src/Utils.js:315
>> >> -#, fuzzy
>> >>   msgid "static"
>> >> -msgstr "Statico"
>> >> +msgstr ""
>> >
>> > This translation is missing.
>> >
>> > --
>> > Maximiliano
>> >
>> >
>> >
>> > _______________________________________________
>> > pve-devel mailing list
>> > pve-devel@lists.proxmox.com
>> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>> >
>> >
>>
>> This is intentional since that is the description for the systemd state,
>> not sure if it makes to translate that in this case?
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
> I've been trying to figure this out myself, I don't think it does.
> Systemd doesn't seem to translate these strings [1,2] so translating
> this probably makes it harder for users to understand what happening, as
> they can't find documentation for these bespoke translations.
>
> [1]: https://github.com/systemd/systemd/blob/main/po/de.po
> [2]: https://github.com/systemd/systemd/blob/main/po/it.po

systemd might not be localizing those strings because some CLI utils are
not being translated at all.

Independent of the reason, the string should be set to its original
english value instead of "". "" is for missing translations.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2024-11-19 12:12 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
2024-11-19 12:01     ` Shannon Sterz
2024-11-19 12:04       ` Maximiliano Sandoval [this message]
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=s8omshv2ziq.fsf@proxmox.com \
    --to=m.sandoval@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal