From mboxrd@z Thu Jan 1 00:00:00 1970 From: swedebugia Subject: Re: Communication and Design at Guix Date: Tue, 15 Jan 2019 00:25:20 +0100 Message-ID: <8736puu8in.fsf@riseup.net> References: <87k1jfuk26.fsf@gnu.org> <705CB66B-E8D5-4119-9F70-D429E1B174B2@pretty.Easy.privacy> <877efd1p56.fsf@gnu.org> <87r2dk4m4g.fsf@elephly.net> <87k1j81bau.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:43271) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gjBby-00065z-S9 for guix-devel@gnu.org; Mon, 14 Jan 2019 18:25:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gjBbw-000754-QD for guix-devel@gnu.org; Mon, 14 Jan 2019 18:25:41 -0500 In-Reply-To: <87k1j81bau.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 13 Jan 2019 22:45:45 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: "guix-devel@gnu.org" , L p R n d n Ludovic Court=C3=A8s writes: > Hi! > > Ricardo Wurmus skribis: >> It=E2=80=99s fine to deviate from the consistent style. We do that alre= ady for >> the style sheet that=E2=80=99s used for our HTML documentation. Compare= this: >> >> https://www.gnu.org/software/sharutils/manual/html_node/index.html >> >> with this: >> >> https://www.gnu.org/software/guix/manual/en/html_node/index.html >> >> It=E2=80=99s fine to change our style sheet, but let=E2=80=99s stay with= Texinfo. > > Note that our manual uses https://gnu.org/software/gnulib/manual.css, > which is the standard CSS produced by Gnulib=E2=80=99s gendocs.sh, and th= is CSS > is used by many (most?) manuals at gnu.org, not just Guix. > > My suggestion was to improve this CSS, if L p R n d n is willing to make > the extra social effort to get changes accepted. If that doesn=E2=80=99t= work, > we can depart from that. Thanks for the clarification :) I looked into the chicken docs and their html and css. They generate their examples from source-code with this MIT chicken egg-script:=20 http://code.call-cc.org/svn/chicken-eggs/release/4/colorize/trunk/colorize.= scm. To use their approach with parens highlighting we would need to either depend on chicken and this egg or port it to guile. I ran it just for fun and got an error as expected. :p It generates nice html like this: 
;; irr=
egex, the regular expression library, is one of the
;; libraries included with CHICKEN.
(import (chicken irregex)
        (chicken io)<=
/span>)


The CSS magic is this (public domain):
#content .highlight .paren1,#content .highlight .paren2,#content .highlight=
 .paren3,#content .highlight .paren4,#content .highlight .paren5,#content .=
highlight .paren6 {
    background-color:inherit;
}

#content .highlight .paren1:hover,#content .highlight .paren2:hover,#conten=
t .highlight .paren3:hover,#content .highlight .paren4:hover,#content .high=
light .paren5:hover,#content .highlight .paren6:hover {
    color:#FFF;
    font-weight:700;
}

#content .highlight .paren1:hover {
    background-color:#DB7859;
}

#content .highlight .paren2:hover {
    background-color:#1B804C;
}

#content .highlight .paren3:hover {
    background-color:#9F214E;
}

#content .highlight .paren4:hover {
    background-color:#DBA059;
}

#content .highlight .paren5:hover {
    background-color:#B64926;
}

#content .highlight .paren6:hover {
    background-color:#64A422;
}

#content .highlight .comment {
    color:#8C8281;
    font-style:italic;
}