Dear developers,
are there any plans to build a Docker image for building LilyPond? It would
be a much more lightweight solution than a VirtualBox image, so I think
contributors would be grateful.
Thanks in advance,
Dénes Harmath, lead of the Hungarian localization team
> I'm not top posting.
alignBelowContext seems to be ignored in this case:
\score { <<
\new Voice = melody {
\relative c' {
c4
<<
{ c8 e }
\new Staff = ossiaStaff {
\new Voice = splitpart { c4 }
}
>>
c4 c | c
}
}
\new L
There should be an option in lilypond to invoke convert-ly on the files before
compiling. This way, the user doesn't have to care with updating the syntax of
her files manually; when updating LilyPond, files will be up to date
automatically when compiled.
Some warning messages are not prefixed with 'warning:', but they should to be
more easily parsable and percievable.
So far, I discovered the following warnings:
No such instrument: contrabassoon
Barcheck failed got 69 expect 123
But I'm sure there are more.
__
> Could you run lilypond --verbose on your file? That still looks a lot like
#811; perhaps I'll Fwd it to the ghostscript team.
The relevant section of the output of lilypond --verbose (2.12.2):
Converting to `./ő.pdf'...
Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841
On 2009.08.04., at 15:06, Valentin Villenave wrote:
> Er, I think it fails no matter the filename:
> http://code.google.com/p/lilypond/issues/detail?id=811
> Regards,
> Valentin
No, it otherwise works perfectly on an Intel Mac. It only fails always with the
kind of mentioned characters. (Strange
Some special characters (e.g. ő or đ) in the output filename cause gs to fail on
OS X (10.5) and Linux (Kubuntu 8.10), under LilyPond 2.12.2 and 2.13.3 also.
Converting to `./ő.pdf'...
`gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
-dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
On 2009.07.23., at 21:58, Mark Polesky wrote:
> This suggests that the command is derived from "hideNotes":
> "un" + "hideNotes" = "unHideNotes"
That logic isn't applied in the case of \set and \unset. That's why I am (and
maybe also others are) always confused.
Sorry for nitpicking about syntax
> I'm not top posting.
% When a connected arpeggio spans multiple voices in one staff after a bar line,
they collide.
\version "2.12.2"
\paper {
ragged-right = ##t
}
\new PianoStaff <<
\new Staff {
\set PianoStaff.connectArpeggios = ##t
R1
The current syntax is misleading: the expression "un hide" doesn't exist but
only "unhide". The capitalization should reflect this correctly.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
When specifying both -dpreview and -dbackend=svg command line arguments,
lilypond fails.
thSoft-MacBook:music thsoft$
/Applications/LilyPond.app/Contents/Resources/bin/lilypond -dpreview
-dbackend=svg clefs.ly
GNU LilyPond 2.13.0
Processing `clefs.ly'
Parsing...
Interpreting music...
Preprocessin
11 matches
Mail list logo