Re: Pagination
On 10 June 2014 07:15, Charles Berger charlesberge...@yahoo.fr wrote: Sorry for my english Thank's for your answer I try \tuplet instead of \times and it's ok Thank you Charles Berger FYI there is a French-speaking LilyPond user mailing list: lilypond-user...@gnu.org (notice the -fr), where you can ask questions in French. Infos : https://lists.gnu.org/mailman/listinfo/lilypond-user-fr Archives : http://lilypond-french-users.1298960.n2.nabble.com/ Cheers, Xavier -- Xavier Scheuer x.sche...@gmail.com ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: changing the appearance for single dots in fret boards
Am 08.06.2014 02:49, schrieb Thomas Morley: 2014-06-07 17:33 GMT+02:00 Marc Hohl m...@hohlart.de: Am 07.06.2014 10:02, schrieb Pierre Perol-Schneider: 2014-06-06 9:59 GMT+02:00 Marc Hohl m...@hohlart.de mailto:m...@hohlart.de: I have some fret diagrams where one dot is placed and removed according to the underlying rhythm, so it would be great to either change its color or put it in parentheses. Hallo Marc, See discussion here : http://www.lilypondforum.de/index.php?topic=1186.msg6498#msg6498 Hi Pierre, thanks for the link! I wasn't aware of 'inverted' as an optional forth argument to place-fret. It looks as if this feature is not documented (it is used in input/regression/fret-diagrams-fingering.ly, though) What about the feature request and a possible patch for using 'parenthesized'? Is this still work-in-progress? I'm cc'ing to Harm, I think he knows best about the patch status. Hi Marc, yes I'm working on it. http://code.google.com/p/lilypond/issues/detail?id=3930 is meant to prepare the final patch for http://code.google.com/p/lilypond/issues/detail?id=2752 Though, it still needs some work before it does the job properly _and_ I'll have to add documentation about it. That's great – thanks for your work! Regards, Marc Cheers, Harm ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
- Original Message -
From: Daniel Rosen drose...@gmail.com
To: lilypond-user@gnu.org
Sent: Monday, June 09, 2014 9:35 PM
Subject: One of these things just isn't the same
\version 2.19.7
{ f4- fis- fes- f!- }
Why is the accent on the final note (the one with the natural sign before
it) so much farther away from its parent NoteHead than the others? Is this
a known issue?
DR
Well, the obvious and simple answer is that it's to allow space for the
natural sign. None of the other accidentals have strokes on the left of the
glyph.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triangle noteheads
2014-06-09 22:42 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
myHead =
#(define-music-function (parser location music)(ly:music?)
(if (music-is-of-type? music 'event-chord)
#{
\override NoteHead.stencil = #(new-head doThin)
#music
#}
#{
\tweak NoteHead.stencil #(new-head doThin)
#music
#}))
Hi Harm,
I suspect you wanted to write : *\once*\override NoteHead.stencil =
#(new-head doThin)
in myHead definition, didn't you ?
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
- Original Message -
From: Phil Holmes m...@philholmes.net
To: Daniel Rosen drose...@gmail.com; lilypond-user@gnu.org
Sent: Tuesday, June 10, 2014 8:25 AM
Subject: Re: One of these things just isn't the same
- Original Message -
From: Daniel Rosen drose...@gmail.com
To: lilypond-user@gnu.org
Sent: Monday, June 09, 2014 9:35 PM
Subject: One of these things just isn't the same
\version 2.19.7
{ f4- fis- fes- f!- }
Why is the accent on the final note (the one with the natural sign before
it) so much farther away from its parent NoteHead than the others? Is
this a known issue?
DR
Well, the obvious and simple answer is that it's to allow space for the
natural sign. None of the other accidentals have strokes on the left of
the glyph.
--
Phil Holmes
That is: on the right. Never was very good with left and right.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Pagination
Le 10 juin 2014 07:04, Charles Berger charlesberge...@yahoo.fr a écrit : Le journal de Lilypond me dit: Démarrage lilypond-windows.exe 2.19.7 [probleme de pagination.ly]... Traitement de « E:/Solfege/Exercices/probleme de pagination.ly » Bonjour Charles, Même remarque : il se pose un gros problème de métrique dans ton fichier ; dès la mes.4 la valeur des mesures change selon les voix et LilyPond ne peut s'y retrouver. LilyPond est très très sensible à cela, il faut impérativement que la valeur des mesures de chaque voix soit symétrique pour éviter ce genre de mise en page surprise. Pierre ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: triangle noteheads
2014-06-10 9:50 GMT+02:00 Pierre Perol-Schneider
pierre.schneider.pa...@gmail.com:
2014-06-09 22:42 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
myHead =
#(define-music-function (parser location music)(ly:music?)
(if (music-is-of-type? music 'event-chord)
#{
\override NoteHead.stencil = #(new-head doThin)
#music
#}
#{
\tweak NoteHead.stencil #(new-head doThin)
#music
#}))
Hi Harm,
I suspect you wanted to write : \once\override NoteHead.stencil = #(new-head
doThin)
in myHead definition, didn't you ?
Yep, an oversight.
Here the next version.
Adding functionality for 'stem-attachment, extending general
functionality, making it more robust, adding comments:
\version 2.18.0
#(define (new-head type)
;; Returns a new stencil for NoteHead, specified via `type'
;; `type' is supposed to be a string containing two things:
;; the first letter after the dot and the actual type from the note-heads
;; listed in NR A.8 The Feta font
;; example: noteheads.d1faThin should be transformed to dfaThin as value for
;; `type'
(lambda (grob)
(if (or (not (string? type)) (string-null? type))
(ly:note-head::print grob)
(let* (;; not every note-head has a glyph for whole or even longer notes
;; as a fall-back, use half note glyph
(duration (max 1 (ly:grob-property grob 'duration-log)))
(head (format #f noteheads.~a~a~a
(string-take type 1)
duration
(string-drop type 1)))
(stil (ly:font-get-glyph
(ly:grob-default-font grob)
head)))
(if (ly:stencil-empty? stil)
(begin
(ly:warning Unknown NoteHead: ~a, ignoring. head)
(ly:note-head::print grob))
stil)
%% adjusts stem-adjustment for note-heads of type doThin
%% other note-head-glyphs may need different settings
adjustStemAttachment =
\once \override NoteHead.stem-attachment =
#(lambda (grob)
(let* ((stem (ly:grob-object grob 'stem))
(stem-dir (ly:grob-property stem 'direction)))
(cons 1 (if (= stem-dir 0) -1 0.75
my-head =
#(define-scheme-function (parser location strg) (string?)
(define-music-function (parser location music)(ly:music?)
(if (music-is-of-type? music 'event-chord)
#{
\once \override NoteHead.stencil = #(new-head strg)
#music
#}
#{
\tweak NoteHead.stencil #(new-head strg)
#music
#})))
%% See comment in (new-head type) how to specify the type
doThinHead = \my-head ddoThin
faThinHead = \my-head dfaThin
\relative c' {
\adjustStemAttachment
\doThinHead
c'2
\adjustStemAttachment
\doThinHead
c,2
\adjustStemAttachment
\doThinHead
c e g4
c
\doThinHead
e
\doThinHead
\tweak duration-log #1
g
4
\adjustStemAttachment
\faThinHead
c
e
g
4
}
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: One of these things just isn't the same
-Original Message-
From: Phil Holmes [mailto:m...@philholmes.net]
Sent: Tuesday, June 10, 2014 4:00 AM
To: Phil Holmes; Daniel Rosen; lilypond-user@gnu.org
Subject: Re: One of these things just isn't the same
- Original Message -
From: Phil Holmes m...@philholmes.net
To: Daniel Rosen drose...@gmail.com; lilypond-user@gnu.org
Sent: Tuesday, June 10, 2014 8:25 AM
Subject: Re: One of these things just isn't the same
- Original Message -
From: Daniel Rosen drose...@gmail.com
To: lilypond-user@gnu.org
Sent: Monday, June 09, 2014 9:35 PM
Subject: One of these things just isn't the same
\version 2.19.7
{ f4- fis- fes- f!- }
Why is the accent on the final note (the one with the natural sign before
it) so much farther away from its parent NoteHead than the others? Is
this a known issue?
DR
Well, the obvious and simple answer is that it's to allow space for the
natural sign. None of the other accidentals have strokes on the left of
the glyph.
Well, I suppose that makes sense, but it still looks Extremely Ugly to me. Does
anyone else agree?
That is: on the right. Never was very good with left and right.
Understandable. I still have to look at my hands sometimes. :-P
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: How to separate these voices??
Minor, but in the interest of clarity:
\score {
\new Staff { \global \guitar } % Don't need ...
\layout { }
}
Knute Snortum
(via Gmail)
On Mon, Jun 9, 2014 at 11:38 AM, st...@linuxsuite.org wrote:
Thanks for the hints. I've looked at them and have come up with the
following which looks a lot like the original. F. Tarrega's transcription
of
Beethoven minuet ( start of the trio ). Not sure if its the best solution
though...
http://imslp.org/wiki/6_Minuets,_WoO_10_%28Beethoven,_Ludwig_van%29
\version 2.18.0
voiceone = \relative c' {
\new Voice { \voiceOne e2. | }
\new Voice { \voiceThree \stemDown \override NoteColumn.force-hshift =
#1.1
gis, 8[ b] gis[ b] gis[ b] | }
}
voicetwo = \relative c {
e, e' 4 dis' cis |
}
guitar = { \voiceone } \\ { \voicetwo }
global = {
\time 3/4
\key e \major
\clef G_8
}
\score {
\new Staff { \global \guitar }
\layout { }
}
thanx - steve
2014-06-09 19:41 GMT+02:00 David Kastrup d...@gnu.org:
st...@linuxsuite.org writes:
Ooops sorry.
\version 2.18.0
voiceone = \relative c' {
{ e2. | }
\\
{ gis,8[ b] gis[ b] gis[ b] | }
}
voicetwo = \relative c {
e, e' 4 dis' cis |
}
guitar = { \voiceone } \\ { \voicetwo }
global = {
\time 3/4
\key e \major
\clef G_8
}
\score {
\new Staff { \global \guitar }
\layout { }
}
Nesting several \\ at different levels does not work. This is one case
where you are better off using explicit voices anyway since you can then
finetune the \voiceXxx things using for shifting voices apart in the
case of collision. That gives you
I'm not overly convinced in how it is typeset, but then I don't have a
better suggestion after juggling with different presets.
--
David Kastrup
Here my code as well.
Second example gives same output as David's
Third example shows strange behaviour of the Dot. IMHO, it should flip
back to the NoteHead. There's enough space.
A bug?
\version 2.18.0
global = {
\time 3/4
\key e \major
\clef G_8
}
\new Staff
\global
\new Voice \relative c' { \voiceOne e2. }
\new Voice
\relative c' {
\voiceFour
\override NoteColumn.force-hshift = #1.1
gis8[ b] gis[ b] gis[ b]
}
\new Voice \relative c' { \voiceTwo e,, e' 4 dis' cis }
\new Staff
\global
\new Voice \relative c' { \voiceOne e2. }
\new Voice \relative c' { \voiceThree gis8[ b] gis[ b] gis[ b] }
\new Voice \relative c' { \voiceTwo e,, e' 4 dis' cis }
\new Staff
\mark bug with Dots?
\global
\new Voice \relative c' { \voiceOne e2. }
\new Voice
\relative c' {
\voiceThree
\once \override NoteColumn.force-hshift = #1.5
gis8[ b] gis[ b] gis[ b]
}
\new Voice \relative c' { \voiceTwo e,, e' 4 dis' cis }
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
Well, I suppose that makes sense, but it still looks Extremely Ugly to
me. Does anyone else agree?
I think it's fine as a default behavior. What would you want it to do?
Knute Snortum
(via Gmail)
On Tue, Jun 10, 2014 at 5:35 AM, Daniel Rosen drose...@gmail.com wrote:
-Original Message-
From: Phil Holmes [mailto:m...@philholmes.net]
Sent: Tuesday, June 10, 2014 4:00 AM
To: Phil Holmes; Daniel Rosen; lilypond-user@gnu.org
Subject: Re: One of these things just isn't the same
- Original Message -
From: Phil Holmes m...@philholmes.net
To: Daniel Rosen drose...@gmail.com; lilypond-user@gnu.org
Sent: Tuesday, June 10, 2014 8:25 AM
Subject: Re: One of these things just isn't the same
- Original Message -
From: Daniel Rosen drose...@gmail.com
To: lilypond-user@gnu.org
Sent: Monday, June 09, 2014 9:35 PM
Subject: One of these things just isn't the same
\version 2.19.7
{ f4- fis- fes- f!- }
Why is the accent on the final note (the one with the natural sign
before
it) so much farther away from its parent NoteHead than the others? Is
this a known issue?
DR
Well, the obvious and simple answer is that it's to allow space for the
natural sign. None of the other accidentals have strokes on the left
of
the glyph.
Well, I suppose that makes sense, but it still looks Extremely Ugly to me.
Does anyone else agree?
That is: on the right. Never was very good with left and right.
Understandable. I still have to look at my hands sometimes. :-P
DR
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
Hi Daniel,
On Tue, Jun 10, 2014 at 7:35 AM, Daniel Rosen drose...@gmail.com wrote:
Well, I suppose that makes sense, but it still looks Extremely Ugly to me.
Does anyone else agree?
I don't know about extremely ugly...
In any case, you can get the accent to move up. Here are two ways:
{
f4- fis- fes-
f!-\tweak horizon-padding #0 - % accent still centered on the notehead
f!-\offset X-offset #0.1 - % move the accent slightly to the right
}
HTH,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
Daniel Rosen drose...@gmail.com writes: That is: on the right. Never was very good with left and right. Understandable. I still have to look at my hands sometimes. :-P Reminds me of that high school test where I used the right hand rule to get the signs of cross products right. And then realized that using the left hand for efficiency because the right was occupied with writing was not a good idea. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: One of these things just isn't the same
On Tue, Jun 10, 2014 at 10:18 AM, David Nalesnik david.nales...@gmail.com wrote: Hi Daniel, On Tue, Jun 10, 2014 at 7:35 AM, Daniel Rosen drose...@gmail.com wrote: Well, I suppose that makes sense, but it still looks Extremely Ugly to me. Does anyone else agree? I don't know about extremely ugly... To clarify: in the context you provide it looks rather out-of-place, but for an isolated instance I think it's OK. Perhaps there should be an option to allow accents to shift right a tiny bit in the case of a collision (i.e., to match the value of horizon-padding which would result in vertical displacement). I prefer the look gotten with \offset X-offset #0.1. --David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
RE: One of these things just isn't the same
On Tue, Jun 10, 2014 at 10:18 AM, David Nalesnik david.nales...@gmail.commailto:david.nales...@gmail.com wrote: Hi Daniel, On Tue, Jun 10, 2014 at 7:35 AM, Daniel Rosen drose...@gmail.commailto:drose...@gmail.com wrote: Well, I suppose that makes sense, but it still looks Extremely Ugly to me. Does anyone else agree? I don't know about extremely ugly... To clarify: in the context you provide it looks rather out-of-place, but for an isolated instance I think it's OK. Perhaps there should be an option to allow accents to shift right a tiny bit in the case of a collision (i.e., to match the value of horizon-padding which would result in vertical displacement). I prefer the look gotten with \offset X-offset #0.1. --David That’s probably what I would have suggested. DR ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Instrument in score block?
Is it possible to define headers (like instrument) in the score context? I've
tried, and nothing comes up.
Background: I play trumpet and use Lilypond to transpose music. You have parts
in F, A, E flat, whatever, and my trumpets are tuned in B flat or C.
So what I do is I write the score in an lyi file and include that in a ly file
that does the transposing.
So I get something like below. Two book parts, one with suffix C (so the
filename is score-C.pdf) and one with suffix Bes. In the \score I do the
transposing. And of course because I do the transposing there, I can only set
the instrument there. It is important that you specify which trumpet to take,
otherwise you're a full note off ofcourse.
But as I said, this does not work. Are there other options?
\book {
\bookOutputSuffix C
\score {
\transpose c bes, { \partI }
\header { instrument = Trumpet in C }
\layout { ragged-last = ##f }
} %% \score
} %%\book
\book {
\bookOutputSuffix Bes
\score {
\transpose bes bes { \partI }
\header { instrument = Trumpet in Bes }
\layout { ragged-last = ##f }
} %% \score
} %%\book
Regards,
Maarten
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Instrument in score block?
Maarten Deen md...@xs4all.nl writes:
Is it possible to define headers (like instrument) in the score
context? I've tried, and nothing comes up.
Background: I play trumpet and use Lilypond to transpose music. You
have parts in F, A, E flat, whatever, and my trumpets are tuned in B
flat or C.
So what I do is I write the score in an lyi file and include that in a
ly file that does the transposing.
\book {
\bookOutputSuffix C
\score {
\transpose c bes, { \partI }
\header { instrument = Trumpet in C }
\layout { ragged-last = ##f }
} %% \score
} %%\book
\book {
\bookOutputSuffix Bes
\score {
\transpose bes bes { \partI }
\header { instrument = Trumpet in Bes }
\layout { ragged-last = ##f }
} %% \score
} %%\book
Not a complete working example. Anything wrong with
partI = { c'1 }
\book {
\bookOutputSuffix C
\header { instrument = Trumpet in C }
\score {
\transpose c bes, { \partI }
\layout { ragged-last = ##f }
} %% \score
} %%\book
\book {
\bookOutputSuffix Bes
\header { instrument = Trumpet in Bes }
\score {
\transpose bes bes { \partI }
\layout { ragged-last = ##f }
} %% \score
} %%\book
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Guile error starts occurring all of a sudden
I have been using the command(?) #(include-special-characters) all morning and yesterday. Then all of a sudden I start getting this error: Parsing... /Users/pat/Documents/LilyPond/tmp/test_guile.ly:3:2: error: GUILE signaled an error for the expression beginning here # (include-special-characters) Unbound variable: include-special-characters I get this error with the following lilypond file, called test_guile.ly: \version 2.18.2 #(include-special-characters) Ordinarily, I run jEdit, but I also get the error when running lilypond from the command line: $ lilypond -V test_guile.ly Log level set to 287 GNU LilyPond 2.18.2 . . . Using `nederlands' note names... [test_guile.lyBacktrace: In unknown file: ?: 0* [lilypond-main (test_guile.ly)] In /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/lily.scm: 965: 1* (let* ((failed #)) (if (ly:get-option #) (begin #)) ...) 965: 2* [lilypond-all (test_guile.ly)] 978: 3 (let* ((failed #) (separate-logs #) (ping-log #) ...) (gc) ...) 990: 4* [for-each #procedure #f (x) (test_guile.ly)] In unknown file: ?: 5* [#procedure #f (x) test_guile.ly] In /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/lily.scm: 992: 6* (let* (# # #) (if separate-logs #) (if ping-log #) ...) 1003: 7* [lilypond-file #procedure #f (key failed-file) test_guile.ly] 1038: 8 [catch ly-file-failed #procedure #f () #procedure #f (x . args)] In unknown file: ?: 9* [#procedure #f ()] In /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/scm/lily.scm: 1039: 10* [ly:parse-file test_guile.ly] In test_guile.ly: 3: 11* (include-special-characters) test_guile.ly:3:1: In expression (include-special-characters): test_guile.ly:3:1: Unbound variable: include-special-characters My OS is OSX 10.7.5. I ran Disk Utility (verify disk) on my hard disk (where /Applications lives) and got a clean bill-of-health. When I first encountered the error, I was still running LilyPond 2.18.0, but I have downloaded and installed version 2.18.2 and still get the error. Does anyone have any clue for me? ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Instrument in score block?
On 2014-06-10 21:52, David Kastrup wrote: Not a complete working example. Anything wrong with Heh, that simple. Makes sense, the header block outside the score block. Thanks. Regards, Maarten ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Guile error starts occurring all of a sudden
2014-06-10 22:16 GMT+02:00 Patrick or Cynthia Karl pck...@mac.com:
I have been using the command(?) #(include-special-characters) all morning
and yesterday. Then all of a sudden I start getting this error:
Parsing...
/Users/pat/Documents/LilyPond/tmp/test_guile.ly:3:2: error: GUILE signaled an
error for the
expression beginning here
#
(include-special-characters)
Unbound variable: include-special-characters
I get this error with the following lilypond file, called test_guile.ly:
\version 2.18.2
#(include-special-characters)
Hi,
you need to do it in \paper
\paper { #(include-special-characters) }
works for me.
Cheers,
Harm
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Guile error starts occurring all of a sudden
On Jun 10, 2014, at 3:32 PM, Thomas Morley wrote:
I get this error with the following lilypond file, called test_guile.ly:
\version 2.18.2
#(include-special-characters)
Hi,
you need to do it in \paper
\paper { #(include-special-characters) }
works for me.
Cheers,
Harm
Doh! Many thanks.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
More questions about using Lilypond for guitar music
Thank you for the kind person who helped me out the last time I was trying to get to grips with Lilypond and guitar music. I suspect these two are more challenging. 1. Is it possible at all to combine bends with hammer-on / pull-offs at all? (e.g., a hammer-on immediately followed by a bend, or a bend-release followed immediately by a pull-off) From what I read, the answer is no - since the current implementation of bend hacks the slur, which is what is also used for hammer-on / pull-offs. (And if that is the case, is there any chance it will be addressed at some point?) 2. A common notation in guitar music is vibrato - is there any way to typeset such notation in Lilypond? Martyn ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Lyrics in a piano staff with { ... } \\ { ... } s
Someone in this lilypond user lists provides the solution to this:
Please use the following will have the lyrics properly associated to upper
(voiceOne) voice.
{\voiceOne .}\new Voice{\voiceTwo }\oneVoice
Emmanuel,
Ming.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Centered Paragraphs
My main goal is to have some simple indented paragraphs which don't
take the full width and are centered horizontally. With a syntax
something like this:
\markuplist
{
\paragraph
{
Some text
}
\vspace #0.6
\paragraph
{
Some more text
}
}
Any idea how to cause the paragraph command (from here:
http://www.lilypond.org/doc/v2.18/Documentation/extending/new-markup-list-command-definition)
to center the paragraph?
I can make it more narrow:
#(define-markup-list-command (paragraph layout props args) (markup-list?)
#:properties ((par-indent 2))
(interpret-markup-list layout props
#{
\markuplist \override-lines #'(line-width . 80)
\justified-lines
{
\hspace #par-indent #args
}
#}))
But this keeps the text on the left edge of the page. All of my
attempts have failed. The mismatch between markuplist and markup
commands is my biggest difficulty.
I tried switching to a markup command:
#(define-markup-command (paragraph layout props args) (markup?)
#:properties ((par-indent 2))
(interpret-markup layout props
#{
\markup
\fill-line
{
\override #'(line-width . 80)
\justify { \hspace #par-indent #args }
}
#}))
But this resulted in each word being on its own line.
Thanks for the help.
-Jay
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
