Federico Bruni | 22 Apr 18:48 2014
Picon

add lilypondblog.org to contact page?

In this page:
http://lilypond.org/contact.html

we currently have a link to news.lilynet.net, which have been down for
months.
I've already opened an issue about lilynet.net links:
http://code.google.com/p/lilypond/issues/detail?id=3903

This is to propose to replace that section ("Stay informed") with
http://lilypondblog.org/, which in almost an year has proven to be a
serious project (regular posts, website working, etc.).
Paul Morris | 21 Apr 17:29 2014

LSR search results: title text doesn't match links or images

Hello,  

There seems to be something odd going on with LSR search results.  When I do
a search for "title:defining" 
http://lsr.di.unimi.it/LSR/Search?q=title%3Adefining

I get these three results:

  Display bracket with only one staff in a system [0.14286]
  Dynamics custom text spanner postfix [0.14286]
  Percent repeat counters for piano music [0.14286]

None of which have "defining" in the title.  However, clicking on the links
takes me to these snippets that do:

  Defining predefined fretboards for other instruments 
  http://lsr.di.unimi.it/LSR/Item?id=578

  Defining an engraver in Scheme: ambitus engraver
  http://lsr.di.unimi.it/LSR/Item?id=805

  Defining a Custom Staff Context
  http://lsr.di.unimi.it/LSR/Item?id=882

And then I notice that the images in the search results are from these 3
"defining" snippets.  So in the list of results the images as well as the
links do not correspond with the titles.  

I'm seeing a similar pattern with other searches too, not just with
"title:defining".  Does anyone else see this?
(Continue reading)

Federico Bruni | 19 Apr 15:00 2014
Picon

robots.txt: disallow /doc/v2.17

I see that on google I get some results for version 2.17. Shouldn't we add
this line to robots.txt?

Disallow: /doc/v2.17/


BTW, in Documentation/web/server/lilypond.org.htaccess I guess that this
line should be deleted:
RedirectMatch ^/wiki    http://wiki.lilynet.net

as the wiki has disappeared
Federico Bruni | 16 Apr 22:47 2014
Picon

\deadNote doesn't work when setting TabNoteHead to a font other than Feta

Three  years ago I didn't follow up to this proposal of Carl:
http://lists.gnu.org/archive/html/lilypond-user/2011-04/msg00326.html

I wonder if you can add an issue now.

Description of the problem
===================

If I use a different font for TabNoteHead

\override TabStaff.TabNoteHead #'font-name = #"Nimbus Sans L Bold"

when a score contains \deadNote I'm forced to comment the line above
and switch back to Feta, otherwise lilypond can't find noteheads.s2cross
(the Feta glyph for dampened notes) and no TabNoteHead is printed. This is
the warning:

warning: none of note heads `noteheads.s' or `noteheads.u' found

The two solutions proposed by Carl in the link above didn't work back then
and don't work now.

Carl's proposal
===========

"Probably the right way to fix this is to have \deadNotesOn set the font to
Feta, and \deadNotesOff set the font to a saved font.  But we don't have
that capability currently implemented.

We also ought to have \deadNote (or better yet, xNote) use a tweak, instead
(Continue reading)

Felix Janda | 12 Apr 15:22 2014
Picon

Make \upbow an empty command + Segmentation fault

Hi,

say I have a violin part with bowing instructions in a variable. Now I want
to use the same variable in the full orchestral score but the bowing marks
should be suppressed.

\upbow is treated by lilypond as an articulation, but the other
articulations should be unaffected by the suppressing of \upbow.

upbow={}

doesn't work because it breaks things like

a\upbow ~ a

Playing a bit with the definition of \upbow gave me a segfault.
Minimal example:

\version "2.18.0"

upbow = #(make-music 'ArticulationEvent
                     'articulation-type "upbow" 'types #f)
downbow = \upbow

Anyway, how do I make a command which has no effect at all?

Cheers,
Felix
Pierre Perol-Schneider | 12 Apr 11:59 2014
Picon

[LSR] "Preventing collisions between two accidentals on the same note" obsolete

I'm not top posting.

Hi Squad,

The following snippet :
http://lsr.di.unimi.it/LSR/Item?id=547

seems obsolete to me.
Shall I delete it ?

Cheers,
Pierre
Pierre Perol-Schneider | 9 Apr 23:27 2014
Picon

Doc "Flamenco notation" has ugly output

Hi Editors,

Please check here;
http://lilypond.org/doc/v2.18/Documentation/snippets/fretted-strings#fretted-strings-flamenco-notation

See discussion here :
http://lilypond.1069038.n5.nabble.com/LSR-v2-18-quot-Flamenco-notation-quot-update-improvement-td159344.html

See workaround here:
http://lsr.di.unimi.it/LSR/Item?id=409

Cheers,
Pierre
Pierre Perol-Schneider | 9 Apr 23:12 2014
Picon

Snippet "Forcing measure width to adapt to MetronomeMark’s width" correction

Hi Editors,

The following snippet:
http://lilypond.org/doc/v2.18/Documentation/snippets/staff-notation#staff-notation-forcing-measure-width-to-adapt-to-metronomemark_0027s-width

does not the job.

see "disscussion" here:
http://lilypond.1069038.n5.nabble.com/LSR-v-218-quot-Forcing-measure-width-to-adapt-to-MetronomeMark-s-width-quot-does-not-work-anymore-td159350.html

See workaround here :
http://lsr.di.unimi.it/LSR/Item?id=659

Cheers,
~Pierre

PS. Why not adding this snippet to the rhythm section ?
Pierre Perol-Schneider | 8 Apr 21:45 2014
Picon

Add "Extending a TrillSpann" in the doc.

Hi Editors,

After a discussion on the french forum I've added this snippet to the LSR:
http://lsr.di.unimi.it/LSR/Item?u=1&id=912

I think it would be helpfull to add it in the doc :
http://lilypond.org/doc/v2.18/Documentation/notation/spanners

with beams and glissandi.

Cheers,
~Pierre
Pierre Perol-Schneider | 8 Apr 18:27 2014
Picon

LSR correction - Partial measures (pickup measures)

Hi Squad, Hi Editors,

In this snippet description :
http://lsr.di.unimi.it/LSR/Item?id=183

I've deleted the following lines :

"<h5>Bugs</h5>

<p>This command does not take into account grace notes at the start of

the music. When a piece starts with graces notes in the pickup, then

the <code>\partial</code> should follow the grace notes (see the second
line of music)."

and untagged "workaround".

If that causes any problem, I'll put them back.

Cheers,

~Pierre
pls | 8 Apr 18:15 2014
Picon
Picon

no bar numbers printed after a line break in the middle of a repeated measure

Hey all,

if this is a bug it might be related to issue 460: in the following tiny example no bar numbers are printed in
the line after a line break in the middle of a repeated measure.  Obviously the bar numbers are only
invisible because they are counted correctly:

\version "2.19.3"
{
  \repeat volta 2 {
    \partial 4 g4
    \repeat unfold 24
    c'1
    d'2.
  }
  \break
  \repeat volta 2 {
    g4
    \repeat unfold 24
    c'1
    d'2.
  }
}

hth
patrick

Gmane