commit 518620beff44c7dbd6598ca2b39288620df62693 Author: Christopher Antila crantila@fedoraproject.org Date: Sat Jun 1 20:54:22 2013 -0400
Significant Revision to LilyPond/LilyPond.xml
In an attempt to increase the professionalism.
en-US/LilyPond/LilyPond.xml | 38 +++++++++----------------------------- en-US/Revision_History.xml | 15 +++++++++++++++ 2 files changed, 24 insertions(+), 29 deletions(-) --- diff --git a/en-US/LilyPond/LilyPond.xml b/en-US/LilyPond/LilyPond.xml index bc587fb..f201336 100644 --- a/en-US/LilyPond/LilyPond.xml +++ b/en-US/LilyPond/LilyPond.xml @@ -5,50 +5,30 @@ ]>
<chapter id="chap-Musicians_Guide-LilyPond"> - <title><application>LilyPond</application></title> - <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> <!-- 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> + <title>LilyPond</title> <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. + <quote>LilyPond is a music engraving program, devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts.</quote><citation><citetitle>LilyPond—Music notation for everyone</citetitle> <ulink url="http://www.lilypond.org" /></citation> </para> <para> - With <application>LilyPond</application>, you can: - <itemizedlist> - <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> + Other proprietary and free engraving (or “notation”) programs, like <application>MuseScore</application> and <application>Denemo</application>, focus on the visual aspects of musical scores, <application>LilyPond</application> focusses on the semantic aspects. Because <application>LilyPond</application> is a text-based music engraving program, the separation between meaning and appearance is similar to HTML and CSS. Web developers use HTML to tell web browsers what an object means (a <title> tag tells a browser that some text is a title, for example), and CSS to tell web browsers how objects with different meaning should look (that all titles are blue, for example). The LilyPond language does not look like HTML and CSS, but you may have a similar experience. <application>LilyPond</application> users use letters and numbers to tell <application>LilyPond</application> what a note means (a “g4” is the pitch G with a quarter-note duration, for exa mple), and can change the visual appearance if they wish (by using a square notehead, for example). </para> <para> - It is the goal of this guide to help users more quickly overcome the initial learning handicap incurred because of the text-based approach. Making use of tools such as the <application>Frescobaldi</application> text-editor will help to increase productivity, to make trouble-shooting easier, and to ease the memory burden associated with the text-based approach. + Advanced <application>LilyPond</application> users can, for example, incorporate scores into LaTeX and HTML documents; create new musical symbols and notation styles using the Scheme programming language; and tweak output quickly and flexibly with SVG-format output. </para>
<section id="sect-Musicians_Guide-LilyPond-How_LilyPond_Works"> - <title>How <application>LilyPond</application> Works</title> - <para> - Think of <application>LilyPond</application> as an automobile mechanic. When your car breaks down, the mechanic knows which tools to use. You can buy tools to fix your car by yourself, but the mechanic is specialized. The mechanic knows what tools to use, how to prepare the tools, and how to fix your car faster than you can fix it. <application>LilyPond</application> uses many programs that you can use by yourself, but <application>LilyPond</application> is specialized. <application>LilyPond</application> knows what programs to use, what settings to use, and most importantly, <application>LilyPond</application> takes much less time than if you use the programs directly. - </para> + <title>How LilyPond Works</title> <para> - We give instructions to <application>LilyPond</application> in specially-formed text files. <application>LilyPond</application> input files describe the music to notate. <application>LilyPond</application> decides how the music will look, then creates an output file. The input file does not contain instructions about how the music looks. Sometimes you must make an adjustment to how the output file looks, so <application>LilyPond</application> lets you change the settings of its internal tools. + When you use <application>LilyPond</application>, think of musical objects in two ways: what it is or means, and how it looks. You should focus on which objects to use and what they mean, then adjust how they look as you need. The <application>LilyPond</application> developers spend a lot of effort to ensure most musical scores are visually appealling with little adjustment. </para> - </section> - - <section id="sect-Musicians_Guide-LilyPond-The_LilyPond_Approach"> - <title>The <application>LilyPond</application> Approach</title> <para> - 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. + After you prepare a specially-formatted text file for <application>LilyPond</application>, the program uses many different components to decide how the score will look. For every type of musical object, <application>LilyPond</application> has a specific rendering component. When a component creates a musical object in a score, the component considers several alternative appearances, then chooses only one. </para> <para> - <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. + Once <application>LilyPond</application> decides how a score will look, the program uses a “back end” component to output the score into a PDF, SVG, or PNG file so you can use the score. </para> <para> - <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. + For more information on how <application>LilyPond</application> works, refer to <citetitle>Essay</citetitle> at <ulink url="http://lilypond.org/essay.html" />. </para> </section>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml index e867133..1eb6a7a 100644 --- a/en-US/Revision_History.xml +++ b/en-US/Revision_History.xml @@ -439,6 +439,21 @@ </revdescription> </revision>
+ <revision> + <revnumber>18.9</revnumber> + <date>?? June 2012</date> + <author> + <firstname>Christopher</firstname> + <surname>Antila</surname> + <email>crantila@fedoraproject.org</email> + </author> + <revdescription> + <simplelist> + <member>Significant revision to LilyPond introductory materials, in an attempt to be more professional.</member> + </simplelist> + </revdescription> + </revision> + <!-- NOTE: When adding a revision above, be sure to update the <edition> tag in "Book_Info.xml" -->
<!-- Fedora 19 (early 2013) -->