@subsubheading Step 2. Compile (with LilyPad)
From the same menus, select
-@w{@code{Compile > Tyepset}}.
+@w{@code{Compile > Typeset}}.
@sourceimage{Learning_Macos_Typeset_menu,,,}
@sourceimage{Learning_Macos_Open_menu,,,}
You must save any new edits you make to your file before you
-@w{@code{Compile > Tyepset}} and if the PDF file is not displayed
+@w{@code{Compile > Typeset}} and if the PDF file is not displayed
check the window with the progress log for any errors.
If you are not using the default Preview PDF viewer that comes
@sourceimage{Learning_Win7_Welcome_File_Whole,,,}
From the menus that appear along the top of the example file,
-select @w{@code{File > Save as}}. Do not use the @w{@code{File > Save}}
+select @w{@code{File > Save as}}. Do not use the @w{@code{File > Save}}
for the example file as this will not work until you have given it a
valid LilyPond file name.
@sourceimage{Learning_Win7_Open_Dragndrop,,,}
-@c FIXME: use 2nd-click? Right/Left depends on where you place your mouse.
Right-click on the file and from the pop-up context menu choose
@w{@code{Open with > LilyPond}}.
@sourceimage{Learning_Win7_Open_Context_Menu,,,}
-@c FIXME: why present/advise the best/simplest for last?
@subsubheading Step 2b. Compile (with double-clicking)
Or simply double-click the @file{test.ly}.
@subsubheading Step 3. View output
During the compilation of the @file{test.ly} file, a command window
-will, very briefly open and then close. Three additional files will
+will, very briefly open and then close. Three additional files will
have been created during this process.
@sourceimage{Learning_Win7_All_Files_Created,,,}
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
+can be ignored. It also gets overwritten each time you compile your
file.
If you are viewing your file in a PDF viewer, then you must close the
@c double \\ required because this is inside a macro!
@example
-\\version "@w{@version{}}"
+\\version "@w{@versionStable{}}"
@{
c' e' g' e'
@}
You will see something resembling:
@example
-GNU LilyPond @w{@version{}}
+GNU LilyPond @w{@versionStable{}}
Processing `test.ly'
Parsing...
Interpreting music...