[musicians-guide] Fixed Bug 665663 and first part of Bug 654187
crantila
crantila at fedoraproject.org
Mon Dec 27 07:59:23 UTC 2010
commit b14a38c761677566a4f0815ff800c48af1a73f27
Author: Christopher Antila <crantila at fedoraproject.org>
Date: Mon Dec 27 02:58:27 2010 -0500
Fixed Bug 665663 and first part of Bug 654187
en-US/Audacity.xml | 6 ++--
en-US/LilyPond/LilyPond-counterpoint.xml | 14 +++++-----
en-US/LilyPond/LilyPond-orchestra.xml | 20 +++++++-------
en-US/LilyPond/LilyPond-piano.xml | 24 +++++++++---------
en-US/LilyPond/LilyPond-syntax.xml | 30 ++++++++++++----------
en-US/Revision_History.xml | 24 ++++++++++++++++--
en-US/SuperCollider/SuperCollider-Composing.xml | 6 ++--
7 files changed, 72 insertions(+), 52 deletions(-)
---
diff --git a/en-US/Audacity.xml b/en-US/Audacity.xml
index db85ec3..d3d31e2 100644
--- a/en-US/Audacity.xml
+++ b/en-US/Audacity.xml
@@ -281,9 +281,9 @@
<para>
Use the <citetitle>Tutorial Start</citetitle> file if you want to do the tutorial. The <citetitle>Tutorial End</citetitle> file and <citetitle>Exported FLAC</citetitle> file are completed examples. When you finish the tutorial, your project will probably not be the same as ours.
<itemizedlist>
- <listitem><para><citetitle>Tutorial Start</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/Audacity/Audacity-start.tar.lzma" /></para></listitem>
- <listitem><para><citetitle>Tutorial End</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/Audacity/Audacity-start.tar.lzma" /></para></listitem>
- <listitem><para><citetitle>Exported FLAC</citetitle>is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/Audacity/Audacity-export.flac" /></para></listitem>
+ <listitem><para><citetitle>Tutorial Start</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/Audacity/Audacity-start.tar.lzma" /></para></listitem>
+ <listitem><para><citetitle>Tutorial End</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/Audacity/Audacity-start.tar.lzma" /></para></listitem>
+ <listitem><para><citetitle>Exported FLAC</citetitle>is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/Audacity/Audacity-export.flac" /></para></listitem>
</itemizedlist>
</para>
</section>
diff --git a/en-US/LilyPond/LilyPond-counterpoint.xml b/en-US/LilyPond/LilyPond-counterpoint.xml
index 0eac8c6..3615f97 100644
--- a/en-US/LilyPond/LilyPond-counterpoint.xml
+++ b/en-US/LilyPond/LilyPond-counterpoint.xml
@@ -5,7 +5,7 @@
]>
<section id="sect-Musicians_Guide-LilyPond-Counterpoint">
- <title>Working on a Counterpoint Exercise (Tutorial)</title>
+ <title>Work on a Counterpoint Exercise (Tutorial)</title>
<para>
Imagine you're in Counterpoint class, and you've been asked to submit a very clean copy of your next assignment. Since you don't want to pay $450,000 for a commercially-available engraving solution and a fruity computer to use it, you decide that LilyPond is the solution for you. <!-- Drop the sarcasm (TODO) -->
</para>
@@ -15,14 +15,14 @@
<para>
You do not need these files to do the tutorial. They are example completions.
<itemizedlist>
- <listitem><para><citetitle>LilyPond Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/LilyPond/Counterpoint-source.ly" /></para></listitem>
- <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/files/LilyPond/Counterpoint-result.pdf" /></para></listitem>
+ <listitem><para><citetitle>LilyPond Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/LilyPond/Counterpoint-source.ly" /></para></listitem>
+ <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/files/LilyPond/Counterpoint-result.pdf" /></para></listitem>
</itemizedlist>
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Counterpoint-Starting_the_Score">
- <title>Starting the Score</title>
+ <title>Start the Score</title>
<procedure>
<step><para>Open Frescobaldi into a blank document</para></step>
<step><para>Use the 'LilyPond > Setup New Score' dialogue</para></step>
@@ -42,14 +42,14 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Counterpoint-Adjusting_Frescobaldis_Output">
- <title>Adjusting Frescobaldi's Output</title>
+ <title>Adjust Frescobaldi's Output</title>
<para>
For this tutorial, Frescobaldi's default output is good enough.
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Counterpoint-Inputting">
- <title>Inputting</title>
+ <title>Input Notes</title>
<procedure>
<step><para>Look over the template. It's not important to understand what any of this means, but it's good if you can figure it out.</para></step>
<step><para>The piano's upper staff will contain the notes between the <literal>{</literal> and <literal>}</literal> following the <code>right = \relative c''</code> portion</para></step>
@@ -73,7 +73,7 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Counterpoint-Formatting_the_Score">
- <title>Formatting the Score</title>
+ <title>Format the Score</title>
<para>
We recommend formatting the score after the notes have been inputting. Formatting after inputting helps you avoid making formatting errors. LilyPond works effectively with this approach.
</para>
diff --git a/en-US/LilyPond/LilyPond-orchestra.xml b/en-US/LilyPond/LilyPond-orchestra.xml
index 0313824..6c87392 100644
--- a/en-US/LilyPond/LilyPond-orchestra.xml
+++ b/en-US/LilyPond/LilyPond-orchestra.xml
@@ -5,7 +5,7 @@
]>
<section id="sect-Musicians_Guide-LilyPond-Orchestra">
- <title>Working on an Orchestral Score (Tutorial)</title>
+ <title>Work on an Orchestral Score (Tutorial)</title>
<para>
Scenario: You volunteer at a community orchestra, and the conductor decides to play a Haydn symphony. The orchestra does not own any Haydn symphonies, so the conductor asks you if you can help to find a full score and parts. You find a book with the conductor's score, but no parts. You decide to input the score in LilyPond, which will allow you to easily create the missing parts.
</para>
@@ -21,14 +21,14 @@
<para>
You do not need the <application>LilyPond</application> input file to do the tutorial. You do need the PDF output file to do the tutorial. Use the input file if you encounter problems, or to check your result.
<itemizedlist>
- <listitem><para><citetitle>LilyPond Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/LilyPond/Orchestra-source.ly" /></para></listitem>
- <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/LilyPond/Orchestra-result.pdf" /></para></listitem>
+ <listitem><para><citetitle>LilyPond Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/LilyPond/Orchestra-source.ly" /></para></listitem>
+ <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/LilyPond/Orchestra-result.pdf" /></para></listitem>
</itemizedlist>
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Starting_the_Score">
- <title>Starting the Score</title>
+ <title>Start the Score</title>
<procedure>
<step><para>'LilyPond > Setup New Score'</para></step>
<step><para>"Titles and Headers" Tab:</para>
@@ -62,7 +62,7 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Adjusting_Frescobaldis_Output">
- <title>Adjusting Frescobaldi's Output</title>
+ <title>Adjust Frescobaldi's Output</title>
<!-- Part of this portion is shared with the Piano example -->
<para>
These steps are useful in establishing a consistent input style for LilyPond. The things suggested here are also useful for getting used to working with large scores, which can be a challenge in any text editor. Thankfully, careful (and consistent!) code organization goes a long way in helping you to quickly find your way around your files. Setting up files the right way to begin with makes this much easier in the end.
@@ -124,12 +124,12 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Inputting">
- <title>Inputting</title>
+ <title>Input Notes</title>
<para>
This tutorial offers step-by-step instructions representing one way to input the score. Only the part before "Allegretto" will be inputted. The full first movement is included in the PDF file, so you can input it yourself.
</para>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Inputting-Start_with_the_Easy_Part">
- <title>Starting with the Easy Part</title>
+ <title>Start with the Easy Part</title>
<para>
The best way to get started on large scores is to just start with something easy. Nothing can be easier than doing nothing, so let's first input the multi-measure rests in the wind sections and timpani.
</para>
@@ -148,7 +148,7 @@
</procedure>
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Inputting-Wind_and_Timpani">
- <title>Continuing with the Wind and Timpani Parts</title>
+ <title>Continue with the Wind and Timpani Parts</title>
<procedure>
<step><para>Now we need to start adding notes. We'll start with the parts that have only rests:</para>
<substeps>
@@ -214,7 +214,7 @@
</procedure>
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Inputting-Strings">
- <title>Moving on to the Strings</title>
+ <title>Continue with the Strings</title>
<para>
After correctly finishing all of the wind and timpani parts, you can move on to the strings.
<itemizedlist>
@@ -249,7 +249,7 @@
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Orchestra-Inputting-Fast_Section">
- <title>To Continue to the Fast Section</title>
+ <title>Continue to the Fast Section</title>
<para>
If you want to finish inputting the first movement, as an exercise, then you will also need to know how to write a tempo-change in an orchestral score:
</para>
diff --git a/en-US/LilyPond/LilyPond-piano.xml b/en-US/LilyPond/LilyPond-piano.xml
index f546751..1100eca 100644
--- a/en-US/LilyPond/LilyPond-piano.xml
+++ b/en-US/LilyPond/LilyPond-piano.xml
@@ -5,7 +5,7 @@
]>
<section id="sect-Musicians_Guide-LilyPond-Piano">
- <title>Working on a Piano Score (Tutorial)</title>
+ <title>Work on a Piano Score (Tutorial)</title>
<para>
Scenario: At a used music store, you encounter a 60-year-old, hand-engraved copy of a Schubert "Impromptu," but it's been badly damaged by a flood. The store's owner says that, if you can use the score, you can keep it for free. The score is barely legible, so you decide to prepare a copy with a computer notation program.
</para>
@@ -21,14 +21,14 @@
<para>
You do not need the <application>LilyPond</application> input file to do the tutorial. You should use the input file if you encounter problems, and to compare your completion. You do need the PDF output file to do the tutorial.
<itemizedlist>
- <listitem><para><citetitle><application>LilyPond</application> Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/LilyPond/Piano-source.ly" /></para></listitem>
- <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/LilyPond/Piano-result.pdf" />.</para></listitem>
+ <listitem><para><citetitle><application>LilyPond</application> Input File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/LilyPond/Piano-source.ly" /></para></listitem>
+ <listitem><para><citetitle>PDF Output File</citetitle> at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/LilyPond/Piano-result.pdf" />.</para></listitem>
</itemizedlist>
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Starting_the_Score">
- <title>Starting the Score</title>
+ <title>Start the Score</title>
<procedure>
<step><para>Open Frescobaldi with a new document.</para></step>
<step><para>Start the "Setup New Score" tool, by clicking '<application>LilyPond</application> > Setup New Score' in the menu.</para></step>
@@ -60,7 +60,7 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Adjusting_Frescobaldis_Output">
- <title>Adjusting Frescobaldi's Output</title>
+ <title>Adjust Frescobaldi's Output</title>
<!-- This section is shared with the orchestral example -->
<para>
These steps are useful in establishing a consistent input style for <application>LilyPond</application>. The things suggested here are also useful for getting used to working with large scores, which can be a challenge in any text editor. Thankfully, careful (and consistent!) code organization goes a long way in helping you to quickly find your way around your files. Setting up files the right way to begin with makes this much easier in the end.
@@ -105,12 +105,12 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Inputting">
- <title>Inputting</title>
+ <title>Input Notes</title>
<para>
Piano scores present some unique challenges with <application>LilyPond</application>, but they're easy to overcome with some careful thought. This tutorial will avoid step-by-step instructions on how to input particular notes, instead focussing on those unique piano challenges presented in this particular composition. The <application>LilyPond</application> "Notation Reference" provides a section dedicated to keyboard and piano music. Most of the situations described there are not present or discussed in this score, which gives this tutorial unique material.
</para>
<section id="sect-Musicians_Guide-LilyPond-Piano-Inputting-Order_of_Inputting">
- <title>Order of Inputting</title>
+ <title>Order of Input</title>
<para>
Choosing the right order to input your scores can make things much easier to troubleshoot. Here are some suggestions:
</para>
@@ -167,7 +167,7 @@
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Inputting-Changing_the_Style_of_Crescendo">
- <title>Changing the Style of Crescendo</title>
+ <title>Change the Style of Crescendo</title>
<para>
Sometimes the composer or editor prefers to use the words <foreignphrase>crescendo</foreignphrase> or its abbreviation, <foreignphrase>cresc.</foreignphrase>, instead of the <literal><![CDATA[\<]]></literal> style of crescendo. In <application>LilyPond</application> these are handled by the same source-file notation (<literal><![CDATA[\<]]></literal> to start and <code>\!</code> to end explicitly). However, if you want to use text and a "spanner" (dotted or dashed line, for example) instead of the < sign, you need to tell <application>LilyPond</application>. This can be accomplished with the following command: <code>\crescTextCresc</code>.
</para>
@@ -219,7 +219,7 @@
</section> <!-- Ends "Inputting" Section --> <!-- <application>LilyPond</application>-Piano-Inputting- -->
<section id="sect-Musicians_Guide-LilyPond-Piano-Troubleshooting_Errors">
- <title>Troubleshooting Errors</title>
+ <title>Troubleshoot Errors</title>
<para>
It can be difficult to troubleshoot inputting errors, especially when you find them days or weeks after originally inputting that section of a score. The best way to fix errors is to input scores in a way that doesn't allow them in the first place. As they say, "an ounce of prevention is worth a pound of cure," which means "if you input your <application>LilyPond</application> files carefully, then you will encounter fewer problems." Such practices as proper spacing, and regular use of the octave- and bar-check features will deal with many common problems.
</para>
@@ -234,7 +234,7 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Formatting">
- <title>Formatting the Score (Piano Dynamics)</title>
+ <title>Format the Score (Piano Dynamics)</title>
<para>
Keyboard instruments use a unique notation when it comes to dynamics. Most instruments use only one staff per player, so the dynamics are, by convention, notated underneath that staff. Keyboard instruments usually use two staves (organs and complex piano music may use three). Because the dynamics are usually meant to apply to both staves, they are usually notated between the two staves. This is similar to notation beneath the upper staff, but in truth, piano dynamics tend to be placed in the middle between the staves - entering the dynamics as belonging to the upper staff, in <application>LilyPond</application>, will not produce that effect.
</para>
@@ -245,7 +245,7 @@
This process looks difficult, and may seem daunting. It's not necessary to understand all of the commands in the "PianoDynamics" Context in order to use the context, so there is no need to worry!
</para>
<section id="sect-Musicians_Guide-LilyPond-Piano-Formatting-Preparing_the_PianoDynamics_Context">
- <title>Preparing the "PianoDynamics" Context</title>
+ <title>Prepare the "PianoDynamics" Context</title>
<para>
It is probably easier to add these commands before inputting most of the score, but there is no reason why this context cannot be added to any score at any time.
</para>
@@ -310,7 +310,7 @@ dynamics =
</procedure>
</section>
<section id="sect-Musicians_Guide-LilyPond-Piano-Formatting-Inputting_the_Dynamics">
- <title>Inputting the Dynamics</title>
+ <title>Input Dynamics</title>
<para>
Now you can input the dynamic markings. These are inputted with a special note called a "spacer," that uses the letter "s" rather than a note name. You can also use rests (both partial- and multi-measure, r and R), but dynamic markings cannot be assigned to them.
</para>
diff --git a/en-US/LilyPond/LilyPond-syntax.xml b/en-US/LilyPond/LilyPond-syntax.xml
index 21fd85f..2160bdc 100644
--- a/en-US/LilyPond/LilyPond-syntax.xml
+++ b/en-US/LilyPond/LilyPond-syntax.xml
@@ -207,7 +207,7 @@
</section>
<section id="sect-Musicians_Guide-LilyPond-Syntax-Source_Files">
- <title>Source Files and Their Formatting</title>
+ <title>Source Files</title>
<para>
Source files are the text files prepared with instructions telling <application>LilyPond</application> the content of the score you want it to create. They are so called because these files are the "source" of what you wish to create. As with programming languages, the text inside these files is often referred to as "source code." It sounds scary to think that you must edit code in order to use <application>LilyPond</application>, but "code" just means that it isn't normal English (or insert-language-here).
</para>
@@ -218,7 +218,7 @@
You will eventually develop your own style, better-suited to the kinds of tasks that you accomplish. When you do this, there is only one rule to keep in mind: be consistent within source files. When source files are programmed in a consistent way, it means that anybody who wants to use those files (like yourself, in the future) will easily be able to determine how they are organized.
</para>
<section id="sect-Musicians_Guide-">
- <title>Organizing Files, and Where to Put the Notes</title>
+ <title>Organizing Source Files</title>
<para>
<application>LilyPond</application> files are constructed as a series of commands. For better or worse, the <application>LilyPond</application> interpreter allows a great deal of flexibility when it comes to source file setup. This can lead to confusion about where things should be done, especially when using automated score-setup tools like <application>Frescobaldi</application>.
</para>
@@ -267,46 +267,48 @@
\header
{
- title = "<replaceable>Example</replaceable>"
+ title = "Empty Example"
}
-<replaceable>something</replaceable> = \relative c''
+violin = \relative c''
{
- \key <replaceable>c \major</replaceable>
- \time <replaceable>4/4</replaceable>
+ \key c \major
+ \time 4/4
% Music follows here.
+
+ <replaceable>Put your music here</replaceable>
}
\score
{
\new Staff \with
{
- instrumentName = "<replaceable>Something</replaceable>"
+ instrumentName = "Violin"
}
- \<replaceable>something</replaceable>
+ \violin
\layout { }
}
</programlisting>
</para>
<para>
- This source file makes use of many commands, and even defines "violin" for its own use. It may not be easy to see from this simple example, but keeping your notes separated from the formatting of a complex <literal>\score</literal> section will greatly improve the readability of both sections. Furthermore, you will easily be able to search through thousands of lines of source file to find the section that you want.
+ This example uses many built-in commands (like <literal>\relative</literal> and <literal>\key</literal>), and it defines the <literal>violin</literal> command. <application>Frescobaldi</application> places a <literal>% Music follows here.</literal> comment where you should input your notes. Notice that your notes belong in the <literal>violin</literal> section. This means that you write part of the <literal>violin</literal> command.
</para>
<para>
- So where do the notes go? In this template, they should go in the "violin" section. <application>Frescobaldi</application> usually marks this off with a friendly comment, stating "% Music follows here." That's exactly what it means: most of your time will be spent working with what follows there.
+ <application>Frescobaldi</application> separates the violin's notes from the <literal>\score</literal> section so that the source file is easier to read. You can fix errors more easily in well-organized source files. If you complete the following tutorials, you will learn three strategies to organize sources files.
</para>
<para>
- As a final note, we caution against removing the "layout" section of the "score" section. Removing the "layout" section would cause <application>LilyPond</application> not to create a score as output.
+ The <literal>\layout</literal> section is empty in this example. Like the <literal>\score</literal> section, <literal>\layout</literal> is a command. The <literal>\layout</literal> command tells LilyPond to output a musical score. Advanced users sometimes remove the <literal>\layout</literal> command, but most source files use it.
</para>
</section>
</section>
<section id="sect-Musicians_Guide-LilyPond-Syntax-Avoiding_Errors">
- <title>Avoiding Errors</title>
+ <title>How to Avoid Errors</title>
<para>
The <application>LilyPond</application> syntax has two built-in symbols for helping to avoid musical errors. The octave-check symbol ensures that your notes are in the octave you intend. The bar-check symbols ensures that your barlines are where you intend.
</para>
<section id="sect-Musicians_Guide-LilyPond-Syntax-Avoiding_Errors-Octave_Check_Symbol">
- <title>Octave-Check Symbol</title>
+ <title>The Octave-Check Symbol</title>
<para>
The octave-check symbol compares a relative pitch with its absolute pitch equivalent. <application>LilyPond</application> prints a warning if the pitches do not match, then continues with the absolute pitch. You should correct the relative pitch when <application>LilyPond</application> prints a warning.
</para>
@@ -324,7 +326,7 @@
</para>
</section>
<section id="sect-Musicians_Guide-LilyPond-Syntax-Avoiding_Errors-Bar_Check_Symbol">
- <title>Bar-Check Symbol</title>
+ <title>The Bar-Check Symbol</title>
<para>
The bar-check symbol tests whether a barline is printed at that point in the music. <application>LilyPond</application> prints a warning if the bar-check symbol does not line up with a barline in the score, then processes the rest of the file. You must correct an inputting mistake when <application>LilyPond</application> prints a warning.
</para>
diff --git a/en-US/Revision_History.xml b/en-US/Revision_History.xml
index a924a5f..a266dd8 100644
--- a/en-US/Revision_History.xml
+++ b/en-US/Revision_History.xml
@@ -189,18 +189,36 @@
</revdescription>
</revision>
- <!-- NOTE: When adding a revision here, be sure to update the <edition> tag in "Book_Info.xml" -->
+ <revision>
+ <revnumber>15.0.1</revnumber>
+ <date>Sun Dec 26 2010</date>
+ <author>
+ <firstname>Christopher</firstname>
+ <surname>Antila</surname>
+ <email>crantila at fedoraproject.org</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Fixed Bug 665663 ("URLs to all Tutorial Files Are Broken") for Fedora 15.</member>
+ <member>Re-wrote Section 12.4.7.1 to fix the first error in Bug 654187.</member>
+ <member>Renamed some section in Chapter 12, making them easier to translate (I hope).</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+
+ <!-- NOTE: When adding a revision above, be sure to update the <edition> tag in "Book_Info.xml" -->
<!-- Finite Tasks -->
- <!-- TODO: Make the Ardour external files work -->
<!-- TODO: Bug 654187 ("Errors in Musicians' Guide LilyPond section") -->
+ <!-- TODO: Bug 665660 ("External Files for Ardour Tutorial Are Missing") -->
+ <!-- TODO: Bug 665662 ("SuperCollider Chapters Are in First Person") -->
+ <!-- TODO: Bug 665664 ("LilyPond Example Scores Are Incomplete") -->
<!-- TODO: Bug 622168 ("Rosegarden Tutorial Is Boring") -->
<!-- TODO: fix the example around line 630 of SC Basic Programming -->
<!-- TODO: convert images to format given by R. Landmann (as line 164 of Audacity?) -->
<!-- TODO: convert SuperCollider examples to <xi:include ... /> -->
<!-- TODO: convert LilyPond examples to <xi:include ... /> -->
<!-- TODO: see whether SELinux can be configured to determine who/what has access to real-time stuff for JACK -->
- <!-- TODO: Rewrite the SuperCollider "Composing" tutorial, to get rid of the first-person -->
<!-- Ongoing Tasks -->
<!-- TODO: ensure that everything is formatted correctly -->
diff --git a/en-US/SuperCollider/SuperCollider-Composing.xml b/en-US/SuperCollider/SuperCollider-Composing.xml
index 6ca48a3..d29d527 100644
--- a/en-US/SuperCollider/SuperCollider-Composing.xml
+++ b/en-US/SuperCollider/SuperCollider-Composing.xml
@@ -21,9 +21,9 @@
<para>
The following files represent complete versions of the program. You should try to complete the program yourself before reviewing these versions:
<itemizedlist>
- <listitem><para><citetitle>Method One</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/SuperCollider/Method_One.sc" /></para></listitem>
- <listitem><para><citetitle>Method One (Optimized)</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/SuperCollider/Method_One-optimized.sc" /></para></listitem>
- <listitem><para>A FLAC-format recording of <citetitle>Method One</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/Musicians_Guide/files/SuperCollider/Method_One.flac" /></para></listitem>
+ <listitem><para><citetitle>Method One</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/SuperCollider/Method_One.sc" /></para></listitem>
+ <listitem><para><citetitle>Method One (Optimized)</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/SuperCollider/Method_One-optimized.sc" /></para></listitem>
+ <listitem><para>A FLAC-format recording of <citetitle>Method One</citetitle> is available at <ulink url="http://docs.fedoraproject.org/en-US/Fedora/15/html/Musicians_Guide/files/SuperCollider/Method_One.flac" /></para></listitem>
</itemizedlist>
</para>
<para>
More information about the docs-commits
mailing list