From 91b57c4218a3e9d33b1d4bf2ab966290ae545be5 Mon Sep 17 00:00:00 2001 From: Reinhold Kainhofer Date: Sun, 30 Mar 2008 01:33:47 +0100 Subject: [PATCH] (l|L)ilypond -> LilyPond, (U|u)nix -> UNIX, MacOs X -> MacOS X --- Documentation/user/changing-defaults.itely | 2 +- Documentation/user/converters.itely | 2 +- Documentation/user/fundamental.itely | 2 +- Documentation/user/input.itely | 10 +++++----- Documentation/user/install.itely | 12 ++++++------ Documentation/user/introduction.itely | 6 +++--- Documentation/user/lilypond-book.itely | 6 +++--- Documentation/user/non-music.itely | 2 +- Documentation/user/programming-interface.itely | 2 +- Documentation/user/running.itely | 10 +++++----- Documentation/user/setup.itely | 10 +++++----- Documentation/user/staff.itely | 2 +- Documentation/user/templates.itely | 6 +++--- Documentation/user/text.itely | 6 +++--- Documentation/user/tutorial.itely | 2 +- Documentation/user/tweaks.itely | 2 +- Documentation/user/vocal.itely | 6 +++--- Documentation/user/working.itely | 14 +++++++------- 18 files changed, 51 insertions(+), 51 deletions(-) diff --git a/Documentation/user/changing-defaults.itely b/Documentation/user/changing-defaults.itely index 746bcdf..7ca47af 100644 --- a/Documentation/user/changing-defaults.itely +++ b/Documentation/user/changing-defaults.itely @@ -968,7 +968,7 @@ properties. To tweak those, use commands in the form For many properties, regardless of the data type of the property, setting the property to false ( @code{##f} ) will result in turning it off, causing -Lilypond to ignore that property entirely. This is particularly useful for +LilyPond to ignore that property entirely. This is particularly useful for turning off grob properties which may otherwise be causing problems. We demonstrate how to glean this information from the notation manual diff --git a/Documentation/user/converters.itely b/Documentation/user/converters.itely index 95cbb92..81965c7 100644 --- a/Documentation/user/converters.itely +++ b/Documentation/user/converters.itely @@ -16,7 +16,7 @@ There are other tools that produce LilyPond input, for example GUI sequencers and XML converters. Refer to the @uref{http://@/lilypond@/.org,website} for more details. -These are separate programs from lilypond itself, and are run +These are separate programs from LilyPond itself, and are run on the command-line; see @ref{Command-line usage} for more information. diff --git a/Documentation/user/fundamental.itely b/Documentation/user/fundamental.itely index c2b0534..3428b65 100644 --- a/Documentation/user/fundamental.itely +++ b/Documentation/user/fundamental.itely @@ -37,7 +37,7 @@ description of the input format, see @ruser{File structure}. @node Introduction to the LilyPond file structure @subsection Introduction to the LilyPond file structure -A basic example of a lilypond input file is +A basic example of a LilyPond input file is @example \version @w{"@version{}"} diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely index 5cb75d3..6ad8ece 100644 --- a/Documentation/user/input.itely +++ b/Documentation/user/input.itely @@ -10,7 +10,7 @@ @node Input syntax @chapter Input syntax -This section deals with general lilypond input syntax issues, +This section deals with general LilyPond input syntax issues, rather than specific notation. FIXME: don't complain about anything in this chapter. It's still @@ -331,7 +331,7 @@ In order to use this feature, LilyPond must be invoked with @code{-dclip-systems}. The clips are output as EPS files, and are converted to PDF and PNG if these formats are switched on as well. -For more information on output formats, see @rprogram{Invoking lilypond}. +For more information on output formats, see @rprogram{Invoking LilyPond}. @seealso @@ -359,7 +359,7 @@ together the individual instrument files. The initialization of LilyPond is done in a number of files that are included by default when you start the program, normally transparent to the -user. Run lilypond --verbose to see a list of paths and files that Lily +user. Run @code{lilypond --verbose} to see a list of paths and files that Lily finds. Files placed in directory @file{PATH/TO/share/lilypond/VERSION/ly/} (where @@ -371,7 +371,7 @@ available to \include from directories in the search path specified as an option when invoking @code{lilypond --include=DIR} which adds DIR to the search path. -The @code{\include} statement can use full path information, but with the Unix +The @code{\include} statement can use full path information, but with the UNIX convention @code{/} rather than the DOS/Windows @code{\}. For example, if @file{stuff.ly} is located one directory higher than the current working directory, use @@ -527,7 +527,7 @@ sections. TODO: everything -By default, lilypond does a pretty jazz'n job of picking +By default, LilyPond does a pretty jazz'n job of picking directions. But in some cases, it may be desirable to force a direction. diff --git a/Documentation/user/install.itely b/Documentation/user/install.itely index faad734..151d08b 100644 --- a/Documentation/user/install.itely +++ b/Documentation/user/install.itely @@ -110,7 +110,7 @@ For information on packaging, see @uref{http://lilypond.org/devel}. @unnumberedsubsubsec Compilation -In addition to the packages needed for running Lilypond (see below), you +In addition to the packages needed for running LilyPond (see below), you need the following extra packages for building. When installing a binary package FOO, you may need to install the @@ -177,7 +177,7 @@ or lyrics. You can view the documentation online at @uref{http://lilypond.org/doc/}, but you can also build it locally. -This process requires a successful compile of lilypond, and some +This process requires a successful compile of LilyPond, and some additional tools and packages @itemize @@ -274,7 +274,7 @@ make conf=prof install @node Building documentation without compiling LilyPond @subsection Building documentation without compiling LilyPond -The documentation can be built locally without compiling lilypond from +The documentation can be built locally without compiling LilyPond from scratch. From a fresh git checkout, do @@ -304,7 +304,7 @@ export LD_LIBRARY_PATH=/usr/lib exec /usr/bin/pngtopnm "$@" @end verbatim -On OSX, I use this: +On address@hidden, I use this: @verbatim export DYLD_LIBRARY_PATH=/sw/lib @@ -317,7 +317,7 @@ writing a script like this: @verbatim ### run from Documentation/user/ -# possibly required on OSX and/or old texinfo +# possibly required on OS X and/or old texinfo # ulimit -n 4096 if [ -e out-www/lilypond.texi ]; then rm out-www/lilypond.* ; fi; if [ -e out-www/lilypond-program.texi ]; then rm @@ -437,7 +437,7 @@ for your hierarchy.) @unnumberedsubsubsec International fonts -On MacOs X, all fonts are installed by default. However, finding all +On address@hidden, all fonts are installed by default. However, finding all system fonts requires a bit of configuration; see @uref{http://lists.gnu.org/archive/html/lilypond-user/2007-03/msg00472.html, this post} on the @code{lilypond-user} mailing list. diff --git a/Documentation/user/introduction.itely b/Documentation/user/introduction.itely index c676108..dbb02ff 100644 --- a/Documentation/user/introduction.itely +++ b/Documentation/user/introduction.itely @@ -721,7 +721,7 @@ users should start here. @item @address@hidden concepts}}, -explains some general concepts about the lilypond file format. If +explains some general concepts about the LilyPond file format. If you are not certain where to place a command, read this chapter! @item @@ -961,7 +961,7 @@ initialization and example files. Throughout this manual, we refer to input files relative to the top-directory of the source archive. For example, @file{input/@/lsr/@/dirname/@/bla@/.ly} may refer to the file @file{lilypond@/2.x.y/@/input/@/lsr/@/dirname/@/bla@/.ly}. On binary -packages for the Unix platform, the documentation and examples can +packages for the UNIX platform, the documentation and examples can typically be found somewhere below @file{/usr/@/share/@/doc/@/lilypond/}. Initialization files, for example @file{scm/@/lily@/.scm}, or @file{ly/@/engraver@/-init@/.ly}, @@ -973,7 +973,7 @@ are usually found in the directory @file{/usr/@/share/@/lilypond/}. @cindex lilypond-internals @cindex internal documentation @cindex Scheme address@hidden extending lilypond address@hidden extending LilyPond @cindex index Finally, this and all other manuals, are available online both as PDF diff --git a/Documentation/user/lilypond-book.itely b/Documentation/user/lilypond-book.itely index 1c46d4a..86f3b2f 100644 --- a/Documentation/user/lilypond-book.itely +++ b/Documentation/user/lilypond-book.itely @@ -295,7 +295,7 @@ kpsewhich feta20.tex Sometimes it is useful to display music elements (such as ties and slurs) as if they continued after the end of the fragment. This can be done by -breaking the staff and suppressing inclusion of the rest of the lilypond +breaking the staff and suppressing inclusion of the rest of the LilyPond output. In @LaTeX{}, define @code{\betweenLilyPondSystem} in such a way that @@ -952,10 +952,10 @@ LilyPond notation can be added to OpenOffice.org with To insert LilyPond output in other programs, use @code{lilypond} instead of @code{lilypond-book}. Each example must be created individually and added to the document; consult the documentation for -that program. Most programs will be able to insert lilypond output in +that program. Most programs will be able to insert LilyPond output in @file{PNG}, @file{EPS}, or @file{PDF} formats. -To reduce the white space around your lilypond score, use +To reduce the white space around your LilyPond score, use the following options @example diff --git a/Documentation/user/non-music.itely b/Documentation/user/non-music.itely index b7a6c3e..db12f12 100644 --- a/Documentation/user/non-music.itely +++ b/Documentation/user/non-music.itely @@ -14,7 +14,7 @@ @node Non-musical notation @chapter Non-musical notation -This section deals with general lilypond issues, rather than +This section deals with general LilyPond issues, rather than specific notation. @menu diff --git a/Documentation/user/programming-interface.itely b/Documentation/user/programming-interface.itely index 4212093..7b82866 100644 --- a/Documentation/user/programming-interface.itely +++ b/Documentation/user/programming-interface.itely @@ -269,7 +269,7 @@ displayBarNum = @end example To actually display bar numbers where this function is called, -invoke lilypond with +invoke LilyPond with @example lilypond -d display-bar-numbers FILENAME.ly diff --git a/Documentation/user/running.itely b/Documentation/user/running.itely index 9c36469..d492f32 100644 --- a/Documentation/user/running.itely +++ b/Documentation/user/running.itely @@ -39,8 +39,8 @@ as @code{midi2ly}) which are only available on the command-line. By @q{command-line}, we mean the command line in the operating system. Windows users might be more familiar with the terms @q{DOS shell} or address@hidden shell}; OSX users might be more familiar with the terms address@hidden or @q{console}. OSX users should also consult @ref{MacOS X address@hidden shell}; address@hidden users might be more familiar with the terms address@hidden or @q{console}. They should also consult @ref{MacOS X on the command-line}. Describing how to use this part of an operating system is outside the @@ -232,7 +232,7 @@ This mode is used by default by lilypond-book. @cindex SVG (Scalable Vector Graphics) You need a SVG viewer which supports embedded fonts, or a SVG viewer which is able to replace the embedded fonts with OTF fonts. - Under Unix, you may use @uref{http://www.inkscape.org,Inkscape} + Under UNIX, you may use @uref{http://www.inkscape.org,Inkscape} (version 0.42 or later), after copying the OTF fonts in directory @file{PATH/TO/share/lilypond/VERSION/fonts/otf/} to @file{~/.fonts/}. @item scm @@ -485,7 +485,7 @@ convert-ly -e myfile.ly @end example @noindent -MacOS X users may execute this command under the menu entry address@hidden users may execute this command under the menu entry @code{Compile > Update syntax}. If there are no changes to myfile.ly and file called myfile.ly.NEW @@ -510,7 +510,7 @@ convert-ly --from=... --to=... -s @end example To upgrade many files at once, combine @code{convert-ly} with -standard unix commands. This example will upgrade all @code{.ly} +standard UNIX commands. This example will upgrade all @code{.ly} files in the current directory @example diff --git a/Documentation/user/setup.itely b/Documentation/user/setup.itely index 63599d4..1294cdd 100644 --- a/Documentation/user/setup.itely +++ b/Documentation/user/setup.itely @@ -36,7 +36,7 @@ operating systems. @subsection MacOS X on the command-line The scripts (such as lilypond-book, convert-ly, abc2ly, and even -lilypond itself) are included inside MacOS X .app. They can be run from +lilypond itself) are included inside the .app file for address@hidden They can be run from the command line by invoking them directly, e.g. @example @@ -158,7 +158,7 @@ set runtimepath+=/usr/local/share/lilypond/address@hidden@}/vim/ @end example @noindent -where address@hidden@} is your lilypond version. If Lilypond was not +where address@hidden@} is your LilyPond version. If LilyPond was not installed in @file{/usr/local/}, then change this path accordingly. @@ -178,7 +178,7 @@ installation instructions, visit @subsection TexShop The @uref{http://@/www@/.uoregon@/.edu/~koch/texshop/index@/.html,TexShop} -editor for Mac OS X can be extended to run LilyPond, lilypond-book and +editor for address@hidden can be extended to run LilyPond, lilypond-book and convert-ly from within the editor, using the extensions available at @uref{http://@/www@/.dimi@/.uniud@/.it/vitacolo/freesoftware@/.html}. @@ -213,8 +213,8 @@ To make this chain work, you should configure your PDF viewer to follow hyperlinks using the @file{lilypond-invoke-editor} script supplied with LilyPond. -For Xpdf on Unix, the following should be present in address@hidden@footnote{On unix, this file is found either in +For Xpdf on UNIX, the following should be present in address@hidden@footnote{On UNIX, this file is found either in @file{/etc/xpdfrc} or as @file{.xpdfrc} in your home directory.} @example diff --git a/Documentation/user/staff.itely b/Documentation/user/staff.itely index e9b770b..08cf25b 100644 --- a/Documentation/user/staff.itely +++ b/Documentation/user/staff.itely @@ -56,7 +56,7 @@ layout object. Staves are created with the @code{\new} or @code{\context} commands. For an explanation on these commands, see @ref{Creating contexts}. -There are different predefined staff contexts available in Lilypond: +There are different predefined staff contexts available in LilyPond: @itemize @item diff --git a/Documentation/user/templates.itely b/Documentation/user/templates.itely index d829be7..19cb4bf 100644 --- a/Documentation/user/templates.itely +++ b/Documentation/user/templates.itely @@ -279,7 +279,7 @@ d4 c b a \usepackage{graphicx} \begin{document} -\title{A short document with lilypond and xelatex} +\title{A short document with LilyPond and xelatex} \maketitle Normal \textbf{font} commands inside the \emph{text} work, @@ -289,7 +289,7 @@ should include them again in a \verb+\ifxetex+ environment. You can use this to print the \ifxetex \XeTeX{} command \else XeTeX command \fi which is not known to normal \LaTeX . -In normal text you can easily use lilypond commands, like this: +In normal text you can easily use LilyPond commands, like this: \begin{lilypond} {a2 b c'8 c' c' c'} @@ -298,7 +298,7 @@ In normal text you can easily use lilypond commands, like this: \noindent and so on. -The fonts of snippets set with lilypond will have to be set from +The fonts of snippets set with LilyPond will have to be set from inside of the snippet. For this you should read the AU on how to use lilypond-book. diff --git a/Documentation/user/text.itely b/Documentation/user/text.itely index 7458a3d..7fc8ed3 100644 --- a/Documentation/user/text.itely +++ b/Documentation/user/text.itely @@ -17,7 +17,7 @@ formatting) in your scores. @cindex Text, other languages @warning{To write accented and special text (such as characters from other languages), simply insert the characters directly into -the lilypond file. The file must be saved as UTF-8. For more +the LilyPond file. The file must be saved as UTF-8. For more information, see @ref{Text encoding}.} @menu @@ -142,7 +142,7 @@ Internals Reference: @internalsref{TextScript}. Checking to make sure that text scripts and lyrics are within the margins is a relatively large computational task. To speed up -processing, lilypond does not perform such calculations by +processing, LilyPond does not perform such calculations by default; to enable it, use @example @@ -399,7 +399,7 @@ See @ref{Overview of text markup commands}, for a list of all commands. @code{\markup} is primarily used for @internalsref{TextScript}s, -but it can also be used anywhere text is called in lilypond +but it can also be used anywhere text is called in LilyPond @lilypond[quote,verbatim] \header{ title = \markup{ \bold { foo \italic { bar! } } } } diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 7e01094..c1f48c0 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -153,7 +153,7 @@ also produces a @file{.log} file that contains some information on what LilyPond has done to the file. If any errors occur, please examine this file. address@hidden Unix address@hidden UNIX Create a text file called @file{test.ly} and enter: diff --git a/Documentation/user/tweaks.itely b/Documentation/user/tweaks.itely index 319e62a..3aabd99 100644 --- a/Documentation/user/tweaks.itely +++ b/Documentation/user/tweaks.itely @@ -3178,7 +3178,7 @@ find the directory appropriate to your system, as follows: Navigate to @address@hidden/lilypond/usr/share/lilypond/current/} address@hidden address@hidden X} Navigate to @address@hidden/LilyPond.app/Contents/Resources/share/lilypond/current/} diff --git a/Documentation/user/vocal.itely b/Documentation/user/vocal.itely index 9ee8c87..6b88aeb 100644 --- a/Documentation/user/vocal.itely +++ b/Documentation/user/vocal.itely @@ -37,7 +37,7 @@ by examining the simplest method, and gradually increase complexity. @snippets Checking to make sure that text scripts and lyrics are within the margins is -a relatively large computational task. To speed up processing, lilypond does +a relatively large computational task. To speed up processing, LilyPond does not perform such calculations by default; to enable it, use @example @@ -906,7 +906,7 @@ These numbers are put just before the start of the first syllable. @subsubsection Adding dynamics marks Stanzas differing in loudness may be indicated by putting a -dynamics mark before each stanza. In Lilypond, everything coming in +dynamics mark before each stanza. In LilyPond, everything coming in front of a stanza goes into the @code{StanzaNumber} object; dynamics marks are no different. For technical reasons, you have to set the stanza outside @code{\lyricmode}: @@ -1002,7 +1002,7 @@ its fleece was white as snow. When a piece of music has many verses, they are often printed in multiple columns across the page. An outdented verse number often introduces each verse. The following example shows how to produce such -output in Lilypond. +output in LilyPond. @lilypond[ragged-right,quote,verbatim] melody = \relative c' { diff --git a/Documentation/user/working.itely b/Documentation/user/working.itely index ab7f328..eead6ec 100644 --- a/Documentation/user/working.itely +++ b/Documentation/user/working.itely @@ -32,23 +32,23 @@ go about doing it? As long as LilyPond can understand your files and produces the output that you want, it doesn't matter what your files look like. However, -there are a few other things to consider when writing lilypond files. +there are a few other things to consider when writing LilyPond files. @itemize address@hidden What if you make a mistake? The structure of a lilypond address@hidden What if you make a mistake? The structure of a LilyPond file can make certain errors easier (or harder) to find. @item What if you want to share your files with somebody else? In fact, what if you want to alter your own files in -a few years? Some lilypond files are understandable at +a few years? Some LilyPond files are understandable at first glance; other files may leave you scratching your head for an hour. address@hidden What if you want to upgrade your lilypond file for use -with a later version of lilypond? The input syntax changes -occasionally as lilypond improves. Most changes can be address@hidden What if you want to upgrade your LilyPond file for use +with a later version of LilyPond? The input syntax changes +occasionally as LilyPond improves. Most changes can be done automatically with @code{convert-ly}, but some changes -might require manual assistance. Lilypond files can be +might require manual assistance. LilyPond files can be structured in order to be easier (or harder) to update. @end itemize -- 1.5.3.6