Am 08.12.2014 07:53, schrieb Knut Petersen:
Why does lilypond think it is a good idea to print a space at origin
using an otherwise unused font?
This is a very good question. IIRC, it comes from headers or footers
added by lilypond. It is obviously not possible to *completely*
disable that, h
On 05.12.2014 20:51, Werner LEMBERG wrote:
Now I thought a bit and added "-dSubsetFonts=false" to the gs
parameter list in backend-library.scm. I also changed
lilyponddefs.ps to include white-on-white print commands for all the
emmentaler glyphs used in the four examples (hint: grep, sed, sort &
Hi,
Since you are naming your staves as "right" and "left" in the \score block,
then you must use \change Staff = "right" or \change Staff = "left" when
changing staves, instead of \change Staff = up. So on line 23 simply
exchange the word up for "right" (with the commas).
Best,
Gilberto
--
Vi
It's the barline check between the end of the \repeat block and the start of
\alternative. It seems a comment is OK there but not a barline check.
Trevor
- Original Message -
From: Do something Artistic
To: lilypond-user@gnu.org
Sent: Sunday, December 07, 2014 10:26 PM
Subj
Hi,
1) you should put it into one music expression by enclosing everything in braces
{} (but that was not the problem).
2) You had a bar check outside of your repeat syntax. This was interpreted as:
{ repeat music expression } + extra music (bar check |) + { alternative music
expression }
That way
Trying to create a second ending in a piano score (am using Frescobaldi) found
the documentation and thought I had followed it to the letter but am getting an
error; unexpected \alternative {.
I can't seem to figure out why. I know this is a long clip but I really don't
know what is relevant
P.P.S.: I've read that the lyric-extender-interface has a user settable
property called "next":
|next| (graphical (layout) object)
Object that is next relation (e.g., the lyric syllable following an
extender).
but I have no idea how to deal with that... :(
_
Hi everybody,
does anyone know how to make the LyricExtender ignore/skip one or more
syllables? I.e. the extender line should *not* stop at the next syllable:
(preview image)
For the above picture, I've used a workaround:
% ---
\version "2.
Hi everybody,
does anyone know how to make the LyricExtender ignore/skip one or more
syllables? I.e. the extender line should *not* stop at the next syllable:
(preview image)
For the above picture, I've used a workaround:
% ---
\version "2.
P.P.S.: I've read that the lyric-extender-interface has a user settable
property called "next":
|next| (graphical (layout) object)
Object that is next relation (e.g., the lyric syllable following an
extender).
but I have no idea how to deal with that... :(
_
A friend retired his Mac G5 and gave it to me. I have installed Debian on it
and wanted to get LilyPond installed as well. In the download section of
lilypond.org there was a 64-bit Linux binary and a PPC binary. It seems that
the PPC binary is 32-bit as I get this when running the install sc
11 matches
Mail list logo