Re: [Lilypond-auto] Issue 4014 in lilypond: Patch: Add an expert font tree interface

[lilypond]

Comment #12 on issue 4014 by address@hidden: Patch: Add an expert font  
tree interface
http://code.google.com/p/lilypond/issues/detail?id=4014

> > On 22. Juli 2014 07:51:00 MESZ, James <address@hidden> wrote:



> > > 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).

> > IISC it does _not_ mean to postpone it, quite the contrary.

> Yes and no.  It does not necessarily mean to postpone the feature, but
> my intention for the announcement of the patch in its current shape was
> threefold:

> a) (ACHIEVED.)
> I needed the feature, right now.  Well, turned out I didn't, but I
> thought I do.

> b) (ACHIEVED.)
> I wanted to have a draft ready before some interface for the music font
> changing is settled, because we might want to do both in one shot.

> c) (TODO)
> I hoped for a small comment or two about the (informal) interface
> proposal (by example).  I do intend to write a piece of documentation
> about it, because I feel that already make-pango-font-tree is not as
> accessible for people which are not familiar with the Linux-/LaTeX-style
> {roman,sans,monospace}-default-definition idea.  I might be mistaken,
> though.  On the other hand, I actually don't know if it is correct when
> I say: "the Pango description string for the font, which is passed as-is
> to the Pango interface".  Is this Pango?  Is it fontconfig?  Is it
> correct that `fc-match <string>` will tell me what
> `(make-expert-font-tree '((... <string>)) ...)' will do, or almost, but
> not quite?  I'm kinda lost there myself.


> The last one is the big TODO, and the reason why I'm also fine with
> postponing it.  And I don't want to have it in master unless it's
> reasonably unlikely that the interface (let's say the format of
> font-spec-list) will change within a few days.


> BTW: I think it's strange that Century Schoolbook is taken as the
> default, while sans is left to the environment.  Is that because there
> was no need for a sans or mono font with built-in features before chords
> and the tagline were introduced?  Or because there was no agreement on a
> "good" (quality/liberty/freedom) font?


> Best,
> Alexander

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings