Doc: automated-engraving: tweaks. Fixes menu structure and appearance.

[lilypond.git] / Documentation / automated-engraving / software.itexi

diff --git a/Documentation/automated-engraving/software.itexi b/Documentation/automated-engraving/software.itexi
index 3cb64e8847c92170e0927017f65aafab1cd38958..8dcd6047ae1854520b8398e6f8ea1b9e393de9e0 100644 (file)
--- a/Documentation/automated-engraving/software.itexi
+++ b/Documentation/automated-engraving/software.itexi
@@ -1,4 +1,4 @@
-\input texinfo @c -*- coding: utf-8; mode: texinfo; -*-
+@c -*- coding: utf-8; mode: texinfo; -*-
 @ignore
     Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
 
@@ -9,13 +9,13 @@
 
 
 @node software 
-@unnumberedsec What's wrong with music notation software
+@unnumberedsec What is wrong with music notation software
 
 Computers have made music printing accessible to the masses, but they
 tend to deliver mediocre typography.  Apparently, programmers have
 been doing a shoddy job on notation programs.  To illustrate that, we
 had an amateur user set a piece of music in one of the most popular
-‘professional’ notation programs sold today, Finale
+@quotedblleft{}professional@quotedblright{} notation programs sold today, Finale
 2003. It was made with all of the default settings. The music is from
 the Sarabande of the 2nd Cello Suite by J. S. Bach.
 
@@ -24,19 +24,19 @@ the Sarabande of the 2nd Cello Suite by J. S. Bach.
 }
 
 @divClass{float-center}
-@divEnd
 @sourceimage{finale-sarabande-full,,,.png}
+@divEnd
 
 This example far surpasses the previous one when it comes to
 formatting errors: there are serious errors in literally
 @emph{every} measure. The errors come in all sizes: a big one is the
-oddly s p a c e d &nbsp o u t last line. A smaller one is the flat in
+oddly s p a c e d @  o u t last line. A smaller one is the flat in
 measure 13, which is covered by the note preceding it. Here is a
 magnification of that measure:
 
 @divClass{float-center}
-@divEnd
 @sourceimage{finale-flat-detail,,,.png}
+@divEnd
 
 The errors go down to the teensy details: below is a blowup of the
 beam in that measure. Of course, in proper typography the beam should
@@ -45,8 +45,8 @@ telling glimpse into Coda Music Technology programmers' aptness (or
 lack thereof) with the underlying PostScript technology.
 
 @divClass{float-center}
-@divEnd
 @sourceimage{finale-beam-detail,,,.png}
+@divEnd
 
 Now, one could refute that Finale has a graphical interface, and it
 lets you easily move about elements to correct errors, or use plug-ins
@@ -64,8 +64,8 @@ too far apart. Did you notice that the eighth rest is too far down?
 Did it occur to you that the stem of the last eighth note is too long?
 
 @divClass{float-center}
-@divEnd
 @sourceimage{finale-flat-correct,,,.png}
+@divEnd
 
 Unless you are an expert, typographical errors will irk you without
 being obvious. Many of them will go uncorrected and will still be in the
@@ -104,11 +104,6 @@ doubt, measure the difference with a magnifying glass.
 @end itemize
 
 @divClass{float-right}
-@divEnd
 Next: @ref{problem-statement,How not to design software},
 or: modeling music notation.
-
-
-
-@bye
-
+@divEnd