public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH widget-toolkit] i18n: mark strings as translatable
Date: Wed, 6 Dec 2023 15:26:29 +0100	[thread overview]
Message-ID: <37d755e3-83ee-4a10-9e94-7f85a56e527b@proxmox.com> (raw)
In-Reply-To: <s8oh6kvmn7g.fsf@proxmox.com>



On 12/6/23 15:04, Maximiliano Sandoval wrote:
> Dominik Csapak <d.csapak@proxmox.com> writes:
> 
>> it's more like DHCP, SLAAC or IPv4. those are names of protocols (like ACME)
>> that shouldn't change across translations
>>
>> and we removed those gettexts (mostly) a while ago
>> e.g. see lxc/Network.js in pve-manager:
>>
>> ---8<---
>> boxLabel: 'DHCP', // do not localize
>> --->8---
> 
> Do note the following examples:


yeah i said we didn't remove all of those instances
and it seems there are some not so good translations still existing.
(bad translations are not a good argument for translating even
more of them? I'd argue they are even an argument that we should
reduce them)


> 
>      #: pve-manager/www/manager6/qemu/IPConfigEdit.js:97
>      #: pve-manager/www/manager6/qemu/IPConfigEdit.js:155
>      msgid "DHCP"
>      msgstr "بروتوكول التهيئة الآلية للمضيفين (DHCP)"

Does not really make sense IMO to translate this, since
DHCP already is an established abbreviation and there
is no need to write it out localized.

> 
>      #: pve-manager/www/manager6/qemu/IPConfigEdit.js:163
>      msgid "SLAAC"
>      msgstr "Autoconfiguration SLAAC"

IMHO this makes even less sense, SLAAC
already includes 'autoconfiguration', so why do this?

> 
>      #: pve-manager/www/manager6/ceph/CephInstallWizard.js:476
>      msgid "First Ceph monitor"
>      msgstr "أول جهاز مراقبة"

doesn't mention ceph in the translation at all....
(which it should!)

> 
> What would be the purpose of removing the translation of the words
> themselves if they are already being translated elsewhere.

none of the examples here translate the words in a meaningful manner,
should be either already known, mentioned in the docs, or be
easily searchable online.
also it only causes issues when using an overly long text
in a field label

> 

> --
> Maximiliano

honestly i don't want to argue/bikeshed about such a small detail,
but i don't see a good reason to translate names and established
(technical) words.

I'm ready to change my mind, but i did not see a good example
of when it would be good to translate 'ACME' (or DHCP, Ceph, etc.)
into something different yet.




  reply	other threads:[~2023-12-06 14:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 13:21 Maximiliano Sandoval
2023-12-06  9:46 ` Dominik Csapak
2023-12-06 10:21   ` Maximiliano Sandoval
2023-12-06 11:00     ` Dominik Csapak
2023-12-06 11:13       ` Maximiliano Sandoval
2023-12-06 11:19         ` Dominik Csapak
2023-12-06 11:20       ` Fiona Ebner
2023-12-06 11:22         ` Dominik Csapak
2023-12-06 14:04       ` Maximiliano Sandoval
2023-12-06 14:26         ` Dominik Csapak [this message]
2023-12-06 15:54           ` Thomas Lamprecht
2023-12-06 15:16         ` Dietmar Maurer

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=37d755e3-83ee-4a10-9e94-7f85a56e527b@proxmox.com \
    --to=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal