bug-texinfo
[Top][All Lists]
Advanced

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

Re: a suggestion for css


From: Karl Berry
Subject: Re: a suggestion for css
Date: Tue, 29 Jul 2003 17:13:54 -0400

    is always of lower precedence 
    with regard with makeinfo produced css.

True, but (1) why would you want to override the makeinfo css?  It's
really a few very simple decls that implement the display environments
more correctly, not stylistic choices at all.

And (2) I was informed (by Torsten Bronger
<address@hidden>) that you can actually override things
"in advance", so to speak, with `inherit ! important'.  I never actually
tried it, but it sounded plausible, and I put it in the manual.

    It doesn't lead to the same order. For example if there is file1.css:

Ah, I see.  Yes, you are right about that.  However, the same result of

   @import file1.css
   @import file2.css

can still be accomplished (modulo the builtin makeinfo css rules) with
things as they are now, by creating trivial files or using stdin to say
exactly "@import file1.css; @import file2.css;".


Anyway, like I say, I recognize that there are certainly cases where it
makes a difference in theory ... But is there a practical case where all
matters?  I'm a lot more inclined to cope with implementing new
complexity if it solves a practical problem ...  Creating and installing
a makeinfo.css really seems like something to avoid to me, if at all
possible.

Thanks,
k




reply via email to

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