Re: Setting font families for entire document in LilyPond version 2.18.2.

Hi Mirosław, On 20.12.2016 20:25, Mirosław Doroszewski wrote: Setting font families for entire document is not possible in template added to document with \include. Yes, it is. Just use something like this in your \include file: \paper { fonts = #(make-pango-font-tree "Linux

Re: Setting font families for entire document in LilyPond version 2.18.2.

Hi Miroslaw, not sure if I understand correctly what you mean. It is perfectly possible to write a file CustomTemplate.ly with a content like that: \paper { #(define fonts (make-pango-font-tree "Times New Roman" "Nimbus Sans,Nimbus Sans L"

Setting font families for entire document in LilyPond version 2.18.2.

Setting font families for entire document in LilyPond version 2.18.2. Setting font families for entire document is not possible in template added to document with \include. If is many documents in a book, there is necessary to set font families in each document separately. But this solution not

Re: ‘\note’ DURATION (string) DIR (number)

Hi Sylvius, there is no bug involved. If you don’t understand something, it’s better to ask on the user list. Help will be gladly given. On 20.12.2016 20:10, Sylvius Pold wrote: Hi, I seem to have some problems understanding the manuals. In lilypond-notation (instrument specific markup)

Re: Putting marks over bar lines in LilyPond version 2.18.2.

Hello again, this is a question for the -user list just the same. Best, Simon On 20.12.2016 20:49, Mirosław Doroszewski wrote: \version "2.18.2" \include "deutsch.ly" %{ Putting marks over bar lines in LilyPond version 2.18.2. 1. When mark is put over bar line, it is placed centrally by

Re: Scaling global staff size without scaling Lyrics in LilyPond version 2.18.2.

Hi Mirosław, I will not answer this e-mail, because it definitely has no place on the bug list. Please refer to the user list at . On 20.12.2016 20:48, Mirosław Doroszewski wrote: 4. So, please, make solution and describe it in manual. Also, please note that

Re: Moving of lyrics in LilyPond version 2.18.2.

Same here. On 20.12.2016 20:51, Mirosław Doroszewski wrote: \version "2.18.2" \include "deutsch.ly" %{ Moving of lyrics in LilyPond version 2.18.2. 1. In song books sometimes after each verse of lyrics is put asterisk (*). Using it implies that syllable is moved left too much. 2. I have not

‘\note’ DURATION (string) DIR (number)

Hi, I seem to have some problems understanding the manuals. In lilypond-notation (instrument specific markup) I read: ‘\note’ DURATION (string) DIR (number) This produces a note with a stem pointing in DIR direction, with the DURATION for the note head type and augmentation dots.

Putting marks over bar lines in LilyPond version 2.18.2.

\version "2.18.2" \include "deutsch.ly" %{ Putting marks over bar lines in LilyPond version 2.18.2. 1. When mark is put over bar line, it is placed centrally by default. But sometimes there is need to place the mark left or right aligned, i.e. in repeats. 2. I tried do so according to manuals

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

On 21.12.2016 00:02, Thomas Morley wrote: \set Score.defaultBarType = #"" \set Score.barAlways = ##t Wow, I wasn’t aware of the barAlways property! That’s exactly what’s needed. Best, Simon ___ bug-lilypond mailing list bug-lilypond@gnu.org

Setting font families for entire document.

Setting font families for entire document in LilyPond version 2.18.2. Setting font families for entire document is not possible in template added to document with \include. If is many documents in a book, there is necessary to set font families in each document separately. But this solution not

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

On 20.12.2016 20:45, Mirosław Doroszewski wrote: In unmetered music staff breaking is not calculated automatically I think that is a valid feature request, and I couldn’t find any tracker issue. Maybe there should be a third option for Score.NonMusicalPaperColumn.line-break-permission,

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

2016-12-20 23:17 GMT+01:00 Simon Albrecht : > On 20.12.2016 20:45, Mirosław Doroszewski wrote: >> >> In unmetered music staff breaking is not calculated automatically > > > I think that is a valid feature request, and I couldn’t find any tracker > issue. > > Maybe there

Slurs and ties — most difficult to make: developer has to think about them before his work.

Slurs and ties — most difficult to make: developer has to think about them before his work. 1. I have noticed in main web site of LilyPond beautiful image of music. 2. The image shows correct breaking of ties between (two) systems. 3. But when I was rewriting songs, it happend that breaking ties

Lyric hyphens in LilyPond version 2.18.2.

Lyric hyphens in LilyPond version 2.18.2. 1. Making hyphens accordingly to manuals is not correct, because when syllables inside words are calculated to be print without hyphens, there is too much space created between them. Confer correct "calculation" of text editors which place not any space

Re: Lyric hyphens in LilyPond version 2.18.2.

Hi Miroslow, 2016-12-21 0:28 GMT+01:00 Mirosław Doroszewski : > Lyric hyphens in LilyPond version 2.18.2. > > 1. Making hyphens accordingly to manuals is not correct, because when > syllables inside words are calculated to be print without hyphens, > there is too

Re: Slurs and ties — most difficult to make: developer has to think about them before his work.

Hi Miroslaw, again: this is not a very good bug report as described on our website: . Please be specific, report one well-defined problem and not a major rant of seven items. As Thomas already said – code examples are quasi-mandatory, except for very special cases. On 21.12.2016 00:24,

Re: Slurs and ties — most difficult to make: developer has to think about them before his work.

2016-12-21 0:24 GMT+01:00 Mirosław Doroszewski : > Slurs and ties — most difficult to make: developer has to think about > them before his work. > > 1. I have noticed in main web site of LilyPond beautiful image of music. > 2. The image shows correct breaking of

Nous ne serons jamais assez nombreux pour signer cette pétition

Salut à Tous , J'ai pas l'habitude d'embêter mes amis, mais la ça craint ! Saviez vous que l'état veut filer 11 vaccins à tous les nourissons (contre 3 actuellement). Nous ne serons jamais assez nombreux pour signer cette pétition, faites suivre à toutes vos relations, il s’agit de l’avenir de