No graphics in several pages
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: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Tutorial http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Compiling-a-file http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Simple-notation etc. I use Internet Explorer 6.0 SP2. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No graphics in several pages
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 http://lilypond.org/doc/v2.10/Documentation/user/source/input/test/collated- files Here it is ok: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Tutorial http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Compiling-a-file http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Simple-notation etc. I use Internet Explorer 6.0 SP2. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: No graphics in several pages
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 Bengtsson wrote: 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 http://lilypond.org/doc/v2.10/Documentation/user/source/input/test/collated- files Here it is ok: http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Tutorial http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Compiling-a-file http://lilypond.org/doc/v2.10/Documentation/user/lilypond/Simple-notation etc. I use Internet Explorer 6.0 SP2. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
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
cause the bug (but it's quite repeatable). Specifically, the combination of
BOTH the down-markup AND the down-articulation TOGETHER WITH the
staff-changing note causes stemming and beaming to completely screw up.
Commenting out EITHER the down-markup OR the down-articulation OR BOTH
causes the stemming and beaming to work perfectly.
Bug shows up in both .29 and .30 but I haven't tested earlier builds to see
when exactly it entered.
%%% BEGIN %%%
\version 2.11.30
\new PianoStaff
\new Staff = RH {
\time 1/4
c''16 [
c''16
\change Staff = LH
c''16 \tenuto _ \markup { foo }
\change Staff = RH
c''16 ]
}
\new Staff = LH {
s4
}
%%% END %%%
Really nasty is some heavily \markup-ed piano music.
Attachments:
stemming-and-beaming-craziness.png 10.2 KB
Issue attributes:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Cross-staff beam craziness (when down-markup combines with down-articulation)
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
staff-changing note causes stemming and beaming to completely screw up.
Commenting out EITHER the down-markup OR the down-articulation OR BOTH
causes the stemming and beaming to work perfectly.
Bug shows up in both .29 and .30 but I haven't tested earlier builds to see
when exactly it entered.
%%% BEGIN %%%
\version 2.11.30
\new PianoStaff
\new Staff = RH {
\time 1/4
c''16 [
c''16
\change Staff = LH
c''16 \tenuto _ \markup { foo }
\change Staff = RH
c''16 ]
}
\new Staff = LH {
s4
}
%%% END %%%
Really nasty is some heavily \markup-ed piano music.
--
Trevor Bača
[EMAIL PROTECTED]
attachment: stemming-and-beaming-craziness.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
programming error: minimise_least_squares (): Nothing to minimise
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 is removed
}
}
Regards,
Neil
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 406 in lilypond: Feathered beams do not work with knees
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: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: font is broken on WinXP Japanese
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 be shown as U+30d5 U+30a1 U+30a4 U+30eb (Fu A-Small I Ru, in Katakana) and (F). $ perl -e 'print \x30\xd5\x30\xa1\x30\xa4\x30\xeb' | iconv -f ucs-2 -t sjis | hexdump -C 83 74 83 40 83 43 83 8b |[EMAIL PROTECTED]| On Japanese Windows, strings should be written in CP932 (or Unicode), but lilypond does not. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 431 in lilypond: menus in windows should be unicode
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 I Ru, in Katakana) and (F). $ perl -e 'print \x30\xd5\x30\xa1\x30\xa4\x30\xeb' | iconv -f ucs-2 -t sjis | hexdump -C 83 74 83 40 83 43 83 8b |[EMAIL PROTECTED]| On Japanese Windows, strings should be written in CP932 (or Unicode), but lilypond does not. Attachments: lilypond-win-ja.png 79.9 KB Issue attributes: Status: Accepted Owner: gpermus Labels: Type-Defect Priority-Low OpSys-Windows -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Alignment problem with RehearsalMark
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 the staff context?
No, I was just speculating, without having really tested my hypothesis.
Sorry about that. Now that I have made some experiments, it seems that
something else is going on when you move the engraver to the staff
context.
Here's an example, which I also send to bug-lilypond.
\relative { \mark C c1 | \mark D d | \clef alto
\mark E e | \mark F f |
}
% Uncommenting this layout block, causes both the C and the E marks
% to move to the left!
%{
\layout {
\context { \Score
\remove Staff_collecting_engraver
\remove Mark_engraver
}
\context { \Staff
\consists Staff_collecting_engraver
\consists Mark_engraver
}
}
%}
/Mats
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 432 in lilypond: odd layout when Mar_engraver is moved into Staff
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 and the E marks
% to move to the left!
\layout {
\context { \Score
\remove Staff_collecting_engraver
\remove Mark_engraver
}
\context { \Staff
\consists Staff_collecting_engraver
\consists Mark_engraver
}
}
Attachments:
foo.preview.png 3.1 KB
Issue attributes:
Status: Accepted
Owner: gpermus
Labels: Type-Defect Priority-Low
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
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 trigger Stem::height, which enters beam formatting. Beam formatting for a cross staff beam needs Y-alignment of the staves, of course. One solution I can see, is to remove the Stem from the script support when it is opposite of the script; this is a bit hackish, as I'm specialcasing in Site_position_interface, but it breaks the cyclic dependency. Issue attribute updates: Status: Accepted Owner: joeneeman -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
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 message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 430 in lilypond: Cross-staff beam craziness (when down-markup combines with down-articulation)
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 you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
