Am 08.01.2013 20:02, schrieb Antonio Gervasoni:
...
Now, I'm almost done and I'm thinking about publishing a complete
description of how I did it. Not that I think that my process for creating
such a score is the right one or even the best one! I just want to share it
with other users that might find it useful and also receive feedback from
other more experienced users in the form of advice on how to improve and
simplify it.
The problem is that I don't know how to do this! If I write a short guide
of, say 20-30 pages, in pdf format, where should I post/upload it? The .ly
files and pdf output could be uploaded to the Mutopia Project. I could also
upload the score and parts to IMSLP. But what about the guide? Where should
that go? Any ideas?
I could use my own website, or create a blog and put it there, but my
concern is about making it immediately "visible" to most Lilypond users, so
that it can attract the attention of those of them who write orchestral
music and generate discussion and a flow of ideas right away.
Regards,
Antonio
This is a _very_ good idea, and I would be pleased to get you 'into my
boat'.
Last year I did something similar because I think that exactly this kind
of information would be very valuable (i.e. essay style material that
complements LilyPond's (very good) reference style documentation).
You can have a look at
http://lilypond.ursliska.de/notensatz/lilypond-tutorials/tackle-complex-tasks.html
if you want.
Since then I have in mind to extend this by more texts and to offer
others to extend it to get a collection of related material. (But I'll
probably change to some kind of PDF delivery because it was
unnecessarily complicated to get it on web pages).
Probably I'll shift this idea to another project, though: During the
development of a musical edition some others and me created the base for
a kind of LilyPond toolkit library. When the edition is finished we'll
change that to be an open source project hosted on Github. This will
consist of sets of functionality, templates and examples which of course
have to be well documented.
It isn't finally decided but the original motivation of this library
could be labeled with 'productivity tools' and '(best) practice
strategies'. The 'includable' library can and is intended to be
accompanied by more or less standalone essays (like how to set up
projects to be variable, how to deal with complicated transpositions,
how to change the overall visual appearance of scores etc.).
I think an essay on how to set up an orchestral score would fit
extremely well into this concept. And source snippets etc. could also be
seamlessly be integrated.
[In theory such a project could on the long run result in a book. But of
course this is pure speculation ATM.]
So if you think that's a good idea don't hesitate to contact my (on or
off list).
Best
Urs
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Guide-to-Writing-Orchestral-Scores-with-Lilypond-tp139065.html
Sent from the User mailing list archive at Nabble.com.
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
