Re: Reorganizing the contents of the \paper block
On 2/7/07, Cameron Horsburgh <[EMAIL PROTECTED]> wrote:
> [Sidenote: if this proposal to collapse \paper and \alyout does make
> sense, then we'll have to decide what to do with the fact that there's
> a second, equally important use for \layout blocks, which is the
> overriding of context attributes ... which is a wholly separate thing
> from making the different settings talked about in this thread, as
> described in 9.2.6. This sort of thing:
>
> \layout {
> ...
> \context {
>\Staff
>
>\set fontSize = #-2
>\override Stem #'thickness = #4.0
>\remove "Time_signature_engraver"
> }
> }
>
\layout has another function, although it may be a special case of one
of its other uses. If a \score block contains a \midi block the
\layout block is needed if PDF output is also desired.
Ah right. I remember that coming up a while back.
OK, duly noted. If there's support for the layout + paper -> settings
proposal, then we'll have to find a way to tell lily to produce a PDF
even when there's no \settings block. Sounds like a good candidate for
a commandline switch.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
> [Sidenote: if this proposal to collapse \paper and \alyout does make
> sense, then we'll have to decide what to do with the fact that there's
> a second, equally important use for \layout blocks, which is the
> overriding of context attributes ... which is a wholly separate thing
> from making the different settings talked about in this thread, as
> described in 9.2.6. This sort of thing:
>
> \layout {
> ...
> \context {
>\Staff
>
>\set fontSize = #-2
>\override Stem #'thickness = #4.0
>\remove "Time_signature_engraver"
> }
> }
>
\layout has another function, although it may be a special case of one
of its other uses. If a \score block contains a \midi block the
\layout block is needed if PDF output is also desired.
--
=
Cameron Horsburgh
=
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Occasional lyrics attached to another voice
Hey, list,
I have a question about fitting lyrics. In the file I've pasted below this
message is the hymn I am arranging for Barbershop chorus. The final stanza
has all the four parts singing separately, as you can see. But there are
occasional spots, as in stanza 1 where some parts will repeat a lyric. If
you compile this file, you will see on the PDF that the \markup words I put
in there follow the notes, rather than being in a nice line. Can someone
suggest how to do this most conveniently? Each of the *other* three parts
(tenor, baritone, bass) might have bits of this in certain spots.
Windoze XP Pro, LilyPond 2.11.14, jEdit 4.4pre9 with LilyPondTool
Blessings,
Father Gordon Gilbert+
--
Fr. Gordon Gilbert
Penetanguishene, ON
\header {
filename = "AmazingGrace-Sweet-Ads.ly"
enteredby = "Gordon Gilbert"
composer = "Traditional American Melody"
poet = "words: Rev'd John Newton, 1779"
arranger = "arr. Gordon Gilbert 2007"
date=""
title = "Amazing Grace"
subtitle = "Arr. for Barbershop Chorus"
metre = ""
meter = \metre
copyright = "Public Domain - Permission granted to perform this
arrangement in a not-for-profit setting"
style = "Hymn"
mutopiacomposer = \composer
mutopiapoet=\poet
maintainer = ""
maintainerEmail = ""
lastupdated = "2007/02/04"
}
\version "2.11.14"
\paper{
#(set-paper-size "letter")
}
global= {
\time 3/4
\key g \major
}
tenor = \context Voice = "tenor" \relative c' {
\voiceOne
%\override NoteHead #'color = #grey
%\override Stem #'color = #grey
%\override Beam #'color = #grey {
\partial 4 d4
b'2 d8 b d2 dis4 e2 c4 b2
a4 b2 d4 e2 e4 fis2 e4 ^\markup {"like"} d4( ^\markup {"me"} c)
b4 b2 d4 d2 b4 c4.( e8 e c) b2
a4 b2 d4 d cis c b4( d) c4 ^ \markup {"I"} b2 ^ \markup {"see"}
d,4
b'2 \times 2/3 {d8( c b)} d2 dis4 e2 c4 b2
a4 b2 \times 2/3 {d8( c b)} e2 e4 fis2 e4 d2
d4 b2 d4 d2 b4 c2 a4 b2
a4 b2 d4 d cis c b2 c4 b2
d,4
b'2 d4 d2 dis4 e2 c4 b2
a4 b2 d4 e2 e4 fis2 e4 d2
d4 b2 d4 d2 b4 c4.( e8 e c) b2
a4 b2 d4 d cis c b2.
r2. r r r
\new Voice = tenorDivisi { \voiceOne
\transpose g b' {
r4 r b4 b r4 r d'4 d'4 dis' e'2. c'4 b2. r4
% }
}}
}
lead=\context Voice = "lead" \relative c' {
\voiceTwo
\override NoteHead #'color = #red
\override Stem #'color = #red
\override Beam #'color = #red {
\partial 4 d4
g2 b8( g) b2 a4 g2 e4 d2
d4 g2 b8( g) b2 a4 d2. ~ d2
b4 d4.^ "x"( b8) d( b) g2 d4 e4.( g8) g( e) d2
d4 g2 b8( g) b2 a4 g2 ( fis4 g2)
%verse 2
d4
g2 \times 2/3 {b8( a g)} b2 a4 g2 e4 d2
d4 g2 \times 2/3 {b8( a g)} b2 a8.( b16) d2. ~ d2
b4 d2 \times 2/3 {b8( a g)} b2 b8.( a16) g2 e8.( d16) d2
d4 g2 \times 2/3 {b8( a g)} b2 a4 g2. ~ g2
%verse 3
d4
g2 b8( g) b2 a4 g2 e4 d2
d4 g2 b8( g) b2 a4 d2. ~ d2
b4 d4.^ "x"( b8) d( b) g2 d4 e4.( g8) g( e) d2
d4 g2 b8( g) b2 a4 g2.
%bridge
a ^ \markup \italic {"Bridge"} g g f2
%verse 4
\key b \major
\transpose g b' {
d4 \time 4/4
g2. b8( g) b2. a4 g2. e4 d2.
d4 g2. b8( g) b2. a4 d'1 ~ d'2.
b4 d'2 ~ d'8( b8) d'( b) g2. d4 e2 ~ e8 ( g8) g( e) d2.
d4 g2. b8( g) b2. a4 g1 ~ g2.
g4 ^ \markup \italic {"Tag"}
a ^ \fermata b ^ \fermata c' ^ \fermata
r8 ^ \fermata d'8 d'1 ~ d' ^ \fermata
}
\bar "||"
}
}
bari = \context Voice = "bari" \relative c' {
\voiceOne
\partial 4 d,4
g2 g4 g2 fis4 g2 a4 g2
a4 b2 b4 cis2 a4 d2 a4 ^ \markup {"like"} a2 ^ \markup {"me"}
g4 g2 g4 d2 g4 c2 a4 g2
a4 b2 g4 fis4. g8 fis4 g4( b) a ^ \markup {"I"} g2 ^ \markup {"see"}
d4
g2 g4 d'2 b4 c2 a4 g2
a4 b2 b4 a2 a4 d2 a4 a2
g4 b2 b4 d2 b4 c2 a4 g2
a4 b2 g4 fis4. e8 fis4 g2. ~ g2
d4
f2 ^ \markup \italic {"Bluesy - Baris, go for the 7ths!"} f4 c'2 b4 bes2
bes4 g2
a4 b2 b4 g2 g4 d2 a'4 a2
g4 g2 g4 d2 b'4 c2 a4 g2
a4 b2 g4 fis4. e8 fis4 g2.
r2. r r r
\new Voice = bariDivisi { \voiceOne
\transpose g b' {
r4 r d d r r g, g,
}
}}
bass = \context Voice = "bass" \relative c {
\voiceTwo
\partial 4 d4
g,2 b4 d2 b4 c2 e4 g2
fis4 e2 e4 a2 cis,4 d2 e4 fis( e) d
b2 d4 g,2 d'4 c2 e4 g2
fis4 e2 e4 d e fis g2 d4 _ \markup {"I"} g,2 _ \markup {"see"}
d'4
b2 d4 g2 d4 c2 e4 g2
fis4 e2 e4 a,2 c4 b2.( a2) d4
g2 g4 b2 b4 c2 a4 g4( g)
fis4 e2 e4 d e fis g2 d4 g2
d4
g,2 b4 d2 b4 c2 e4 f2
fis4 e2 e4 a,2 cis4 d2( e4 fis d) d
b2 d4 g,2 b4 c2 e4 g2
fis4 e2 e4 d e fis g2.
g2. c, b' fis2
\key b \major
\new Voice = bassDivisi { \voiceTwo
\transpose g b {
d4
g2. b4 d2. b,4 c2. e4 g2.
fis4 e2. e4 a,2. cis4 d2.( e4 fis2 d4) d
b,2. d4 g,2. b,4 c2. e4 g2.
fis4 e2. e4 d2( e4) fis g2.( c4 g,2.)
g4 c b, a, r8 g, g,1 ~ g,
}
}}
accomp=\chordmode {
r4 g2 g4:/b g2:/d b4:7 c2 c4:6/e g2
d4:/fis e2.:m a2:9 a4:/cis d2. d2.:7
}
stanzaa = \lyricmode {
\set stanza = "1."
A -- ma -- zing Grace, how s
Re: Reorganizing the contents of the \paper block
On Wed, 7 Feb 2007 17:52:54 -0600, Trevor Bača wrote: > ... But maybe this logical, user-centric division can be > handled perfectly cleanly just in the docs? The docs for settings can > then look something like this (and this is obviously just a sketch, > some pseudocode for the actual docs that I'll clean up long before > sending to Graham): > > "LilyPond supports 47 different different page layout and setup > settings. These settings divide into 5 different functional areas. > These five functional areas are: > > * page dimensions > * page margins > * headers and footers > * the layout of systems > * the location of line- and page-breaks > > In addition, LilyPond input files support three different places where > these different settings can be made. These three levels where > settings can be made are: > > * score level > * book level > * top level > > Some settings can be made only at score level and book level. Other > settings can be made at all three levels. In the detailed descriptions > that follow, we note whether a setting can be set at 2 or 3 levels. > > < insert descriptions of all settings here, according to the five > functional areas given above >." > > > So how does this sound? This type of plan makes good sense to me. This non-programmer user can see how it works, and I would be happy to use and explain it. I hope it's workable from the Lilypond internal code point of view. David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Bryan Stanbridge <[EMAIL PROTECTED]> wrote: David Rogers wrote: > The correct answer is (I believe) exactly as you proposed earlier. Talking about Lilypond's internal logic is IMHO counterproductive. In fact, internally, I suspect Lilypond should stay the same - it just needs to allow the user to use it effectively by making (or even just *allowing*) the logical separation between paper, headers, and music, which you already outlined. It would be great if we could also leave the current mechanism in place if we do such a change. The system made sense to me from the beginning and I'd prefer to think in terms of scope (I have a strong programming background). I don't oppose a division on its merits, but it would be nice if the format would stay the same. Right. The scoping mechanism is actually fantastic. So what do you think about the collapsing of \paper and \layout into \settings which is then a *pure* representation of the scope at which the variable sets? [Side question: had you realized that there were actually *three* levels of scope (at least in input files) rather than two? I certainly didn't. But I never use \book explicitly ...] -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, David Rogers <[EMAIL PROTECTED]> wrote:
On Wed, 7 Feb 2007 16:45:26 -0600, Trevor Bača wrote:
> And now I see why Han-Wen keeps inviting a name change of the \paper
> and \layout buckets (while implicitly discouraging the moving around
> of settings between those two buckets): the buckets show the *scope*
> of the different settings, which isn't really an attribute that can be
> easily changed.
>
> OK. I get it. Now I see why the task is a renaming task rather than a
> moving-around task.
>
> Hm ... more thinking ...
The way this is typed in an input file has to make sense to the user. The user
should not be required to think like a computer. It has taken you, an obvious
expert, months and months to get his head around this. I never got it at all
until you explained it.
The correct answer is (I believe) exactly as you proposed earlier. Talking
about Lilypond's internal logic is IMHO counterproductive. In fact, internally,
I suspect Lilypond should stay the same - it just needs to allow the user to
use it effectively by making (or even just *allowing*) the logical separation
between paper, headers, and music, which you already outlined.
Hi David, hi list,
I'm *definitely* in favor of clarifying the daylights out of what's
going on here with the different settings. They're *so* powerful but
very much in need of doc clarification.
However, I really do think we can have our cake (clear delineation of
functionality in a user-centric way that fits the problem domain of
engraving score) and eat it too (preserve the CSS-style overrides of
settings that Han-Wen has been explaining).
(BTW, the reason I've been cluttering up everyone's inbox here with so
much of this is that I've given myself the task of rewriting both the
vertical spacing docs in chapter 11 and also the proportional spacing
stuff, too. And, as it turns out, those things both hinge crucially on
two concepts -- the settings that started this thread, and also line-
and page-breaking. So this is all part of peeling back the onion to
hopefully get a good an even more accurate set of docs for vertical
and horizontal spacing.)
So how to have our cake and eat it too?
What if we start (and hear me out here because I know it sounds weird)
with abolishing the distinction between \paper and \layout altogether.
Just forget they ever existed. And let's instead create a generic
\settings block where we can make any of the 30 or 40 settings that
currently live today in either \paper or \layout. Oh, and we'll allow
ourselves to instantiate a \settings block at any of the three lexical
levels of scope allowed for in an .ly file -- at score-level, at
book-level, and at top-level:
%%% BEGIN GENERIC SETTINGS BLOCK %%%
\settings { } % these are top-level settings
\book {
\settings { } % these are book-level settings
\score {
\new Staff { c'4 }
\settings { } % these are score-level settings
}
}
%%% END %%%
Now with this structure it's at least 100% clear how the three
different possible \settings blocks all interact with each other:
1. lily first checks for a value at score-level; if found, use that
value, otherwise ...
2. check for the value at book-level; if found, use that value, otherwise ...
3. check for the value at top-level; if found, use that value,
otherwise use the system default value.
Pefectly clean, perfectly clear. And the term \settings doesn't
confuse anyone by making us wonder how it is that the different
settings can relate to each other. They're just settings. Big bags of
settings. Some deal with padding between systems, some deal with the
text used to render the composer's name.
But what about the (semantic) grouping that I started this thread
with? Doesn't it still make sense to group, for example, these ...
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
... settings together somehow? I mean, these things actually do
pertain to each other at a logical level, right?
Yes, definitely. But maybe this logical, user-centric division can be
handled perfectly cleanly just in the docs? The docs for settings can
then look something like this (and this is obviously just a sketch,
some pseudocode for the actual docs that I'll clean up long before
sending to Graham):
"LilyPond supports 47 different different page layout and setup
settings. These settings divide into 5 different functional areas.
These five functional areas are:
* page dimensions
* page margins
* headers and footers
* the layout of systems
* the location of line- and page-breaks
In addition, LilyPond input files support three different places where
these different settings can be made. These three levels where
settings can be made are:
* score level
* book level
* top level
Some settings can be made only at score level and book level. Other
settings can be made at all three levels. In the detailed descriptions
that follow, we note whether a setting can be set at 2 or
Re: Reorganizing the contents of the \paper block
David Rogers wrote: The correct answer is (I believe) exactly as you proposed earlier. Talking about Lilypond's internal logic is IMHO counterproductive. In fact, internally, I suspect Lilypond should stay the same - it just needs to allow the user to use it effectively by making (or even just *allowing*) the logical separation between paper, headers, and music, which you already outlined. It would be great if we could also leave the current mechanism in place if we do such a change. The system made sense to me from the beginning and I'd prefer to think in terms of scope (I have a strong programming background). I don't oppose a division on its merits, but it would be nice if the format would stay the same. Cheers, Bryan... ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On Wed, 7 Feb 2007 16:45:26 -0600, Trevor Bača wrote: > And now I see why Han-Wen keeps inviting a name change of the \paper > and \layout buckets (while implicitly discouraging the moving around > of settings between those two buckets): the buckets show the *scope* > of the different settings, which isn't really an attribute that can be > easily changed. > > OK. I get it. Now I see why the task is a renaming task rather than a > moving-around task. > > Hm ... more thinking ... The way this is typed in an input file has to make sense to the user. The user should not be required to think like a computer. It has taken you, an obvious expert, months and months to get his head around this. I never got it at all until you explained it. The correct answer is (I believe) exactly as you proposed earlier. Talking about Lilypond's internal logic is IMHO counterproductive. In fact, internally, I suspect Lilypond should stay the same - it just needs to allow the user to use it effectively by making (or even just *allowing*) the logical separation between paper, headers, and music, which you already outlined. David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Reorganizing the contents of the \paper block
My suggestion:
\paper {}
paper-width
paper-height
top-margin
bottom-margin
left-margin
\page-layout{}
first-page-number
print-first-page-number
print-page-number
auto-first-page-number
head-separation
foot-separation
printallheaders
after-title-space
before-title-space
between-title-space
blank-page-force
blank-last-page-force
\music-layout{} or \system-layout{}
indent
line-width
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
page-spacing-weight
ragged-right
ragged-last
systemSeparatorMarkup (should be changed to system-separator-markup?)
Carl Sorensen
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On Wed, 07 Feb 2007 14:17:36 -0800, Graham Percival wrote: > David Rogers wrote: >> I propose: >> >> \papersize (for only the actual paper-related items) >> \systemlayout (for Trevor's list 1) >> \headerlayout (for Trevor's list 2) > > I second this proposal, although they should probably be > \paperSize > \systemLayout > \headerLayout > > or > \paper-size > \system-layout > \header-layout Good point Graham. I didn't think about that. Of course this should use hyphens or internal capitals, whichever fits in best. The way this is implemented now is inherently confusing. Re-naming the old \paper and \layout will not really take care of it. David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Trevor Bača escreveu:
> Right now both list 1 and list 2 will just be put together into the
> outside-of-score (\paper) bucket.
>
> But it seems that may list 1 is really concerned with the *the layout
> of music on the page* whereas list 2 is concerned with *adding headers
> and footers outside the music*.
>
> So does it make sense to divide list 1 and list 2? And if so, with what
> names?
I think this doesn't make sense. There are two output-def objects with nested
scope. Variables that by their nature have \book-wide effect, go into the outer
scope, variables that are score-wide may be put in the inner scope.
If that confuses you, it might be a better idea to rename \layout and \paper to
better reflect this.
Another point of clarification:
So this means there are really three levels of scope at which these
settings can be made ...
1. at score level (which is most specific)
2. at book level (which is intermediate), and
3. at top level
... as reflected in the following example:
%%% BEGIN 3-LEVELS OF SCOPE %%%
\version "2.11.16"
\paper { indent = #100 }
\book {
\paper { indent = #50 }
\score {
\new Staff { c'1 }
\layout { indent = #0 }
}
}
%%% END %%%
If I comment out the score-level indent, then the book-level indent
will take over. If I comment out both the score-level and book-level
indents, then the top-level indent will take over.
Of course we're almost completely unaware of this most of the time
since probably no one ever explicitly instantiates \books.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Reorganizing the contents of the \paper block
I like this suggestion also, though I prefer Graham's second set of names. Stephen -Original Message- From: [EMAIL PROTECTED] on behalf of Graham Percival Sent: Wed 2/7/2007 4:17 PM To: David Rogers Cc: lilypond-devel; lilypond-user Subject: Re: Reorganizing the contents of the \paper block David Rogers wrote: > I propose: > > \papersize (for only the actual paper-related items) > \systemlayout (for Trevor's list 1) > \headerlayout (for Trevor's list 2) I second this proposal, although they should probably be \paperSize \systemLayout \headerLayout or \paper-size \system-layout \header-layout Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user 2007-02-07, 16:32:10 The information contained in this e-mail message and any attachments may be privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this e-mail and delete the message and any attachments from your computer. 2007-02-07, 17:00:17 The information contained in this e-mail message and any attachments may be privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this e-mail and delete the message and any attachments from your computer.___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Trevor Bača escreveu: > Right now both list 1 and list 2 will just be put together into the > outside-of-score (\paper) bucket. > > But it seems that may list 1 is really concerned with the *the layout > of music on the page* whereas list 2 is concerned with *adding headers > and footers outside the music*. > > So does it make sense to divide list 1 and list 2? And if so, with what > names? I think this doesn't make sense. There are two output-def objects with nested scope. Variables that by their nature have \book-wide effect, go into the outer scope, variables that are score-wide may be put in the inner scope. If that confuses you, it might be a better idea to rename \layout and \paper to better reflect this. OK. I think I finally see what's going on and what's been confusing me for months. Let me see if I can get it into words: What's really going in the current implementation is that there are a whole bunch of different settings. The settings have names like ragged-right, indent, left-margin, between-system-space, and so on. There are probably 30 or 40 or more of these settings. And all 30 or 40 settings divide into one of two classes: CLASS I. Class I settings -- by their very nature -- have only \book-wide effect and can NEVER have score-local effect. An example of a \book-wide-only setting are top-margin and bottom-margin. These are settings that affect *ENTIRE PAGE AT A TIME* and can not under any circumstances change midpage. Page margins of course can not change in the middle of a page. So page margins make excellent examples of Class I settings. CLASS II. Class II settings -- again, by their very nature -- are more flexible and may be set either at the \book-level, or at the more specific score-level, or at both. An example of this second class of setting is ragged-right. It is entirely possible to have two scores on a single page (or "in a single \book") such that score 1 is ragged-right and score 2 is not ragged right. I think these two classes perfectly map to what Han-Wen keeps patiently describing: two different levels of scope in which settings can be made. (Han-Wen, if this isn't right, please correct.) Now with this division between Class I and Class II settings it's possible to clearly explain where the confusion arises. (And, in so doing, to explain why Han-Wen keeps inviting a rename of \paper and \layout rather than a moving around of settings from one bucket to the other.) Basically, the real division of settings is into class I and class II. And -- as an accident of naming history -- the bucket into which class I settings fit happens to have been named "\paper". Likewise, the bucket into which class II settings fit happens to have been named "\layout". (And, in fact, the history of convert-ly points to the fact that these two buckets used to be named differently, in fact.) The buckets could just have easily been called "red" and "blue". And this explains the confusion: I'm sitting here looking at the 27 different settings that 11.1.2 puts into the \paper (class I) bucket and thinking "My God, how on earth do these things relate to each other? Some are page setup settings like margins while others have nothing at all to do with page set up and concern how systems of music lay out across the page, like between-system-padding. How did these different settings all wind up in the same category?" And now the answer is clear: the 27 settings that 11.1.2 puts into the \paper (class I) bucket are all there not because they relate to each other semantically (ie, not because they all share a similar purpose) but instead because all share the same SCOPE -- you can stick any setting you want in \paper provided that the setting can have \book-level scope. OTOH, \layout is a more "selective" place to stick your settings: you can only stick settings into \layout that can have a more localized score-level scope. And now I see why Han-Wen keeps inviting a name change of the \paper and \layout buckets (while implicitly discouraging the moving around of settings between those two buckets): the buckets show the *scope* of the different settings, which isn't really an attribute that can be easily changed. OK. I get it. Now I see why the task is a renaming task rather than a moving-around task. Hm ... more thinking ... (If I'm getting something factually incorrect, somebody please correct me.) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Two staves one stops with repeat the other continues
I wrote a little chaconne duet violin/cello The cello part has the ostinato of 4 bars and repeats 3 times the violin part has 7 bars a repeat then a 2nd ending. I wanted to print it out that way but the repeat sign always extends to the other staff. version 2.8.4 XP Thanks if you can just point me to the link in the manual, I couldn't figure out what to search for. Jay Jay Hamilton www.soundand.com 206-328-7694 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
David Rogers wrote: I propose: \papersize (for only the actual paper-related items) \systemlayout (for Trevor's list 1) \headerlayout (for Trevor's list 2) I second this proposal, although they should probably be \paperSize \systemLayout \headerLayout or \paper-size \system-layout \header-layout Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
midi to ly
Hello! First, I want to thank Mats B., Valentin V. and Graham P. for their useful comments on the reference manual. I also have a question about midi to ly. I am using Lilypond version 2.10.14 on a Windows XP SP2. When I open Lilypond I get a DOS command window and a lilypond text editor. I am unable to input text in the DOS shell, say the midi2ly commands (the cursor blinks but does not move) and if I do open another DOS line command window I get a reply saying that the commands are not known. Also, I am not even very sure what sequence of code I need to use to make a MIDI file become an *.ly document on the desktop. I am very thankful of any help on this matter. Marc. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
Trevor Bača escreveu:
> I'm used to thinking of ragged-right as a "layout setting". But,
> apparently, ragged-right can go in either the (top-level) \paper or
> (top-level) \layout block equally. Why is this allowed? Is there some
> benefit?
As I said, the scoping is nested at runtime: if a lookup in \layout of a
\score fails, it is looked up in the \paper{} of the enclosing \book block.
(in a lot of cases, the \book block is implicit, and supplied by lilypond)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
Trevor Bača escreveu: > Question for anyone who can answer: are there *any* settings that > *can* go in a score-level \layout block but *can not* go in the > top-level \paper block? No, not that I know. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
Trevor Bača escreveu: > Right now both list 1 and list 2 will just be put together into the > outside-of-score (\paper) bucket. > > But it seems that may list 1 is really concerned with the *the layout > of music on the page* whereas list 2 is concerned with *adding headers > and footers outside the music*. > > So does it make sense to divide list 1 and list 2? And if so, with what > names? I think this doesn't make sense. There are two output-def objects with nested scope. Variables that by their nature have \book-wide effect, go into the outer scope, variables that are score-wide may be put in the inner scope. If that confuses you, it might be a better idea to rename \layout and \paper to better reflect this. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
Question for anyone who can answer: are there *any* settings that
*can* go in a score-level \layout block but *can not* go in the
top-level \paper block?
Second question: why do the top-level
\layout { ragged-right = ##t }
and
\paper { ragged-right = ##t }
have exactly the same effect on the output in the following file?
%%% BEGIN %%%
\version "2.11.16"
% these have exactly the same effect, no matter which one is commented out
%\layout { ragged-right = ##t }
\paper { ragged-right = ##t }
\score {
\new Staff {
c'1 \break c'1
}
}
\score {
\new Staff {
d'1 \break d'1
}
\layout { ragged-right = ##f }
}
%%% END %%%
I'm used to thinking of ragged-right as a "layout setting". But,
apparently, ragged-right can go in either the (top-level) \paper or
(top-level) \layout block equally. Why is this allowed? Is there some
benefit?
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Trevor Bača escreveu:
> > On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >> Trevor Bača escreveu:
> >>
> >> >
> >> > I wouldn't ask except for the fact that I've now been laying out score
> >> > very successfully with lily for going on two years and I still have to
> >> > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so
> >> > that they lay out more loosely. So that concerns layout and I'll look
> >> > for settings over here in the \layout block. Oh wait. Settings for
> >> > system layout live in the \paper block ..."
> >>
> >> the \layout block only affects what's in a score. Page layout (margins,
> >> titles, etc) fall outside that and therefore are in the \paper block.
> >> Perhaps better names can be found for paper/layout; suggestions
> >> appreciated.
> >
> > Hmmm.
> >
> > Just thinking out loud here ... so there's an inside-of-score /
> > outside-of-score dichotomy going on here. I don't think I had ever
> > realized that ...
> >
> > So that means that ragged-right (which currently lives in \layout) is
> > perceived as inside-of-score, whereas ragged-bottom (which currently
> > lives in \paper) is outside-of-score?
>
> yes. However, \layout settings default to what is in the \paper block,
> so ragged-right may also be defined in the \paper{} block.
OK.
Hm. So ragged-right can live in the *\layout* block (and have
score-level scope). Or ragged-right can live in the *\paper* block
(and have file-level scope).
Would it make more sense to have the idea that ragged-right only ever
live in a \layout block, together with the companion idea that there
can be both score-level \layout blocks and also one file-level \layout
block?
Question for anyone who can answer: are there *any* settings that
*can* go in a score-level \layout block but *can not* go in the
top-level \paper block?
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
I propose: \papersize (for only the actual paper-related items) \systemlayout (for Trevor's list 1) \headerlayout (for Trevor's list 2) Not perfect but maybe clear enough. David ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Kress, Stephen <[EMAIL PROTECTED]> wrote:
I think Han-Wen said it himself (though he didn't realize it).
I like the idea if \paper being as you described (with just the six
properties).
Me too. I think that greatly clears up what belongs in the \paper
block -- just stuff that has to do with the physical dimensions and
printable area of actual paper.
Put all the other stuff (the outside-the-score layout stuff) in a new block
called \page-layout
Maybe, if folks get too confused between \page-layout and \layout, the
\layout block can be moved inside the \score block since that's what it
applies to the most. It might also be that a \layout block that is outside
a \score block (for the purposes of a "global" style) could be renamed to
\score-layout.
So what do think about dividing the outside-of-score stuff into two
categories? Because it seems like maybe these two lists of settings do
different things:
list 1:
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
blank-page-force
blank-last-page-force
page-spacing-weight
list 2:
first-page-number
print-first-page-number
print-page-number
auto-first-page-number
head-separation
foot-separation
print-all-headers (iso printallheaders)
after-title-space
before-title-space
between-title-space
Right now both list 1 and list 2 will just be put together into the
outside-of-score (\paper) bucket.
But it seems that may list 1 is really concerned with the *the layout
of music on the page* whereas list 2 is concerned with *adding headers
and footers outside the music*.
So does it make sense to divide list 1 and list 2? And if so, with what names?
Just some q&d thoughts...
Stephen
-Original Message-
From:
[EMAIL PROTECTED]
on behalf of Trevor Baca
Sent: Wed 2/7/2007 12:47 PM
To: Han-Wen Nienhuys
Cc: lilypond-devel; lilypond-user
Subject: Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Trevor Baca escreveu:
> > On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >> Trevor Baca escreveu:
> >>
> >> >
> >> > I wouldn't ask except for the fact that I've now been laying out
score
> >> > very successfully with lily for going on two years and I still have
to
> >> > stop and ask myself "Hmm ... I'm wanting to pad systems on the page
so
> >> > that they lay out more loosely. So that concerns layout and I'll
look
> >> > for settings over here in the \layout block. Oh wait. Settings for
> >> > system layout live in the \paper block ..."
> >>
> >> the \layout block only affects what's in a score. Page layout
(margins,
> >> titles, etc) fall outside that and therefore are in the \paper block.
> >> Perhaps better names can be found for paper/layout; suggestions
> >> appreciated.
> >
> > Hmmm.
> >
> > Just thinking out loud here ... so there's an inside-of-score /
> > outside-of-score dichotomy going on here. I don't think I had ever
> > realized that ...
> >
> > So that means that ragged-right (which currently lives in \layout) is
> > perceived as inside-of-score, whereas ragged-bottom (which currently
> > lives in \paper) is outside-of-score?
>
> yes. However, \layout settings default to what is in the \paper block,
> so ragged-right may also be defined in the \paper{} block.
OK.
Hm. So ragged-right can live in the *\layout* block (and have
score-level scope). Or ragged-right can live in the *\paper* block
(and have file-level scope).
Would it make more sense to have the idea that ragged-right only ever
live in a \layout block, together with the companion idea that there
can be both score-level \layout blocks and also one file-level \layout
block?
--
Trevor Baca
[EMAIL PROTECTED]
2007-02-07, 13:02:32
The information contained in this e-mail message and any attachments may be
privileged and confidential. If the reader of this message is not the
intended recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that any review, dissemination,
distribution or copying of this communication is strictly prohibited. If
you have received this communication in error, please notify the sender
immediately by replying to this e-mail and delete the message and any
attachments from your computer.
2007-02-07, 13:33:40
The information contained in this e-mail message and any attachments may be
privileged and confidential. If the reader of this message is not the
intended recipient or an agent responsible for delivering it to the intended
recipient, you are hereby notified that any review, dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please notify the sender
immediately by replying to this e-mail and delete the message and any
attachments from your computer.
--
Trevor Bača
[EMAIL PROTECTED]
_
Lyric Ties
I'm setting a Renaissance madrigal and am getting a series of compilation errors with regards to lyric ties. programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+1000203F, file /home/aaron/lilypond/usr/share/lilypond/current/fonts/otf//CenturySchL-Roma.otf continuing, cross fingers programming error: FT_Get_Glyph_Name returns error continuing, cross fingers Now, the documentation says that I have to make sure I have an appropriate font to render this glyph. The font listed (DejaVuLGC) does not come with the Lilypond FreeBSD package. Is there a packaged font I need to use to render these ties? If it's an external font, how do I install that into the FreeBSD Lilypond tree so it's seen? Thank you for your time and assistance! -- Aaron Dalton Super Duper Games http://superdupergames.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Reorganizing the contents of the \paper block
I think Han-Wen said it himself (though he didn't realize it).
I like the idea if \paper being as you described (with just the six properties).
Put all the other stuff (the outside-the-score layout stuff) in a new block
called \page-layout
Maybe, if folks get too confused between \page-layout and \layout, the \layout
block can be moved inside the \score block since that's what it applies to the
most. It might also be that a \layout block that is outside a \score block
(for the purposes of a "global" style) could be renamed to \score-layout.
Just some q&d thoughts...
Stephen
-Original Message-
From: [EMAIL PROTECTED] on behalf of Trevor Baca
Sent: Wed 2/7/2007 12:47 PM
To: Han-Wen Nienhuys
Cc: lilypond-devel; lilypond-user
Subject: Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Trevor Baca escreveu:
> > On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >> Trevor Baca escreveu:
> >>
> >> >
> >> > I wouldn't ask except for the fact that I've now been laying out score
> >> > very successfully with lily for going on two years and I still have to
> >> > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so
> >> > that they lay out more loosely. So that concerns layout and I'll look
> >> > for settings over here in the \layout block. Oh wait. Settings for
> >> > system layout live in the \paper block ..."
> >>
> >> the \layout block only affects what's in a score. Page layout (margins,
> >> titles, etc) fall outside that and therefore are in the \paper block.
> >> Perhaps better names can be found for paper/layout; suggestions
> >> appreciated.
> >
> > Hmmm.
> >
> > Just thinking out loud here ... so there's an inside-of-score /
> > outside-of-score dichotomy going on here. I don't think I had ever
> > realized that ...
> >
> > So that means that ragged-right (which currently lives in \layout) is
> > perceived as inside-of-score, whereas ragged-bottom (which currently
> > lives in \paper) is outside-of-score?
>
> yes. However, \layout settings default to what is in the \paper block,
> so ragged-right may also be defined in the \paper{} block.
OK.
Hm. So ragged-right can live in the *\layout* block (and have
score-level scope). Or ragged-right can live in the *\paper* block
(and have file-level scope).
Would it make more sense to have the idea that ragged-right only ever
live in a \layout block, together with the companion idea that there
can be both score-level \layout blocks and also one file-level \layout
block?
--
Trevor Baca
[EMAIL PROTECTED]
2007-02-07, 13:02:32
The information contained in this e-mail message and any attachments may be
privileged and confidential. If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended recipient,
you are hereby notified that any review, dissemination, distribution or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify the sender immediately by replying to
this e-mail and delete the message and any attachments from your computer.
2007-02-07, 13:33:40
The information contained in this e-mail message and any attachments may be
privileged and confidential. If the reader of this message is not the intended
recipient or an agent responsible for delivering it to the intended recipient,
you are hereby notified that any review, dissemination, distribution or copying
of this communication is strictly prohibited. If you have received this
communication in error, please notify the sender immediately by replying to
this e-mail and delete the message and any attachments from your computer.___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Trevor Bača escreveu:
> On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> Trevor Bača escreveu:
>>
>> >
>> > I wouldn't ask except for the fact that I've now been laying out score
>> > very successfully with lily for going on two years and I still have to
>> > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so
>> > that they lay out more loosely. So that concerns layout and I'll look
>> > for settings over here in the \layout block. Oh wait. Settings for
>> > system layout live in the \paper block ..."
>>
>> the \layout block only affects what's in a score. Page layout (margins,
>> titles, etc) fall outside that and therefore are in the \paper block.
>> Perhaps better names can be found for paper/layout; suggestions
>> appreciated.
>
> Hmmm.
>
> Just thinking out loud here ... so there's an inside-of-score /
> outside-of-score dichotomy going on here. I don't think I had ever
> realized that ...
>
> So that means that ragged-right (which currently lives in \layout) is
> perceived as inside-of-score, whereas ragged-bottom (which currently
> lives in \paper) is outside-of-score?
yes. However, \layout settings default to what is in the \paper block,
so ragged-right may also be defined in the \paper{} block.
OK.
Hm. So ragged-right can live in the *\layout* block (and have
score-level scope). Or ragged-right can live in the *\paper* block
(and have file-level scope).
Would it make more sense to have the idea that ragged-right only ever
live in a \layout block, together with the companion idea that there
can be both score-level \layout blocks and also one file-level \layout
block?
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
Trevor Bača escreveu:
> On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>> Trevor Bača escreveu:
>>
>> >
>> > I wouldn't ask except for the fact that I've now been laying out score
>> > very successfully with lily for going on two years and I still have to
>> > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so
>> > that they lay out more loosely. So that concerns layout and I'll look
>> > for settings over here in the \layout block. Oh wait. Settings for
>> > system layout live in the \paper block ..."
>>
>> the \layout block only affects what's in a score. Page layout (margins,
>> titles, etc) fall outside that and therefore are in the \paper block.
>> Perhaps better names can be found for paper/layout; suggestions
>> appreciated.
>
> Hmmm.
>
> Just thinking out loud here ... so there's an inside-of-score /
> outside-of-score dichotomy going on here. I don't think I had ever
> realized that ...
>
> So that means that ragged-right (which currently lives in \layout) is
> perceived as inside-of-score, whereas ragged-bottom (which currently
> lives in \paper) is outside-of-score?
yes. However, \layout settings default to what is in the \paper block,
so ragged-right may also be defined in the \paper{} block.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
On 2/7/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Trevor Bača escreveu: > > I wouldn't ask except for the fact that I've now been laying out score > very successfully with lily for going on two years and I still have to > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so > that they lay out more loosely. So that concerns layout and I'll look > for settings over here in the \layout block. Oh wait. Settings for > system layout live in the \paper block ..." the \layout block only affects what's in a score. Page layout (margins, titles, etc) fall outside that and therefore are in the \paper block. Perhaps better names can be found for paper/layout; suggestions appreciated. Hmmm. Just thinking out loud here ... so there's an inside-of-score / outside-of-score dichotomy going on here. I don't think I had ever realized that ... So that means that ragged-right (which currently lives in \layout) is perceived as inside-of-score, whereas ragged-bottom (which currently lives in \paper) is outside-of-score? -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
lilypond-book --pdf doesn't work for me (was Re: Failed to extract font)
> "Mats" == Mats Bengtsson <[EMAIL PROTECTED]> writes: Mats> I recommend to use the pdflatex mode of lilypond-book: Mats> lilypond-book --pdf --output=out 1-test1.lytex Mats> cd out Mats> pdflatex 1-test1 I'm having trouble making this work. I'm on an Ubuntu edgy system running lilypond 2.10. I can run the commands, but the PDF file has only a page number, not any music or headers or anything. I get a lot of error messages of the form: Non-PDF special ignored! I can run pdflatex on normal latex (without lilypond-book), and I can run lilyond-book without the --pdf output and get reasonable output. Is there something I have to do so that lilypond-book will put something where pdflatex expects to find it? Here's my simple test case. Running "make simplebook.pdf" produces a five page output file with staves and notes. Running "make simplebook-p.pdf" produces 5 blank pages. simplebook.lytex Description: .lytex file to test lilypond-book testsimple.ly Description: simple lilypond test file Makefile Description: Makefile with commands for running lilypond-book with and without --pdf option -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Reorganizing the contents of the \paper block
Trevor Bača escreveu: > > I wouldn't ask except for the fact that I've now been laying out score > very successfully with lily for going on two years and I still have to > stop and ask myself "Hmm ... I'm wanting to pad systems on the page so > that they lay out more loosely. So that concerns layout and I'll look > for settings over here in the \layout block. Oh wait. Settings for > system layout live in the \paper block ..." the \layout block only affects what's in a score. Page layout (margins, titles, etc) fall outside that and therefore are in the \paper block. Perhaps better names can be found for paper/layout; suggestions appreciated. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Reorganizing the contents of the \paper block
Hi,
Hopefully this won't be rocking the boat too much, but I'd like to
open a small discussion about reorganizing the contents of the \paper
block.
Section 11.1.2 "Page formatting" lists 27 \paper settings:
first-page-number
print-first-page-number
print-page-number
paper-width
paper-height
top-margin
bottom-margin
left-margin
line-width
head-separation
foot-separation
page-top-space
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
after-title-space
before-title-space
between-title-space
printallheaders
systemSeparatorMarkup
blank-page-force
blank-last-page-force
page-spacing-weight
auto-first-page-number
Seems to me that in most programs, stuff like paper dimensions and
margins are included in a page setup dialog somewhere, but that stuff
having to do with headers and footers and titles and other types of
text usually lives somewhere else. So, when I look at these 27 \paper
settings, I see them organizing into something like the following
categories:
Two settings for the physical paper itself:
paper-width
paper-height
Four settings for margins (closely related to the physical paper):
top-margin
bottom-margin
left-margin
line-width (instead of right-margin)
Seven settings for headers and footers:
first-page-number
print-first-page-number
print-page-number
auto-first-page-number
head-separation
foot-separation
printallheaders
Three for titles (which are text and probably a type of one-time header):
after-title-space
before-title-space
between-title-space
Six for the (mostly vertical, but one horizontal) layout of systems:
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
And three page-layout settings that probably influence decisions about
pageBreaks:
blank-page-force
blank-last-page-force
page-spacing-weight
These settings are all important and are certainly possible to lay out
score with sucessfully.
Maybe the settings would be easier to find and make more conceptual
sense like this?
Strip \paper down to settings pertaining to paper:
\paper {
paper-width
paper-height
top-margin
bottom-margin
left-margin
right-margin (new; line-width moves elsewhere?)
}
Move over the settings having to do with page layout into the \layout block:
\layout {
ragged-bottom
ragged-last-bottom
system-count
between-system-space
between-system-padding
horizontal-shift
blank-page-force
blank-last-page-force
page-spacing-weight
}
And create a new block for headers and footers:
\headers-and-footers {
first-page-number
print-first-page-number
print-page-number
auto-first-page-number
head-separation
foot-separation
print-all-headers (iso printallheaders)
after-title-space
before-title-space
between-title-space
}
Does this add value? Or just create a huge mess?
I wouldn't ask except for the fact that I've now been laying out score
very successfully with lily for going on two years and I still have to
stop and ask myself "Hmm ... I'm wanting to pad systems on the page so
that they lay out more loosely. So that concerns layout and I'll look
for settings over here in the \layout block. Oh wait. Settings for
system layout live in the \paper block ..."
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: OT: Japanese translator wanted
On 2/3/07, Trevor Bača <[EMAIL PROTECTED]> wrote: Hi, I'm looking for someone to translate the score preface of a new piece from English into Japanese. The piece is for unaccompanied flute. The preface is a page or two long and covers fingerings, breathing and other aspects of the notation. If you're a native speaker of Japanese and this sounds interesting, please mail me back privately. There will be French and German translations available, too, if that helps. And I'm thinking a fee of EUR 100 for the Japanese would be good. Hi, Thanks to everybody for the kind replies off the list. This mail serves to close the thread. I've found a great Japanese translator and I really appreciate the opportunity to use the linguistic resources of the list (as well as the musical resources of the list)! Thanks again. -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Different bar lines, musica ficta & lyrics font style
Marcel Korpel wrote:
Dear all,
When using Lilypond to typeset a transcription of a Palestrina Mass
the past couple of days, I stumbled upon several things which bother
me more or less:
1. Is it possible to change the bar line depending on whether the note
values exceed the measure or not? For instance, when typing
dl = \set Timing.defaultBarType = "dashed"
nl = \set Timing.defaultBarType = "|"
\new Voice \relative c'' {
\clef G
\time 3/1
\set Staff.timeSignatureFraction = #'(3 . 2) % tempus perfectum
d1 d2 c1 c2 d1 a2 c1 \dl b \nl a4 g a1 g4 a b c
[etc.]
}
it would be nice to automatically change the bar line to dashed when
the b exceeds the measure, instead of enclosing it with macros that
change the default bar type to dashed and back.
There's no such feature available as far as I know.
2. When notating musica ficta using 'suggestAccidentals', an
accidental should be written above the bar for every altered note. At
the end of a section I wrote
\new Voice \relative c'' {
\set suggestAccidentals = ##t
\clef G
\time 3/1
\set Staff.timeSignatureFraction = #'(3 . 2)
[...] f2 g1 fis4 e fis1
\set Staff.measureLength = #(ly:make-moment 4 1) g\longa
\bar "|."
}
and only above the first f an accidental is printed. I know I can
place it manually adding '^\markup{\sharp}', but I don't think that's
a good solution.
Read the section on Automatic Accidentals. I guess you want to add
#(set-accidental-style 'forget)
3. When entering lyrics I need to italicize part of the text (to
indicate the text is my addition). But I get error messages when using
text = \lyricmode { Ky -- ri -- e e -- le -- i -- son
\italic Ky -- ri -- _ e e -- _ _ _ _ _ _ _ le -- i -- son
Ky -- ri -- e e -- le -- _ _ _ _ _ _ _ i -- son }
or several variations on \italic.
There are no such macros defined, but you can make them yourself:
italics = \override LyricText #'font-shape = #'italic
upright = \revert LyricText #'font-shape
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Different bar lines, musica ficta & lyrics font style
Dear all,
When using Lilypond to typeset a transcription of a Palestrina Mass
the past couple of days, I stumbled upon several things which bother
me more or less:
1. Is it possible to change the bar line depending on whether the note
values exceed the measure or not? For instance, when typing
dl = \set Timing.defaultBarType = "dashed"
nl = \set Timing.defaultBarType = "|"
\new Voice \relative c'' {
\clef G
\time 3/1
\set Staff.timeSignatureFraction = #'(3 . 2) % tempus perfectum
d1 d2 c1 c2 d1 a2 c1 \dl b \nl a4 g a1 g4 a b c
[etc.]
}
it would be nice to automatically change the bar line to dashed when
the b exceeds the measure, instead of enclosing it with macros that
change the default bar type to dashed and back.
2. When notating musica ficta using 'suggestAccidentals', an
accidental should be written above the bar for every altered note. At
the end of a section I wrote
\new Voice \relative c'' {
\set suggestAccidentals = ##t
\clef G
\time 3/1
\set Staff.timeSignatureFraction = #'(3 . 2)
[...] f2 g1 fis4 e fis1
\set Staff.measureLength = #(ly:make-moment 4 1) g\longa
\bar "|."
}
and only above the first f an accidental is printed. I know I can
place it manually adding '^\markup{\sharp}', but I don't think that's
a good solution.
3. When entering lyrics I need to italicize part of the text (to
indicate the text is my addition). But I get error messages when using
text = \lyricmode { Ky -- ri -- e e -- le -- i -- son
\italic Ky -- ri -- _ e e -- _ _ _ _ _ _ _ le -- i -- son
Ky -- ri -- e e -- le -- _ _ _ _ _ _ _ i -- son }
or several variations on \italic.
I ploughed through the manual, but I couldn't find a way to deal with
these things.
Your suggestions would be much appreciated!
Kind regards,
Marcel
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
