Justus Schümmer | 21 Jul 19:12 2014
Picon

Repeated accidentals after ties

Hi. Here are two small issues:

1. When I repeat a chord with q which contains a reminder accidental,
both notes get the accidental:
\version "2.18.2"
\relative c'' {
 	<c bes!>2~ q
}
I think (maybe I am wrong) even the reminder should be printed only once.

2. This is a special case so the example explains it better than I can.
\version "2.18.2"
\relative c'' {
	\key g \major
	f1~ \break
	| f2 f2
}
The natural here appears two times in the second bar.
Aliosha Bielenberg | 21 Jul 21:40 2014
Picon

Hairpins not aligned/symmetrical

> I'm not top posting.

% To be aesthetically pleasing, the end of one
% hairpin should line up with the start of the
% next, i.e. be symmetrical, if they're right next to one another.
\version "2.18.2"

\relative c' {
  f8.\< d16\! g4.\> f8\!
}

This produces [this](https://i.imgur.com/0IP29F6.png), whereas in the hand-
engraved score it's like [this](https://i.imgur.com/3ob5H5Z.png).
Paul Morris | 21 Jul 21:21 2014

Dots are shifted to avoid non-existent ledger lines (with custom ledger line positions)

Here's an obscure one: when ledger line positions have been overridden, the positions of dots on dotted
notes are still shifted to avoid ledger lines that are no longer there.  They don't seem to be shifted based
on actual ledger line positions.

-Paul

\version "2.18.2"

greenNote =  \once \override NoteHead.color = #green

\markup { Dots are shifted to avoid non-existent ledger lines (see green notes). }

\new Staff \with {
  \override StaffSymbol.line-positions = #'(-4 0 4)
  \override StaffSymbol.ledger-positions = #'(-4 0 4)
}
\relative f' {
  \time 12/4
  c,4. d e
  \greenNote f
  g a b
  \greenNote c
  g''
  \greenNote a
  b c d
  \greenNote e
  f g
}

\markup { Dots are not being shifted based on actual ledger line positions.}
(Continue reading)

Markus Olbrich | 20 Jul 20:45 2014
Picon
Picon

Bug on first page of German lilypond website

Hi!

On the German version of the website there is a mistake in the first
sentence of the first page (http://www.lilypond.org/index.de.html):

Incorrect is:
"LilyPond ist ein Notensatzprogramm, dass es sich zum Ziel gemacht hat,
Notendruck von der bestmöglichen Qualität zu erstellen."

Correct is:
"LilyPond ist ein Notensatzprogramm, das es sich zum Ziel gemacht hat,
Notendruck von der bestmöglichen Qualität zu erstellen."

Stylistically even better would be:
"LilyPond ist ein Notensatzprogramm, das es sich zum Ziel gemacht hat,
Notendruck in bestmöglicher Qualität zu erstellen."

Kind regards,
Markus

--

-- 
Dr.-Ing. Markus Olbrich
Institute of Microelectronic Systems - EDA
Leibniz Universität Hannover - http://www.ims.uni-hannover.de
Phone: +49 511 762-19661 - Fax: +49 511 762-19694
Abel Cheung | 20 Jul 03:11 2014
Picon

packed-spacing setting produce bad layout with long text

It is illustrated with this fragment:

\paper { ragged-rigth = ##t ragged-last = ##t }
\relative c' {
  \override Score.SpacingSpanner #'packed-spacing = ##t
  c8 c c-\markup{"some very very very very very very long text"} c c c c c |
  \repeat unfold 16 {c}
}

The packed-spacing setting acts as if \textLengthOn is in effect, producing 
unsightly layout between 3rd and 4th note.
Karol Majewski | 20 Jul 00:25 2014
Picon

binding-offset bug

Hi,

it seems that binding-offset size scales accordingly to global-staff-size, which of course is a bug:

%%%%%%%%%%%%%%%%%%%%%%%%%%%

\version "2.19.10"

#(set-global-staff-size 20)

\paper {
  top-markup-spacing = #'((basic-distance . 0) (minimum-distance . 0) (padding . 0) (stretchability . 0))
  two-sided = ##t
  binding-offset = 2\cm
}

\bookpart {
  \header {
    poet = \markup { \abs-fontsize #13 "left" }
    composer = \markup { \abs-fontsize #13 "right" }
  }
  \score {
    \new Staff { d'4 }
  }
}

%%%%%%%%%%%%%%%%%%%%%%%%%%%

Now, change global-staff-size to smaller and you'll notice that inner-margin becomes smaller too!
However, when binding-offset is disabled, changing global-staff-size does not affect inner-margin size.
(Continue reading)

'Jan Nieuwenhuizen | 17 Jul 23:08 2014
Picon

midi2ly produces 8*5, can we do better?

Hi,

Running

    lilypond bug.ly
    midi2ly bug.midi
    grep fis bug-midi.ly 

produces

    fis1 
    fis'4. d8*5 

While technically correct, duration-wise, in printed output it
will look as if the d2 has been omitted.  In other words

    fis'4. d8 ~ d2

looks so much nicer!  Tested with 2.16.2 and 2.19.11.

Greetings, Jan

Attachment (bug.ly): text/x-lilypond, 139 bytes

--

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  
(Continue reading)

David Nalesnik | 15 Jul 13:48 2014
Picon

Re: Accidentals on repeated notes separated by rests in certain styles

---------- Forwarded message ----------
From: guoguocuozuoduo <brian777guo <at> hotmail.com>
Date: Tue, Jul 15, 2014 at 12:13 AM
Subject: RE: Accidentals on repeated notes separated by rests in certain
styles
To: David Nalesnik <david.nalesnik <at> gmail.com>

>There should be for neo-modern, neo-modern-cautionary, neo-modern-voice,
neo-modern-voice-cautionary, but not dodecaphonic-no-≥repeat.

For the record, I think that all of the styles should suppress the repeated
accidental, or none should.  It comes down to whether the same pitch
separated by a rest should be considered an immediate repetition.  I think
so.  Consider the following:

{ fis'4-. fis'-. }

vs.

{ fis'8 r fis' r }

It doesn't make much sense to me that there should be a difference in
behavior between the two in any style which detects immediate repetition.

--David
David Nalesnik | 15 Jul 02:39 2014
Picon

accidentals on note overlaps

Hi,

In the following example, the half-note F# counts as an immediate
repetition and should not get an accidental in neo-modern and
neo-modern-cautionary styles,  This issue is seen in the documentation at
http://lilypond.org/doc/v2.19/Documentation/notation/displaying-pitches#automatic-accidentals:
the c-sharps in the upper staff of the second measure shouldn't appear in
these two styles.  (The repetition makes sense in neo-modern-voice and
neo-modern-voice-cautionary.)

{

  \accidentalStyle neo-modern

  << fis'1 \\ { r2 fis' } >>

}

 {

  \accidentalStyle neo-modern-cautionary

  << fis'1 \\ { r2 fis' } >>

}
_______________________________________________
bug-lilypond mailing list
(Continue reading)

David Nalesnik | 15 Jul 02:03 2014
Picon

Accidentals on repeated notes separated by rests in certain styles

Certain accidental styles suppress accidentals on immediately repeated
notes.  (These styles are neo-modern, neo-modern-cautionary,
neo-modern-voice, neo-modern-voice-cautionary, and dodecaphonic-no-repeat.)
 When a pitch repetition occurs across a rest, however, the accidental is
repeated: as an ordinary accidental or a cautionary.

Should there be an accidental on the second f-sharp in the following
example?

\new Staff {

  \accidentalStyle neo-modern

  fis'4 r fis'4 r

}
Simon Albrecht | 15 Jul 00:27 2014
Picon

ps2pdf and file name encoding

Hello,

if I include any non-ASCII character into a file name, I get the 
following at the end of the log

warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 
-dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH 
-r1200 -sDEVICE=pdfwrite -sOutputFile=./non-áscii.pdf -c.setpdfwrite 
-fnon-áscii.ps)' failed (256)

fatal error: failed files: "/home/simon/Notensatz ly/tests/non-áscii.ly"

and Lily produces a .ps file, but no .pdf. See attachment for a simple 
test file. I run ubuntu.
I'm not sure if this is unrelated to issue 2173 
<http://code.google.com/p/lilypond/issues/detail?id=2173>, which is 
about Windows mainly.

Yours, Simon
Attachment (non-áscii.ly): text/x-lilypond, 32 bytes
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Gmane