commit c609939ca7392aed5b8140d8c6e175aa292e1515
Author: Christopher Antila <crantila(a)fedoraproject.org>
Date: Mon Sep 5 16:40:54 2011 -0400
some LilyPond updates
en-US/LilyPond/LilyPond-syntax.xml | 10 ++++++++--
en-US/LilyPond/LilyPond.xml | 22 +++++++++++-----------
2 files changed, 19 insertions(+), 13 deletions(-)
---
diff --git a/en-US/LilyPond/LilyPond-syntax.xml b/en-US/LilyPond/LilyPond-syntax.xml
index f68ed6c..5601257 100644
--- a/en-US/LilyPond/LilyPond-syntax.xml
+++ b/en-US/LilyPond/LilyPond-syntax.xml
@@ -13,10 +13,16 @@
<section id="sect-Musicians_Guide-LilyPond-Syntax-Letters_Are_Pitches">
<title>Letters Are Pitches</title>
<para>
- One letter is all that's required to create a note in
<application>LilyPond</application>. There are additional symbols and letters
that are added to indicate further details, like the register, and whether the note is
"sharp" or "flat."
+ One letter signifies a note in a <application>LilyPond</application>
source file. Use other letters, numbers, and symbols to change the duration, articulation,
and other properties.
</para>
<para>
- Although it can be changed, the default (and recommended) way to indicate
"sharp" or "flat" is by using Dutch note-names: "-is" to
indicate a sharp, and "-es" to indicate a flat. For example, the following
command would create b-double-flat, b-flat, b, b-sharp, and b-double-sharp:
<code>beses bes b bis bisis</code> Getting used to these names happens
quickly, and they take less time to input than the English alternative. Furthermore, with
these names, it becomes possible to sing note-names when you are ear training!
+ We recommend the default way to indicate a "sharp" or "flat" note:
add "is" to sharp a note, or add "es" to flat a note. This command
means "b-flat, b, b-sharp": <code>bes b bis</code>.
+ </para>
+ <para>
+ Show a double-sharp or double-flat with "isis" or "eses." This
command means "b-double-flat, b, b-double-sharp": <code>beses b
bisis</code>.
+ </para>
+ <para>
+ "Is" and "es" are the Dutch names for "sharp" and
"flat." <application>LilyPond</application> can read English names:
<code>bflat b bsharp</code>. We recommend you use Dutch names because they are
faster.
</para>
<para>
Pitch can be entered either absolutely, or relative to the preceding notes. Usually
(for music without frequent large leaps) it is more convenient to use the
"relative" mode. The symbols <literal>,</literal> and
<literal>'</literal> (comma and apostrophe) are used to indicate
register.
diff --git a/en-US/LilyPond/LilyPond.xml b/en-US/LilyPond/LilyPond.xml
index 6236791..9d886e2 100644
--- a/en-US/LilyPond/LilyPond.xml
+++ b/en-US/LilyPond/LilyPond.xml
@@ -6,23 +6,23 @@
<chapter id="chap-Musicians_Guide-LilyPond">
<title><application>LilyPond</application></title>
- <para>
- <application>LilyPond</application> is a notation engraving program, with a
focus on creating a visually appealing product.
<application>LilyPond</application> is text-based, and allows you to focus on
the (semantic?) content of your musical scores, rather than on their visual appearance.
Conventional commercial notation engraving programs allow users to edit the score
visually. While this approach has its benefits, especially because it's very easy to
see exactly what the printed score will look like, it also has disadvantages - chief among
these is the fact that users of those programs are constantly worrying about what their
score looks like.
+ <para> <!-- proof-read -->
+ <application>LilyPond</application> is a musical notation program that
creates a visually appealing musical score.
<application>LilyPond</application> text files contain the semantic meaning of
a musical score, rather than details about a musical score's visual appearance.
Popular proprietary musical notation applications represent the visual apperance of a
score. People who use visual notation applications constantly worry about how their score
looks. <application>LilyPond</application> users only worry about what the
score means, because <application>LilyPond</application> automatically creates
an expert result.
</para>
- <para>
+ <para> <!-- not proof-read -->
This is where <application>LilyPond</application> comes in - users
don't need to worry about how their score will work, because they know that the
expertly-crafted methods of <application>LilyPond</application> will
automatically configure the objects on the score so that they look good, and are easy to
read. <application>LilyPond</application>'s users focus on
<emphasis>what</emphasis> needs to be displayed, rather than on
<emphasis>how</emphasis> it is going to be displayed.
</para>
<para>
As with any particular approach, the <application>LilyPond</application>
approach is not for everybody. However, once you have become accustomed to working with
the software, and once you have learned methods to help deal with problems and organize
your scores' source-files, you will probably realize that
<application>LilyPond</application> is both much faster, and much more
flexible, than traditional, commercially-available music engraving programs.
</para>
<para>
- <application>LilyPond</application> offers many other features, too. Some
of these features include:
+ With <application>LilyPond</application>, you can:
<itemizedlist>
- <listitem><para>Putting scores into LaTeX or HTML
documents.</para></listitem>
- <listitem><para>Putting scores into
<application>OpenOffice.org</application> documents, with the
<application>ooolilypond</application> program.</para></listitem>
- <listitem><para>Being compatible with all major operating
systems.</para></listitem>
- <listitem><para>Managing parts and full scores for large
compositions.</para></listitem>
- <listitem><para>Allowing new musical symbols with the Scheme programming
language.</para></listitem>
+ <listitem><para>Put a score into LaTeX or HTML
documents.</para></listitem>
+ <listitem><para>Put a score into an
<application>LibreOffice</application> document, with the
<application>ooolilypond</application> program.</para></listitem>
+ <listitem><para>Use any major operating
system.</para></listitem>
+ <listitem><para>Manage parts and full scores for large
compositions.</para></listitem>
+ <listitem><para>Create new musical symbols with the Scheme programming
language.</para></listitem>
</itemizedlist>
</para>
<para>
@@ -45,10 +45,10 @@
For an extensive explanation of the following section, please see the
<citetitle><application>LilyPond</application> Website</citetitle>
at <ulink
url="http://www.lilypond.org/about/automated-engraving/" />,
from where this was sourced.
</para>
<para>
- <application>LilyPond</application> works by separating the tasks of what
to put, and where to put it. Each aspect of an object's position is controlled by a
specific plug-in. You can think of the plug-ins as tools.
<application>LilyPond</application> knows how and when to use each tool; if it
doesn't know enough about a tool, then it isn't used.
+ <application>LilyPond</application> breaks score set-up into two parts:
know what to put, and know where to put it.
<application>LilyPond</application> users decide
<emphasis>what</emphasis> notation objects to place, but
<application>LilyPond</application> itself decides
<emphasis>where</emphasis> to place it.
<application>LilyPond</application> uses a plug-in to know where to place each
notation object. A <application>LilyPond</application> plug-in is like a
specialized tool that works for specific notation objects.
</para>
<para>
- Before <application>LilyPond</application> places an object, it first
considers many different possibilities for the specific alignment and layout of that
object. Then it evaluates the possibilities according to aesthetic criteria set out to
reflect those used in hand-engraved notation. After assigning each possibility a score
representing how closely it resembles to the aesthetic ideal,
<application>LilyPond</application> then chooses the better possibility.
+ <application>LilyPond</application> uses plug-ins to get a list of
possible places for all notation objects. Then
<application>LilyPond</application> uses another plug-in to find the best
placement of all notation objects; this plug-in assigns a score to each possible
placement, based on how closely the placement resembles an esthetic ideal. The placement
with the highest score becomes an outputted musical score.
</para>
</section>