[Top][All Lists]

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

RE: On being web-friendly and why info must die

From: Phillip Lord
Subject: RE: On being web-friendly and why info must die
Date: Wed, 10 Dec 2014 19:36:39 +0000

Way back, Achim Gratz posted a link to the port of the org-manual
to org-mode.


This clearly does show (by example) how to write a manual in org-mode. That 
post also 
explains the difficulties with doing this (i.e. the performance sucks).

Org-mode doesn't export to info (directly) at the moment. AFAICT, through info 
is simpler than texinfo, so there is no reason that it shouldn't be made to (at 
least once the 
current changes in the exported infrastructure are complete).

The advantage from a point of view of the author with org is that a significant 
amount of the functionality
of org-mode export (i.e. hyperlinks and the like) also works inside org-mode. 
So you can test it at source 
level. It would imagine some people would also be quite happy using org-mode as 
a replacement for info.
After all, headers and the like all work, navigation is quite functional.

Just a thought.

From: address@hidden address@hidden on behalf of Jay Belanger address@hidden
Sent: 10 December 2014 19:18
To: address@hidden
Cc: address@hidden
Subject: Re: On being web-friendly and why info must die

> John Kitchin wrote a GFDL licensed book on Density Functional Theory
> (a computationally efficient way of computing many quantum mechanical
> properties of materials) in Org mode.

Which is cool, but doesn't say how to write a manual in org mode.
Neither does mentioning a few pages in the middle of a long manual.

Is it feasible to have another program, besides texinfo, produce info
documents?  For example, could org be converted to info directly?

reply via email to

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