From bf41bb2eb8df456cdf738d42062b28d21bf42b6c Mon Sep 17 00:00:00 2001 From: Han-Wen Nienhuys Date: Sat, 18 Jun 2005 23:45:11 +0000 Subject: [PATCH] * Documentation/user/tutorial.itely (Running LilyPond for the first time): separate subsections for windows, macos and unix. * Documentation/user/invoking.itely (Updating files with convert-ly): add MacOS X note. --- ChangeLog | 22 ++++++++---- Documentation/user/invoking.itely | 7 ++-- Documentation/user/tutorial.itely | 60 ++++++++++++++++++------------- scm/output-svg.scm | 6 ++++ 4 files changed, 61 insertions(+), 34 deletions(-) diff --git a/ChangeLog b/ChangeLog index 80cd2c6932..2fee536c38 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,11 @@ +2005-06-19 Han-Wen Nienhuys + + * Documentation/user/tutorial.itely (Running LilyPond for the + first time): separate subsections for windows, macos and unix. + + * Documentation/user/invoking.itely (Updating files with + convert-ly): add MacOS X note. + 2005-06-18 Han-Wen Nienhuys * lily/paper-outputter.cc (file): open file in binary mode. This @@ -1195,7 +1203,7 @@ * scm/backend-library.scm (postscript->pdf): Invoke gs instead of going through ps2pdf wrappers. -2005-05-09 Jürgen Reuter +2005-05-09 Jürgen Reuter * Documentation/user/instrument-notation.itely: petrucci note heads: updated docu @@ -1590,11 +1598,11 @@ * lily/mensural-ligature.cc (brew_flexa): apply thickness property only on vertical lines of flexa shape, and use a constant thickness value for horizontal lines (patch slightly modified by - Jürgen Reuter) + Jürgen Reuter) * lily/include/mensural-ligature.hh: make 2 comments clearer -2005-04-28 Jürgen Reuter +2005-04-28 Jürgen Reuter * lily/vaticana-ligature-engraver.cc (need_extra_space): renamed to need_extra_horizontal_space; bugfix: use class scope to avoid @@ -2859,7 +2867,7 @@ * Documentation/user/global.itely (Page layout): remove printpagenumber. -2005-03-13 Jürgen Reuter +2005-03-13 Jürgen Reuter * input/regression/mensural-ligatures.ly: new file (with examples compiled by Pal Benko). @@ -3595,7 +3603,7 @@ * Documentation/user/notation.itely: small but urgent fix. -2005-02-21 Jürgen Reuter +2005-02-21 Jürgen Reuter * lily/duration-scheme.cc: bugfix: correct parameters to SCM_ASSERT_TYPE. @@ -3685,7 +3693,7 @@ * configure.in: add endian test. -2005-02-19 Jürgen Reuter +2005-02-19 Jürgen Reuter * Documentation/user/examples.itely: small simplification/beautification @@ -6838,7 +6846,7 @@ * tex/lily-pdf-defs.tex, tex/lily-ps-defs.tex (\lilypondexperimentalfeatures): Removed. -2004-10-20 Jürgen Reuter +2004-10-20 Jürgen Reuter * Documentation/user/notation.itely: fixed 2 typos diff --git a/Documentation/user/invoking.itely b/Documentation/user/invoking.itely index ab6271d664..7e8780ffc0 100644 --- a/Documentation/user/invoking.itely +++ b/Documentation/user/invoking.itely @@ -422,9 +422,10 @@ often is no longer compatible with older input files. To remedy this, the program @command{convert-ly} can be used to deal with most of the syntax changes between LilyPond versions. -It uses @code{\version} statements in the input files to detect the old -version number. In most cases, to upgrade your input file it is sufficient -to run +It uses @code{\version} statements in the input files to detect the +old version number. In most cases, to upgrade your input file it is +sufficient to run@footnote{MacOS X users may execute this command +under the menu entry @samp{Compile > Update syntax}.} @example convert-ly -e myfile.ly diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 6064d2517c..0ce658214a 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -200,21 +200,47 @@ see @ref{Time signature}. @c cheesy title to avoid clash with chapter name. -In the last section we explained what kind of things you can enter -in a LilyPond file. In this section we will explain what commands to -run and how to view or print the output. If you have not used -LilyPond before, want to test your setup, or want to run an example -file yourself, read this section. The instructions that follow are -for Unix-like systems. Some additional instructions for Microsoft -Windows are given at the end of this section. +In the last section we explained what kind of things you can enter in +a LilyPond file. In this section we will explain what commands to run +and how to view or print the output. If you have not used LilyPond +before, want to test your setup, or want to run an example file +yourself, read this section. + +@unnumberedsubsec MacOS X + +If you double click LilyPond.app, it will open with an example +file. Save it, for example, to @file{test.ly} on your Desktop, and +then process it with the menu command @samp{Compile > Typeset File}. +The resulting PDF file will be displayed on your screen. + +Be warned that first-ever run will take a minute or two, because all +of the system fonts have to be analyzed first. + +@unnumberedsubsec Windows + +On Windows, start up a text-editor@footnote{Any simple or +programmer-oriented editor will do, for example Notepad. Do not use a +word processor, since these insert formatting codes that will confuse +LilyPond.} and enter + +@example +@{ c'4 e' g' @} +@end example + +Save it on the desktop as @file{test.ly} and make sure that it is not +called @file{test.ly.TXT}. Double clicking @file{test.ly} will process +the file and show the resulting PDF file. + + +@unnumberedsubsec Unix Begin by opening a terminal window and starting a text editor. For example, you could open an xterm and execute @code{joe}.@footnote{There are macro files for VIM addicts, and there is a @code{LilyPond-mode} for Emacs addicts. If they have not been -installed already, refer to -the file @file{INSTALL.txt}.} In your text editor, enter the following -input and save the file as @file{test.ly} +installed already, refer to the file @file{INSTALL.txt}.} In your +text editor, enter the following input and save the file as +@file{test.ly} @example @{ c'4 e' g' @} @@ -263,20 +289,6 @@ installed, you can try @uref{http://@/www@/.cs@/.wisc@/.edu/@/~ghost/,Ghostscript}, a freely available package for viewing and printing PDF and PostScript files.} -On Windows, start up a text-editor@footnote{Any simple or -programmer-oriented editor will do, for example Notepad. Do not use a -word processor, since these insert formatting codes that will confuse -LilyPond.} and enter - -@example -@{ c'4 e' g' @} -@end example - -Save it on the desktop as @file{test.ly} and make sure that it is not -called @file{test.ly.TXT}. Double clicking @file{test.ly} will process -the file and show the resulting PDF file. - - @node More about pitches @section More about pitches diff --git a/scm/output-svg.scm b/scm/output-svg.scm index be1bb04db6..786efb8602 100644 --- a/scm/output-svg.scm +++ b/scm/output-svg.scm @@ -59,6 +59,12 @@ "c = close" (format #f "\n" entity)) + +(define-public (setcolor r g b)) + +(define-public (resetcolor)) + + (define-public (entity entity string . attributes-alist) (if (equal? string "") (apply eoc entity attributes-alist) -- 2.39.5