bug-texinfo
[Top][All Lists]
Advanced
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @format and @display in HTML output

From: Torsten Bronger
Subject: Re: @format and @display in HTML output
Date: Sun, 20 Apr 2003 11:03:59 +0200
User-agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 
Halloechen!

address@hidden (Karl Berry) writes:

>     <style type="text/css">
>       pre.format { font-family: serif }
>     </style>
>
> Do you think <style> is supported by enough browsers to make this
> acceptable?  I guess so.  The downside is small, anyway (typewriter text
> for @format/@display output).

I've made awful experiences with CSS in my own project.  Every CSS
interpreter I've seen so far is full of bugs.  On the other hand,
the *simple* CSS commands are very secure nowadays, and makeinfo
needs only the simplest.  (Just changes in fontspace -- but to whom
I say that ;-)

>     at the end of the <head>.  (Because the class attribute is set I
>     assume that a makeinfo developer wanted to use CSS.?)
>
> Yes, Stephen Gildea sent me the changes for all those class= attributes,
> precisely so changes like this could be made.
>
> I think I'll do it, thereby starting down the slippery slope :).  Thanks.

These are all class attributes that I could find in the source code:

small.dots      { }
small.enddots   { }
h1.titlefont    { }
div.footnote    { }
div.node        { }
div.contents    { }
div.shortcontents       { }
h1.settitle     { }  /* Global title */
ul.index-cp     { }
ul.index-fn     { }
ul.index-vr     { }
ul.index-ky     { }
ul.index-pg     { }
ul.index-tp     { }
ul.menu         { }
pre.display     { }
pre.smalldisplay        { }
pre.example     { }
pre.smallexample        { }
pre.lisp        { }
pre.smalllisp   { }
pre.smallformat { }
pre.format      { }
pre.verbatim    { }

.chapter        { }
.unnumbered     { }
.appendix       { }
.majorheading   { }
.chapheading    { }
.section        { }
.unnumberedsec  { }
.appendixsec    { }
.heading        { }
.subsection     { }
.unnumberedsubsec       { }
.appendixsubsec { }
.subheading     { }
.subsubsection  { }

Most of them will remain empty probably.  I see two weak points:
The user may define a new index.  Then the program must create CSS
code instead of just including a static CSS fragment (unless, of
course, ul.index-?? does nothing anyway).

The second issue are the .chapter etc. selectors.  I couldn't be
more specific here, because they can occure in all combinations with
<h1>...<h6> as far as I understand it.  The alternative would be to
fish for <h?>.  But I think all .chapter's have more in common than
all <h2>'s.

It would be wonderful if the user could give the filename of a CSS
fragment as an argument to makeinfo that is merely appended to the
predefined CSS code.  This would be a simple, clean, and typical CSS
approach.

Tschoe,
Torsten.
reply via email to
[Prev in Thread] Current Thread [Next in Thread]