GDP: tutorial @seealso links

Hi all, I updated Learning Manual 2.1.2 to use the same @seealso format as the notation reference. You can see the old method in 2.2.1, and actually the rest of the section for now. I'd like to change all the @seealso sections to match 2.1.2. Does anybody have a huge objection to this?

Re: Guitar Tab not using 6th string

It's only fixed in 2.11, not 2.10. Cheers, - Graham Tom Gendai wrote: Hello! Sorry if someone has posted about this before but I couldn't find any useful information via Google etc. My problem is this. I'm transcribing pieces of music from piano to guitar to be played as duets. As one of

Guitar Tab not using 6th string

Hello! Sorry if someone has posted about this before but I couldn't find any useful information via Google etc. My problem is this. I'm transcribing pieces of music from piano to guitar to be played as duets. As one of the players is a beginner and learning to read music has been sort of an issue

Re: Markup with multi-measure rests

Thanks, this first item has been added as http://code.google.com/p/lilypond/issues/detail?id=495 Cheers, - Graham Mats Bengtsson wrote: To me it seems a bug that you get collisions in your first example. The second example can easily be modified to get what you want. Just add \fatText before t

SOLUTION: Re: scheme function to align time-sig above nearest RehearsalMark?

There is a much easier way to do this thant I originally imagined. I enclosed the function that I came up with and a snippet to demonstrate. When you compile, note that the only problem is that the alignment behavior of the ReheasalMarks is undesirable, due to the ReheasalMark being moved to the

Re: GDP: nothing to do with examples

Hans Aberg wrote: On 19 Oct 2007, at 23:29, Graham Percival wrote: In particular, look at the "GDP docs" and the "policy.txt". So what is "Music Glossary" and "Notation Reference" relative to the names listed on: Thanks, good catch. Glossary is music glossary. User manual is notation ref

Re: ReheasalMark in Staff context is broken - sponsorship of fix?

Hi Mats et al, (RE: this bug: http://code.google.com/p/lilypond/issues/detail?id=432) Moving Break_align_engraver to the Staff context works to get the correct alignment of RehearsalMarks, but the side effect is that if there is a mid-system Clef change in one Staff and not another, you get a bro

Re: GDP: introducing examples

On 19.10.2007 (14:58), Graham Percival wrote: > Mark Knoop wrote: > >Graham Percival wrote: > >>1) The text just continues directly into > >>2) The text suggests that one may do foo, > >>3) The text directs the reader to the following example: > >>4) The text forms a complete sentence. >

Re: GDP: nothing to do with examples

On 19 Oct 2007, at 23:29, Graham Percival wrote: I suspected that. - So it might be better putting at least the more prominent examples in a special examples PDF, and reference that. The LSR could still be there, for new examples that have not yet worked up the hierarchy. GDP is not on t

GDP: output website changed

Hi all, Thanks to a generous offer from Reinhold Kainhofer, we now have a more stable location for the GDP output. You should not need to change any bookmarks, though. The main GDP website is still here: http://web.uvic.ca/~gperciva/ The link to "GDP output" has been changed from opihi (wh

Re: GDP: introducing examples

Mark Knoop wrote: Graham Percival wrote: 1) The text just continues directly into 2) The text suggests that one may do foo, 3) The text directs the reader to the following example: 4) The text forms a complete sentence. Should allow all? Specify one method? Disallow one or two metho

Re: GDP: where do we discuss MIDI?

Mats Bengtsson wrote: Graham Percival wrote: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Ok, this option is overwhelmingly favored. We will remove discussion about MIDI from the rest of the manual, and concentrate it in 4.3. Anybody

Re: GDP: nothing to do with examples

Hans Aberg wrote: I suspected that. - So it might be better putting at least the more prominent examples in a special examples PDF, and reference that. The LSR could still be there, for new examples that have not yet worked up the hierarchy. Hans, GDP is not on the main lilypond website. Pl

Re: GDP: introducing examples

On 19 Oct 2007, at 16:38, Francisco Vila wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ Actually, I see now where the problem is: If one follows the shortcuts on the main

Re: GDP: introducing examples

On 19 Oct 2007, at 16:38, Francisco Vila wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ Thank you, but the question is then why the search on the first page did not find

Re: GDP: introducing examples

On 19 Oct 2007, at 16:59, Eyolf Østrem wrote: So how do you find the LSR?... You have the link into the main documentaion page http://lilypond.org/web/documentation and it links to http://lsr.dsi.unimi.it/ ... and in the final GDP, there will be so many LSR links that you're going to moan: "

Re: Church Rests

On 19.10.2007 (16:24), Francisco Vila wrote: > 2007/10/19, Trevor Daniels <[EMAIL PROTECTED]>: > > > > In the section on multi-measure rests the manual talks about > > "church rests", meaning the use of increasing numbers of > > little rectangles to indicate how many measures are included > > in th

Re: GDP: introducing examples

On 19.10.2007 (16:38), Francisco Vila wrote: > 2007/10/19, Hans Aberg <[EMAIL PROTECTED]>: > > So how do you find the LSR?... > > You have the link into the main documentaion page > http://lilypond.org/web/documentation > and it links to http://lsr.dsi.unimi.it/ ... and in the final GDP, there wi

Re: GDP: introducing examples

2007/10/19, Hans Aberg <[EMAIL PROTECTED]>: > On 19 Oct 2007, at 14:37, Mats Bengtsson wrote: > > > What you describe sounds like the LSR, which already now has free > > text search facilities (at least if you stay connected). > > So how do you find the LSR?... You have the link into the main docu

Re: GDP: where do we discuss MIDI?

On 19 Oct 2007, at 15:24, Mark Knoop wrote: On 19 Oct 2007, at 08:45, Graham Percival wrote: [1) Gather everything about MIDI into one section] It seems that this option is favored - and then one can just as well put the MIDI stuff in a separate manual. Um, by who? Sorry for the typo

Re: GDP: introducing examples

On 19 Oct 2007, at 14:37, Mats Bengtsson wrote: What you describe sounds like the LSR, which already now has free text search facilities (at least if you stay connected). So how do you find the LSR? If I search on , it translates to a Goole search site:www.lilypo

Re: Church Rests

2007/10/19, Trevor Daniels <[EMAIL PROTECTED]>: > > In the section on multi-measure rests the manual talks about > "church rests", meaning the use of increasing numbers of > little rectangles to indicate how many measures are included > in the multi-measure rest. In this a generally accepted > mus

Re: ReheasalMark in Staff context is broken - can someone verify this snippet is a bug?

The bug has already been reported, see http://code.google.com/p/lilypond/issues/detail?id=432 In your simple example, it helps to move also the Break_align_engraver from the Score to the Staff context, but I have no idea if such an operation will work well also for multi-stave scores or if somet

Church Rests

In the section on multi-measure rests the manual talks about "church rests", meaning the use of increasing numbers of little rectangles to indicate how many measures are included in the multi-measure rest. In this a generally accepted musical term, or one invented for lily? Or is there a better

Re: Markup with multi-measure rests

To me it seems a bug that you get collisions in your first example. The second example can easily be modified to get what you want. Just add \fatText before the first spacer note. /Mats Trevor Daniels wrote: In the following example of writing a typical part containing multi-measure rests, th

Markup with multi-measure rests

In the following example of writing a typical part containing multi-measure rests, the annotation of the rests in 2.11.34 collides if more notes are added to fill the line (to simulate this, I've added ragged-right = ##t). This seems to be a bug. The collisions can be avoided in 2.11 by attachin

Re: GDP: where do we discuss MIDI?

Hans Aberg wrote: > On 19 Oct 2007, at 08:45, Graham Percival wrote: > >> 2) Mention MIDI everywhere in the manual. > > It seems that this option is favored - and then one can just as well put > the MIDI stuff in a separate manual. Um, by who? -- Mark Knoop _

Re: GDP: introducing examples

What you describe sounds like the LSR, which already now has free text search facilities (at least if you stay connected). /Mats Hans Aberg wrote: On 19 Oct 2007, at 08:40, Graham Percival wrote: Currently we have a few different ways of introducing examples in the docs. Should we standard

Re: GDP: where do we discuss MIDI?

On 19 Oct 2007, at 08:45, Graham Percival wrote: 2) Mention MIDI everywhere in the manual. It seems that this option is favored - and then one can just as well put the MIDI stuff in a separate manual. Hans Åberg ___ lilypond-user mailing l

Re: GDP: introducing examples

On 19 Oct 2007, at 08:40, Graham Percival wrote: Currently we have a few different ways of introducing examples in the docs. Should we standardize on a particular way, or just let doc writers do whatever they want? I have the idea that there should be created a separate PDF doc with exam

Re: GDP: introducing examples

Graham Percival wrote: > Currently we have a few different ways of introducing examples in the > docs. Should we standardize on a particular way, or just let doc > writers do whatever they want? > > Currently we have a combination of four different ways. > > 1) The text just continues directly

Re: GDP: where do we discuss MIDI?

Trevor Daniels wrote: > Eyolf said: >> On 18.10.2007 (23:45), Graham Percival wrote: >> > There are two options to this: >> >> No, there's only one: >> >> > 1) Gather everything about MIDI into one >> section (currently 4.3) and >> > mention everything there >> > > I agree Absolutely. --

RE: pitches second draft

Graham wrote: > Trevor Daniels wrote: > > 2. At the bottom of Accidentals there is a > cryptic comment > > about microtones and MIDI. As neither micro > tones nor MIDI > > have been mentioned so far this seems misplaced. > > In the example immediately preceding that sentence: > > \set Staff

RE: GDP: where do we discuss MIDI?

Eyolf said: > On 18.10.2007 (23:45), Graham Percival wrote: > > There are two options to this: > > No, there's only one: > > > 1) Gather everything about MIDI into one > section (currently 4.3) and > > mention everything there > I agree Trevor _

Re: GDP: where do we discuss MIDI?

On 18.10.2007 (23:45), Graham Percival wrote: > There are two options to this: No, there's only one: > 1) Gather everything about MIDI into one section (currently 4.3) and > mention everything there :-) -- He who lives without folly is less wise than he believes. __

Re: GDP: where do we discuss MIDI?

Mats Bengtsson wrote: Graham Percival wrote: There are two options to this: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Currently LilyPond MIDI support includes Dynamicsyes Repeatsno, unless \unfoldRepeats is used Articulation

Re: GDP: where do we discuss MIDI?

Graham Percival wrote: There are two options to this: 1) Gather everything about MIDI into one section (currently 4.3) and mention everything there: Currently LilyPond MIDI support includes Dynamicsyes Repeatsno, unless \unfoldRepeats is used Articulationsno Textno,