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 12:19:39 +0100 [thread overview]
Message-ID: <db297fc2-7cb4-41ef-a878-79088d23097e@proxmox.com> (raw)
In-Reply-To: <s8olea7mvki.fsf@proxmox.com>
On 12/6/23 12:13, Maximiliano Sandoval wrote:
>
> Dominik Csapak <d.csapak@proxmox.com> 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 he shouldn't be translating these strings
in a vacuum. I'd expect a minimum of cross checking the gui
and familiarity with the product/gui.
we don't give the translation files to people that have
never seen/used the pve/pbs/pmg interfaces, rather
it's users that want to use it in their own
language. If they don't know what the name/phrase/etc.
means or show up in the gui context, that's a problem
in general and leads to weird translations either way.
As an example: if i wanted to translate 'ACME'
without context and know nothing about proxmox products,
i might just put 'GIPFEL' for german
(the literal translation of the english word 'acme' in all caps...)
like google translate would suggest
>
> --
> Maximiliano
next prev parent reply other threads:[~2023-12-06 11:19 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 [this message]
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=db297fc2-7cb4-41ef-a878-79088d23097e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.