3.3 Texinfo introduction and usage policy


3.3.1 Texinfo introduction

The language is called Texinfo; you can see its manual here:

http://www.gnu.org/software/texinfo/manual/texinfo/

However, you don’t need to read those docs. The most important thing to notice is that text is text. If you see a mistake in the text, you can fix it. If you want to change the order of something, you can cut-and-paste that stuff into a new location.

Note: Rule of thumb: follow the examples in the existing docs. You can learn most of what you need to know from this; if you want to do anything fancy, discuss it on lilypond-devel first.


3.3.2 Documentation files

The user manuals lives in ‘Documentation/user/’. In particular, the files ‘lilypond-learning.ly’ (LM), ‘lilypond.itely’ (NR), ‘music-glossary.tely’ (MG), and ‘lilypond-program’ (AU). Each chapter is written in a separate file (ending in ‘.itely’ for files containing lilypond code, and ‘.itexi’ for files without lilypond code); see the “main” file for each manual to determine the filename of the specific chapter you wish to modify.

Developer manuals live in ‘Documentation/devel’. Currently there is only one; ‘contrib-guide.texi’.

Although snippets are part of documentation, they are not (directly) part of the manuals. For information about how to modify them, see LSR work.


3.3.3 Sectioning commands

Most of the manual operates at the

@node Foo
@subsubsection Foo

level. Sections are created with

@node Foo
@subsection Foo

3.3.4 LilyPond formatting


3.3.5 Text formatting


3.3.6 Syntax survey


3.3.7 Other text concerns


Contributor’s Guide