Am 06/12/2023 um 15:26 schrieb Dominik Csapak:
> 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
> Do note the following examples:
>
> #: pve-manager/www/manager6/qemu/IPConfigEdit.js:97
> #: pve-manager/www/manager6/qemu/IPConfigEdit.js:155
> msgid "DHCP"
> msgstr "بروتوكول التهيئة الآلية للمضيفين (DHCP)"
>
> #: pve-manager/www/manager6/qemu/IPConfigEdit.js:163
>
On 12/6/23 15:04, Maximiliano Sandoval wrote:
Dominik Csapak 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<---
Dominik Csapak 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
>
On 12/6/23 12:20, Fiona Ebner wrote:
Am 06.12.23 um 12:00 schrieb Dominik Csapak:
On 12/6/23 11:21, Maximiliano Sandoval wrote:
Dominik Csapak writes:
translating ACME does not make sense to me since it's
the name of the protocol and stands for
Automatic Certificate Management
Am 06.12.23 um 12:00 schrieb Dominik Csapak:
> On 12/6/23 11:21, Maximiliano Sandoval wrote:
>>
>> Dominik Csapak 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
On 12/6/23 12:13, Maximiliano Sandoval wrote:
Dominik Csapak writes:
the translator must make sure the terms are consistent anyway...
This is the heart of the issue. The translator cannot know there are
more uses of the string if it is not marked as translatable.
yes he can, because
Dominik Csapak writes:
> the translator must make sure the terms are consistent anyway...
This is the heart of the issue. The translator cannot know there are
more uses of the string if it is not marked as translatable.
--
Maximiliano
___
On 12/6/23 11:21, Maximiliano Sandoval wrote:
Dominik Csapak 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
Dominik Csapak 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
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
rest looks fine to me though
On 11/29/23 14:21, Maximiliano
Note that ACME is already in 3 translatable strings, a similar remark
applies to N/A which is already translated in many languages.
Signed-off-by: Maximiliano Sandoval
---
src/node/DNSView.js | 2 +-
src/panel/ACMEDomains.js | 2 +-
src/panel/DiskList.js
12 matches
Mail list logo
