Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Dmytro O. Redchuk]

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't it?

-- 
  Dmytro O. Redchuk
  Bug Squad

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters

[lilypond]

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 on Windows XP so I will attach:

1) my Lilypond input file
-) skip the PostScript because it embeds a font and gets big
2) the PDF

I say the PDF is good because:
Adobe Reader shows everything perfectly in the information fields.
Sumatra's popup box uses a font that shows a box instead of the e-ogonek,  
but everything else is good.
PDF-XChange spells out all the non-ascii characters as octal escape  
sequences.


Attachments:
WinXP.ly  202 bytes
WinXP.pdf  19.7 KB
WinXP.png  4.4 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Colin Campbell]

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 the imported one.  To do 
this from a script will, after all, take some sed or perhaps python 
magic.  I'll keep at it, as much for education as for the satisfaction!


In the meantime, though, does lilypond -dpreview bug.ly not work 
adequately?


Colin



Sorry for the noise!  Mere moments after inserting my foot in my mouth, 
I ran across David's earlier message about needing two systems, which 
-dpreview doesn't provide.  The irony is all the gr4eater in that I 
rewrote a bit of that page in the CG myself!


Colin

--
The human race has one really effective weapon, and that is laughter.
-- Mark Twain

 



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Colin Campbell]

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 --png bug.ly
   convert bug.png -trim bug-upload.png

something like that.  Could you test it, then we can have a set
script for bug squad members (on linux and osx at least) to
produce great pngs for the tracker?

I would start with this:

#!/bin/bash
#
#

ly=${1:?Usage: $0 test[.ly]}

# strip extension, if any:
lynoext=${ly%%.ly}

# process test file:
echo "\\header { tagline = ##f }" | lilypond -dinclude-settings=- --png $ly

# trim PNG:
convert ${lynoext}.png -trim ${lynoext}-trim.png

# do we want to overwrite "original" PNG?
# mv ${lynoext}-trim.png ${lynoext}.png


Do we need more options? For trimming "in place" or something else?



Cheers,
- Graham

On Wed 22 Jun 2011, 13:17 David Kastrup wrote:

lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly

I does not work here; i don't know why.



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 the imported one.  To do this 
from a script will, after all, take some sed or perhaps python magic.  
I'll keep at it, as much for education as for the satisfaction!


In the meantime, though, does lilypond -dpreview bug.ly not work adequately?

Colin

--
The human race has one really effective weapon, and that is laughter.
-- Mark Twain

 



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1685 in lilypond: links to spanish "changes" manual

[lilypond]

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.  Then I can access to it locally via  
/out-www/offline-root/Documentation/changes/index.es.html


Attachments:
0001-Doc-es-build-an-HTML-Changes-manual-in-Spanish.patch  755 bytes


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

[bruys .]

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 is
talking about the rise of the notation of tonal music, and mentions Bach's
Well Tempered Clavier on the same page. The issue of whether this was
practiced in the 19th Century, to any great extent, is still open.
Regards,
Bruys

On Wed, Jun 22, 2011 at 10:27 PM, bruys .  wrote:

> 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.
> I can imagine there might have been some composers who might have used a
> single sharp when the flat was in the key signature, but a natural and sharp
> combination to cancel a flattened note that actually appeared in the same
> bar. But, finding an example of a consistent practice of that is going to be
> practically impossible.
>
> In the Ninth Edition (1955) of the Oxford Companion to Music, it mentions
> that sometimes (although "rarely") a doubled natural sign is used to cancel
> a double sharp or a double flat sign. I haven't seen that, either.
>
> Mind you, all the references seem to suggest that the combination of a
> natural sign with a sharp or flat sign is redundant, anyway, and don't
> recommend it even for setting older music. We can agree that the
> combination's use was standard practice to cancel a doubled accidental, and
> it's great to have the option available, but maybe it shouldn't be the
> default.
>
> Regards,
> Bruys
>
> On Wed, Jun 22, 2011 at 5:32 AM,  wrote:
>
>>
>> Comment #6 on issue 1701 by k-ohara5...@oco.net: default accidental style
>> prints too many 'extra' naturals
>>
>> http://code.google.com/p/**lilypond/issues/detail?id=1701
>>
>>  I believe the [wikipedia] source quoted in that message is wrong.
>>>
>>
>> Well, that is too strong a statement.  It says that "some composers put a
>> natural" in front of ges following gis.  Probably some composers do, but I
>> have never seen it.
>>
>> Has anyone seen the extra natural without a preceding double-accidental
>> consistently that it might have been standard?
>>
>>
>>
>>
>> __**_
>> bug-lilypond mailing list
>> bug-lilypond@gnu.org
>> https://lists.gnu.org/mailman/**listinfo/bug-lilypond
>>
>
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1685 in lilypond: links to spanish "changes" manual

[lilypond]

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 other  
manuals are treated?  How does the English changes/ get built, and why  
isn't the es changes/ being build in exactly the same way?



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1287 in lilypond: Notation 2.9 Ancient notation does not follow doc policy

[lilypond]

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
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: 2.12 docs link redirects to current stable

[Francisco Vila]

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

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1685 in lilypond: links to spanish "changes" manual

[lilypond]

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-www/changes.es.pdf

However, I can not find any translated html pages in  
Documentation/es/out-www/ for Changes.


So the situation is, we are generating a PDF manual and we are linking to  
it, but we are not generating an HTML manual.


Let's build one. What can I do?


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

[lilypond]

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.)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1219 in lilypond: Broken tie may become a too small dot

[lilypond]

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 the first  
line.


Attachments:
TieBroken.png  8.3 KB


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile

[lilypond]

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.

:)


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

[bruys .]

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.
I can imagine there might have been some composers who might have used a
single sharp when the flat was in the key signature, but a natural and sharp
combination to cancel a flattened note that actually appeared in the same
bar. But, finding an example of a consistent practice of that is going to be
practically impossible.

In the Ninth Edition (1955) of the Oxford Companion to Music, it mentions
that sometimes (although "rarely") a doubled natural sign is used to cancel
a double sharp or a double flat sign. I haven't seen that, either.

Mind you, all the references seem to suggest that the combination of a
natural sign with a sharp or flat sign is redundant, anyway, and don't
recommend it even for setting older music. We can agree that the
combination's use was standard practice to cancel a doubled accidental, and
it's great to have the option available, but maybe it shouldn't be the
default.

Regards,
Bruys

On Wed, Jun 22, 2011 at 5:32 AM,  wrote:

>
> Comment #6 on issue 1701 by k-ohara5...@oco.net: default accidental style
> prints too many 'extra' naturals
>
> http://code.google.com/p/**lilypond/issues/detail?id=1701
>
>  I believe the [wikipedia] source quoted in that message is wrong.
>>
>
> Well, that is too strong a statement.  It says that "some composers put a
> natural" in front of ges following gis.  Probably some composers do, but I
> have never seen it.
>
> Has anyone seen the extra natural without a preceding double-accidental
> consistently that it might have been standard?
>
>
>
>
> __**_
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/**listinfo/bug-lilypond
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Dmytro O. Redchuk]

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.png
> 
> something like that.  Could you test it, then we can have a set
> script for bug squad members (on linux and osx at least) to
> produce great pngs for the tracker?

I would start with this:

#!/bin/bash
#
#

ly=${1:?Usage: $0 test[.ly]}

# strip extension, if any:
lynoext=${ly%%.ly}

# process test file:
echo "\\header { tagline = ##f }" | lilypond -dinclude-settings=- --png $ly

# trim PNG:
convert ${lynoext}.png -trim ${lynoext}-trim.png

# do we want to overwrite "original" PNG?
# mv ${lynoext}-trim.png ${lynoext}.png


Do we need more options? For trimming "in place" or something else?


> 
> Cheers,
> - Graham

On Wed 22 Jun 2011, 13:17 David Kastrup wrote:
> lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly
I does not work here; i don't know why.

-- 
  Dmytro O. Redchuk
  Bug Squad

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

RE: bug report on 2.15.2 Mac OS X Intel version

[James Lowe]

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 discovered that the PDF file has links from notes to their entries 
in the source file (if both the PDF and the source file in Lilypond are open); 
cool! Is this a new feature, or am I just showing my ignorance here? ;-)

---

It's been in the product a while.

It does make the PDFs significantly larger in some cases, but you can simply 
add an explicit function to the .ly file.

add \pointAndClickOff to the .ly file (and comment it out when you want it 
back).

It caused some issues when I gave PDFs to less technically minded friends who 
use Windows and their PDF viewer would 'tooltip' every single note head on the 
music as their cursor ran across the page, with the 'URL' to my .ly file on my 
own machine. So I remember to turn it off for that final compilation.

James

PS you can also use \pointAndClickOn (and comment it out) if you prefer that 
way.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Graham Percival]

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 this without having to cater for an external file as
> lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly

Wow, awesome!  Thanks!

Colin: you're responsible for adding this to the docs.  I think it
would go in Usage ?  basically, find the place that discusses
-dinclude-settings, and add this possibility there.  Patch to
James for pushing.

Cheers,
- Graham

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[David Kastrup]

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),
>> > and then call convert automatically?  I'd really like to add this
>> > to the CG so that we have a simple way to generate images.
>> > (at least on non-windows machines)
>> As far as I can see, Phil asked how to remove the tagline from the comand
>> line*, but the answer was "it's impossible".
>
> Ick, I'd forgotten about that.
>
>> Another option, proposed by Valentin, was to use external file
>> (-dinclude-settings=...), but i would find this "inconvenient" for the build
>> system?
>
> 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 this without having to cater for an external file as
lilypond -dinclude-settings=<(echo "\header { tagline = ##f }") --png bug.ly

-- 
David Kastrup


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Graham Percival]

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 automatically?  I'd really like to add this
> > to the CG so that we have a simple way to generate images.
> > (at least on non-windows machines)
> As far as I can see, Phil asked how to remove the tagline from the comand
> line*, but the answer was "it's impossible".

Ick, I'd forgotten about that.

> Another option, proposed by Valentin, was to use external file
> (-dinclude-settings=...), but i would find this "inconvenient" for the build
> system?

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
  convert bug.png -trim bug-upload.png

something like that.  Could you test it, then we can have a set
script for bug squad members (on linux and osx at least) to
produce great pngs for the tracker?
(oh, maybe replace bug.ly with $1 ... maybe add some explanations
or a help message... dunno, depends on how much work you feel like
doing, and/or how easy you want to make it for yourself in the
future)

Cheers,
- Graham

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[Dmytro O. Redchuk]

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!
> 
> 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 automatically?  I'd really like to add this
> to the CG so that we have a simple way to generate images.
> (at least on non-windows machines)
As far as I can see, Phil asked how to remove the tagline from the comand
line*, but the answer was "it's impossible".

Another option, proposed by Valentin, was to use external file
(-dinclude-settings=...), but i would find this "inconvenient" for the build
system?

And... I'd be happy to appear wrong -- so, please, is this really possible
with scheme?  I will search more if "yes" .)

> This would allow us to standardize on 1-page pngs (automatically
> trimmed) and multi-page pdfs, and avoid -dpreview entirely.

___
 * http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00080.html

-- 
  Dmytro O. Redchuk
  Bug Squad

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond