1 @c -*- coding: utf-8; mode: texinfo; -*-
3 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 When revising a translation, copy the HEAD committish of the
6 version that you are working on. See TRANSLATION for details.
10 hmm, the one big page is too big, but it was really inviting to
11 read. this is not. maybe just scrap this menu and introduction
15 @c @setfilename automated-engraving.info
16 @c @settitle Obsessed with putting ink on paper
17 @c @documentencoding UTF-8
18 @c @documentlanguage en
21 @c @include macros.itexi
31 @node automated-engraving
32 @unnumbered Obsessed with putting ink on paper
35 @heading What is behind LilyPond?
37 @sourceimage{hader-collage,,,.png}
39 LilyPond is not unique in making music notation: there are a lot of
40 programs that print music, and nowadays most of the newly printed
41 music is made with computers. Unfortunately, that also shows: just
42 ask any musician that plays classical music: new scores do not look as
45 What is the difference between hand-work and machine work, and what
46 has caused it? How can we improve the situation? This essay explains
47 problems in music notation (software), and our approach to solving
51 * introduction:: Introduction -- what is wrong with computer music notation.
52 * software:: What is wrong with software -- or how Finale is not the end-all of music software.
53 * problem-statement:: How not to design software -- or modeling music notation.
54 * divide-and-conquer:: Divide and conqueror -- a blue print for automated notation.
55 * implementing-notation:: Impressive, but does it also work in theory -- a practical approach to capturing notation.
56 * engraving:: Music engraving -- the art of printing music.
57 * implementing-typography:: Implementing typography -- hackers attack the engraving problem.
58 * formatting-architecture:: A flexible program architecture -- lets us write engraving software
59 * scoring-esthetics:: Beautiful numbers -- how LilyPond participates in the Miss World contests.
60 * benchmarking:: Notation benchmarking -- is a flexible architecture enough?
61 * schubert:: Notation benchmarking -- project too?
62 * typography-features:: Typographical features -- unique to LilyPond.
63 * input-format:: Input format -- how to enter music.
64 * conclusion:: Conclusion.
69 @c This essay is also available in @ref{big-page.html,one big page}.
71 @include automated-engraving/introduction.itexi
72 @include automated-engraving/software.itexi
73 @include automated-engraving/problem-statement.itexi
74 @include automated-engraving/divide-and-conquer.itexi
75 @include automated-engraving/implementing-notation.itexi
76 @include automated-engraving/engraving.itexi
77 @include automated-engraving/implementing-typography.itexi
78 @include automated-engraving/formatting-architecture.itexi
79 @include automated-engraving/scoring-esthetics.itexi
80 @include automated-engraving/benchmarking.itexi
81 @include automated-engraving/schubert.itexi
82 @include automated-engraving/typography-features.itexi
83 @include automated-engraving/input-format.itexi
84 @include automated-engraving/conclusion.itexi