From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Timothy Nicholson <t.nicholson@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v2] fix #5847: ui: gettextize several strings in ui
Date: Tue, 12 Nov 2024 12:55:33 +0100 [thread overview]
Message-ID: <e1232c9f-d44c-4378-82f6-1f83ec9b1909@proxmox.com> (raw)
In-Reply-To: <f7ae331b-cfb1-4f88-8b3d-a8b149884c3e@proxmox.com>
Am 12.11.24 um 12:49 schrieb Thomas Lamprecht:
> Am 12.11.24 um 10:38 schrieb Timothy Nicholson:
>> Signed-off-by: Timothy Nicholson <t.nicholson@proxmox.com>
>> ---
>>
>> I missed one occurence of the String 'TFA' not using gettext, so
>> here is the updated patch.
>
> well that's the only one I'm not 100% certain about, how would such an
> abbreviation even get translated?
>
> Albeit it might make sense to change that to the seemingly more frequent
> "MFA" (Mutli-factor authentication) variant in a separate patch; I write
> seemingly, because I only checked a handful of Wikipedia languages for
> this and that was the one abbreviation that I saw in everyone.
>
> https://en.wikipedia.org/wiki/Multi-factor_authentication
I now saw Dominik's and Shannon's replies to the other patch, but I'm still
not convinced if putting TFA under translation is that good, as it really
seems to be outdated and thus might not be the ideal source to decide what
translation is best for it.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-12 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 9:38 Timothy Nicholson
2024-11-12 11:49 ` Thomas Lamprecht
2024-11-12 11:55 ` Thomas Lamprecht [this message]
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=e1232c9f-d44c-4378-82f6-1f83ec9b1909@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.nicholson@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