From: Christian Ebner <c.ebner@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@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:05:22 +0100 [thread overview]
Message-ID: <b4cbd5e0-b405-4fcd-9c9b-b1f6732e3f00@proxmox.com> (raw)
In-Reply-To: <s8or077302a.fsf@proxmox.com>
On 11/19/24 12:58, Maximiliano Sandoval wrote:
>
> Christian Ebner <c.ebner@proxmox.com> writes:
>
>> 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?
>
> Maybe, but perhaps then it makes sense to remove the english string? I
> mean there are more similar strings which do have a translation:
>
>> #: proxmox-widget-toolkit/src/Utils.js:317
>> -#, fuzzy
>> msgid "starting"
>> -msgstr "Riavvia"
>> +msgstr "in avvio"
>>
>> #: proxmox-widget-toolkit/src/Utils.js:315
>> -#, fuzzy
>> msgid "static"
>> -msgstr "Statico"
>> +msgstr ""
>>
>> #: proxmox-widget-toolkit/src/Utils.js:57
>> msgid "stopped"
>> msgstr "fermato"
This one should be translated in my opinion, that is not a systemd
service state.
For the others you are right, they should also get no translation. Will
send a new version without the systemd service states translated.
>>
>> #: proxmox-widget-toolkit/src/Utils.js:318
>> -#, fuzzy
>> msgid "stopping"
>> -msgstr "fermato"
>> +msgstr "fermare in corso"
_______________________________________________
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:05 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 [this message]
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
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=b4cbd5e0-b405-4fcd-9c9b-b1f6732e3f00@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=m.sandoval@proxmox.com \
--cc=pve-devel@lists.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