On Monday 25 February 2008, Hamish wrote: > Dylan Beaudette wrote: > > I wonder if now would be a good time to investgate the use of CSS in > > the man pages. If we define a couple types of "container" objects > > (<div>, <span>, etc) we can use a single style file to later > > manipulate the look and feel of the manual pages. > > ... > > > I am not CSS expert, but it would seem that we could easily create a > > set of classes - or class hierarchy to allow global changes to the > > style of the manual. The self-documenting 'class' operator might be > > helpful as well. > > It is already in place: > > $ head -n 7 dist.i686-pc-linux-gnu/docs/html/r.random.html > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > <html> > <head> > <title>GRASS GIS: r.random</title> > <meta http-equiv="Content-Type" content="text/html; > charset=iso-8859-1"> > <link rel="stylesheet" href="grassdocs.css" type="text/css"> > </head> > > > notice how the <H2> text is already green+sans? and all the <div > class=code> sections in the examples? > > grassdocs.css is in tools/ > > I see no compelling reason to add a new class for module names, etc. > K.I.S.S. > > > Hamish >
Thanks for the reminder. My original post was mostly about block elements, but keeping it simple might be more important. Dylan -- Dylan Beaudette Soil Resource Laboratory http://casoilresource.lawr.ucdavis.edu/ University of California at Davis 530.754.7341 _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
