From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Translation: Would regional translation fall back to primary language?
Date: Wed, 21 Sep 2022 18:22:03 +0200 [thread overview]
Message-ID: <87h710r93o.fsf@pelzflorian.de> (raw)
In-Reply-To: <WUltsjigfhd6NL82Ykq_F3hUcbrt6Swytppbo_zv5603uwuTbMCdFlFkZtHSpxqQVIvy2disMiG2w9WeAlV8XcXTYtY9B3SgoWKDn0zi45w=@protonmail.com> (Luis Felipe's message of "Tue, 20 Sep 2022 16:38:29 +0000")
Hello Luis.
Luis Felipe <luis.felipe.la@protonmail.com> writes:
> I think I'll go with that option, thanks.
:)
> I don't know if I understand correctly the organizational problem
> related to leaving the es-CO catalog partially translated,
> intentionally. Is it that Weblate would display the es-CO translation
> as incomplete and so translators would end up duplicating work? (Start
> translating the rest of the catalog not knowing that the "es-CO"
> regional catalog is supposed to be left incomplete so that the missing
> translations are taken from the almost complete "es" catalog?)
Yes, that is precisely what I expect to happen.
> 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.
Regards,
Florian
next prev parent reply other threads:[~2022-09-21 16:42 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) [this message]
2022-09-21 17:40 ` Luis Felipe
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h710r93o.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).