On 11/29/08 5:13 AM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 27, 2008 at 3:53 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>> I'm not sure who is currently managing the development of the main LilyPond
>> web page, so I'm not sure who this should be addressed to.
>>
>> I
2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> I tried out both:
> If I only implement 1), then center-column markups that are not inside a line,
> but rather on their own, are still wrongly aligned (e.g. the first time
> signature in my examples). So 2) is definitely needed to fix this issu
> > It seems that the TeX backend should be removed completely now,
> > since fonts are no longer available. Objections?
>
> When you'll do this, remember to delete the usage notice string for
> the --tex option.
Of course. This option is also obsolete too, I think.
> Possibly the string "1996
2008/11/30 Werner LEMBERG <[EMAIL PROTECTED]>:
>
> It seems that the TeX backend should be removed completely now, since
> fonts are no longer available. Objections?
When you'll do this, remember to delete the usage notice string for
the --tex option.
Possibly the string "1996--2007" in copyrigh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 22:52:45 schrieb Reinhold Kainhofer:
> So, basically, there are two solutions:
> 1) Change stack-stencil-line to use the whole extents of the stencil (i.e.
> make it work correctly with stencils where the left edge is not
It seems that the TeX backend should be removed completely now, since
fonts are no longer available. Objections?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> > Are you aware of the fact that
> >
> > (ly:font-load foo)
> >
> > only loads an OTF font with the name `foo.otf'? Additionally, the
> > font should contain OpenType tables `LILC', `LILY', and `LILF', or
> > you get a warning message.
>
> Feel free to update the name to reflect this.
Done.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 19:06:09 schrieb Neil Puttock:
> 2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > So, this is a general problem with the general-column scheme function...
>
> Perhaps there's a bug in stack-lines?
I've now done some
2008/11/30 Neil Puttock <[EMAIL PROTECTED]>:
> That's because the 'space-alist for BarLine uses 'extra-space instead
> of 'minimum-space for time-signature; why this should stop the
> collision, I don't know.
Right, I've had a dig around in break-alignment-interface.cc, and I
think I've worked ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 17:55:19 schrieb Reinhold Kainhofer:
> No, the keyAlterationOrder only affects the generation of the keySignature
> alist from the pitch-alist of the KeyChangeEvent. The
> Key_engraver::read_event function also creates the
2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> If you take a look at
> http://www.fam.tuwien.ac.at/~reinhold/temp/time_sigs.pdf
> (where each fraction is a separate make-center-column-markup), you will see at
> the first time signature that the extents to the right of the enter of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 19:06:09 schrieb Neil Puttock:
> 2008/11/30 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > It's actually not a problem of spacing between the clef and the time
> > signature, but rather a problem with make-center-column-marku
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 30. November 2008 16:41:14 schrieb Neil Puttock:
> 2008/11/30 Trevor Daniels <[EMAIL PROTECTED]>:
> > I've added a suitable comment to the snippet.
>
> I'm afraid it's not necessarily the case that they'll always be in
> reverse order, sinc
2008/11/30 Trevor Daniels <[EMAIL PROTECTED]>:
> I've added a suitable comment to the snippet.
I'm afraid it's not necessarily the case that they'll always be in
reverse order, since the ordering is controlled by keyAlterationOrder
(which obviously defaults to standard classical ordering).
Regar
Reinhold Kainhofer wrote Sunday, November 30, 2008 3:02 PM
The documentation of the non-standard key signature feature (in the
selected
snippets section of the Key Signatures section) gives an example of such a
key:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/Displaying-
pitche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The documentation of the non-standard key signature feature (in the selected
snippets section of the Key Signatures section) gives an example of such a
key:
http://kainhofer.com/~lilypond/Documentation/user/lilypond/Displaying-
pitches.html#Key-sign
The correct way to do this, which incidentally lily uses, is to use
binary search over the glyphs, until you've found the closest one.
On Sat, Nov 29, 2008 at 6:19 PM, Mats Bengtsson
<[EMAIL PROTECTED]> wrote:
> Quoting Neil Puttock <[EMAIL PROTECTED]>:
>
>> 2008/11/28 Mats Bengtsson <[EMAIL PROTE
17 matches
Mail list logo
