Yes, impressive work!
If using Frescobaldi (I can only speak for the Mac version), one can install
the fonts in the System/Library/Fonts file and access them by setting the path
in Frescobaldi's Preferences. This works around the need to reinstall when
updating LilyPond to a new version.
At least, it works for me.
Stan
> On Oct 28, 2014, at 5:29 PM, tisimst <tisimst.lilyp...@gmail.com> wrote:
>
> Federico,
>
>> On Tue, Oct 28, 2014 at 4:11 PM, Federico Bruni [via Lilypond] <[hidden
>> email]> wrote:
>>
>> Hey Abraham, wonderful work!
>>
>> I didn't have the time to try your fonts so far. I'm trying now but I can't
>> find any minimal example in the website. All I have to do is adding a proper
>> \paper block or there's more?
>> I see that the font is found by fontconfig but I'm getting this error:
>>
>> fatal error: cannot find font: `haydn-11'
>>
>> I'm using lilypond v2.19.15
>
> You need to do two things:
>
> 1. Install the fonts in the correct LILYPOND font directory (NOT the system
> font directory)--see my instructions on the main page at
> fonts.openlilylib.org.
>
> 2. Use the following (minimal) syntax, for example, in your .ly file:
>
> #(set-global-staff-size 16) % this MUST come PRIOR to defining the fonts
> \paper {
> #(define fonts
> (set-global-fonts
> #:music "haydn"
> #:brace "haydn"
> #:factor (/ staff-height pt 20)
> ))
> }
>
> I thought I made that pretty clear on the website, but perhaps I did not. I
> do make mistakes like that.
>
>> BTW, why don't you make these fonts available through github's
>> openlilylib?It would be easier to update and test.
>
> That was the original intention, but after some discussion with Urs, we felt
> that it would probably do better to have their own site to make it seem more
> "professional".
>
> See, it's more than just maintaining a font file because if you take the font
> files and edit them in FontForge (or any other font editor), then re-save
> them, they won't work with LilyPond because there is some internal data that
> FontForge gets rid of when you open the good files.
>
> I use a handful of build scripts that make the fonts work with LilyPond, and
> I maintain them personally. I also update all the example files that showcase
> the fonts on the website, so it is easier for me to just do it that way.
> There is still a proposition to maintain the font stylesheets on github's
> openlilylib repository, but I haven't gotten there yet.
>
>> If you want to encourage donations or bounties for your work:
>> http://blog.bountysource.com/post/48954271533/improved-github-integration-automatically-update
>
>
> That's very interesting! I've never heard of this... I'll definitely have to
> think about that :)
>
> Let me know if I can help in any other way and thanks for the feedback!
>
> HTH,
> Abraham
>
>
> View this message in context: Re: Big Music Font Update
> Sent from the User mailing list archive at Nabble.com.
> _______________________________________________
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
