diff options
| author | Jan Nieuwenhuizen <janneke@gnu.org> | 2009-08-13 00:32:36 +0200 |
|---|---|---|
| committer | Jan Nieuwenhuizen <janneke@gnu.org> | 2009-08-13 01:30:27 +0200 |
| commit | 3fcb1f38d96cd2b5d49deebcde8b476ff96430e4 (patch) | |
| tree | de750c4e73199299a74fda1e2c7eca1b8f963e83 /Documentation/automated-engraving/divide-and-conquer.itexi | |
| parent | 480e203052571809f1a11ee7c7728f08aa042fe9 (diff) | |
Doc: automated-engraving: build fixes and images.
Diffstat (limited to 'Documentation/automated-engraving/divide-and-conquer.itexi')
| -rw-r--r-- | Documentation/automated-engraving/divide-and-conquer.itexi | 16 |
1 files changed, 6 insertions, 10 deletions
diff --git a/Documentation/automated-engraving/divide-and-conquer.itexi b/Documentation/automated-engraving/divide-and-conquer.itexi index 6f28836bf6..566af1a4ce 100644 --- a/Documentation/automated-engraving/divide-and-conquer.itexi +++ b/Documentation/automated-engraving/divide-and-conquer.itexi @@ -7,19 +7,17 @@ @end ignore - +@node divide-and-conquer @unnumberedsec Plan de campagne Since content and form of a score are separate, we have to match that in the design of software. Hence, the basic blueprint of our program should follow this scheme -@table asis +@multitable @columnfractions .3 .3 .3 @item -@tab - -@image{pictures/simple-notation,,,.png} +@sourceimage{simple-notation,,,.png} @tab @@ -29,15 +27,13 @@ should follow this scheme @tab -@code{{ c'4 d'8 }} +@code{@{ c'4 d'8 @}} @item -@tab - 1. form @@ -53,7 +49,7 @@ should follow this scheme -@end table +@end multitable In effect, we are conquering the problem by dividing it into subproblems @@ -79,7 +75,7 @@ Finally, whenever you subdivide a problem, a new problem is created, @divClass{float-right} @divEnd -Next: @ref{implementing-notation.html,Impressive, but does it also +Next: @ref{implementing-notation,Impressive, but does it also work in theory}? A practical approach to capturing notation. @bye |