2016-12-21 18:44 GMT+01:00 Mirosław Doroszewski
:
> 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
Hi Miroslaw,
your post is something like "I want to do . How
to get there?" and so more appropriate for the user list.
This is the _bug_-list and you don't even report one. Btw, _if_ you
found a bug a tiny example is _needed_.
That said, there is no real builtin method for your wish, so you will
> Two sided mode in LilyPond version 2.18.2. [...]
Mirosław,
the 2.18.x series will no longer be updated. Please try the current
development version! IMHO, it is stable enough for daily use. [And
don't forget to use `convert-ly' to update your files to the recent
syntax.]
Another issue:
Two sided mode in LilyPond version 2.18.2.
1. Usually printed publications are made int two sided mode.
2. It implies that istead of margins left and right are inner and outer.
3. Bug: when two sided mode is set (two-sided = ##t), then margins are
always the same and unexpected, even with
Moving of lyrics in LilyPond version 2.18.2.
1. In song books sometimes after each verse of lyrics is put an
asterisk (*). Using it implies that syllable is moved left too much.
2. I have not find solution for it in manuals.
3. My solution not perfect: putting three (sometimes two or four)
linked
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:
\paper {
#(define fonts
(make-pango-font-tree "Times New Roman" % roman
"Nimbus
Size of titles when staff size and lyrics size are set independently
in LilyPond version 2.18.2.
1. When staff size and lyrics size are set independently, happens that
size of titles is too small.
2. My solution is not universal: it has to be dane on every titles of
large document (book).
3. And
Hi Simon,
thanks for your explanation. Now I get it. I think that the unexpected
use of #UP in the example in the docs is very confusing. Maybe it should
be mentioned somewhere that #UP equals 1 and #DOWN equals -1.
Sylvius
On 20.12.2016 20:26, Simon Albrecht wrote:
Hi Sylvius,
there is
Hello all,
I believe there is a issue with the way LilyPond handles grace notes on
ledger lines. As far as I know, ledger lines should be always visible and
nothing must block them (beams, slurs, slashes, etc.). LilyPond does that
automatically for regular notes, but the beams and slashes of