lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Font switching docs - add a font to LilyPond?


From: tisimst
Subject: Re: Font switching docs - add a font to LilyPond?
Date: Fri, 19 Dec 2014 11:33:47 -0700 (MST)

Urs,

I think that's a great idea!

Also, I was wondering if we could look into how to make Pango look in the 
system font folder if it can't find a music font and the LilyPond font folder. 
If we could do that then the fonts are version independent. What do you think 
of that? This could eventually lead to not requiring a separate font based on 
the font size if one is not available.

-Abraham

Sent from my iPhone

> On Dec 18, 2014, at 3:59 AM, Urs Liska [via Lilypond] <address@hidden> wrote:
> 
> 
> Am 18.12.2014 01:38, schrieb James Lowe: 
> 
> > Urs, 
> > 
> > On 15/12/14 11:24, Urs Liska wrote: 
> >> Hi all, 
> >> 
> >> 
> >> Abraham has sent me documentation for his recent font switch improvement 
> >> to incorporate into LilyPond's manuals. 
> >> However, there is one issue I'd like to sort out before I start editing 
> >> the .itely files. 
> >> 
> >> Of course the documentation gives an example of the use of the new font 
> >> selection function. But this will require the used font(s) to be 
> >> installed on the build system because otherwise the build will fail. 
> >> 
> >> ... 
> >> 
> > https://code.google.com/p/lilypond/issues/detail?id=1494
> > 
> > This is a 'patch abandoned'. Take a look here and see if this is 
> > something you can work with.
> 
> Well, not directly. It rather tells me that it *is* a non-trivial issue. 
> But I think that now that we have the infrastructure of switching fonts 
> built-in with LilyPond the situation has slightly changed. 
> 
> So I "officially" propose to 
> 
> - ship LilyJAZZ, LilyJAZZText and LilyJAZZChord with LilyPond 
>    as this is the most fundamental alternative (allowing for a 
> completely different type of scores 
>    while the other fonts are "merely" stylistic alternatives. 
>    I would do so even if we can only ship the resulting font files. 
>    It's somewhat less nice than having the MF sources like with 
> Emmentaler, but e.g. TeXLive would 
>    only say: Provide the sources if that's possible, otherwise use only 
> the font files. 
> - Host the binary font files in the lilypond-extra repository 
>    (I can prepare a pull request) 
> - Add something to the build process that copies those fonts to the 
> right location in LilyPond 
>    (I can look into that if someone points me in the right direction) 
> 
> Urs 
> 
> > 
> > James 
> > 
> 
> 
> _______________________________________________ 
> lilypond-devel mailing list 
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://lilypond.1069038.n5.nabble.com/Font-switching-docs-add-a-font-to-LilyPond-tp169460p169508.html
> To start a new topic under Dev, email address@hidden 
> To unsubscribe from Lilypond, click here.
> NAML




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Font-switching-docs-add-a-font-to-LilyPond-tp169460p169523.html
Sent from the Dev mailing list archive at Nabble.com.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]