From: Alexander Zeidler <a.zeidler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-i18n] use xgettext to extract translatable strings
Date: Mon, 04 Dec 2023 15:43:41 +0100 [thread overview]
Message-ID: <2bddf575a7144eedc72b7bafd18458e6ba0140e6.camel@proxmox.com> (raw)
In-Reply-To: <20231201142527.213620-1-m.sandoval@proxmox.com>
From a brief look at it:
I also think it's a good idea to provide more information for translators
(where it actually adds value and doesn't just bloat code).
> Cons:
> - In total 3 translations were marked as fuzzy. Translators will have to
> review and mark them as translated again.
since ~12k translations are already marked as fuzzy ...
> - If using -c, gettext can't distinguish if the comment above is useful
> for translators. The common practice is to add a `TRANSLATORS:` tag to
> these comments.
There's also "-cTAG"
> + find . -iname "*.js" -path "./$(2)*" | xargs xgettext -c -s \
rather: -name
prev parent reply other threads:[~2023-12-04 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 14:25 Maximiliano Sandoval
2023-12-04 14:43 ` Alexander Zeidler [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=2bddf575a7144eedc72b7bafd18458e6ba0140e6.camel@proxmox.com \
--to=a.zeidler@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