From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Translation: Would regional translation fall back to primary language?
Date: Wed, 21 Sep 2022 17:40:20 +0000 [thread overview]
Message-ID: <UErSQl5CoGC0AhesNaPhsPEsAtWbZleBVry3in38vFJhMQJjPyaBjnkf4PqZZWEXt0o_gHq9y0YREwdpAk9yc2-712YBAYrSBIdmhWwyJi8=@protonmail.com> (raw)
In-Reply-To: <87h710r93o.fsf@pelzflorian.de>
[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]
On Wednesday, September 21st, 2022 at 16:22, pelzflorian (Florian Pelz) <pelzflorian@pelzflorian.de> wrote:
> Luis Felipe luis.felipe.la@protonmail.com writes:
>
> > Because if that's the case, I'd like to propose Weblate developers
> > that progress gauges for regional catalogs take into account the
> > progress of the primary language. That way, the progress of a regional
> > catalog would always be greater or equal to the progress of the
> > catalog of the primary language.
>
>
> It’s not just the progress bars. Yes, Weblate could somehow display it
> as already translated if the fallback language has a translation, but
> when downloading the PO file, other editors would not display it.
True.
Thanks again, Florian.
Cheers,
[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]
prev parent reply other threads:[~2022-09-21 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 16:17 Translation: Would regional translation fall back to primary language? Luis Felipe
2022-09-19 11:53 ` pelzflorian (Florian Pelz)
2022-09-19 19:01 ` Liliana Marie Prikler
2022-09-20 16:38 ` Luis Felipe
2022-09-21 16:22 ` pelzflorian (Florian Pelz)
2022-09-21 17:40 ` Luis Felipe [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='UErSQl5CoGC0AhesNaPhsPEsAtWbZleBVry3in38vFJhMQJjPyaBjnkf4PqZZWEXt0o_gHq9y0YREwdpAk9yc2-712YBAYrSBIdmhWwyJi8=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.