From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#26302: [website] translations Date: Sun, 08 Sep 2019 21:44:44 +0200 Message-ID: <878sqy7etv.fsf@gnu.org> References: <20170329154040.ddscahwp2agknihb@abyayala> <8760e8l3bd.fsf@gnu.org> <20170731215448.6zsu2qcfykuzbcd2@abyayala> <20190906142548.4crfjgvxilgalgrs@pelzflorian.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57837) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i737Q-0007gV-5p for bug-guix@gnu.org; Sun, 08 Sep 2019 15:45:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i737O-0000BE-QC for bug-guix@gnu.org; Sun, 08 Sep 2019 15:45:04 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:58565) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i737O-0000B5-Mc for bug-guix@gnu.org; Sun, 08 Sep 2019 15:45:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1i737O-0000F0-Jd for bug-guix@gnu.org; Sun, 08 Sep 2019 15:45:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20190906142548.4crfjgvxilgalgrs@pelzflorian.localdomain> (pelzflorian@pelzflorian.de's message of "Fri, 6 Sep 2019 16:25:48 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: "pelzflorian (Florian Pelz)" Cc: 26302@debbugs.gnu.org Hi Florian, "pelzflorian (Florian Pelz)" skribis: > Find attached preliminary patches that add a working website > translation system to guix-artwork. Of course, the patches should > *not* be pushed before there is a working nginx configuration with > appropriate redirects. (Except the first three patches; I do not > understand how you could even build the website without my first > patch?) Cool, thanks for opening this issue! > In my patches, I have used spaces for indentation. Most previous > website code used a mix of tabs and spaces, like in emacs=E2=80=99 strange > default setting. If you want, I can tabify my patches. I cannot see > any reason for using mixed tabs+spaces with emacs-style Lisp > indentation though. Spaces are good (easily pastable in the REPL), the whole Guix code base is meant to use spaces only. > For redirecting previous URLs based on the HTTP Accept-Language > header, there is > . > It could be added to nginx. Good. > I do not know what the new URLs should be. After reading > > I now understand that there indeed should be separate URLs for each > language and Accept-Language headers are not sufficient. However, > Ludo=E2=80=99s idea of translating URLs including the basename > , > i.e. /help.html as /es/ayuda.html, leads to questions about the > implementation such as what Jelle Licht mentioned > . > We can do whatever we want, so let=E2=80=99s do what is best. What do you > think, /es/ayuda/ or /es/help/ or something else? > > For ayuda, we would then need to make `guix build -f .guix.scm` build > with the static website also some kind of association list for > redirects that is readable by nginx lua code or whatever (could there > be guile plugins for nginx??). > > We can do /es/help/ now and make /es/ayuda/ later. Yeah, let=E2=80=99s keep that for later. > One of the attached patches adds a PO file with a German translation > that was needed for testing purposes; of course translations should > normally be submitted via the Translation Project. The patch need not > be applied; do as you see fit. I wonder if we should use the TP for this. Thoughts? > With respect to the help mailing list blurbs on the website, my code > gives priority to the PO file translation of the blurb and uses the > previous hard-coded translations as a fall-back. I would keep the > blurbs this way until all are part of a PO file at the Translation > Project. Sounds good. > The Chinese language blurb is written in traditional Chinese > characters. I believe there never was a decision on > , > so I leave the language code as =E2=80=9Czh=E2=80=9D for now, even though= someone may > add a =E2=80=9Czh-cn=E2=80=9D too. Yeah, we can always adjust later. Thanks! Ludo=E2=80=99.