From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, sirgazil <sirgazil@zoho.com>,
matias_jose_seco@autoproduzioni.net,
julien lepiller <roptat@lepiller.eu>
Subject: Re: Website translation
Date: Mon, 26 Aug 2019 05:08:07 +0200 [thread overview]
Message-ID: <20190826030807.ketacpthnbq35qmv@pelzflorian.localdomain> (raw)
In-Reply-To: <20190825185831.6bcfajoe6hcep2eo@pelzflorian.localdomain>
On Sun, Aug 25, 2019 at 08:58:31PM +0200, pelzflorian (Florian Pelz) wrote:
> On Thu, Aug 22, 2019 at 11:13:53PM +0200, Ludovic Courtès wrote:
> > It would be great to add the right steps to website/.guix.scm (in
> > guix-artwork.git).
> >
>
> Even though the attached patches allow building with .guix.scm, I
> found that my previous code does not work correctly. The
> deconstruction of the translation into an sexp happened at macro
> expansion time before the evaluation phase when setlocale calls took
> effect, so both or neither of index.en_US.html and index.de_DE.html
> contained the German translation, depending on the system-wide locale
> setting.
>
I will change it so `haunt build` only builds the website only for the
currently set locale. .guix.scm will call `haunt build` once for each
lingua.
Regards,
Florian
next prev parent reply other threads:[~2019-08-26 3:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 12:50 Guix beyond 1.0: let’s have a roadmap! matias_jose_seco
2019-07-07 14:20 ` Ludovic Courtès
2019-07-07 16:57 ` Website translation (was: Re: Guix beyond 1.0: let’s have a roadmap!) pelzflorian (Florian Pelz)
2019-07-07 18:00 ` pelzflorian (Florian Pelz)
2019-07-07 22:28 ` Christopher Lemmer Webber
2019-07-11 15:15 ` Website translation Ludovic Courtès
2019-07-12 5:35 ` pelzflorian (Florian Pelz)
2019-07-14 14:12 ` Ludovic Courtès
2019-07-14 14:26 ` pelzflorian (Florian Pelz)
2019-07-15 12:33 ` Ludovic Courtès
2019-07-15 14:57 ` Julien Lepiller
2019-07-15 15:54 ` pelzflorian (Florian Pelz)
2019-07-17 21:16 ` Ludovic Courtès
2019-07-18 15:08 ` pelzflorian (Florian Pelz)
2019-07-18 16:59 ` Ricardo Wurmus
2019-07-18 20:28 ` pelzflorian (Florian Pelz)
2019-07-18 20:57 ` pelzflorian (Florian Pelz)
2019-07-19 12:29 ` pelzflorian (Florian Pelz)
2019-07-26 11:11 ` pelzflorian (Florian Pelz)
2019-07-26 11:23 ` pelzflorian (Florian Pelz)
2019-08-05 13:08 ` pelzflorian (Florian Pelz)
2019-08-07 22:33 ` pelzflorian (Florian Pelz)
2019-08-22 21:13 ` Ludovic Courtès
2019-08-23 6:03 ` pelzflorian (Florian Pelz)
2019-08-23 12:18 ` Ludovic Courtès
2019-08-23 13:54 ` pelzflorian (Florian Pelz)
2019-08-23 14:08 ` Jelle Licht
2019-08-23 20:47 ` pelzflorian (Florian Pelz)
2019-08-25 18:58 ` pelzflorian (Florian Pelz)
2019-08-26 3:08 ` pelzflorian (Florian Pelz) [this message]
2019-09-06 14:27 ` pelzflorian (Florian Pelz)
2019-07-18 17:06 ` sirgazil
2019-07-15 12:59 ` Ricardo Wurmus
2019-07-18 5:06 ` 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=20190826030807.ketacpthnbq35qmv@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=matias_jose_seco@autoproduzioni.net \
--cc=roptat@lepiller.eu \
--cc=sirgazil@zoho.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.