On 6 April 2012 11:48, Moreno Marzolla <mor...@moreno.marzolla.name> wrote: > I have uploaded a new version which hopefully fixes both issues. > The tarball contains the texinfo sources which can immediately be used to > build the pdf manual using "makeinfo". > > Building the doc from scratch is a bit tricky as it involves extracting > relevant bits of information from info and %!demo blocks in the m-scripts. > The tarball contains the texinfo sources obtained after such preprocessing, > ready to be compiled (even by hand) with a single "makeinfo" command.
I have uploaded it to the server. About the documentation, I have never bothered much to check how octave builds its documentation but there's a @DOCSTRING that automatically gets the help text from a functino. You may want to check it out. I also think that pkg can deal with texinfo files on the doc directory so that one can use "doc queueing" to read the manul from the octave prompt. Carnë ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
