Mercurial > hg > octave-nkf > gnulib-hg
changeset 17362:5cadd9d309b1
autoupdate
author | Karl Berry <karl@freefriends.org> |
---|---|
date | Sat, 09 Mar 2013 07:23:53 -0800 |
parents | 35650a3443e8 |
children | c332767f3c68 |
files | doc/standards.texi |
diffstat | 1 files changed, 8 insertions(+), 8 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/standards.texi +++ b/doc/standards.texi @@ -3,7 +3,7 @@ @setfilename standards.info @settitle GNU Coding Standards @c This date is automagically updated when you save this file: -@set lastupdate February 13, 2013 +@set lastupdate March 8, 2013 @c %**end of header @dircategory GNU organization @@ -3373,13 +3373,13 @@ the framework for a beginner to understand the rest of the manual. The Bison manual provides a good example of how to do this. -To serve as a reference, a manual should have an Index that list all the -functions, variables, options, and important concepts that are part of -the program. One combined Index should do for a short manual, but -sometimes for a complex package it is better to use multiple indices. -The Texinfo manual includes advice on preparing good index entries, see -@ref{Index Entries, , Making Index Entries, texinfo, GNU Texinfo}, and -see @ref{Indexing Commands, , Defining the Entries of an +To serve as a reference, a manual should have an Index that lists all +the functions, variables, options, and important concepts that are +part of the program. One combined Index should do for a short manual, +but sometimes for a complex package it is better to use multiple +indices. The Texinfo manual includes advice on preparing good index +entries, see @ref{Index Entries, , Making Index Entries, texinfo, GNU +Texinfo}, and see @ref{Indexing Commands, , Defining the Entries of an Index, texinfo, GNU Texinfo}. Don't use Unix man pages as a model for how to write GNU documentation;