Vincent escreveu:
I suspect that the directory /usr/var/cache/fontconfig/ and the files
it contains are created in the wrong place (the root directory,
instead below the lilypond directory)
this continues to happen, (no matter with which commandline parameters
I invoke lilypond) but it don't
Joe Neeman escreveu:
Why not just a Grob::skyline function that
1) if 'elements or 'element is empty, get the bounding box of the
stencil
2) otherwise merge the skylines of child grobs
Obviously (1) would be more accurate if we had a skylining algorithm for
stencils, but I don't know if that's
> I still can't get a svg file with the correct text fonts. I keep
> getting the "can't decipher Pango description: Century SchoolBook L"
> warnings in version 2.9.22.
>> http://code.google.com/p/lilypond/issues/detail?id=114
this warning has gone in 2.9.26-3-mingw. thanks for looking into this :
On Thu, 2006-10-26 at 21:03 +0200, Han-Wen Nienhuys wrote:
> Joe Neeman escreveu:
> > On Thu, 2006-10-26 at 11:06 -0700, Graham Percival wrote:
> >> Marcus Macauley wrote:
> >>
> >>> 1. Vertical interlocking of staff objects should be allowed by default,
> >>> with an option to disable;
> >> Due t
Joe Neeman wrote:
On Thu, 2006-10-26 at 11:06 -0700, Graham Percival wrote:
Marcus Macauley wrote:
1. Vertical interlocking of staff objects should be allowed by default,
with an option to disable;
Due to technical issues, I doubt that this will happen by default in the
next few years. I agr
Joe Neeman escreveu:
On Thu, 2006-10-26 at 11:06 -0700, Graham Percival wrote:
Marcus Macauley wrote:
1. Vertical interlocking of staff objects should be allowed by default,
with an option to disable;
Due to technical issues, I doubt that this will happen by default in the
next few years. I
On Thu, 2006-10-26 at 11:06 -0700, Graham Percival wrote:
> Marcus Macauley wrote:
>
> > 1. Vertical interlocking of staff objects should be allowed by default,
> > with an option to disable;
>
> Due to technical issues, I doubt that this will happen by default in the
> next few years. I agree
Han-Wen Nienhuys wrote:
Vincent schreef:
Hi,
I still can't get a svg file with the correct text fonts. I keep
getting the "can't decipher Pango description: Century SchoolBook L"
warnings in version 2.9.22.
I suspect that the directory /usr/var/cache/fontconfig/ and the files
it contains are
Marcus Macauley wrote:
1. Vertical interlocking of staff objects should be allowed by default,
with an option to disable;
Due to technical issues, I doubt that this will happen by default in the
next few years. I agree that it would be nice, but it's not an easy
task to do.
That said, it
Han-Wen Nienhuys wrote:
You can use LAissezVibrerTieColumn #'tie-configuration. See also the
regtest laissez-vibrer-ties.ly
Added a feature request
http://code.google.com/p/lilypond/issues/detail?id=124
- Graham
___
bug-lilypond mailing list
bug-l
Added as
http://code.google.com/p/lilypond/issues/detail?id=123
- Graham
Paul Scott wrote:
Laura Conrad wrote:
"Paul" == Paul Scott <[EMAIL PROTECTED]> writes:
Paul> When using continuation lines, common figures are always put
in the
Paul> same vertical position.
I kno
Hi Mirosław,
We're very busy preparing for a release right now. Could you send these
bugs again, separated into one bug per email, and with a short lilypond
example which demonstrates each bug?
If you see any bugs in deutsch.ly or nederlands.ly in version 2.9,
please submit a diff file of t
Will Oram wrote:
I see. I would not expect you to do the boiling down for me, regardless
of your workload.
Well, that _is_ part of my duties as the Bug Meister. If this was your
first bug report, I'd do that boiling down without giving it a second
thought. But I know that you're not a lilyp
Hi Cameron and Marcus,
Both of you reported this bug. Could you check if it has anything to do
with #'break-align-symbol ? I'm thinking of something like the
examples in the doc section on Text marks.
- Graham
Cameron Horsburgh wrote:
Hi folks,
These bugs were reported in April, but Gr
Graham Percival escreveu:
Carlo Stemberger wrote:
“print-page-number = ##t” should be the default (so unnecessary), but
I must put this command into a \paper block so that version 2.8 (also
2.8.7) generates page numbers.
Han-Wen,
I second the suggestion that print-page-number should be #t b
On Wed, 2006-10-25 at 14:27 -0700, Graham Percival wrote:
> Joe, is
> \paper{
>breakbefore = ##t
> }
> depreciated? I wouldn't be surprised if it was, but I need to know so I
> can remove it from the docs. (if it is, how are users supposed to get
> that effect now?)
The new way of doing it
As far as I can see, it is set to true in ly/paper-defaults.ly, both in
version 2.8 and
2.10. Still, the setting doesn't seem to have any effect. What's going
on here?
/Mats
Graham Percival wrote:
Carlo Stemberger wrote:
“print-page-number = ##t” should be the default (so unnecessary), but
17 matches
Mail list logo
