Complement for those of us using Mac OS X:
the fonts files should be placed in:
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/fonts/otf
and:
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/fonts/svg
respectively.
JM
> Le 26 juin 2017 à 17:25, Federico Bruni <[email protected]> a écrit :
>
>
>
> Il giorno lun 26 giu 2017 alle 17:04, Urs Liska <[email protected]
> <mailto:[email protected]>> ha scritto:
>> Am 26.06.2017 um 16:53 schrieb Federico Bruni:
>>> Il giorno lun 26 giu 2017 alle 16:29, Urs Liska <[email protected]>
>>> ha scritto:
>>>> So, what is the content (tree) of /usr/share/lilypond/2.19.62 in your
>>>> installation?
>>> $ tree -d /usr/share/lilypond/2.19.62
>>> /usr/share/lilypond/2.19.62
>>> ├── fonts
>>> │ ├── otf -> /usr/share/fonts/lilypond
>>> │ ├── source
>>> │ └── svg
>>> ├── ly
>>> ├── ps
>>> ├── python
>>> ├── scm
>>> └── tex
>> Oh my, now I finally realize why these folders are used at all ...
>> But guessing from "otf -> /usr/share/fonts/lilypond" - did you ever try
>> to simply copy the alternative fonts into that folder? Basically this
>> will be accessible from *any* LilyPond installation, provided the
>> package manager doesn't purge unknown files in that directory.
>
> Yes, if I copy all the font otf files to /usr/share/fonts/lilypond, it is
> recognized and I can compile the snippet.
> I don't think that these files will be purged by the package manager. I'll
> see.
>
> Thanks for the help
>
>
>
>
> _______________________________________________
> lilypond-user mailing list
> [email protected] <mailto:[email protected]>
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> <https://lists.gnu.org/mailman/listinfo/lilypond-user>
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
