From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pve-devel-bounces@lists.proxmox.com>
Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68])
	by lore.proxmox.com (Postfix) with ESMTPS id B740C1FF170
	for <inbox@lore.proxmox.com>; Tue, 19 Nov 2024 13:39:37 +0100 (CET)
Received: from firstgate.proxmox.com (localhost [127.0.0.1])
	by firstgate.proxmox.com (Proxmox) with ESMTP id 826DC2B430;
	Tue, 19 Nov 2024 13:39:42 +0100 (CET)
Message-ID: <a3270657-03ea-404b-9d1e-b04fd1247e8c@proxmox.com>
Date: Tue, 19 Nov 2024 13:39:06 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
 Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
 Shannon Sterz <s.sterz@proxmox.com>
References: <20241119113730.171826-1-c.ebner@proxmox.com>
 <s8o4j434f68.fsf@proxmox.com>
 <e7ee6899-ce76-4521-b898-4e4415dc1ba3@proxmox.com>
 <s8or077302a.fsf@proxmox.com> <D5Q57HLQG7A4.13UU5EOR74ZM4@proxmox.com>
 <ee89f00e-a708-4a6b-9596-6ca09852b66e@proxmox.com>
Content-Language: en-US, de-DE
From: Christian Ebner <c.ebner@proxmox.com>
In-Reply-To: <ee89f00e-a708-4a6b-9596-6ca09852b66e@proxmox.com>
X-SPAM-LEVEL: Spam detection results:  0
 AWL 0.031 Adjusted score from AWL reputation of From: address
 BAYES_00                 -1.9 Bayes spam probability is 0 to 1%
 DMARC_MISSING             0.1 Missing DMARC policy
 KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment
 SPF_HELO_NONE           0.001 SPF: HELO does not publish an SPF Record
 SPF_PASS               -0.001 SPF: sender matches SPF record
Subject: Re: [pve-devel] [PATCH proxmox-i18n] update Italian translations
X-BeenThere: pve-devel@lists.proxmox.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com>
List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe>
List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/>
List-Post: <mailto:pve-devel@lists.proxmox.com>
List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help>
List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, 
 <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe>
Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: pve-devel-bounces@lists.proxmox.com
Sender: "pve-devel" <pve-devel-bounces@lists.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