Re: a suggestion for css

[Dumas Patrice]

Hi,

>     would be handy if it was possible to @import 
>     "http://my.site.org/site_widestyle.css"; instead of having it inlined.
> 
> How about:
> 
> echo '@import "http://my.site.org/site_widestyle.css";;' \
> | makeinfo --css-file=-

This doesn't really solve the issue because the content of
"http://my.site.org/site_widestyle.css"; is always of lower precedence 
with regard with makeinfo produced css.

>     The second issue is that it is not possible to take the rules overriding 
>     makeinfo css rules from 2 different files, only from one.
> 
> We could change --css-file so that it can be specified more than once,
> and all the output concatenated.  It will be a pain to read all the css
> files and collect all the @imports before outputting any of them, but it
> can be done, and it seems cleaner than introducing new options, if we
> can avoid it.

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

and file2.css:
   @import file4.css
   rule2

the resulting order would be in your case (all @imports before the rules)
   @import file3.css
   @import file4.css
   rule1
   rule2

and in my case (import files in the same order)
   @import file1.css
   @import file2.css

resulting in the following order:
   @import file3.css
   rule1
   @import file4.css
   rule2

This doesn't mean that allowing for multiple --css-file isn't a good idea,
but it solves another issue.

>     @import "makeinfo.css";
> 
> I really wanted to avoid putting the default css in an external file
> like this, because then makeinfo.css has to get installed
> somewhere/somehow, and it would just generally be an additional complication.

In that case it isn't possible to have something similar with my proposal
as the @import have to be before the makeinfo produced css.

Pat