lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GLISS] why the hell all this fuss


From: Joseph Rushton Wakeling
Subject: Re: [GLISS] why the hell all this fuss
Date: Sun, 09 Sep 2012 12:22:16 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0

On 08/09/12 16:10, Han-Wen Nienhuys wrote:
I have in the past talked with people from Henle; also, Schirmer has a
style guide that you can order as a book.

How far in the past are we talking about?  (Just for clarity.)

My overall impression is that they are primarily interested in:

* Strict adherence to their publisher style
* Delivering printed parts on a low budget.

Once the edition is printed, there is little reason to keep the files
around, and in some cases (due to editing PS output), it's not useful
at all. Music publishers (at least a few years ago) are still very
much focused on putting ink on dead trees in large quantities in the
most uniform and cost-efficient way possible, a business model which
makes ever less sense in the digital age.

But that's great news for Lilypond, because it suggests that publishers are completely agnostic about software choices so long as their (visual) stylistic requirements are met.

It suggests that two very productive lines of work for Lilypond would be making it easy to implement publisher styles, and making sure that they are indeed implemented for several of the major publishers.

This is something that's interesting to think of in terms of Janek's work reproducing an old hand-engraved Bärenreiter score:
http://news.lilynet.net/?The-LilyPond-Report-26#lilypond_output_analysis

... as it's quite revealing about what aspects of Lilypond engraving can be tweaked easily, what engraving details need to be "coupled" so that they are changed in proportion to one another, and what small aspects of placement can be problematic when implementing a non-default style.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]