On this pages I don't get any graphics (the examples):
http://lilypond.org/doc/v2.10/input/test/collated-files
http://lilypond.org/doc/v2.10/Documentation/user/music-glossary-big-page
http://lilypond.org/doc/v2.10/Documentation/user/source/input/test/collated-
files
Here it is ok:
Strange! It works well over here.
/Mats
Henning Plumeyer wrote:
On this pages I don't get any graphics (the examples):
http://lilypond.org/doc/v2.10/input/test/collated-files
http://lilypond.org/doc/v2.10/Documentation/user/music-glossary-big-page
Fine for me as well (Firefox on WinxP).
Looking at the page source I do notice that the img tag has no
indication of graphics file format (the src attribute does not have an
extension).
That might be a reason for your browser to give up on trying to figure
out the format.
--Gait.
Mats
Issue 430: Cross-staff beam craziness (when down-markup combines with
down-articulation)
http://code.google.com/p/lilypond/issues/detail?id=430
New issue report by trevorbaca:
This one was really, really nasty to find.
In the following snippet we need the whole witches' brew of settings to
Hi,
Crossposted as Google #430.
This one was really, really nasty to find.
In the following snippet we need the whole witches' brew of settings to
cause the bug (but it's quite repeatable). Specifically, the combination of
BOTH the down-markup AND the down-articulation TOGETHER WITH the
Hi there,
The following snippet spits out this error, but the output is
unobjectionable:
\version 2.11.30
\paper{ ragged-right=##t }
\score {
\new Staff \relative c'' {
{ \time 12/16 c16[ b a r b g] } \\ { r8. r } %error
disappears if manual beaming or second rest in lower voice
Issue 406: Feathered beams do not work with knees
http://code.google.com/p/lilypond/issues/detail?id=406
Comment #2 by gpermus:
Sorry, I misunderstood the bug report or something. The png that I posted with
the
bug report doesn't even demonstrate the problem.
Issue attribute updates:
Thanks for the report; this has been added as
http://code.google.com/p/lilypond/issues/detail?id=431
Cheers,
- Graham
YAMASHINA Hio wrote:
screenshot:
http://fleur.hio.jp/~hio/prive/lilypond-win-ja.png
For example, `File' is showed as [EMAIL PROTECTED](F) (left most item on
menu).
It should
Issue 431: menus in windows should be unicode
http://code.google.com/p/lilypond/issues/detail?id=431
New issue report by gpermus:
(screenshot attached)
For example, `File' is showed as [EMAIL PROTECTED](F) (left most item on
menu).
It should be shown as U+30d5 U+30a1 U+30a4 U+30eb
(Fu A-Small
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=432
Cheers,
- Graham
Mats Bengtsson wrote:
Neil Puttock wrote:
Just to clarify this, are you saying that this happens as a result of
the default setting of break-align-symbols combined with moving the
mark engraver to
Issue 432: odd layout when Mar_engraver is moved into Staff
http://code.google.com/p/lilypond/issues/detail?id=432
New issue report by gpermus:
\version 2.11.30
\relative {
\mark C c1 | \mark D d | \clef alto
\mark E e | \mark F f |
}
% Uncommenting this layout block, causes both the C
Issue 430: Cross-staff beam craziness (when down-markup combines with
down-articulation)
http://code.google.com/p/lilypond/issues/detail?id=430
Comment #1 by hanwenn:
Joe,
can you have a look? I'm not very familiar with this code anymore.
It seems that the Y alignment of the staves ends up
Issue 430: Cross-staff beam craziness (when down-markup combines with
down-articulation)
http://code.google.com/p/lilypond/issues/detail?id=430
Comment #2 by hanwenn:
Hi Joe,
can you review my patch for this fix?
Issue attribute updates:
Labels: fixed_2_11_32
--
You received this
Issue 430: Cross-staff beam craziness (when down-markup combines with
down-articulation)
http://code.google.com/p/lilypond/issues/detail?id=430
Comment #3 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
--
You received this message because
14 matches
Mail list logo
