From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: Language menu in the HTML manual
Date: Wed, 19 Jan 2022 15:48:07 +0100 [thread overview]
Message-ID: <8735ljbx3s.fsf@gnu.org> (raw)
In-Reply-To: <05C4E6E6-C3A7-4B55-A030-BD6B89C2F409@lepiller.eu> (Julien Lepiller's message of "Wed, 19 Jan 2022 10:11:25 +0100")
Hello,
Julien Lepiller <julien@lepiller.eu> skribis:
> 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.
Oops, indeed.
Commit fa580bf3b456273ebbbba20b3f4de1afdac3d031 should fix that. It
also introduces the navigation bar as found on the Guix web site; I
didn’t plan to do that, but that sorta came with the rest, so…
(Clearly, we’re past the limits of what I manage on the CSS side.)
It should show up soon.
> 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.
Yes. What makes it difficult is that Texinfo transliterates node names
to ASCII (which I find imperialistic and ridiculous, or at least
anachronistic):
https://guix.gnu.org/manual/devel/ru/html_node/Nachinaya.html
https://guix.gnu.org/manual/devel/zh-cn/html_node/Ru-Men-.html
Probably the easiest (and ugliest?) way to fix it would be to view the
transliteration algorithm as a black box and to implement a mapping from
node names to file names, similar to the indexes computed in
‘doc/build.scm’.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-01-19 15:06 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
2022-01-19 14:48 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735ljbx3s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).