all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 51456-done@debbugs.gnu.org
Subject: bug#51456: website: Language selection dropdown not translated
Date: Tue, 2 Nov 2021 16:08:25 +0100	[thread overview]
Message-ID: <20211102150825.ghde3dpk5tpjmlaj@pelzflorian.localdomain> (raw)
In-Reply-To: <20211028100956.iebrx6v7iommkgdn@pelzflorian.localdomain>

On Thu, Oct 28, 2021 at 12:09:56PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, Oct 28, 2021 at 10:13:49AM +0200, pelzflorian (Florian Pelz) wrote:
> > 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.)
> 
> Seems to work.  I have guix build -f .guix.scm but only one lingua got
> built so far, it looks right.  Patch attached.  Shall I push or …
> > 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?

Patch pushed as f2ac98776b321755b672a8f6a1b07d4ab10fff7c.

This undid some of Ludo’s 3689f95c7f197ca83fd78b4e1693c18779da8bb1 and
4d5bf8522e24e2939968dc40ab1ff9809e423ac6, but it seems the only clean
solution.

Regards,
Florian




      reply	other threads:[~2021-11-02 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28  8:13 bug#51456: website: Language selection dropdown not translated pelzflorian (Florian Pelz)
2021-10-28 10:09 ` pelzflorian (Florian Pelz)
2021-11-02 15:08   ` pelzflorian (Florian Pelz) [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=20211102150825.ghde3dpk5tpjmlaj@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=51456-done@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.