From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 51456@debbugs.gnu.org
Subject: bug#51456: website: Language selection dropdown not translated
Date: Thu, 28 Oct 2021 10:13:40 +0200 [thread overview]
Message-ID: <20211028081340.hj2ceeagqfjay2m2@pelzflorian.localdomain> (raw)
Ludo recently divided building the website into one computed file for
each language (“lingua”) in order to offload the build (a good thing;
thank you Ludo).
However, this includes making available for each lingua only the
translations MO file for that lingua.
Specifically .guix.scm now links only that file:
(symlink (string-append #$(lingua-mo-files lingua) "/" lingua)
lingua)
But on the website, there is a language selection dropdown at the top
right and the names of alternative language are taken from that
language’s MO file.
Because the build does not have available all MO files anymore, all
foreign languages are now called English.
(Another effect is that the contact web page only lists the German
message for the Help mailing list on the German website but meh …)
Is the proper solution to symlink all lingua-mo-files, i.e. reinstate
from before commit 4d5bf8522e2 a for-each like
(for-each
(lambda (lingua mo-directory)
(symlink (string-append mo-directory "/" lingua)
lingua))
(list #$@%linguas)
'#$(map lingua-mo-files %linguas))
(I have not tried.)
Or should website/apps/base/templates/components.scm look up the
language dropdown’s language names in a different way such as from the
PO file, which is more complicated?
Regards,
Florian
next reply other threads:[~2021-10-28 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 8:13 pelzflorian (Florian Pelz) [this message]
2021-10-28 10:09 ` bug#51456: website: Language selection dropdown not translated pelzflorian (Florian Pelz)
2021-11-02 15:08 ` pelzflorian (Florian Pelz)
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=20211028081340.hj2ceeagqfjay2m2@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=51456@debbugs.gnu.org \
/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.