On 2/6/10 1:53 PM, "Michael J. O'Donnell" wrote:
> Carl,
>
> Thanks for the note. One thing that I discovered in source, but can't find in
> manuals, is "not-first-page" (in titling-init.ly). I used it to define my own
> "part-not-first-page", since I like to format lots of things as bookpart
On 1/2/10 10:06 AM, "Michael J. O'Donnell" wrote:
> In the hope that I had overlooked
> something (I've read the whole notation manual, but there are clearly
> things that haven't made it in yet---I've found some of them in the
> *.scm and *.ly sources but there are bound to be others that I've
>
On 02.01.2010, at 20:49, Carl Sorensen wrote:
May I suggest that the proper way to handle this is not to try to turn
LilyPond into an information manager?
Instead, the proper way is to use an information manager with
LilyPond.
I would recommend that the semantically appropriate way to handl
Michael J. O'Donnell acm.org> writes:
>
> Thanks for pointing out \tag. I've already read up, and experimented
> with it. It doesn't solve the problem, because it requires that I
> anticipate every possible correction when entering the data from the MS.
> The only way to get useful coverage is t
On 02.01.2010, at 20:49, Carl Sorensen wrote:
May I suggest that the proper way to handle this is not to try to turn
LilyPond into an information manager?
Instead, the proper way is to use an information manager with
LilyPond.
I would recommend that the semantically appropriate way to han
I don't foresee anything happening for months if not years, but
I've added it to the tracker. If I wasn't doing release and
manager tasks, I'd like to tackle it myself:
http://code.google.com/p/lilypond/issues/detail?id=955
You can do something like this with the last version of
"extractMusic
Hi Michael,
> Unfortunately, editorial changes to note durations are particularly
> problematic, since they change all of the time values downstream.
Agreed.
> adjustments that went above the level of a single tweak-voice would hit the
> full staff context.
If the Scheme function took a conte
I might attack this myself some day, if it can really
be accomplished at the Scheme interface. I doubt that I will ever
penetrate the C++ substrate. At present, I don't understand the data
structures quite well enough, and I think a few more iterations of the
documentation are probably required
Xavier Scheuer wrote:
> > Look into \tag.
>
> Which is documented there:
> Notation Reference (NR) 3.2.2 "Different editions from
> one source"
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Different-editions-from-one-source
> ;-)
That's 3.3.2, not 3.2.2
On Sat, Jan 02, 2010 at 12:22:27PM -0500, Kieren MacMillan wrote:
> If someone with real Scheme-fu could build a function that took a series of
> moments and tweaks, you might be able to do something like
>
> ms = \relative e'' {
>e4 e c d |
> }
>
> correctionsEditionA = {
> \coolSchemeF
On 1/2/10 10:06 AM, "Michael J. O'Donnell" wrote:
> You are proposing very good solutions for the short term production of
> scores. I am more concerned with the very long term management of the
> information.
>
> The object is to
>
> 1. have a file containing data entry from the MS which re
Hi Michael,
>> Clearly, this doesn't require tagging "every note with a different tag" —
>> you simply tag the notes for different editions as you need them.
> Perhaps I should have just answered this point directly. The problem is
> that I don't know what the "different editions" will be. They a
Kieren MacMillan wrote:
> Clearly, this doesn't require tagging "every note with a different tag" — you
> simply tag the notes for different editions as you need them.
Perhaps I should have just answered this point directly. The problem is
that I don't know what the "different editions" will be. T
You are proposing very good solutions for the short term production of
scores. I am more concerned with the very long term management of the
information.
The object is to
1. have a file containing data entry from the MS which represents the
uncorrected manuscript, and which (almost) never needs t
Hi Michael,
> Thanks for pointing out \tag. I've already read up, and experimented
> with it. It doesn't solve the problem, because it requires that I
> anticipate every possible correction when entering the data from the MS.
> The only way to get useful coverage is to tag every note with a
> diff
Thanks for pointing out \tag. I've already read up, and experimented
with it. It doesn't solve the problem, because it requires that I
anticipate every possible correction when entering the data from the MS.
The only way to get useful coverage is to tag every note with a
different tag, which is too
Le Sat, 2 Jan 2010 00:32:08 -0500,
Kieren MacMillan a écrit :
> Hi Michael,
>
> > I am experimenting with methods to enter notes from a manuscript
> > and produce several typeset scores, including at least • one that
> > looks very much like the manuscript, for proof reading • another
> > that i
Hi Michael,
> I am experimenting with methods to enter notes from a manuscript and produce
> several typeset scores, including at least
> • one that looks very much like the manuscript, for proof reading
> • another that is good for performance.
> There will probably be other versions
I am experimenting with methods to enter notes from a manuscript and
produce several typeset scores, including at least
one that looks very much like the manuscript, for proof reading
another that is good for performance.
There will probably be other versions too.
Problem: the manuscript
19 matches
Mail list logo
