1 \input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. For details, see the Contributors'
7 Guide, node Updating translation committishes..
10 @setfilename lilypond-usage.info
11 @settitle LilyPond Application Usage
12 @documentencoding UTF-8
17 This file explains how to execute the programs distributed with
18 LilyPond version @version{}. In addition, it suggests some
19 @qq{best practices} for efficient usage.
22 @c `Usage' was born 1999-10-10 with git commit c82c30c...
23 @macro copyrightDeclare
24 Copyright @copyright{} 1999--2012 by the authors.
31 @c don't remove this comment.
33 @omfcreator Han-Wen Nienhuys, Jan Nieuwenhuizen and Graham Percival
34 @omfdescription Application Usage of the LilyPond music engraving system
35 @omftype program usage
36 @omfcategory Applications|Publishing
47 @c maybe add a "Tasks" or "Specific tasks" or something like
48 @c that, after Suggestions -gp
50 * Running lilypond:: Operation.
51 * Updating files with convert-ly:: Updating input files.
52 * lilypond-book:: Integrating text and music.
53 * External programs:: Mixing LilyPond and other programs.
54 * Suggestions for writing files:: Best practices and effective bug-fixing.
58 * GNU Free Documentation License:: License of this document.
68 @allowcodebreaks false
70 @include usage/running.itely
71 @include usage/updating.itely
72 @include usage/lilypond-book.itely
73 @include usage/external.itely
74 @include usage/suggestions.itely
79 @appendix LilyPond index