There was some discussion on -devel about this; I believe it has
to do with the .fontcache information not being solved.
Let me know if it still occurs with .37 when it's released.
Cheers,
- Graham
On Mon, 31 Dec 2007 21:52:32 + (UTC)
corey <[EMAIL PROTECTED]> wrote:
> I'm sorry to be compl
I'm sorry to be complaining about how Lilypond runs on Vista, but my laptop
doesn't have the hard drive space for a dual boot like my last one did. :(
Basically, Lilypond takes around a minute to parse and render a .ly file,
whereas it used to take (on Linux and WinXP) only a few seconds. This is
Issue 544: partial in polymetric fails
http://code.google.com/p/lilypond/issues/detail?id=544
Comment #1 by milarepa7:
% I didn't really understand what you wanted me to do. I hope it's fine.
\version "2.11.36"
\paper{ ragged-right=##t }
\score {
\relative c'' <<
\new Staff {
\partial 1
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=544
Cheers,
- Graham
On Sun, 30 Dec 2007 12:42:46 -0800 (PST)
milarepa7 <[EMAIL PROTECTED]> wrote:
>
> Hello,
> It seems that starting by an anacrousis pertubates the polymetric
> notation, i just have to comment it in the exem
Issue 544: partial in polymetric fails
http://code.google.com/p/lilypond/issues/detail?id=544
New issue report by gpermus:
% the second staff is oddly mis-aligned; I can't find a combination
% of \partial or non-partial that results in the bar lines being aligned.
\version "2.11.36"
\score {
\
Yes, this is a known issue. Please see
http://code.google.com/p/lilypond/issues/detail?id=504
Cheers,
- Graham
On Sun, 30 Dec 2007 19:37:24 + (UTC)
Benjie Westafer <[EMAIL PROTECTED]> wrote:
> Hi,
> The introductory file opens with instructions;
> but, I'm not able to go any further. I'm c
2007/12/31, Risto Vääräniemi <[EMAIL PROTECTED]>:
>
> I'll continue my monologue. :-)
Hi, the quick fix is to patch out
/type1/
and
/otf/
which appear somewhere in the binary lilypond.exe: replace the
trailing slash with a \0 character. I hope to release a new versions
shortly, which will
Ok found it!
We just have to add the \set Timing.measurePosition = #(ly:make-moment x y)
just after the anacrusis and add manually the bar line between the anacrusis
and the first measure!
I don't know if we can talk of a real bug here, sorry for the post.
Regards.
PS : maybe it should be in the m
I'll continue my monologue. :-)
Risto Vääräniemi wrote:
> I think there are two font bugs after all (they could be interrelated,
> though).
> One is related to missing accents and the other to substituting all fonts
> with Verdana.
>
> programming error: FT_Get_Glyph_Name () error: invalid argu
