On Fri, May 07, 2021 at 11:26:53AM +0200, Patrice Dumas wrote:
>
> > NO_CSS has other effects.
>
> Indeed, in addition to removing the CSS lines, it removes class
> definitions (and probably only some classes, not all). Maybe the best
> would be to remove NO_CSS completly and document that -c 'C
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> It seems wrong to include inline css in generated html files,
> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> The documentation is complicated. The advice to use !important
> to override the default style rules feels
On 5/6/21 1:13 PM, Gavin Smith wrote:
On 5/6/21 12:36 PM, Gavin Smith wrote:
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
It seems wrong to include inline css in generated html files,
especially when using the --ccs-ref or -C INFO_JS_DIR options.
The documentation is complicated
> On 5/6/21 12:36 PM, Gavin Smith wrote:
> > On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> >> It seems wrong to include inline css in generated html files,
> >> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> >> The documentation is complicated. The advice to use !
On 5/6/21 12:36 PM, Gavin Smith wrote:
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
It seems wrong to include inline css in generated html files,
especially when using the --ccs-ref or -C INFO_JS_DIR options.
The documentation is complicated. The advice to use !important
to ov
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> It seems wrong to include inline css in generated html files,
> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> The documentation is complicated. The advice to use !important
> to override the default style rules feels
[I missed your reply. Sorry for the delay.]
On 5/2/21 2:49 AM, Gavin Smith wrote:
Could you test the following and see if it works okay for using NO_CSS
with --css-ref?
Doesn't seem to work. Specifically I tried:
makeinfo -I=doc --html --split=section --no-number-sections -c INFO_JS_DIR=sty
On Sat, May 01, 2021 at 07:07:28PM -0700, Per Bothner wrote:
> It seems wrong to include inline css in generated html files,
> especially when using the --ccs-ref or -C INFO_JS_DIR options.
> The documentation is complicated. The advice to use !important
> to override the default style rules feels
It seems wrong to include inline css in generated html files,
especially when using the --ccs-ref or -C INFO_JS_DIR options.
The documentation is complicated. The advice to use !important
to override the default style rules feels quite wrong-headed.
However, looking at _default_format_css_lines
