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: Mon, 19 Sep 2022 13:53:32 +0200 [thread overview]
Message-ID: <87fsgn4m2r.fsf@pelzflorian.de> (raw)
In-Reply-To: <3es6YqHFeDoZ3H5Ssvt5xTf8yC1H2U1VpWKlYdvQSkSCua6Dvt7lbFa3sBLi-WEF05tE0RuOp0ecdBL2emwoIfH1exeWsvfsGFPY-LYiVT4=@protonmail.com> (Luis Felipe's message of "Sat, 17 Sep 2022 16:17:00 +0000")
Hello Luis/sirgazil. Translation help sounds great.
That said, I believe that, because others will add to the translation,
that it would be best if you Downloaded the Spain Spanish file from
Weblate and then uploaded that PO file as the first translation in
Colombian Spanish. Then change it from that base.
Luis Felipe <luis.felipe.la@protonmail.com> writes:
> So, assuming an incomplete es-CO translation catalog already exists,
> would the translation system (gettext?) retrieve missing translations
> from the catalog corresponding to the primary language (es) or would
> it retrieve the source string in English?
I just tested adding a dummy de_CH.po translation file to Guix and yes,
it falls back to de translations if the msgstr in de_CH is empty, even
without changing the LANGUAGE environment variable and only setting
LC_ALL=de_CH.utf8.
But still, from an organizational view, I suggest not doing a partial
translation. I don’t know though.
Regards,
Florian
next prev parent reply other threads:[~2022-09-19 12:01 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) [this message]
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
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=87fsgn4m2r.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 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.