Hi,
using Lilypond, I can use transparency and resolution _separately_, but
unfortunately not together.
These two command lines work fine:
d:/resources/LilyPond/usr/bin/lilypond -dresolution=169.333 --png --pdf
prc44_3.ly
d:/resources/LilyPond/usr/bin/lilypond -dpixmap-format=pngalpha --png --p
hi squadders
I've done 40-50 so far, but getting tired now - hope someone can continue
tomorrow.
good night!
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/verifying-issues-Fixed-2-19-0-tp157269.html
Sent from the Bugs mailing list archive at Nabble.com.
__
David Kastrup gnu.org> writes:
>
> Matthias Steup arcor.de> writes:
>
> > Lilypond-book seems to be broken in lilypond version 18.0. The score runs
> > beyond the margin of the page. Up to 16.2 everything was working fine. I
> > work with MikTex and lilypond.
>
> Are you sure that Lilypond-bo
2014/1/6 Esa Erola
>
>
> The snippet putting bar numbers on odd bars does not seem to work on 2.16.0
> - it worked on an earlier release
>
>
> \context {
> \Score
> barNumberVisibility = #all-bar-numbers-visible
> barNumberVisibility = #(lambda (n) (= (modulo n 2) 1))
> \override
The snippet putting bar numbers on odd bars does not seem to work on 2.16.0
- it worked on an earlier release
\context {
\Score
barNumberVisibility = #all-bar-numbers-visible
barNumberVisibility = #(lambda (n) (= (modulo n 2) 1))
\override BarNumber #'break-visibility = #all
Matthias Steup writes:
> Lilypond-book seems to be broken in lilypond version 18.0. The score runs
> beyond the margin of the page. Up to 16.2 everything was working fine. I
> work with MikTex and lilypond.
Are you sure that Lilypond-book is able to find LaTeX in the system PATH?
--
David Kast
Lilypond-book seems to be broken in lilypond version 18.0. The score runs
beyond the margin of the page. Up to 16.2 everything was working fine. I
work with MikTex and lilypond.
Here an example code:
\documentclass[11pt,a5paper,footinclude=true,headinclude=true]{scrbook}
\usepackage[T1]{fontenc}
Hi,
In lexer.ll, there is some code that checks the version specified in the
.ly file against a hard-coded variable oldest-version and issues a
warning (well, a non-fatal error message) that the file needs to be
updated. However, "oldest-version" has been set to 2.7.38 since 2006 or
so. Perha