From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao!not-for-mail From: Jean-Christophe Helary Newsgroups: gmane.comp.tex.texinfo.general,gmane.emacs.devel Subject: Re: html manual +css Date: Wed, 15 Jan 2020 21:12:15 +0900 Message-ID: <7D24D068-4BEF-4EC3-8C31-BED768533BEF@gmail.com> 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=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao:159.69.161.202"; logging-data="57475"; mail-complaints-to="usenet@ciao.gmane.io" To: Texinfo Help , emacs-devel Original-X-From: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Wed Jan 15 15:49:53 2020 Return-path: Envelope-to: gnu-help-texinfo2@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1irho9-00024N-6B for gnu-help-texinfo2@m.gmane-mx.org; Wed, 15 Jan 2020 13:30:01 +0100 Original-Received: from localhost ([::1]:52836 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irhX8-0008MH-C8 for gnu-help-texinfo2@m.gmane-mx.org; Wed, 15 Jan 2020 07:12:26 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46108) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1irhX3-0008M1-OE for help-texinfo@gnu.org; Wed, 15 Jan 2020 07:12:22 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1irhX2-0003Wx-Dh for help-texinfo@gnu.org; Wed, 15 Jan 2020 07:12:21 -0500 Original-Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]:44032) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1irhX2-0003Vt-7k; Wed, 15 Jan 2020 07:12:20 -0500 Original-Received: by mail-pg1-x533.google.com with SMTP id x7so8121240pgl.11; Wed, 15 Jan 2020 04:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=BnOFGPD1nGphC3JJlXev1n/nh+OLefO79KV7oD1NXMI=; b=Gq2LJQ6m9gMdyTFOOU0SXJXqWP1bElT1tk59ilGtF/Kc7JOz+TZhPaqun8MYHrn+Np TUUKcAzJp1JsSEHpwCe7zUkWyxVeQF/cZw2/11Eyd7e840mwzgI6BT/4ARPbMGzrg/yi VYfsfFt0fyrrd0SbU/DiQ3Pmn+gkBeeFcaYcGpJohUouIEHfF0vczpC2RqV8RubSZhKn SdGqIMvAztcoPHhbDI38etJ3x0EvdJ1EuKN36pzOGTZR7JIjLj1ReCZDloTAAuhXAzX+ juzevcQhR/apNPOS6cLdpi86oj4scuZSGN10Ee0zWphOXymQoDzzkkNi1feJcyilhZuY hAIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=BnOFGPD1nGphC3JJlXev1n/nh+OLefO79KV7oD1NXMI=; b=Xo5HNmYVf/eD4GYO8Kbt84+wW1/jmfiHASfTXjCbvG8t9mJR1hylXb5dEfz8KR1U/f Bwq8A90aTqPKcQqLZkgTfP8846/eRdQL3HH6PxqKC4pNkFRfZ0Q5buvpPrBETkEFUd5K dbXCv3SlOxbgpq3M0f5JypzcH9UPg/AoYBTM/oG7tt+JkgooU3AI22aU7yUwxT/UGlIN qzqsWMjRt9HUF+RO0XkrUq192eJExealQV8uLslVQuXF1dukEPV9SF41TTB2SWFh6BbK iDRatyyxOkzvZ00hq+clTaZTgHSKQGtSMuH90/EjpWoGxbzRsARCZxy01i3reYpCxi4I PGcA== X-Gm-Message-State: APjAAAUeS21eM4uNnQdc/iOFC7gnos3vM2sd0o9MnhoJSkgt/6gdQxTo x5d5YwgxgP5k5f7XHMqIXDJ9VMg5 X-Google-Smtp-Source: APXvYqy+ny9Pvx7qJO7e1NJvFFoN4eJX+c8NnU2Z/pOIRTJMI0s6S2CNG2nJ/sZHnfmopGOMOIfWsw== X-Received: by 2002:a65:530d:: with SMTP id m13mr32798208pgq.351.1579090338226; Wed, 15 Jan 2020 04:12:18 -0800 (PST) Original-Received: from [172.20.10.2] (KD182251137042.au-net.ne.jp. [182.251.137.42]) by smtp.gmail.com with ESMTPSA id c22sm21140674pfo.50.2020.01.15.04.12.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jan 2020 04:12:17 -0800 (PST) In-Reply-To: X-Mailer: Apple Mail (2.3608.40.2.2.4) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::533 X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Original-Sender: "help-texinfo" Xref: news.gmane.io gmane.comp.tex.texinfo.general:2335 gmane.emacs.devel:244269 Archived-At: Thank you for the reply Gavin. > On Jan 15, 2020, at 20:20, Gavin Smith = wrote: >=20 >> I have eventually resumed "work" on this and here is what I got: >>=20 >> Original: >> = https://www.gnu.org/software/emacs/manual/html_node/elisp/Visiting-Functio= ns.html >>=20 >> Sample: >> https://brandelune.github.io/code/Visiting-Functions.html >>=20 >> The css I wrote: >> = https://github.com/brandelune/brandelune.github.io/blob/gh-pages/code/emac= s.css >=20 > This looks quite good. If you change the width, or look at the file in a mobile phone or table = the menu should be able to change. Also, I've put online the emacs manuals for real life testing of that = css, if you want to try other manuals (they all share the same css so = it's not very exciting) you can find the set here: https://doublet.jp/gnu/ I'll probably remove the set when I am done testing. >> 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. >=20 > Possibly: this should be possible if somebody would implement it in > texi2any. texinfo.tex already detects the &optional keyword and > outputs it in boldface. Thank you for the hints. >> 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 >> @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 > The Guix developers managed to implement syntax highlighting by > post-processing the HTML. > (https://lists.gnu.org/archive/html/bug-texinfo/2019-11/msg00004.html) Wow, I just checked this page: = https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-Sys= tem.html and the source if full of css "hooks" even for the parens in the code... What they do is interesting, and I guess some kind of postprocessing = would be possible to achieve what I suggest, but instead of that, I'm = guessing that just having texinfo add the css selectors would be easier. Your video too is quite exciting, in the end that would be nice to have = a number of css variations if you manage to complete the system. Also, what's interesting with the current HTML export is that even = though it is quite "old" in terms of standard (supposed to accept HTML = 3.2 if I remember correctly ?) adding appropriate classes and IDs is = just enough to access even bleeding edge CSS. Hence the idea of adding = the appropriate "hooks" directly from texinfo. Jean-Christophe Helary ----------------------------------------------- http://mac4translators.blogspot.com @brandelune