[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: html manual +css

From: Jean-Christophe Helary
Subject: Re: html manual +css
Date: Tue, 24 Dec 2019 01:54:43 +0900

I have eventually resumed "work" on this and here is what I got:



The css I wrote:

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 :)

Anyway, if it looks useful I'd like to think of ways to have it more widely 

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).

For ex:

@deffn Command find-file filename &optional wildcards


<dt id="index-find_002dfile">Command: <strong>find-file</strong> <em>filename 
&amp;optional wildcards</em></dt>

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:

<dt id="index-find_002dfile" class="command">Command: <strong 
class="command-name">find-file</strong> <em class="argument">filename</em> 
<span class="keyword">&amp;optional</span> <em 

Also, examples should have similar tagging:

(switch-to-buffer (find-file-noselect filename nil nil wildcards))
@end smallexample

could be something like 

(@commandname switch-to-buffer (@commandname find-file-noselect @arguments 
filename nil nil wildcards))
@end smallexample

so that we can have ways to target their contents with css.


> On Jun 7, 2017, at 23:27, Jean-Christophe Helary <address@hidden> wrote:
>> Jun 7, 2017 8:47、Jean-Christophe Helary <address@hidden>のメール:
>>>> What I did to get the same CSS as the site is curl the css files. There 
>>>> are 3 of those:
>>> 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.
>>> 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.
>> CSS is not high level wizardry, maybe it would be simpler to create a new 
>> set of rules for the offline manual ?
> 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).
> I'd like to know what kind of licence should such a CSS file come with.
> Jean-Christophe

Jean-Christophe Helary
----------------------------------------------- @brandelune

reply via email to

[Prev in Thread] Current Thread [Next in Thread]