From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Dominik Csapak <d.csapak@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, 06 Dec 2023 11:21:03 +0100 [thread overview]
Message-ID: <s8oplzjmwuj.fsf@proxmox.com> (raw)
In-Reply-To: <50f3e171-c2b4-4e59-bd7f-07f81b11c0b7@proxmox.com>
Dominik Csapak <d.csapak@proxmox.com> writes:
> translating ACME does not make sense to me since it's
> the name of the protocol and stands for
> Automatic Certificate Management Environment
>
> i don't think/believe this should be translated
> into other languages as a standalone word
"ACME" appears in four translatable strings, e.g.
msgid "ACME Accounts"
Having the term itself being translatable allows the translator to be
consistent on which term to use when there are multiple translatable
strings containing it. It would be confusing for the user if the only
place where they see "ACME" is in the original string.
While there are no examples of this specifically for "ACME", there is a
similar one:
"ACL" is a translatable string which appears in two other translations
#: proxmox-widget-toolkit/src/window/AuthEditLDAP.js:361
#: proxmox-widget-toolkit/src/window/SyncWindow.js:110
#: pve-manager/www/manager6/dc/AuthEditLDAP.js:333
#: pve-manager/www/manager6/dc/RealmSyncJob.js:355
#: pve-manager/www/manager6/dc/SyncWindow.js:129
msgid "ACL"
msgstr ""
There are at least two languages that actually translate it:
ru:
msgid "ACL"
msgstr "Список управления доступом"
ar:
msgid "ACL"
msgstr "قائمة التحكم في الوصول"
Both translation make use of this in other translations, as shown in the
following translations:
ru:
msgid "Remove ACLs of vanished users and groups."
msgstr "Удалить списки управления доступом исчезнувших пользователей и групп."
ar:
msgid "Remove ACLs of vanished users and groups."
msgstr "إزالة قوائم التحكم بالوصول للمستخدمين والمجموعات المختفية."
I personally lean towards not translating it, but in my option, that is
a decision that belongs to the translator, having the string be
translatable gives them more context to make this choice.
All of this would be simpler if we could extract comments with xgettext
to signal that certain parts of strings should ideally not be
translated.
Of course, if this is polemic enough, it could be separated into a
different commit/mail-discussion.
--
Maximiliano
next prev parent reply other threads:[~2023-12-06 10:47 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 [this message]
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
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=s8oplzjmwuj.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=d.csapak@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