Re: New articulation character for half-open hi-hats?
>> Perhaps I'm wrong, and the whole thing is a non-issue: ghostscript >> can compute the exact bounding box of an EPS file, AFAIK, taking >> care of the real dimensions of all glyphs (relying on the outlines >> instead of the metrics). > > I don't know what ghostscript can do, but even if it cannot compute > the bounding box by considering the real glyph dimensions, this > functionality could be simulated by enlarging the boundary of the > EPS file by a suitable "safety" margin and then calling pnmcrop > after the EPS file has been converted into an image. Yes, this sounds like a sensible solution to avoid issues with GhostScript. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: devel-chat mailing list
>> > I never realized un-archived mailing lists existed. :-) I would be >> > okay with either option. >> >> Although I'm pretty certain that we could make such a list on >> savannah, I was thinking about just doing it on lilynet. Presumably, a "list on savannah" is run using GNU Mailman, in which archiving is a choice (yes/no) on the "Archiving Options" tab. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improving the ROADMAP
John Mandereau wrote: > Where has gone the comment on the directory structure of a > translation? It's still needed in the new roadmap. Oops. How's this? | | TRANSLATED MANUALS: | | Each language's directory can contain... | | 1) translated versions of: | | * top sources for manuals | | * individual chapters for each manual | | 2) a texidocs/ directory for snippet translations | | | |-- de/ German | |-- es/ Spanish | |-- fr/ French | |-- hu/ Hungarian | |-- it/ Italian | |-- ja/ Japanese | |-- nl/ Dutch > I'm not wild about listing nl/ by the way, as it's a > purely technical trial rather than a translation. I would worry if you *were* wild about it! But if it's not a translation, then the directory should be removed or renamed to something like "test". Then we could file it under "MISCELLANEOUS DOC STUFF". As it stands, I thought it's presence might inadvertently inspire some future translator. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] CG Feedback
>Original Message >From: c_soren...@byu.edu >Date: 17/01/2010 1:19 >To: "pound...@lineone.net", "fr...@lilynet.net" , "lilypond-devel" >Subj: Re: [frogs] CG Feedback > > >I think that ./autogen.sh will automatically run configure, so that it's not >necessary to run ./configure after you do ./autogen.sh. > >If somebody else corrects me on this, I'll make the change to the CG. > I'm sure you're right - my problem was that the generic instructions for building were different from the instructions for building on a virtual machine and I couldn't understand why. It wasn't a major problem though. > >Thanks to all who have helped put it together! +1 - David 2009: A year in review - http://www.tiscali.co.uk/2009 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improving the ROADMAP
Le vendredi 15 janvier 2010 à 22:27 -0800, Mark Polesky a écrit : > ROADMAP has always confused me. I prefer something more > like the attached file. Hi Mark, thanks for you work work; I only have two nitpicks below to suggest. > | | TRANSLATED MANUALS: > | | > | |-- de/ German > | |-- es/ Spanish > | |-- fr/ French > | |-- hu/ Hungarian > | |-- it/ Italian > | |-- ja/ Japanese > | |-- nl/ Dutch Where has gone the comment on the directory structure of a translation? It's still needed in the new roadmap. I'm not wild about listing nl/ by the way, as it's a purely technical trial rather than a translation. Best, John signature.asc Description: Ceci est une partie de message numériquement signée ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: [frogs] CG Feedback
On 1/16/10 11:14 AM, "pound...@lineone.net" wrote: > Hi list. > > I thought I'd post a quick note of the issues I faced downloading and > building LilyPond. On the whole the experience was far less painful > that I thought it would be but I hope the following may be of use. I > would have posted this earlier, but I made the mistake of doing a 'make > check' and I've only just got my PC back again :) > > My main misunderstanding was to do with 'git add' and 'git commit' as > I had the impression that git commit only commits modifications and not > additions. The new section 2 of the CG is much clearer on this than > before, but I think the line in 2.3.4: > > "The -a is short for --all which includes modified and deleted files, > but not newly created files." > > would be better as: > > "The -a is short for --all which includes modified and deleted files, > but only newly created files which have been added with git add." Thanks for the suggestion. I've made the change in git. > or something to that effect. > > My next problem was not being sure how to look at the changes but this > has been addressed (git diff HEAD.) > > When building LilyPond I was confused that the general build > instructions (3.1.3) were different from the instructions for building > on a Virtual Machine (3.3), in particular that there is no ./configure > after the ./autogen.sh - in the end I assumed that it should have been > there and ran the configure script anyway. I think that ./autogen.sh will automatically run configure, so that it's not necessary to run ./configure after you do ./autogen.sh. If somebody else corrects me on this, I'll make the change to the CG. > Something went wrong with my > build as, although LilyPond and the docs all seemed fine, convert-ly > couldn't find a library. Unfortunately I have no idea what I did wrong > to cause this. Rebuilding from scratch fixed it. > > Everything else was quite pain free. I deliberately chose a more > difficult route to contributing a snippet than necessary but the > learning trip was useful to me and I hope the feedback can be of use to > someone else. Thanks for providing the test of our documentation. It's great to have you helping to make things better. And it's *wonderful* to have the Contributor's Guide to capture this knowledge that used to be buried in the -devel archives. Thanks to all who have helped put it together! Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: devel-chat mailing list
On Sat, Jan 16, 2010 at 04:15:22PM -0800, Patrick McCarty wrote: > On 2010-01-16, Graham Percival wrote: > > I'm thinking that an open mailing list with no archives would be > > ok, but we could make it closed instead if we wanted to feel a bit > > more private. > > I never realized un-archived mailing lists existed. :-) I would be > okay with either option. Although I'm pretty certain that we could make such a list on savannah, I was thinking about just doing it on lilynet. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: devel-chat mailing list
On 2010-01-16, Graham Percival wrote: > One idea that I've been considering for over a year is making a > "social" mailing list for lilypond developers. Not for discussing > bugs or new features; just to get to know each other better. > Think of it as the electronic equivalent of office-mates going to > the pub together on a Thursday night. I could tell stories about > being a PhD student in a foreign country, or having lunch with an > exotic dancer who studies medieval string instruments, etc. Other > people could talk about amateur theatre, or complain about > university administration, or whatever takes their fancy. Interesting! > Is there any interest in this? Sure! > I'm thinking that an open mailing list with no archives would be > ok, but we could make it closed instead if we wanted to feel a bit > more private. I never realized un-archived mailing lists existed. :-) I would be okay with either option. Thanks, Patrick ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
devel-chat mailing list
One idea that I've been considering for over a year is making a "social" mailing list for lilypond developers. Not for discussing bugs or new features; just to get to know each other better. Think of it as the electronic equivalent of office-mates going to the pub together on a Thursday night. I could tell stories about being a PhD student in a foreign country, or having lunch with an exotic dancer who studies medieval string instruments, etc. Other people could talk about amateur theatre, or complain about university administration, or whatever takes their fancy. Is there any interest in this? I'm thinking that an open mailing list with no archives would be ok, but we could make it closed instead if we wanted to feel a bit more private. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
[PATCH] Fix issues with episema formatting (Issue #189/comments in docs)
Hi everybody, This patch allows an episema to be typset over a single neume (issue #189) and ensures it can be positioned correctly inside the stave. Since the requirements of an episema are slightly different from standard TextSpanner grobs, I've decided to create a new engraver for this purpose: this ensures simultaneous events (i.e., start- and stop-spans on a single neume) aren't junked, and allows the correct positioning by adding the acknowledged NoteHead grobs as 'side-support-elements and setting 'quantize-position. Please review: http://codereview.appspot.com/186189/show Thanks, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: the name "lily-git"
On 16.01.2010, at 18:04, Graham Percival wrote: On Sat, Jan 16, 2010 at 4:59 PM, Mark Polesky wrote: A while back I proposed the name "lilypatch" for what is now "lily-git". I didn't hear any response so I suppose that most of you prefer the current name. I thought I'd mention it once more though, because I like the pun on the word "patch". But I'll drop it if no one cares. Err, what's the pun? We had a whole bunch (10+) of suggestions for the name; in the end,Carl and I liked "lily-git" the best. I'm not overly eager to change it now, but I'm still interested in this pun. Cheers, - Graham Just a guess here, but instead of "pond' of lilies, it would be a "patch" (as in a patch of ground" of lilies. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
2010/1/16 Mark Polesky : > http://kainhofer.com/~lilypond/Documentation/changes/index.html This always happens with font changes on kainhofer.com since it doesn't do a clean docs build every day. Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: the name "lily-git"
Graham Percival wrote: > Err, what's the pun? 1) a patch of lilies, as in http://www.thelilypatch.org/ 2) a git patch for LilyPond - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: the name "lily-git"
On Sat, Jan 16, 2010 at 4:59 PM, Mark Polesky wrote: > A while back I proposed the name "lilypatch" for what is now > "lily-git". I didn't hear any response so I suppose that > most of you prefer the current name. I thought I'd mention > it once more though, because I like the pun on the word > "patch". But I'll drop it if no one cares. Err, what's the pun? We had a whole bunch (10+) of suggestions for the name; in the end,Carl and I liked "lily-git" the best. I'm not overly eager to change it now, but I'm still interested in this pun. Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
Neil Puttock wrote: >> The example on the "changes" page is not displaying >> properly. > > Where? http://kainhofer.com/~lilypond/Documentation/changes/index.html ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
the name "lily-git"
A while back I proposed the name "lilypatch" for what is now "lily-git". I didn't hear any response so I suppose that most of you prefer the current name. I thought I'd mention it once more though, because I like the pun on the word "patch". But I'll drop it if no one cares. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
Looks fine to me: http://lilypond.org/doc/v2.13/Documentation/changes (hint: since this changed something in mf/, you need to do a make doc-clean, make clean, why not make distclean, and then rebuild everything from scratch. Yes, this is already in the issue tracker) Cheers, - Graham On Sat, Jan 16, 2010 at 4:39 PM, Mark Polesky wrote: > Neil Puttock wrote: >> LGTM, pushed to master. >> >> I've just made one minor change: new features go at the >> top of changes.tely. > > The example on the "changes" page is not displaying > properly. > > - Mark > > > > > > ___ > bug-lilypond mailing list > bug-lilyp...@gnu.org > http://lists.gnu.org/mailman/listinfo/bug-lilypond > ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
2010/1/16 Mark Polesky : > The example on the "changes" page is not displaying > properly. Where? Looks fine here: http://lilypond.org/doc/v2.13/Documentation/changes/index#top Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New articulation character for half-open hi-hats?
Neil Puttock wrote: > LGTM, pushed to master. > > I've just made one minor change: new features go at the > top of changes.tely. The example on the "changes" page is not displaying properly. - Mark ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Getting string events from the music stream
On 1/16/10 7:47 AM, "Neil Puttock" wrote: > 2010/1/16 Carl Sorensen : > >> Now if we didn't find an articulation on the note event, we search through >> the list of tabstring events to find a non-empty tabstring event. Why are >> we doing this second check? Is there another way to get a tabstring event >> besides adding a string as an articulation to a note? Is this code >> redundant, like I think it is? > > No. If you removed it, then string numbers set outside chords would be > ignored. Ah, thank you. So inside chords, strings are set as articulations (which is why fretboards uses them; fretboards deals with chords); outside chords, strings are set as string_events. As you can see, I missed this subtlety. I'll add some comments to the code about this. Thanks! Carl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Getting string events from the music stream
2010/1/16 Carl Sorensen : > Now if we didn't find an articulation on the note event, we search through > the list of tabstring events to find a non-empty tabstring event. Why are > we doing this second check? Is there another way to get a tabstring event > besides adding a string as an articulation to a note? Is this code > redundant, like I think it is? No. If you removed it, then string numbers set outside chords would be ignored. > Actually, it seems to me to be wrong, > because it loses the registration with the note event, because nothing makes > i stay the same as j. I don't think it needs to; since the events are mapped to the note events in order, unless a string number articulation gets in the way, the first note gets the first string number. \1\2\3 -> c\1 e\2 g\3 The following is the exception, but I can't imagine many users mixing up string numbers this way: \2\3 or \1\3 -> c\1 e\2 g\3 Cheers, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improving the ROADMAP
LTGM although I'd put input/ under REGRESSION TESTING, and elisp/ + vim/ under MISC, or something like that. But it's definitely an improvement over the current file. Please push. Cheers, - Graham On Fri, Jan 15, 2010 at 10:27:42PM -0800, Mark Polesky wrote: > ROADMAP has always confused me. I prefer something more > like the attached file. > > Comments? > - Mark > > > > Prebuilt Documentation and packages are available from: > > http://www.lilypond.org > > LilyPond development is hosted at: > > http://savannah.gnu.org/projects/lilypond > > Here is a simple explanation of the directory layout for > LilyPond's source files. > > > .Toplevel READMEs, ChangeLog, > | build bootstrapping, patches > | for third party programs > | > |-- Documentation/ Top sources for manuals > | | > | | > | | INDIVIDUAL CHAPTERS FOR EACH MANUAL: > | | > | |-- contributor/ Contributor's Guide > | |-- essay/ Essay on automated music engraving > | |-- extending/ Extending > | |-- learning/Learning Manual > | |-- notation/Notation Reference > | |-- usage/ Usage > | |-- web/ The website > | | `-- ly-examples/ .ly files for the "Examples" page > | | > | | > | | TRANSLATED MANUALS: > | | > | |-- de/ German > | |-- es/ Spanish > | |-- fr/ French > | |-- hu/ Hungarian > | |-- it/ Italian > | |-- ja/ Japanese > | |-- nl/ Dutch > | | > | | > | | MISCELLANEOUS DOC STUFF: > | | > | |-- css/ CSS files for HTML docs > | |-- included/.ly files used in the manuals > | |-- logo/Web logo and "note" icon > | |-- misc/Old announcements, ChangeLogs and NEWS > | |-- pictures/Images used (eps/jpg/png/svg) > | | `-- pdf/ (pdf) > | |-- po/ Translated build/maintenance scripts > | |-- snippets/Auto-generated .ly snippets (from the LSR) > | | `-- new/ Snippets too new for the LSR > | `-- topdocs/ AUTHORS, INSTALL, README > | > | > | C++ SOURCES: > | > |-- flower/ A simple C++ library > |-- lily/C++ sources for the LilyPond binary > | > | > | LIBRARIES: > | > |-- elisp/ Emacs LilyPond mode and syntax coloring > |-- ly/ .ly \include files > |-- mf/ MetaFont sources for Emmentaler and Aybabtu fonts > |-- ps/ PostScript library files > |-- scm/ Scheme sources for LilyPond and subroutine files > |-- tex/ TeX and texinfo library files > |-- vim/ Vi(M) LilyPond mode and syntax coloring > | > | > | SCRIPTS: > | > |-- python/ Python modules, MIDI module > | `-- auxiliar/Python modules for build/maintenance > |-- scripts/ End-user scripts (--> lilypond/usr/bin/) > | |-- auxiliar/Maintenance and non-essential build scripts > | `-- build/ Essential build scripts > | > | > | BUILD PROCESS: > | (also see SCRIPTS section above) > | > |-- make/Specific make subroutine files > |-- stepmake/Generic make subroutine files > | > | > | MISCELLANEOUS: > | > |-- input/ Regression tests > | `-- regression/ .ly regression tests > | |-- abc2ly/ .abc regression tests > | `-- musicxml/.xml and .itexi regression tests > `-- po/ Translations for binaries and end-user scripts > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
> Here's a file with all different spacings from 2.0 to 4.0... Thanks again. I like 2.5 most. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
Reinhold Kainhofer wrote:
Here's a file with all different spacings from 2.0 to 4.0...
Looking at some scores with two lyrics lines (mostly oratorios with two
different language), I would tend to choose 2.8 or 3.0.
+1.
There are some other issues I notice with the layout:
1) For my taste the piece names are too close to the previous score (and too
far away from the one they are attached to).
+1.
2) The distance between the last lyrics line to the next staff is not constant
throughout the page!
It's not a bug, it's a feature. At least I think so - it's because of
the default 'staff-affinity to the top staff. See the attached file
with 'staff-affinity = #CENTER. You won't change the 'minimum-distance
for each system in a real-world example, so IMHO it'd be a very minor
problem, anyway.
Still, the lyrics have a larger subjective whitespace distance to the
staff below than the one above, probably due to the spacing based on the
baseline.
\version "2.13.11"
\pointAndClickOff
\paper { ragged-last-bottom = ##f }
lyr = \lyricmode {
These are just some ran -- dom __ _ _ ly -- rics, these are just some ran -- _ _ dom ly -- rics!
}
cs = \new ChoirStaff <<
\new Staff { \new Voice ="1" \relative c'' { \repeat unfold 5 { c4 c c c } } }
\new Lyrics \with { \override VerticalAxisGroup #'staff-affinity = #CENTER } \lyricsto "1" \lyr
\new Lyrics \with { \override VerticalAxisGroup #'staff-affinity = #CENTER } \lyricsto "1" \lyr
\new Lyrics \with { \override VerticalAxisGroup #'staff-affinity = #CENTER } \lyricsto "1" \lyr
\new Staff { \new Voice ="2" \relative c' {\clef "bass" \repeat unfold 5 { c2 c } } }
\new Lyrics \lyricsto "2" \lyr
\new Lyrics \lyricsto "2" \lyr
>>
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.0
}
}
\header { piece = "Lyrics minimum-distance = 2.0" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.25
}
}
\header { piece = "Lyrics minimum-distance = 2.25" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.5
}
}
\header { piece = "Lyrics minimum-distance = 2.5" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.8
}
}
\header { piece = "Lyrics minimum-distance = 2.8" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.0
}
}
\header { piece = "Lyrics minimum-distance = 3.0" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.2
}
}
\header { piece = "Lyrics minimum-distance = 3.2" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.5
}
}
\header { piece = "Lyrics minimum-distance = 3.5" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.7
}
}
\header { piece = "Lyrics minimum-distance = 3.7" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #4.0
}
}
\header { piece = "Lyrics minimum-distance = 4.0" }
}
lyrics_spacing.pdf
Description: Adobe PDF document
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
Reinhold Kainhofer wrote Saturday, January 16, 2010 11:32 AM Here's a file with all different spacings from 2.0 to 4.0... Looking at some scores with two lyrics lines (mostly oratorios with two different language), I would tend to choose 2.8 or 3.0. 2.8 looks good to me. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
Am Samstag, 16. Januar 2010 08:56:43 schrieben Sie:
> >> #'minimum-distance = #3.2
> >
> > ... and for everyone who is just as lazy as I am: Attached is a
> > sample file so that you don't have to try to create a minimal
> > example yourself...
>
> Thanks. IMHO the distance between lyrics lines is slightly too big.
Here's a file with all different spacings from 2.0 to 4.0...
Looking at some scores with two lyrics lines (mostly oratorios with two
different language), I would tend to choose 2.8 or 3.0.
There are some other issues I notice with the layout:
1) For my taste the piece names are too close to the previous score (and too
far away from the one they are attached to).
2) The distance between the last lyrics line to the next staff is not constant
throughout the page! It seems largest at the top of the page and decreases
towards the end of the page. I don't think this has to do with the minimum-
distance, as also the distance of the lyrics to the staff above decreases,
althouth not as much.
3) The distance between the last lyrics and the tagline is way too small...
Cheers,
Reinhold
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
\version "2.13.11"
\pointAndClickOff
\paper { ragged-last-bottom = ##f }
lyr = \lyricmode {
These are just some ran -- dom __ _ _ ly -- rics, these are just some ran -- _ _ dom ly -- rics!
}
cs = \new ChoirStaff <<
\new Staff { \new Voice ="1" \relative c'' { \repeat unfold 5 { c4 c c c } } }
\new Lyrics \lyricsto "1" \lyr
\new Lyrics \lyricsto "1" \lyr
\new Lyrics \lyricsto "1" \lyr
\new Staff { \new Voice ="2" \relative c' {\clef "bass" \repeat unfold 5 { c2 c } } }
\new Lyrics \lyricsto "2" \lyr
\new Lyrics \lyricsto "2" \lyr
>>
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.0
}
}
\header { piece = "Lyrics minimum-distance = 2.0" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.25
}
}
\header { piece = "Lyrics minimum-distance = 2.25" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.5
}
}
\header { piece = "Lyrics minimum-distance = 2.5" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #2.8
}
}
\header { piece = "Lyrics minimum-distance = 2.8" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.0
}
}
\header { piece = "Lyrics minimum-distance = 3.0" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.2
}
}
\header { piece = "Lyrics minimum-distance = 3.2" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.5
}
}
\header { piece = "Lyrics minimum-distance = 3.5" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #3.7
}
}
\header { piece = "Lyrics minimum-distance = 3.7" }
}
\score {
\cs
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing #'minimum-distance = #4.0
}
}
\header { piece = "Lyrics minimum-distance = 4.0" }
}
lyrics_spacing.pdf
Description: Adobe PDF document
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
Reinhold Kainhofer wrote Friday, January 15, 2010 11:01 PM
Am Freitag, 15. Januar 2010 18:24:55 schrieb Joe Neeman:
On Fri, 2010-01-15 at 18:08 +0100, Reinhold Kainhofer wrote:
> If you can send us an example of what it looks like (so that we
> don't
> have to guess which settings you will set exactly), it would be
> much
> easier to complain ;-)
Just add
\layout {
\context {
\Lyrics
\override VerticalAxisGroup #'inter-loose-line-spacing
#'minimum-distance = #3.2
}
}
to your favourite score with multiple adjacent lyric lines.
... and for everyone who is just as lazy as I am: Attached is a
sample file so
that you don't have to try to create a minimal example yourself...
Thanks Reinhold - very helpful!
What jumps into my eye is that the lyrics are way too close to the
notes of
the upper staff and too far from the staff below
Agreed, and I'd prefer the spacing between the lyric lines to be
slightly smaller too.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: (bug?) irregular lyrics distance in 2.13.10
>> #'minimum-distance = #3.2 > ... and for everyone who is just as lazy as I am: Attached is a > sample file so that you don't have to try to create a minimal > example yourself... Thanks. IMHO the distance between lyrics lines is slightly too big. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
