From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Language menu in the HTML manual
Date: Wed, 19 Jan 2022 10:11:25 +0100 [thread overview]
Message-ID: <05C4E6E6-C3A7-4B55-A030-BD6B89C2F409@lepiller.eu> (raw)
In-Reply-To: <877dawd2jn.fsf@inria.fr>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
I have only tested on mobile. The language menu is always visible and takes up the whole screen. We should hide the menu by default. Is that what the icon is supposed to do? If possible, the links should go to the same page in the other language, but that might be difficult.
Le 19 janvier 2022 00:53:00 GMT+01:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hello Guix!
>
>I added a language menu in the on-line HTML manual that you can see in
>the top-right corner of manual pages:
>
> https://guix.gnu.org/manual/devel/es/html_node/Empezando.html
> https://guix.gnu.org/manual/devel/ru/guix.ru.html
>
>(CSS needs to be fixed so the menu item colors look right.)
>
>This is done with these two commits:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=7eb883b7c284c78cc17093bfc4ef2d70e0acad83
> https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/commit/?id=db26102d4149a3a857701add00d23bdf38e21911
>
>I think eventually we could also add explicit links to, say, report
>translation errors or other issues.
>
>Let me know what you think!
>
>Ludo’.
>
[-- Attachment #2: Type: text/html, Size: 1752 bytes --]
next prev parent reply other threads:[~2022-01-19 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 23:53 Language menu in the HTML manual Ludovic Courtès
2022-01-19 9:11 ` Julien Lepiller [this message]
2022-01-19 14:48 ` Ludovic Courtès
2022-01-19 15:39 ` André A. Gomes
2022-01-19 21:14 ` pelzflorian (Florian Pelz)
2022-01-20 10:29 ` Andreas Enge
2022-01-24 15:11 ` Ludovic Courtès
2022-01-26 9:18 ` Andreas Enge
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=05C4E6E6-C3A7-4B55-A030-BD6B89C2F409@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=ludo@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.