On 6 February 2016 at 01:30, Per Bothner wrote:
> What is the use case for --xml format? I'd drop it in favor of --xhtml,
> where --xhtml is the same as --html except strictly XML compatible - with
> no required DTDs or entity definitions.
I wondered the same myself; here is a response from Patr
On 9 February 2016 at 02:11, Per Bothner wrote:
> Currently, in html output the node "Foo" generates a
> element. In general I think it is better to an id="Foo" attributes.
> Reasons that come to mind:
> (1) Simpler and less cluttered html, since we can attach the id attribute
> to some other su
On 02/08/2016 12:23 PM, Gavin Smith wrote:
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
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
Currently, in html output the node "Foo" generates a
element. In general I think it is better to an id="Foo" attributes.
Reasons that come to mind:
(1) Simpler and less cluttered html, since we can attach the id attribute
to some other suitable element, rather than generating a separate one.
(2)
On 8 February 2016 at 15:20, Masamichi HOSODA wrote:
>> I hope it's clear what I'm trying to do here: instead of redefining,
>> change the value of a conditional that is used within the macro. I
>> thought that something similar might be possible with XeTeX's native
>> Unicode.
>
> Thank you for y
On 8 February 2016 at 18:55, Per Bothner wrote:
> The demo link doesn't work so it's hard to try it out:
> It depends on docker and elnode and proxying the GNU website.
> Interesting, and probably has some useful code, but
> it looks like a dead end to me.
>
> What I have in mind is much simpler:
Per> Also with JavaScript one could have the same keyboard shortcuts
Per> (more or less) as the info program or Emacs info mode.
See https://github.com/nicferrier/gnudoc-js
Tom
> I hope it's clear what I'm trying to do here: instead of redefining,
> change the value of a conditional that is used within the macro. I
> thought that something similar might be possible with XeTeX's native
> Unicode.
Thank you for your advice.
I've made a patch.
ChangeLog:
Native Unicode re
