On 21/07/14 09:46, Alexander Kobel wrote:
> On 07/20/2014 11:47 AM, Janek Warchoł wrote:
>> 2014-07-19 16:48 GMT+02:00 tisimst <tisi...@gmail.com>:
>>> - Question 1: *Should the new syntax be something like this?* (where
>>> the
>>> music and piano-brace fonts are put at the first)
>>>
>>> \paper {
>>> #(define fonts
>>> (make-pango-font-tree
>>> *"lilyjazz"* ; music font
>>> *"gonville"* ; piano brace font
>>> "FreeSerif"
>>> "FreeSans"
>>> "Inconsolata"
>>> (/ staff-height pt 20)))
>>> }
>>
>> I agree with David's comment here.
>> Btw, just to make sure: have you seen
>> https://code.google.com/p/lilypond/issues/detail?id=4014 ?
>
> Hi all,
>
> and Janek: thanks for the ping... I'm currently travelling, I won't
> have too much internet access for the next week or so, and then again
> just for a few days til vacation starts. In other words, don't expect
> much time from me until mid-August.
> @all: feel free to modify the make-expert-font-tree as you think it
> fits if you want to!
> I think if the make-expert-font-tree makes it into master at some
> point in some variant, it would be worth to check whether we should
> have this as the backend for make-pango-font-tree.
>
>
> Best,
> Alexander
So does that mean this patch 'needs work' now?
It's currently on countdown (I'm the owner/patch-shepherd as Alexander
doesn't have commit access).
James
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
