Re: make score be line break aware
2007/10/1, Joe Neeman [EMAIL PROTECTED]: On Mon, 1 Oct 2007 17:55:46 Francisco Vila wrote: Hello. Is this possible? I want to typeset something (like a spanner or a different height of the lyrics baseline) that I want to last only until it reaches the next line break. If only I could explain it well, it would be a sort of intelligent tweak that 'knows' when a line break has happened and it then kills himself. There would be as liquid layout as possible meaning that layout does not interfere with content, i.e. making an explicit \break would not be an optimal solution. Does the Difficult Tweaks section in the manual have the sort of thing you want? Yes! Only that's too much Scheme for me. Thank you! I'll try to dive into Scheme sooner or later. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Elision/lyric tie again
One more thing about the elision/lyric tie, which I discovered today: I generated eps files from two different but structurally identical files, in the same batch process, and one ended up at 100 kb, the other at 1.2 Mb. I couldn't understand why, but eventually, I realized that there was an elision tie in the big file. I understand that the sign is not part of LPs own font and that it is taken from some other font available on the system, but it seems a huge difference just for one sign. It may not be something that everyone uses all the time, but I do, and I'd very much like to see a better solution to this. Another thing is that the sign as it now is -- at least as it is generated on my system -- is way too wide. Common practice is that it looks more like a semi-circle than a musical tie, and it goes *between* the syllables, not *under* them. Consider this a request and a sponsorship offer for a better elision mechanism. Eyolf -- * lilo hereby declares OPN a virtual pain in the ass :) ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score imbedded in markup text (in-line)
Quoting Maximilian Albert [EMAIL PROTECTED]:
In the example, I have also changed the vertical alignment, to
make it look better. You may want to try \general-align #Y #DOWN
instead.
... or even some value in between like \general-align #Y #-0.2 so as
to make the text appear at about the height of the middle staff line,
in case this is what you want (though unfortunately the value -0.2
was obtained by trial and error).
There's no need for trial and error. If you want the text exactly
centered with the music, then you can use
\markup {
{
\general-align #Y #CENTER foo
\general-align #Y #CENTER \snip
}
}
which sets the alignment point of both the text and the \snip
on the vertical of the respective markup. What my previous suggestion
does is to align the baseline of the text with the
center of \snip, which explains why the text ended up slightly too
high, in your opinion.
/Mats
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: score imbedded in markup text (in-line)
Mats Bengtsson schrieb:
There's no need for trial and error. If you want the text exactly
centered with the music, then you can use
\markup {
{
\general-align #Y #CENTER foo
\general-align #Y #CENTER \snip
}
}
which sets the alignment point of both the text and the \snip
on the vertical of the respective markup. What my previous suggestion
does is to align the baseline of the text with the
center of \snip, which explains why the text ended up slightly too high,
in your opinion.
Ha! I should learn not to stop thinking in the middle of experiments. :)
Of course you are right. Thanks for the explanation and for pointing me
to this solution!
Best,
Max
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
guitar chords
Hi,
I'm newbie here. I have just started to learn lilypond. It looks very nice
(altough it needs some time to learn syntax, commands and tricks). :-)
Is it possible to add guitar chords above a staff (accompanying guitar
chords for a vocal)? Like Em, D, C, H, etc. I have played with \chords,
\chordmode, ChordNames, but I'm not sure I'm doing the right thing:
introchords = \chordmode { e2:min d4 c2. b2. b2. e2:min d4 c2. b2. b2 }
\new ChordNames {
\germanChords \introchords }
\context Voice { \Intro }
I couldn't add H4 (B4) for example.
At the link below you can find my first lilypond source file, and the
original, manually prepared score in jpg I would like to reproduce. It would
be nice if somebody could check it and let me know my mistakes, and give
some suggestions how it can be improved.
http://public.box.net/s09376
Thanks
Zoltan
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pitches rewrite draft
On 01.10.2007 (13:12), Graham Percival wrote: Trevor Daniels wrote: Graham wrote: - move Micro tones into Accidentals. No, too specialist. Should it be moved into Specialist notation? Wherever it is it needs a link to Other languages. I disagree with this, although I admit that I can't come up with a good reason. One of the things I was trying to do was to make the new doc sections a complete reference for each item. So Pitches would include everything about pitches, expressive marks would include everything about that, etc. Here's where my reasoning falls down: I admit that this doesn't work with Ancient music. Pitches-displaying-clefs doesn't include ancient music clefs, for example. This should be solved through a cross-ref. I think the reason that you say you can't come up with, has to do with the question Where would a user be most likely to go looking for it? In the case of ancient music, it would be counter-intuitive and -productive to strictly follow any technical-analytical distinction, since the ancient music features come as a package: you would rarely write an ordinary score and then use a petrucci-g clef, e.g. (whereas Modern music is more about adding bits and pieces to standard notation, hence it is justified to put the bits and pieces where they belong, technically). I'm still confident that the manual should be split up this way, but I can't point to a general principle to back me up on this. :|(other than our ancient music support is a bit old, no pun intended, so I'd rather hide it at the back of the manual) I'm looking forward to taking part in the upcoming revision of the Ancient section :-) Eyolf -- Why do so many foods come packaged in plastic? It's quite uncanny. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Pitches rewrite draft
Graham replied: Trevor Daniels wrote: Graham wrote: - move Micro tones into Accidentals. No, too specialist. Should it be moved into Specialist notation? Wherever it is it needs a link to Other languages. I disagree with this, although I admit that I can't come up with a good reason. One of the things I was trying to do was to make the new doc sections a complete reference for each item. So Pitches would include everything about pitches, expressive marks would include everything about that, etc. Ah, yes - I'd forgotten this principle, which I support. So I withdraw my comment - see below. Here's where my reasoning falls down: I admit that this doesn't work with Ancient music. Pitches-displaying-clefs doesn't include ancient music clefs, for example. I'm still confident that the manual should be split up this way, but I can't point to a general principle to back me up on this. :|(other than our ancient music support is a bit old, no pun intended, so I'd rather hide it at the back of the manual) Is this a better reason? The section on Ancient music is very substantial and includes much more than just clefs. It is right that it forms a self-contained section within Specialist notation rather than attempting to split it up into its component parts - noteheads, clefs, rests, time signatures, etc. Splitting it would result in a loss in clarity rather than an increase (that's the reason). OTOH the section on Microtones is tiny (at least for the present) and concerns a single topic - accidentals. It therefore slips easily into Accidentals. However, we should be conscientious to add prominent links to the Ancient music section from all the standard parts - from Accidentals to Ancient accidentals, etc - to compensate. Cheers, - Graham Trevor ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: guitar chords
On 02.10.2007 (09:57), Zoltan Kota wrote:
Hi,
I'm newbie here. I have just started to learn lilypond. It looks very nice
(altough it needs some time to learn syntax, commands and tricks). :-)
Is it possible to add guitar chords above a staff (accompanying guitar
chords for a vocal)? Like Em, D, C, H, etc. I have played with \chords,
\chordmode, ChordNames, but I'm not sure I'm doing the right thing:
You're making it too complicated. Try to add the following:
versechords = \chords { e2:m d4 c2. } %etc,
and replace your current score section with the following:
\score {
\versechords
\context ChoirStaff
\context Voice = sop \Soprano
\new Lyrics \lyricsto sop \soptext
\context Voice = ooo \Chor
\new Lyrics \lyricsto ooo \chortext
}
Also, in the ooo section, you could replace Oo- with Oo __ (two
underscores), that will produce nice extenders under the whole chord
passage.
I couldn't add H4 (B4) for example.
b:sus4 is probably what you're after.
Eyolf
--
BOFH excuse #256:
You need to install an RTFM interface.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
odd beaming in tuplets
Hi there.
Is the strange beaming inside the tuplet in the first 4/8 measure of
this sniplet expected? Right now im overriding with manually setting
stemBeamCount to correct values, but its very tedious.
[2. image notation --- image/jpeg; lilypond-beaming-oddness.jpg]...
\version 2.10.20
\relative c' {
\time 2/4
\times 4/5 { a32 a a16. } a8 a a |
a32 a a16 a8 a a |
\time 4/8
\times 4/5 { a32 a a16. } a8 a a |
a32 a a16 a8 a a |
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: printing Staff Symbol before \stopStaff
You can set firstClef to #f, and remove Time_signature_engraver from the ossia-staff. See e.g. http://lilypond.org/doc/v2.11/input/manual/lily-6910c8f3a6.ly Met vriendelijke groet, Wilbert Berendsen -- http://www.wilbertberendsen.nl/ You must be the change you wish to see in the world. -- Mahatma Gandi ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Lyric tie and MS-Gothic font
I'm having problems with the lyric tie on a Windows XP
system. Here's a simple example containing it:
\version 2.10.20
\paper {
ragged-right = ##t
}
\relative c' {
c4.~ c8 d b
}
\addlyrics {
Lar -- go~al fac
}
On my system this gives the error message:
Parsing...
Interpreting music...
Preprocessing graphical objects...
Layout output to `bug.ps'...
warning: don't know how to embed
MS-Gothic=C:/WINDOWS/fonts/msgothic.ttc
Converting to `bug.pdf'...
`gs -q -dDEVICEWIDTHPOINTS#595.28 -dDEVICEHEIGHTPOINTS#841
.89 -dCompatibilityLevel#1.4 -dNOPAUSE -dBATCH -r1200 -sD
EVICE#pdfwrite -sOutputFile#bug.pdf -c .setpdfwrite -f
bug.ps' failed (1)
The manual says that the lyric tie is printed using the
Undertie glyph, U+203F, and requires a font to be installed
which includes this glyph, like DejaVu LGC. I tried
installing DejaVuLGCSans.ttf but this makes no difference to
the error message.
I now see that this glyph is already included in the
MS-Gothic font, installed in XP by default, and it seems LP
is attempting to use this font rather than the DejaVu one.
I can use undertie from both fonts in MS Word without
difficulty. The glyph in DejaVu is somewhat longer than the
one from MS Gothic, but they are basically the right glyphs.
I get the same error if I encode the .ly file in DejaVu,
replace the tilde with undertie, and save it in utf-8.
Any ideas on fixing this? Is it a bug, or do I need to do
something else?
Trevor
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Question about piano template with centered dynamics
Hi all,
There's a question here about the piano template with centered dynamics. I
never used this template but it seemed quite fashionable to have centered
dynamics. However, it appears somewhat strange. First of all there are two
score blocks. Is this really needed?
Second... some syntax errors occur...
This is the message the compiler gives me:
Verwerken van `/Users/MartijnVromans/Desktop/lenfer.ly'
Ontleden...
/Users/MartijnVromans/Desktop/lenfer.ly:49:24: fout: syntax error,
unexpected '{', expecting '='
context
{
/Users/MartijnVromans/Desktop/lenfer.ly:59:24: fout: syntax error,
unexpected \consists
\consists Piano_pedal_engraver
/Users/MartijnVromans/Desktop/lenfer.ly:75:24: fout: onbekende ontsnapte
string: `\PianoStaff'
\PianoStaff
fout: gefaalde bestanden: /Users/MartijnVromans/Desktop/lenfer.ly
The source of the template is on the user manual on page 332.
All the best,
Martijn
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Question about piano template with centered dynamics
Quoting Martijn Vromans [EMAIL PROTECTED]: Hi all, There's a question here about the piano template with centered dynamics. I never used this template but it seemed quite fashionable to have centered dynamics. However, it appears somewhat strange. First of all there are two score blocks. Is this really needed? One for printed output, the other one for MIDI output, if I recall correctly. Second... some syntax errors occur... Are you sure that you copied all relevant lines? Are you sure that the version of the manual that you copied them from is the same as the version of LilyPond you have installed. Finally, I have posted an alternative approach to get a similar output with simpler techniques, see http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00239.html I haven't tested it in any recent version of LilyPond, though, so I cannot promise that it still works. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Question about piano template with centered dynamics
Are you sure that you copied all relevant lines? Are you sure that the version of the manual that you copied them from is the same as the version of LilyPond you have installed. Oh yes! I copied it from the online version from the latest stable version. But I remember that this example never worked here. I wrote another template last year, but it's lost now. Finally, I have posted an alternative approach to get a similar output with simpler techniques, see http://lists.gnu.org/archive/html/lilypond-user/2007-01/msg00239.html I haven't tested it in any recent version of LilyPond, though, so I cannot promise that it still works. Thanks, I'll figure it out. All the best, Martijn Vromans ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: GDP: add extender line to the glossary?
On 9/28/07 12:05 PM, Graham Percival [EMAIL PROTECTED] wrote: Should we add extender line to the glossary? Is this a real musical term, or a made-up lilypond term? Any vocalists want to comment? I've found a couple references: In a set of songs published by A-R Editions in their Music of the United States of America series, volume 7, p. 352: The original sheet music [from the late 1800s] indicates prolongation of one syllable of text over an extended pitch usually by means of a series of dots. These have been changed to a standard extender line in accordance with modern practice. Second citation from A Music Representation Requirement Specification for Academia, by Donald Byrd at the Indiana Univerisity School of Music: Item 15.3, Graphic. Prioritized as Very desireble An optional ³extender² line of arbitrary extent after the text. (This can be useful for many purposes, such as melismatic lyrics, indications of the string to play, etc.) Since Dr. Byrd is well respected in musical academia, I think his use of the term qualifies it as authoritative, and therefore deserving of a spot in the glossary. Regards, Kurtis ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Paper size (A4) problems
Hi list,
I've been trying to something which I though would be simple with Lilypond: to
print music paper. Nothing took me too long to get done. Except for one
important detail: the size of the paper.
I've tried using set-paper-size on several sections of the Lilypond source, and
the result is always the same:
- The Postscript code generated seems to be larger than the pre-defined paper
size and appears clipped when viewed with a document viewer or when printed
(using Ghostscript). Of the 24 staves per page I expected, I see only 21!
- When looking at the generated postscript I see the following (I'm using A4
210x297 paper):
/page-height 307.289763779528 def
/page-width 217.275590551181 def
Now, I don't know what units are these, but they can't be milimeters, picas, or
anything related to the output-scale parameter...
What are these?
What can I do to have output of the correct size?
Bellow is the source code and part of the generated Postscript. Sorry about the
comments in portuguese.
Thank you,
Miguel Ramos
generated postscript snippet:
/lily-output-units 2.83464566929134 def %% millimeter
/staff-line-thickness 0.153766233766234 def
/line-width 196.582677165354 def
/paper-size (a4) def
/staff-height 4.0 def
/output-scale 0.966514459665145 def
/page-height 307.289763779528 def
/page-width 217.275590551181 def
the full source file:
% Miguel Ramos, Out/2007.
\version 2.10.29
% Número de pautas por página.
staves = 24
% Tipo de papel e tamanho da pauta.
#(set-default-paper-size a4)
#(set-global-staff-size 11)
\paper {
%head-separation = 4\mm
%foot-separation = 4\mm
page-top-space = 6\mm
ragged-last-bottom = ##f
between-system-space = 4\mm
between-system-padding = 4\mm
}
\header {
% Elimina a etiqueta do Lilypond.
tagline = ##f
}
\score {
\new Staff {
% Um espaçador de um compasso para cada pauta.
\repeat unfold \staves { s1 \break \noPageBreak }
}
\layout {
% Elimina o espaçamento especial para o primeiro sistema.
indent = 0
% No contexto partitura,
\context { \Score
% Elimina o gravador do número de compasso.
\remove Bar_number_engraver
}
% No contexto pauta,
\context { \Staff
% Elimina o gravador da clave.
\remove Clef_engraver
% Elimina o gravador da indicação de compasso.
\remove Time_signature_engraver
% Elimina o gravador das barras de compasso.
\remove Bar_engraver
% Faz as linhas ficarem mais fininhas.
\override StaffSymbol #'ledger-line-thickness = #'(0.2 . 0.02)
% Extende a área de cada pauta um espaço para cima e para baixo.
\override VerticalAxisGroup #'minimum-Y-extent = #'(-3 . 3)
}
}
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Lilypond-book -- almost there...
I've been struggling to get lilypond-book do what I want it to do, and
I think I'm almost there. Now, I have working output, my question is
if there is a better way to work to get there.
I want to include files with lp-examples in chapters that I \include
in a main LaTeX document, fullbook.tex, something like this:
\documentclass[a4paper]{memoir}
\begin{document}
\include{ch1}
\include{ch2}
\include{lp-examples}
\end{document}
How I finally made it work, was to have a file lp-examples.lytex
containing sth like the following:
\chapter{appendix}
\section{1 Gioia et amore}
This is a song.
\lilypondfile{graphics/01-gioia-et-amore.ly}
which I first process through lilypond-book. This gives a file
lp-examples.tex, which is then processed nicely when I do latex
fullbook.
1. Is this the recommended way to work?
2. Is there a way to automatize the process? E.g. in Kile, vim, or
-- god forbid -- emacs/auctex?
Eyolf
--
I already have too much problem with people thinking the efficiency of
a perl construct is related to its length. On the other hand, I'm
perfectly capable of changing my mind next week... :-) --lwall
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pitches rewrite draft
On 01.10.2007 (16:16), Trevor Daniels wrote: Some comments on Pitches - move Micro tones into Accidentals. No, too specialist. Should it be moved into Specialist notation? Wherever it is it needs a link to Other languages. I say yes, in accordance with the general principle that everything that belongs together, should be together, no matter how advanced or basic it is. Also, the specialist notation section is for specialized areas of use (guitar, piano, ancient, etc) rather than very advanced features that only 20th-c. music freaks will ever need :-) BTW, I've been thinking about that title... I was trying to find the section on vocal music, which ought to be easy enough, but it took me a while to find it there, even though I knew it was there. I didn't think of it as specialist in any way. I think specialized notation would make it a little better, but I'm not sure. -- Han Solo: You said you wanted to be around when I made a mistake, well, this could be it, sweetheart. Princess Leia: I take it back. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pitches rewrite draft
On 10/1/07, Eyolf Østrem [EMAIL PROTECTED] wrote: On 01.10.2007 (16:16), Trevor Daniels wrote: Some comments on Pitches - move Micro tones into Accidentals. No, too specialist. Should it be moved into Specialist notation? Wherever it is it needs a link to Other languages. I say yes, in accordance with the general principle that everything that belongs together, should be together, no matter how advanced or basic it is. Also, the specialist notation section is for specialized areas of use (guitar, piano, ancient, etc) rather than very advanced features that only 20th-c. music freaks will ever need :-) BTW, I've been thinking about that title... I was trying to find the section on vocal music, which ought to be easy enough, but it took me a while to find it there, even though I knew it was there. I didn't think of it as specialist in any way. I think specialized notation would make it a little better, but I'm not sure. FWIW, I'm not a fan of the specialist / nonspecialist distinction. All notation is specialist ... until you realize that you need it ... and then it suddenly becomes very ordinary. So I would put microtones right alongside the other accidentals. (So I vote with Eyolf.) -- Trevor Bača [EMAIL PROTECTED] ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lilypond-book -- almost there...
2007/10/2, Eyolf Østrem [EMAIL PROTECTED]: 2. Is there a way to automatize the process? E.g. in Kile, vim, or You can obtain a reasonable degree of automation using the 'make' utility. Search for Marcus Brinkmann, (marcus dot brinkmann at rub dot de) for a nice example of how to use it on a complete book (Slave Songs of the United States, 1867) -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Spanner - markup collision
On 10/2/07, Palmer, Ralph [EMAIL PROTECTED] wrote:
Greetings -
I'm running LilyPond 2.11.23 under Windows XP Pro, SP2.
I'm having a problem with a markup vs. a TextSpanner. In the snippet,
the markup:
(One stand opt.8va)
is above the spanner if I do not move the markup. I'd like to have the
markup appear below the spanner. Can anyone point me in the right
direction? Perhaps the correct #'extra-offset command or qualifier for
the TextSpanner?
Thanks for your help.
% Snippet %%
\version 2.11.23
\include english.ly
Test = {
\key c \major
\clef G
\time 3/4
d''8[ g''] bf''
\textSpannerUp \override TextSpanner #'bound-details #'left
#'text = \markup\italic {(Opt. 8va) }
\override TextSpanner #'bound-details #'right #'text = \markup {
\draw-line #'(0 . -1) }
d''4--\upbow\startTextSpan( g''8--) |
\time 4/4
bf''4 g'' a''2~ |
a''2.~\_\markup\italic{molto rit.} a''8. a'16\!\stopTextSpan
|
\textSpannerUp \override TextSpanner #'bound-details #'left
#'text = \markup\italic {(One stand opt. 8va) }
\override TextSpanner #'bound-details #'right #'text = \markup {
\draw-line #'(0 . -1) }
\once\override TextScript #'extra-offset = #'( 0 . -2 )
cs''1~^\markup\italic{bow freely, staggering
bows}\downbow\startTextSpan\ |
cs''1~ |
cs''1~\fermata |
cs''8\stopTextSpan\! r8 r4 r2 |
\bar |.
}
\Score
{
\Test
}
End Snippet %%
Hi Ralph,
outside-staff-priority is your friend:
%%% BEGIN %%%
\version 2.11.33
\include english.ly
Test = {
\key c \major
\clef G
\time 3/4
d''8[ g''] bf''
\textSpannerUp \override TextSpanner #'bound-details #'left #'text =
\markup\italic {(Opt. 8va) }
\override TextSpanner #'bound-details #'right #'text =
\markup { \draw-line #'(0 . -1) }
d''4--\upbow\startTextSpan( g''8--) |
\time 4/4
bf''4 g'' a''2~ |
a''2.~\_\markup\italic{molto rit.} a''8. a'16\!\stopTextSpan
|
\textSpannerUp
\override TextSpanner #'outside-staff-priority = #500
\override TextScript #'outside-staff-priority = #100
\override TextSpanner #'bound-details #'left #'text =
\markup\italic {(One stand opt. 8va) }
\override TextSpanner #'bound-details #'right #'text =
\markup { \draw-line #'(0 . -1) }
cs''1~^\markup\italic{bow freely, staggering bows}
\downbow\startTextSpan\ |
cs''1~ |
cs''1~\fermata |
cs''8\stopTextSpan\! r8 r4 r2 |
\bar |.
}
\score {
\Test
}
%%% END %%%
Seems to be a popular question these days ;-)
http://lists.gnu.org/archive/html/lilypond-user/2007-09/msg00448.html
To the GDP team: there seems to be a general principle here about
using outside-staff-priority to control the *stacking order* of stuff
that seems to be difficult for users to extract from the docs. Which
is too bad because if you know that outside-staff-priority controls
stacking order, then you've got hold of a very general and powerful
layout principle that works in a very predictable and visible way.
I can write a paragraph on stacking order if somebody can suggest the
appropriate *section* to stick it in. (Even better might be for Graham
to stick write new paragraph on stacking order with
outside-staff-priority in his magic jar of action items and mail me
when GDP progresses to the appropriate chapter / section.)
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
lowering chord symbols
Sometimes, apparently due to the height of notes and markups above the staff, my chord symbols print too far above the staff to read easily. Is there a way to either raise an individual staff, lower chord symbols on one line only, standardize the distance between chord symbols and staff regardless of such high notes and markups, or otherwise solve this problem? Thanks, Ruth ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Method of including PDF document information in LilyPond files?
Dear LilyPonders,
Is there a way to include PDF metainfo (document information) in LilyPond
documents? For example, I would like to do something like the following:
\header {
title = Test title
subject = Description of title
maintainer = John Zaitseff
}
and then have LilyPond and/or my own Scheme code generate the following
pdfmark PostScript to be included in the output PS file:
[
/Title (Test title)
/Subject (Description of title)
/Author (John Zaitseff)
/DOCINFO
pdfmark
Of course, I'd like the actual contents of the pdfmark output to be
generated from the header:title, header:subject and header:maintainer
properties.
Yours truly,
John Zaitseff
--
John Zaitseff,--_|\The ZAP Group
Phone: +61 2 9643 7737 / \ Sydney, Australia
E-mail: [EMAIL PROTECTED] \_,--._* http://www.zap.org.au/
v
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Scheme code for extracting LilyPond header properties?
Dear LilyPonders,
I am not a particular expert on Scheme, hence my request for help.
I am trying to write a new version of tagline that includes the
particular document maintainer's name and e-mail address. Thus, I
have the following in my header:
\header {
...
maintainer = John Zaitseff
maintainerEmail = [EMAIL PROTECTED]
}
and I redefine tagline as:
tagline = \markup {
\teeny
\override #'(word-space . 0)
\line {
% [... other information ...]
Document maintained by
\fromproperty #'header:maintainer
.
}
}
So far, so good. What I would like to do, however, is to replace
the \fromproperty #'header:maintainer with something like:
\with-url #mailto:[EMAIL PROTECTED]
\fromproperty #'header:maintainer
except that I would like to extract the actual e-mail address from
header:maintainerEmail: something like:
\with-url #(string-append mailto:; XXX)
It's the XXX that I'm having problems with! How do I extract the
header:maintainerEmail property as a Scheme string? Any help would
be much appreciated!
Yours truly,
John Zaitseff
--
John Zaitseff,--_|\The ZAP Group
Phone: +61 2 9643 7737 / \ Sydney, Australia
E-mail: [EMAIL PROTECTED] \_,--._* http://www.zap.org.au/
v
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
