>> Interesting, though, that you like it better this way. I thought it
>> might cause some confusion later on or in users unfamiliar with the new
>> method of setting the style if there is only one exception to the
>> otherwise consistent naming convention for the alists.
>>
>
> Hmm,
> which conve
Issue 258: microtonal shift should be undone before next note
http://code.google.com/p/lilypond/issues/detail?id=258
New issue report by hanwenn:
\score
{
\relative {
a geseh \acciaccatura a geseh
}
\midi {}
}
Issue attributes:
Status: Fixed
Owner: hanwenn
Mats Bengtsson escreveu:
> Please send future bug reports to the bug-lilypond mailing list.
> I forward your email there.
please file bugreports against the latest 2.10 version, not 2.10.0
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code
Maximilian Albert escreveu:
> Han-Wen Nienhuys schrieb:
>
>> actually, I prefer a change in convertrules.py
>>
>
> Something like this? You probably have added this yourself already, but
> just in case ... (I hope I didn't get anything wrong with the python
> syntax).
>
> Interesting, though, th
Please send future bug reports to the bug-lilypond mailing list.
I forward your email there.
/Mats
Mike Blackstock wrote:
I need to convert .ly version 2.0 files to version 2.10
Conversion stops with the following output:
convert-ly (GNU LilyPond) 2.10.0
Processing `trio_flute.ly'...
Apply
Hi folks
Sorry if I missed any changes between my Lily version (2.8.8.) and the
bleeding-edge version. But here goes:
I stumbled into behaviour that I think is a bug in the PartCombiner. In
the case where one of the two parts is (temporarily) silent and the
playing voice has a rest, the rest
Thanks a lot, this would never have occurred to me.
Georg
>-Original Message-
>From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
>Sent: Monday, January 29, 2007 10:35 AM
>To: Georg Dummer
>Cc: bug-lilypond@gnu.org
>Subject: Re: Fonts included in all lilypond-book snippets
>
>Then you have
Issue 253: 2.11.13 bus error
http://code.google.com/p/lilypond/issues/detail?id=253
Comment #8 by trevorbaca:
No, no: it's the same glissando-over-pageBreak error mentioned in comment #2,
running
against a two-note file:
%%% BEGIN %%%
\version "2.11.14"
\new Staff {
c'1 \glissando
\pageB
Han-Wen Nienhuys schrieb:
>
> actually, I prefer a change in convertrules.py
>
Something like this? You probably have added this yourself already, but
just in case ... (I hope I didn't get anything wrong with the python
syntax).
Interesting, though, that you like it better this way. I thought
Fred Leason wrote:
On Mac OS X, the latex route works fine.
$ dvips -Ppdf -h psalm71.psfonts psalm71.dvi
$ ps2pdf psalm71.ps
or if I click on psalm71.dvi in Finder, then TeXShop opens it and converts it.
Are you sure that it takes care of the -h psalm71.psfonts argument to dvips?
If it
Maximilian Albert escreveu:
> Hi,
>
> if I understand it correctly, in newer versions the style of accidentals
> is supposed to be set by
>
> \override Accidental #'glyph-name-alist =
>#alteration-...-glyph-name-alist
>
> instead of
>
> \override Accidental #'style =
Thanks, you were right.
I actually had two problems.
I had some old version of latex in my path before the it found the web2c 7.5.5
installation. How the path changed in a week will remain a mystery.
I forgot the equals in --output=
Once I fixed those, everything worked fine.
On Mac OS X, the
Issue 253: 2.11.13 bus error
http://code.google.com/p/lilypond/issues/detail?id=253
Comment #7 by hanwenn:
warning: cannot find line breaking that satisfies constraints
Sounds like you have notes overrunning barlines or similar, so that there
are no places at all where to break the line.
--
Then you have found yet another reason not to use the extra-offset
property. In general, LilyPond does not take extra-offset into account
when it handles collisions and apparently not when it calculates the
bounding boxes either. Better methods to obtain the same result are
described in a generic
I think, I narrowed the problem down to the line:
\override Score.ChordName #'extra-offset = #'(0.0 . 1.5)
I use this sometimes for better readability if a song has lyrics above the
soprano voice.
Georg
>-Original Message-
>From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
>Sent: Monday, J
I can't repeat the problem here. Could you please send a small example
including the input file.
Also, I hope you made sure to remove all temporary lily-* files when
you switched from using --psfonts to --pdf.
/Mats
Georg Dummer wrote:
I discovered a problem with this straight PDF "route". S
16 matches
Mail list logo
