[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Setting font families for entire document in LilyPond version 2.18.2
From: |
Thomas Morley |
Subject: |
Re: Setting font families for entire document in LilyPond version 2.18.2. |
Date: |
Thu, 22 Dec 2016 01:21:36 +0100 |
2016-12-21 18:44 GMT+01:00 Mirosław Doroszewski
<address@hidden>:
> Setting font families for entire document in LilyPond version 2.18.2.
>
> 1. I have put solution to template which has been not in the same
> directory, according to manuals:
Nope, the manuals don't include wrong comments.
You are in guile-syntax, there you have to comment with semicolon
>
> \paper {
> #(define fonts
> (make-pango-font-tree "Times New Roman" % roman
> "Nimbus Sans" % sans
> "Luxi Mono" % typewriter
> (/ staff-height pt 20)))
> }
>
> 2. Effect has been for template file:
>
> GUILE signaled an error for the expression beginning here
> #
> (define fonts
The whole error-message gives the correct hint:
error: GUILE signaled an error for the expression beginning here
#
(define fonts
Unbound variable: %
> 3. I have put the solution inside a piece, not in template, and effect
> was perfect.
Only without %-comment
> 4. I have put the solution to template which has been in the same
> directory, and effect was perfect, too.
Only without %-comment
> 5. So, bug is this: setting font families for entire document does not
> work when template is not in the same directory.
No bug, but user-error with comments.
-Harm