On Wed 22 Jun 2011, 18:52 Colin Campbell wrote:
> overridden if the tag exists in the destination file. Where a .ly
> file already has the tagline set, it cancels the imported one. To
Yes, right, imported tagline overrides default one only .)
This is enough for most (all?) of tests however, isn
Comment #8 on issue 1502 by k-ohara5...@oco.net: Document information in
PDF headers requires escapes for accented characters
http://code.google.com/p/lilypond/issues/detail?id=1502
Sounds like cut-and-paste did not result in a proper UTF8-encoded .ly file
for Phil. I get a good PDF file o
On 11-06-22 06:52 PM, Colin Campbell wrote:
After a bit of testing, it seems that settings in \included files,
however the include is done (very smooth trick, that, David!), are
overridden if the tag exists in the destination file. Where a .ly
file already has the tagline set, it cancels t
On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
On Wed 22 Jun 2011, 11:53 Graham Percival wrote:
ok, how about this? Your script should:
echo "\header { tagline = ##f } "> /tmp/lilypond-no-header.ly
. o O ( \\header, of course )
lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --
Comment #3 on issue 1685 by paconet@gmail.com: links to
spanish "changes" manual
http://code.google.com/p/lilypond/issues/detail?id=1685
Thanks. The attached (stupid) patch makes a
Documentation/es/out-www/changes directory to appear, with an HTML
translated Changes manual in it. The
I came across a further reference, in Richard Rastall's The Notation of
Western Music (2nd edition), if you look at the main index reference under
"accidental" (I'd quote the page number, but I don't have the book with me),
you'll see that he explicitly refers to cancelling single accidentals. He i
Comment #2 on issue 1685 by percival.music.ca: links to spanish "changes"
manual
http://code.google.com/p/lilypond/issues/detail?id=1685
I would begin by looking at
Documetnation/es/GNUmakefile
Documentation/GNUmakefile
What's the difference between how changes.tely is treated, vs. how o
Comment #6 on issue 1287 by pkx1...@gmail.com: Notation 2.9 Ancient
notation does not follow doc policy
http://code.google.com/p/lilypond/issues/detail?id=1287
No you are right, I am not. It's not forgotten though.
___
bug-lilypond mailing list
bu
2011/6/20 Federico Bruni :
> Hi,
>
> the link to 2.12 Docs redirects to 2.14 docs:
> http://lilypond.org/all.html
I see it correctly pointing to 2.12, so it seems that somebody has
fixed it. Right?
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
_
Comment #1 on issue 1685 by paconet@gmail.com: links to
spanish "changes" manual
http://code.google.com/p/lilypond/issues/detail?id=1685
We are generating a Documentation/es/out-www/changes.texi from
Documentation/es/changes.tely.
Also, we are generating a translated Documentation/out
Updates:
Status: Verified
Comment #38 on issue 1562 by philehol...@googlemail.com: using \sans on
Windows gives 'gs' error (2.13.53) fails to compile
http://code.google.com/p/lilypond/issues/detail?id=1562
(No comment was entered for this change.)
___
Comment #8 on issue 1219 by philehol...@googlemail.com: Broken tie may
become a too small dot
http://code.google.com/p/lilypond/issues/detail?id=1219
The regtest tie-broken.ly illustrates this sort of behaviour quite well.
See heavily enlarged image with vestigial tie on the top note of th
Comment #37 on issue 1562 by lemniska...@gmail.com: using \sans on Windows
gives 'gs' error (2.13.53) fails to compile
http://code.google.com/p/lilypond/issues/detail?id=1562
I tried it. { c1^\markup { \sans "word" } } compiles without errors using
2.14.0 on Win7 + SP1.
:)
__
An interesting question. I can't say I have. The trouble is, is that as soon
as you get a both a flattened and a sharpened note within the same bar, you
are likely to be looking at something fairly recent. The original bug
observation, too, referred to the flattened note being in the key signature.
On Wed 22 Jun 2011, 11:53 Graham Percival wrote:
> ok, how about this? Your script should:
> echo "\header { tagline = ##f } " > /tmp/lilypond-no-header.ly
. o O ( \\header, of course )
> lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --png bug.ly
> convert bug.png -trim bug-upload.
Hans,
From: Henk Verhaar [hjmverh...@googlemail.com] on behalf of Henk Verhaar
[h...@stichtsend.xs4all.nl]
Sent: 21 June 2011 15:10
To: Hans Aberg
Cc: bug-lilypond@gnu.org bug; James Lowe
Subject: Re: bug report on 2.15.2 Mac OS X Intel version
Hey, I just
On Wed, Jun 22, 2011 at 01:17:25PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > ok, how about this? Your script should:
> > echo "\header { tagline = ##f } " > /tmp/lilypond-no-header.ly
> > lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --png bug.ly
>
> You can write
Graham Percival writes:
> On Wed, Jun 22, 2011 at 10:05:51AM +0300, Dmytro O. Redchuk wrote:
>> On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
>> > Could you write a short shell script to do this? i.e. using
>> > lilypond -e ...
>> > to remove the tagline (maybe that's already in LSR),
>> >
On Wed, Jun 22, 2011 at 10:05:51AM +0300, Dmytro O. Redchuk wrote:
> On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> > Could you write a short shell script to do this? i.e. using
> > lilypond -e ...
> > to remove the tagline (maybe that's already in LSR),
> > and then call convert automatical
On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> On Tue, Jun 21, 2011 at 12:52:01PM +0300, Dmytro O. Redchuk wrote:
> > In such cases I add
> > \header { tagline = "" }
> > to a source file and then:
> >
> > lilypond --png test.ly
> > convert test.png -trim test-trim.png
>
> Excellent!
>
20 matches
Mail list logo
