bug-texinfo
[Top][All Lists]
Advanced

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

Re: CSS file for texinfo HTML output


From: Per Bothner
Subject: Re: CSS file for texinfo HTML output
Date: Mon, 8 Feb 2016 18:31:24 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0

On 02/08/2016 12:23 PM, Gavin Smith wrote:

I could say more around the subject of HTML and Info, most of which
has been said already, but I doubt it would make much difference. The
only way that anything will happen is if there are very concrete
proposals. Even a 95%-complete proof of concept is probably not good
enough without a plausible way to deploy it.

There is probably no great barrier to this question, other than taking
care of this last 5%. I haven't said what the "HTML-Info" question is,
because defining the question is part of the problem. It seems easy
enough, but talk is cheap, and anyone one who comes forward with an
answer will need to define the question thoroughly themselves.

Certainly.  I did mention earlier a possible Google Summer of Code project,
which I'm willing to mentor.  However, it might require a bit more
taste and experience than we'd entrust to someone new.

Perhaps a GNU fundraiser or something like a Kickstarter project?
I've done a lot of JavaScript programming recently (see http://domterm.org),
so I could handle at least the JavaScript / HTML side of it.

and then add the following in the <head>:

<script type="text/javascript" src="info.js"></script>

How do people add this in the <head>? By typing it in with a text
editor? With a browser plugin that adds the line automatically?

Of course not.

That's the kind of specific point that needs to be taken care of.

The obvious simply approach is to add --javascript-include and/or
--javascript-ref command-line options to makeinfo, by analogy
with --css-include and --css-ref.

It might be desirable to "plug in" user-selectable JavaScript
user-interface libraries on the fly depending on the user preference,
but the simple makeinfo-time --javascript-ref option will do to start with.

The info.js is unnecessarily complex because the structure
of the html generated by makeinfo (texinfo 6.0) is very poor.
To start with texinfo really should generate id="xxx" attributes
rather than <a name="xxx"> nodes.

Please elaborate on why "name" is better that "id", and anything else
that is wrong with the HTML that is generated.

Other way around ("id" is better than "name") - see separate message.

--
        --Per Bothner
address@hidden   http://per.bothner.com/



reply via email to

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