From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.emacs.devel Subject: Re: html manual +css Date: Tue, 24 Dec 2019 23:43:46 +0900 Message-ID: <1BACB908-1E1F-40F7-BC27-8B6B64326B94@traduction-libre.org> References: <05A866DB-4211-476E-9107-14E5F9BE9232@gmail.com> <53DA475D-B063-470A-BB87-D3FFC9A7CF79@gmail.com> <834lvyct3t.fsf@gnu.org> <01B655FC-51F0-4A33-ADBF-3E1268E9E0EA@gmail.com> <3D282E00-27F3-451A-9895-5BCEEE0B7FA8@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="206464"; mail-complaints-to="usenet@blaine.gmane.org" To: emacs-devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 24 15:45:53 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ijlRZ-000rUY-ED for ged-emacs-devel@m.gmane.org; Tue, 24 Dec 2019 15:45:53 +0100 Original-Received: from localhost ([::1]:39608 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijlRX-0000ui-NV for ged-emacs-devel@m.gmane.org; Tue, 24 Dec 2019 09:45:51 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53076) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijlQo-0000Pg-9g for emacs-devel@gnu.org; Tue, 24 Dec 2019 09:45:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ijlQm-0006uX-Rk for emacs-devel@gnu.org; Tue, 24 Dec 2019 09:45:06 -0500 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:54441) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ijlQm-0006tB-JB for emacs-devel@gnu.org; Tue, 24 Dec 2019 09:45:04 -0500 Original-Received: from [172.20.10.3] (KD182251133105.au-net.ne.jp [182.251.133.105]) (Authenticated sender: jean.christophe.helary@traduction-libre.org) by relay10.mail.gandi.net (Postfix) with ESMTPSA id 1FBE7240005 for ; Tue, 24 Dec 2019 14:44:55 +0000 (UTC) In-Reply-To: X-Mailer: Apple Mail (2.3608.40.2.2.4) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 217.70.178.230 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243610 Archived-At: > 2) when the display is not wide enough to have the full horizontal = menu, the menu is displayed on the right side of the screen,=20 I meant "left side". JC > On Dec 24, 2019, at 23:37, Jean-Christophe Helary = wrote: >=20 >=20 >=20 >> On Dec 24, 2019, at 2:20, Stefan Monnier = wrote: >>=20 >>> Sample: >>> https://brandelune.github.io/code/Visiting-Functions.html >>=20 >> Thanks, this looks pretty good on my desktop (haven't tried it >> elsewhere yet). One thing I'd find useful is to keep the next/up = first >> line "floating at the top", so they're always available without = having >> to scroll to the top or to the bottom. >> [ Tho I guess when reading on a small screen I might prefer it the = way >> it is now. ] >=20 > Ok, so I have something that works both ways: >=20 > 1) when the display is wide enough to have the full horizontal menu, = the menu is displayed horizontally and follows the scrolling. >=20 > 2) when the display is not wide enough to have the full horizontal = menu, the menu is displayed on the right side of the screen, as a list = of links, with "icons" before the link names to hint at their use, and = the menu sticks to its original position. >=20 > All that is implemented without modifying the HTML output by texinfo. = I'm just using the existing HTML tags and attributes to "anchor" CSS = variations on them. >=20 > Would you mind checking if that works as you intended ? >=20 > Jean-Christophe >=20 >>=20 >>=20 >> Stefan >>=20 >>=20 >>> The css I wrote: >>> = https://github.com/brandelune/brandelune.github.io/blob/gh-pages/code/emac= s.css >>>=20 >>> It is something I had done a while ago so I just spent a few hours = today >>> cleaning it up but I'm really not sure how I came up with the = various values >>> anymore :) >>>=20 >>> Anyway, if it looks useful I'd like to think of ways to have it more = widely used. >>>=20 >>> Also, there are plenty of things that would be nice to have but in a = way >>> we're hitting the limits of the texinfo output (and my css skills = too, of >>> course). >>>=20 >>> For ex: >>>=20 >>> @deffn Command find-file filename &optional wildcards >>>=20 >>> becomes >>>=20 >>>
Command: find-file >>> filename &optional wildcards
>>>=20 >>> it would be nice to have the arguments tagged individually and the = &optional >>> or &rest keywords tagged in a different way. Also to have the = various >>> templates identified for what they are. Maybe something like: >>>=20 >>>
Command: >> class=3D"command-name">find-file filename >>> &optional >> class=3D"optional">wildcards
>>>=20 >>> Also, examples should have similar tagging: >>>=20 >>> @smallexample >>> (switch-to-buffer (find-file-noselect filename nil nil wildcards)) >>> @end smallexample >>>=20 >>> could be something like=20 >>>=20 >>> @smallexample >>> (@commandname switch-to-buffer (@commandname find-file-noselect = @arguments >>> filename nil nil wildcards)) >>> @end smallexample >>>=20 >>> so that we can have ways to target their contents with css. >>>=20 >>> Jean-Christophe=20 >>>=20 >>>> On Jun 7, 2017, at 23:27, Jean-Christophe Helary = wrote: >>>>=20 >>>>=20 >>>>> Jun 7, 2017 8:47=E3=80=81Jean-Christophe Helary = =E3=81=AE=E3=83=A1=E3=83=BC=E3=83=AB: >>>>>=20 >>>>>>> What I did to get the same CSS as the site is curl the css = files. There are 3 of those: >>>>>>> https://www.gnu.org/software/emacs/manual.css >>>>>>> https://www.gnu.org/style.css >>>>>>> https://www.gnu.org/reset.css >>>>>>=20 >>>>>> Each of these files has a licensing problem. I asked FSF staff = to fix >>>>>> the last two, and mailed to emacs-devel about the first. >>>>>>=20 >>>>>> In the meantime, please don't copy any of that code, with or = without changes, >>>>>> to any other file that will be distributed to the public. >>>>>=20 >>>>> CSS is not high level wizardry, maybe it would be simpler to = create a new >>>>> set of rules for the offline manual ? >>>>=20 >>>> I've created a single css file which renders in a way that's = similar to >>>> the web version of the HTML pages (it is not identical though). >>>>=20 >>>> I'd like to know what kind of licence should such a CSS file come = with. >>>>=20 >>>> Jean-Christophe >>>=20 >>> Jean-Christophe Helary >>> ----------------------------------------------- >>> http://mac4translators.blogspot.com @brandelune