@cindex example, first
@cindex case sensitive
-@qq{Compiling} is the term used for processing an input file
-in LilyPond format to produce a file which can be printed and
-(optionally) a MIDI file which can be played. LilyPond input
-files are simple text files. The first example
-shows what a simple input file looks like.
+@qq{Compiling} is the term used for processing an input file in
+LilyPond format to produce output file(s). Output files are
+generally PDF (for printing or viewing), MIDI (for playing), and
+PNG (for online use). LilyPond input files are simple text files.
-To create sheet music, we write an input file that specifies the
-notation. For example, if we write:
+This example shows a simple input file:
@example
@{
@}
@end example
-@noindent
-the result looks like this:
+The graphical output is:
@c in this case we don't want verbatim
@lilypond[quote]
@smallspace
-@subheading Viewing output
+@subheading Producing output
@c TODO: move index entries
@cindex PDF file
@cindex running LilyPond under Unix
@cindex Unix, running LilyPond
-Producing output depends on your operating system and the
-program(s) you use.
+The method of producing output depends on your operating system
+and the program(s) you use.
@itemize
@end itemize
-There are several other text editors available with better support
-for LilyPond. For more information, see
+There are several other text editors available with specific
+support for LilyPond. For more information, see
@rweb{Alternate input}.
@warning{The first time you ever run LilyPond, it may take a
@node MacOS X
@subsection MacOS X
-@warning{These instructions assume that you are using the Lilypond
+@warning{These instructions assume that you are using the LilyPond
application. If you are using any of the programs described in
@rweb{Alternate input}, please consult the documentation for
those programs if you have any problems.}
@rweb{Alternate input}, please consult the documentation for
those programs if you have any problems compiling a file.}
+@subsubheading Step 1. Create your @file{.ly} file
+
Double-click the @command{LilyPond.app}, an example file will open.
@sourceimage{Learning_Win7_Welcome_File_Whole,,,}
@sourceimage{Learning_Win7_Save_File_With_Name,,,}
+@subsubheading Step 2a. Compile with drag-and-drop
+
Depending on what you prefer, to compile your file either:
Drag-and-drop the file directly onto the LilyPond icon.
@sourceimage{Learning_Win7_Open_Context_Menu,,,}
+@subsubheading Step 2b. Compile with double-clicking
+
Or simply double-click the @file{test.ly}.
+@subsubheading Step 3. Processing and viewing
+
During the compilation of the @file{test.ly} file, a command window
will, very briefly open and then close. Three additional files will
have been created during this process.
@sourceimage{Learning_Win7_Pdf_Output,,,}
+@subsubheading Other commands
+
To create a new file, begin by selecting @w{@code{File > New}} from
within any previously created file.
@sourceimage{Learning_Win7_New_Menu,,,}
+@noindent
or @w{@code{File > Open}} to open and edit any files you have saved
before.
@sourceimage{Learning_Win7_Log_File,,,}
-This log file is overwritten each time you compile your lilypond file.
+This log file is overwritten each time you compile your LilyPond file.
The PS file is used internally by LilyPond to create the PDF file and
can be ignored. It also gets overwritten each time you compile your
PDF if you wish to make a new compilation as it may fail to create
the new PDF while it is still being viewed.
+
@node Command-line
@subsection Command-line
-@warning{These instructions assume that you are using commond unix
-command-line programs. If you are using any of the programs
-described in @rweb{Alternate input}, please consult the
+@warning{These instructions assume that you are familiar with
+common unix command-line programs. If you are using any of the
+programs described in @rweb{Alternate input}, please consult the
documentation for those programs if you have any problems
compiling a file.}