Re: Integration of Info manuals in programming modes, Re: Integration of Info manuals in programming modes

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > We can for example also export from Org Mode to info, and that also does
  > not replace texinfo but rather extends the possibilities we have to
  > generate well-usable manuals.

  > Ideally all the different code documentation tools could export either
  > to texinfo or to info, and pandoc[1] can already convert most manual
  > formats to info.

It is posible to convert from any format to Texinfo and make some sort
of a manual in Texinfo.  That is presumably an advance compared with
no Texinfo version at all.

But if that other format cannot express the distinctions that are
standard for Texinfo, the output of this conversion won't be a very
good Texinfo manual.  It will be an inferior Texinfo manual, compared
with the ones natively written in Texinfo.

That might be better than what we have now, but it is not good.

To get a _good_ Texinfo manual requires people to manually convert the
manual into Texinfo, or into some possible future format which can
makes those distinctions.

So the question is how we can stimulate work to produce the _best_
result, rather than accepting forever an inferior result.

Any ideas?

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)