Markup problem
Good morning\evening to everyone,
attached a little problem of mine, please let me understand (and thanks a
lot to all users that helped me with the stencil definition, maybe I forgot
to answer!):
why, after the score, the second markup goes directly on the other page?
Thanks in advance
\version "2.22.1"
\header {
title = "HUGE TITLE"
tagline = ##f
}
\bookpart {
\header {
subtitle = "BOOKPART TITLE" }
\markup {
\vspace #2
\justify-string #
"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed sapien neque, efficitur quis iaculis in, tincidunt ut odio. In purus sem, sollicitudin in ante in, eleifend molestie libero. Curabitur facilisis malesuada lectus non lacinia. Nam sagittis orci nulla, nec pulvinar arcu facilisis eget. In hac habitasse platea dictumst. Sed consectetur tincidunt nulla id porta. Nulla pretium mi leo, vitae dapibus sem rhoncus quis. Morbi sed est in nibh convallis eleifend vel vel diam. Vestibulum in arcu in ligula ullamcorper finibus.
Cras facilisis, neque eu pretium ornare, leo ipsum sagittis augue, at lobortis odio augue ut diam. Cras suscipit consequat fermentum. Mauris ullamcorper lacus laoreet ipsum sagittis, quis blandit leo maximus. Nam vel elementum nisi. Nulla tempus malesuada ante at porttitor. Aliquam erat volutpat. Sed commodo, ligula sit amet efficitur finibus, arcu risus ultrices nisi, sit amet tristique enim elit sit amet eros. Praesent rhoncus nunc eu dolor dapibus vehicula. Nulla hendrerit dignissim libero, non suscipit arcu fringilla vitae. Pellentesque nisl tellus, faucibus id augue a, condimentum luctus augue. Etiam quis maximus elit, in hendrerit orci. Vestibulum elit tellus, porttitor vel odio vel, ullamcorper tincidunt dolor. Vestibulum a porta orci. Donec iaculis velit vehicula mi sagittis convallis.
Nullam at ex dapibus, molestie nulla eget, rutrum lectus. Ut cursus eu elit in semper. Duis fringilla leo metus, eget pharetra urna tempus sit amet. Aenean ac lectus maximus, tristique nisl quis, convallis tellus. Donec laoreet sem sit amet vehicula sodales. In a risus lacinia, dapibus odio sed, pellentesque quam. Ut eget nibh eu lacus consectetur egestas. Fusce sed maximus odio. Morbi posuere eu ante ut cursus. Morbi tempor leo sed elit elementum congue. Donec porttitor orci vitae nibh commodo, id elementum erat facilisis.
Vestibulum a viverra mauris, eget pellentesque risus. Nulla eu sapien elit. Sed pharetra turpis at eros volutpat, nec consequat tortor convallis. Proin nec cursus dolor. Donec consequat efficitur felis eu placerat. Vestibulum congue, velit id rutrum posuere, nunc velit sagittis dolor, at suscipit neque arcu quis tellus. Donec leo tellus, fringilla sed condimentum ac, sodales a nibh. Praesent eu tellus vestibulum, finibus nunc fringilla, semper odio. Sed ultricies at erat ac ornare. Duis a facilisis lacus, eu elementum quam.
Vivamus id enim gravida, auctor elit a, viverra nisi. Aliquam imperdiet ornare felis a molestie. Maecenas rhoncus lobortis tellus, quis cursus ipsum posuere eu. Cras vel mi sed nisl vulputate facilisis. Proin aliquam lacus at sagittis fermentum. Donec ut rhoncus enim, id finibus tortor. Phasellus porttitor, nisl quis cursus interdum, orci justo condimentum risus, quis pulvinar dui enim eu metus. Aliquam congue mollis dui, pretium commodo leo. Aliquam tincidunt tellus et ligula tristique fermentum. Aliquam auctor velit condimentum velit rutrum sodales."
}
\markup { \vspace #0.5 }
\score {
\relative c' {
c4 d e f g a g f e1
}
}
\markup { \vspace #0.5 }
\markup {
\justify-string #
"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed sapien neque, efficitur quis iaculis in, tincidunt ut odio. In purus sem, sollicitudin in ante in, eleifend molestie libero. Curabitur facilisis malesuada lectus non lacinia. Nam sagittis orci nulla, nec pulvinar arcu facilisis eget. In hac habitasse platea dictumst. Sed consectetur tincidunt nulla id porta. Nulla pretium mi leo, vitae dapibus sem rhoncus quis. Morbi sed est in nibh convallis eleifend vel vel diam. Vestibulum in arcu in ligula ullamcorper finibus.
Cras facilisis, neque eu pretium ornare, leo ipsum sagittis augue, at lobortis odio augue ut diam. Cras suscipit consequat fermentum. Mauris ullamcorper lacus laoreet ipsum sagittis, quis blandit leo maximus. Nam vel elementum nisi. Nulla tempus malesuada ante at porttitor. Aliquam erat volutpat. Sed commodo, ligula sit amet efficitur finibus, arcu risus ultrices nisi, sit amet tristique enim elit sit amet eros. Praesent rhoncus nunc eu dolor dapibus vehicula. Nulla hendrerit dignissim libero, non suscipit arcu fringilla vitae. Pellentesque nisl tellus, faucibus id augue a, condimentum luctus augue. Etiam quis maximus elit, in hendrerit orci. Vestibulum elit tellus, porttitor vel odio vel, ullamcorper tincidunt dolor. Vestibulum a porta orci. Donec iaculis velit vehicula mi sagittis convallis.
Nullam at ex dapibus, molestie nulla eget, rutrum lectus. Ut cursus eu elit in sem
Re: Markup problem
Hi, Am 13.02.22 um 11:35 schrieb Rip _Mus: Good morning\evening to everyone, attached a little problem of mine, please let me understand (and thanks a lot to all users that helped me with the stencil definition, maybe I forgot to answer!): why, after the score, the second markup goes directly on the other page? LilyPond is not very good at supporting text paragraphs running across page breaks. (Try making your first lorem ipsum-text longer and see what happens.) Part of a solution may be found in https://lilypond.org/doc/v2.23/Documentation/snippets/text.html#text-markup-list But for combining large amounts of text with interspersed LilyPond scores, I'd rather recommend a combination of LilyPond and LaTeX. LilyPond comes shipped with lilypond-book, but if you're willing to use LuaLaTeX, you can use lyluatex (https://github.com/jperon/lyluatex) which is a huge improvement ober lilypond-book. Lukas
Re: Markup problem
Am 13.02.2022 um 11:35 schrieb Rip _Mus: Good morning\evening to everyone, attached a little problem of mine, please let me understand (and thanks a lot to all users that helped me with the stencil definition, maybe I forgot to answer!): why, after the score, the second markup goes directly on the other page? Because it is too large to fit on the first page? If you want breaks inbetween the paragraphs you need to split it into separate markups. HTH, Michael -- Michael Gerdau email: m...@qata.de GPG-keys available on request or at public keyserver
Re: Markup problem
Thank you! I would like to avoid lilypond-book, because I only need to manage performance notes which, if they are extended, need to be spread over several pages automatically. The snippet works well! Rip_Mus Il giorno dom 13 feb 2022 alle ore 11:48 Lukas-Fabian Moser ha scritto: > Hi, > > Am 13.02.22 um 11:35 schrieb Rip _Mus: > > Good morning\evening to everyone, > > attached a little problem of mine, please let me understand (and > > thanks a lot to all users that helped me with the stencil definition, > > maybe I forgot to answer!): > > > > why, after the score, the second markup goes directly on the other page? > > LilyPond is not very good at supporting text paragraphs running across > page breaks. (Try making your first lorem ipsum-text longer and see what > happens.) Part of a solution may be found in > > https://lilypond.org/doc/v2.23/Documentation/snippets/text.html#text-markup-list > > But for combining large amounts of text with interspersed LilyPond > scores, I'd rather recommend a combination of LilyPond and LaTeX. > LilyPond comes shipped with lilypond-book, but if you're willing to use > LuaLaTeX, you can use lyluatex (https://github.com/jperon/lyluatex) > which is a huge improvement ober lilypond-book. > > Lukas > >
Re: Markup problem
Rip _Mus writes:
> Good morning\evening to everyone,
> attached a little problem of mine, please let me understand (and thanks a
> lot to all users that helped me with the stencil definition, maybe I forgot
> to answer!):
>
> why, after the score, the second markup goes directly on the other page?
Because markups are not broken across pages and it does not fit. Try
\version "2.22.1"
\header {
title = "HUGE TITLE"
tagline = ##f
}
\bookpart {
\header {
subtitle = "BOOKPART TITLE" }
\markuplist {
\vspace #2
\column-lines \wordwrap-string-internal ##t #
"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed sapien neque, efficitur quis iaculis in, tincidunt ut odio. In purus sem, sollicitudin in ante in, eleifend molestie libero. Curabitur facilisis malesuada lectus non lacinia. Nam sagittis orci nulla, nec pulvinar arcu facilisis eget. In hac habitasse platea dictumst. Sed consectetur tincidunt nulla id porta. Nulla pretium mi leo, vitae dapibus sem rhoncus quis. Morbi sed est in nibh convallis eleifend vel vel diam. Vestibulum in arcu in ligula ullamcorper finibus.
Cras facilisis, neque eu pretium ornare, leo ipsum sagittis augue, at lobortis odio augue ut diam. Cras suscipit consequat fermentum. Mauris ullamcorper lacus laoreet ipsum sagittis, quis blandit leo maximus. Nam vel elementum nisi. Nulla tempus malesuada ante at porttitor. Aliquam erat volutpat. Sed commodo, ligula sit amet efficitur finibus, arcu risus ultrices nisi, sit amet tristique enim elit sit amet eros. Praesent rhoncus nunc eu dolor dapibus vehicula. Nulla hendrerit dignissim libero, non suscipit arcu fringilla vitae. Pellentesque nisl tellus, faucibus id augue a, condimentum luctus augue. Etiam quis maximus elit, in hendrerit orci. Vestibulum elit tellus, porttitor vel odio vel, ullamcorper tincidunt dolor. Vestibulum a porta orci. Donec iaculis velit vehicula mi sagittis convallis.
Nullam at ex dapibus, molestie nulla eget, rutrum lectus. Ut cursus eu elit in semper. Duis fringilla leo metus, eget pharetra urna tempus sit amet. Aenean ac lectus maximus, tristique nisl quis, convallis tellus. Donec laoreet sem sit amet vehicula sodales. In a risus lacinia, dapibus odio sed, pellentesque quam. Ut eget nibh eu lacus consectetur egestas. Fusce sed maximus odio. Morbi posuere eu ante ut cursus. Morbi tempor leo sed elit elementum congue. Donec porttitor orci vitae nibh commodo, id elementum erat facilisis.
Vestibulum a viverra mauris, eget pellentesque risus. Nulla eu sapien elit. Sed pharetra turpis at eros volutpat, nec consequat tortor convallis. Proin nec cursus dolor. Donec consequat efficitur felis eu placerat. Vestibulum congue, velit id rutrum posuere, nunc velit sagittis dolor, at suscipit neque arcu quis tellus. Donec leo tellus, fringilla sed condimentum ac, sodales a nibh. Praesent eu tellus vestibulum, finibus nunc fringilla, semper odio. Sed ultricies at erat ac ornare. Duis a facilisis lacus, eu elementum quam.
Vivamus id enim gravida, auctor elit a, viverra nisi. Aliquam imperdiet ornare felis a molestie. Maecenas rhoncus lobortis tellus, quis cursus ipsum posuere eu. Cras vel mi sed nisl vulputate facilisis. Proin aliquam lacus at sagittis fermentum. Donec ut rhoncus enim, id finibus tortor. Phasellus porttitor, nisl quis cursus interdum, orci justo condimentum risus, quis pulvinar dui enim eu metus. Aliquam congue mollis dui, pretium commodo leo. Aliquam tincidunt tellus et ligula tristique fermentum. Aliquam auctor velit condimentum velit rutrum sodales."
}
\markup { \vspace #0.5 }
\score {
\relative c' {
c4 d e f g a g f e1
}
}
\markup { \vspace #0.5 }
\markuplist {
\column-lines \wordwrap-string-internal ##t #
"Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed sapien neque, efficitur quis iaculis in, tincidunt ut odio. In purus sem, sollicitudin in ante in, eleifend molestie libero. Curabitur facilisis malesuada lectus non lacinia. Nam sagittis orci nulla, nec pulvinar arcu facilisis eget. In hac habitasse platea dictumst. Sed consectetur tincidunt nulla id porta. Nulla pretium mi leo, vitae dapibus sem rhoncus quis. Morbi sed est in nibh convallis eleifend vel vel diam. Vestibulum in arcu in ligula ullamcorper finibus.
Cras facilisis, neque eu pretium ornare, leo ipsum sagittis augue, at lobortis odio augue ut diam. Cras suscipit consequat fermentum. Mauris ullamcorper lacus laoreet ipsum sagittis, quis blandit leo maximus. Nam vel elementum nisi. Nulla tempus malesuada ante at porttitor. Aliquam erat volutpat. Sed commodo, ligula sit amet efficitur finibus, arcu risus ultrices nisi, sit amet tristique enim elit sit amet eros. Praesent rhoncus nunc eu dolor dapibus vehicula. Nulla hendrerit dignissim libero, non suscipit arcu fringilla vitae. Pellentesque nisl tellus, faucibus id augue a, condimentum luctus augue. Etiam quis maximus elit, in hendrerit orci. Vestibulum elit tellus, porttitor vel odio vel, ullamcorper tincidunt dolor. Vestibulum a
Re: LilyPond 2.23.6 released
Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > LilyPond user discussion: > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > Hello developers, > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > The only issue I have currently encountered is when the filename is in > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > file. It could generate corrected "中文.midi", and also could generate > > > > correct ps and svg file, but the filenames are unreadable characters. > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > however I remember that I tested this in the past and made it work, > > > after fixing something in the LilyPond code. I'll have to dig up > > > details and figure out what broke / changed... > > > > Yep, I remembered correctly that there was a general issue with special > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > The problem was fixed quite some time ago in > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > works, ie LilyPond produces the correct filenames and correctly encoded > > contents. What doesn't work is Ghostscript converting the generated > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > error on our side since it works with the official Windows binaries > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > have to investigate how to solve this. > > Thanks a lot for your efforts on this issue. > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > filenames but correctly encoded contents. The only correct filename > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > 1.8 produced all correct filenames. > > The following is the output in CMD terminal. You will find that > filenames of ps and svg are not correct. However the content are correct. Okay, interesting. So there actually may be multiple problems on Windows, again working fine on Linux... > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe 中文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Converting to `涓枃.pdf'... > warning: `(gs -q -dNODISPLAY -dNOSAFER -dALLOWPSTRANSPARENCY -dNOPAUSE > -dBATCH -dAutoRotatePages=/None -dPrinted=false ./tmp--tmp-5651466)' > failed (1) > > fatal error: failed files: "涓枃.ly" > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --ps 中文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Copying to `涓枃.ps'... > Success: compilation successfully completed > > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 > 文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > D:\Jinso\Desktop\ly>d:\Program\lilypond-2.23.6\bin\lilypond.exe --svg 中 > 文.ly > GNU LilyPond 2.23.6 (running Guile 2.2) > Processing `涓枃.ly' > Parsing... > Interpreting music...[8][16] > Preprocessing graphical objects... > Interpreting music... > MIDI output to `涓枃.mid'... > Finding the ideal number of pages... > Fitting music on 1 page... > Drawing systems... > Success: compilation successfully completed > > D:\Jinso\Desktop\ly>dir > 驱动器 D 中的卷是 Data > 卷的序列号是 D6A8-795E > > D:\Jinso\Desktop\ly 的目录 > > 2022/02/12 20:32 . > 2022/02/12 20:32 .. > 2022/02/12 20:28 211 tmp--tmp-5651466 > 2022/02/12 19:57 1,617 中文.ly > 2022/02/12 20:32 1,295 中文.mid > 2022/02/12 20:28 2,187 涓枃-tmp-5790652.457878.pdf > 2022/02/12 20:2843,410,812 -tmp-5790652 > 2022/02/12 20:3243,410,812 .ps > 2022/02/12 20:3288,064 .svg > 7 个文件 86,914,998 字节 > 2 个目录 592,849,948,672 可用字节 signature.asc Description: This is a digitally signed message part
Re: Windows laptop
Wols Lists writes: > Oh - and the other route to consider, there always used to be Ubuntu > Virtualbox or Vmware images of lilypond. Virtualbox is a freebie, and > I think you can get free Vmware. Why would you need that? Just run lilypond natively in Ubuntu. (Or am I misunderstanding?) I a Mac user is thinking of getting a Windows PC just to run Lilypond, I would think they'd be better off running Ubuntu (or some flavor of Linux) instead. -David
Re: Windows laptop
On 13/02/2022 17:36, David Zelinsky wrote: Wols Lists writes: Oh - and the other route to consider, there always used to be Ubuntu Virtualbox or Vmware images of lilypond. Virtualbox is a freebie, and I think you can get free Vmware. Why would you need that? Just run lilypond natively in Ubuntu. (Or am I misunderstanding?) Sorry yes you are. The whole point of the suggestion is (1) run lilypond natively in Ubuntu, and (2) avoid shelling out for a new PC! I a Mac user is thinking of getting a Windows PC just to run Lilypond, I would think they'd be better off running Ubuntu (or some flavor of Linux) instead. See above :-) Cheers, Wol
Re: Windows laptop
Wols Lists writes: > On 13/02/2022 17:36, David Zelinsky wrote: >> Wols Lists writes: >> >>> Oh - and the other route to consider, there always used to be Ubuntu >>> Virtualbox or Vmware images of lilypond. Virtualbox is a freebie, and >>> I think you can get free Vmware. >> >> Why would you need that? Just run lilypond natively in Ubuntu. >> (Or am I misunderstanding?) >> > Sorry yes you are. The whole point of the suggestion is (1) run > lilypond natively in Ubuntu, and (2) avoid shelling out for a new PC! I wholeheartedly agree with those points! But why would you need Virtualbox or VMware? Just install the binaries from lilypond.org. -David
More about stencil
Hello everyone,
thanks to your many suggestions, I was able to get a little into the
perspective of modifying the stencils.
I created a stencil modification that adds a small arrow (sort of a
glissando) to the left of the note or accident.
However, I cannot understand why the ascending arrows let the stem no
longer attached to the notehead. Do you have any ideas?
Rip_mus
\version "2.22.1"
glis-su-acc = {
\once \override Accidental.stencil =
#(lambda (grob)
(let* (
(acc (ly:accidental-interface::print grob))
(arr (ly:stencil-add
(make-line-stencil 0.1 (- X 0.3) (- Y 1.25) (- X 0.9) (- Y 1.85));tratto principale 0.6
(make-line-stencil 0.1 (- X 0.15) (- Y 1.4) (- X 0.75) (- Y 2));tratto principale 0.6
(make-line-stencil 0.15 (- X 0.15) (- Y 1.25) (- X 0.55) (- Y 1.25));tratto orizzontale 0.4
(make-line-stencil 0.15 (- X 0.15) (- Y 1.25) (- X 0.15) (- Y 1.65));tratto verticale 0.4
)
)
)
(ly:stencil-combine-at-edge arr X RIGHT acc 0.2)
)
)
}
glis-giu-acc = {
\once \override Accidental.stencil =
#(lambda (grob)
(let* (
(acc (ly:accidental-interface::print grob))
(arr (ly:stencil-add
(make-line-stencil 0.1 (- X 0.3) (- Y 0.75) (- X 0.9) (- Y 0.15));tratto principale 0.6
(make-line-stencil 0.1 (- X 0.15) (- Y 0.6) (- X 0.75) (+ Y 0));tratto principale 0.6
(make-line-stencil 0.15 (- X 0.15) (- Y 0.75) (- X 0.55) (- Y 0.75));tratto orizzontale 0.4
(make-line-stencil 0.15 (- X 0.15) (- Y 0.75) (- X 0.15) (- Y 0.35));tratto orizzontale 0.4
)
)
)
(ly:stencil-combine-at-edge arr X RIGHT acc 0.2)
)
)
}
glis-su-nat = {
\once \override Stem.X-offset = #(lambda (grob)
(if (= UP (ly:grob-property grob 'direction))
1.43
0.19))
\once \override NoteHead.stencil =
#(lambda (grob)
(let* (
(note (ly:note-head::print grob))
(arr (ly:stencil-add
(make-line-stencil 0.1 (- X 0.3) (- Y 1.25) (- X 0.9) (- Y 1.85));tratto principale 0.6
(make-line-stencil 0.1 (- X 0.15) (- Y 1.4) (- X 0.75) (- Y 2));tratto principale 0.6
(make-line-stencil 0.15 (- X 0.15) (- Y 1.25) (- X 0.55) (- Y 1.25));tratto orizzontale 0.4
(make-line-stencil 0.15 (- X 0.15) (- Y 1.25) (- X 0.15) (- Y 1.65));tratto verticale 0.4
)
)
)
(ly:stencil-combine-at-edge arr X RIGHT note 0.2)
)
)
}
glis-giu-nat = {
\once \override Stem.X-offset = #(lambda (grob)
(if (= UP (ly:grob-property grob 'direction))
1.23
0))
\once \override NoteHead.stencil =
#(lambda (grob)
(let* (
(note (ly:note-head::print grob))
(arr (ly:stencil-add
(make-line-stencil 0.1 (- X 0.3) (- Y 0.75) (- X 0.9) (- Y 0.15));tratto principale 0.6
(make-line-stencil 0.1 (- X 0.15) (- Y 0.6) (- X 0.75) (+ Y 0));tratto principale 0.6
(make-line-stencil 0.15 (- X 0.15) (- Y 0.75) (- X 0.55) (- Y 0.75));tratto orizzontale 0.4
(make-line-stencil 0.15 (- X 0.15) (- Y 0.75) (- X 0.15) (- Y 0.35));tratto orizzontale 0.4
)
)
)
(ly:stencil-combine-at-edge arr X RIGHT note 0)
)
)
}
#(set-global-staff-size 20)
\header {
title = \markup {\column { "About stencils" \vspace #2 }}
tagline = ##f
}
\new Staff {
\relative c' {
\once \override Score.FootnoteItem.annotation-line = ##f
\footnote "*" #'(-0.2 . -1) "* glissando at the end of previous note" NoteHead
\stemDown \glis-giu-nat f2 \glis-su-nat b2 |
\glis-giu-acc fis4 \glis-su-acc bes2.
\glis-giu-nat c32 \glis-su-nat c c c c c c c \glis-giu-nat c \stemUp \glis-giu-nat c
}
}
\paper {
top-margin = 2 \cm
bottom-margin = 2 \cm
left-margin = 2 \cm
right-margin = 2 \cm
indent = 0\mm
}
Re: Wide screen Windows question
Not a PDF viewer, but if you open a PDF file in Firefox and select Wrapped Scrolling from the Tools menu (the >> button), you should see pages side-by-side dependent upon your Zoom settings and how wide you have resized your Firefox window. Just play with the zoom % and window width to suit your taste, i.e., 4 pages side by side. Doesn't this also address your 2nd point? That is 1 page = 1 panel. On 2022-02-12 10:29, Paul McKay wrote: Hi Apologies that only half this question is Lilypond, but I'm sure someone in this group will have shared my frustration. I am very tempted to buy a nice wide monitor. I currently play from the screen of my laptop which sits on top of my grand piano. It's a real pain if I have to rotate the screen and the laptop to play from an A4 page at more or less full size. If I got a nice big monitor, the laptop could sit beside the piano and everything would be lovely … … except … any PDF reader will display 2 pages side by side. On a monitor with a 4:1 aspect ratio, this means that half of it is unused. Despite searching for a week, I haven't found any PDF reader which even thinks that wasting 50% of the display area is a bad idea. Does anyone know of any PDF reader which will display more than 2 pages at once? This is the best solution I have so far thought of. Other suggestions would be very welcome. On the other hand, I spend a huge percentage of my time playing music I've typed into LilyPond. It would be very easy to make a PDF file where pages were 4:1 and landscape. But rather than have a single line of music 80cm long, it would be good to have the page divided into four 20cm panels. Could someone tell me how to ask LilyPond to put music into columns? So far, I've only been able to find out about how to ask LilyPond to put words into columns. Many thanks in advance Paul McKay
Re: Windows laptop
On 13/02/2022 18:35, David Zelinsky wrote: Wols Lists writes: On 13/02/2022 17:36, David Zelinsky wrote: Wols Lists writes: Oh - and the other route to consider, there always used to be Ubuntu Virtualbox or Vmware images of lilypond. Virtualbox is a freebie, and I think you can get free Vmware. Why would you need that? Just run lilypond natively in Ubuntu. (Or am I misunderstanding?) Sorry yes you are. The whole point of the suggestion is (1) run lilypond natively in Ubuntu, and (2) avoid shelling out for a new PC! I wholeheartedly agree with those points! But why would you need Virtualbox or VMware? Just install the binaries from lilypond.org. If you'd been following the thread ... the whole point was the binaries wouldn't run on updated MacOS. That appears to be fixed, which was why I opened my original email with the comment that I hoped the information would be irrelevant ... :-) (but useful :-) Cheers, Wol
Re: LilyPond 2.23.6 released
Am So., 13. Feb. 2022 um 16:02 Uhr schrieb Jonas Hahnfeld via LilyPond user discussion : > > Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > > LilyPond user discussion: > > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > > Hello developers, > > > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > > > The only issue I have currently encountered is when the filename is in > > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > > file. It could generate corrected "中文.midi", and also could generate > > > > > correct ps and svg file, but the filenames are unreadable characters. > > > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > > however I remember that I tested this in the past and made it work, > > > > after fixing something in the LilyPond code. I'll have to dig up > > > > details and figure out what broke / changed... > > > > > > Yep, I remembered correctly that there was a general issue with special > > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > > The problem was fixed quite some time ago in > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > > works, ie LilyPond produces the correct filenames and correctly encoded > > > contents. What doesn't work is Ghostscript converting the generated > > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > > error on our side since it works with the official Windows binaries > > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > > have to investigate how to solve this. > > > > Thanks a lot for your efforts on this issue. > > > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > > filenames but correctly encoded contents. The only correct filename > > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > > 1.8 produced all correct filenames. > > > > The following is the output in CMD terminal. You will find that > > filenames of ps and svg are not correct. However the content are correct. > > Okay, interesting. So there actually may be multiple problems on > Windows, again working fine on Linux... Not for me, being on Ubuntu 20.04 Compiling \markup \override #'(font-name . "思源黑体 HW Bold") "中文" returns: ERROR: In procedure ly:text-interface::interpret-markup: Invalid read access of chars of wide string: "思源黑体 HW Bold 3.8662109375" For both setups (see my recent mail on devel), i.e. self-compiled 2.23.6 and the GitLab-archive Cheers, Harm Verbose output: $ lilypond-git -V atest-109.ly Log level set to 287 GNU LilyPond 2.23.6 (running Guile 2.2) Relocation LilyPond binary has absolute file name: /home/hermann/lilypond-git/build/out/bin/lilypond Setting INSTALLER_PREFIX to '/home/hermann/lilypond-git/build/out' Using run-time value for datadir, setting it to '/home/hermann/lilypond-git/build/out/share/lilypond/current' Using compile-time value for libdir, setting it to '/usr/local/lib/lilypond/2.23.6' Using compile-time value for localedir, setting it to '/usr/local/share/locale' Using compile-time value for relocdir, setting it to '' Prepending '/home/hermann/lilypond-git/build/out/bin' to PATH Setting PATH to '/home/hermann/lilypond-git/build/out/bin:/home/hermann/openlilylib:/home/hermann/extending-lilypond:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin' Setting GUILE_AUTO_COMPILE to '0' Setting GUILE_WARN_DEPRECATED to 'detailed' Setting XDG_CACHE_HOME to '/home/hermann/lilypond-git/build/out/share/lilypond/current' Setting GC_INITIAL_HEAP_SIZE to '40M' Setting GC_NPROCS to '1' Setting GC_FREE_SPACE_DIVISOR to '1' Effective prefix: '/home/hermann/lilypond-git/build/out/share/lilypond/current' PATH="/home/hermann/lilypond-git/build/out/bin:/home/hermann/openlilylib:/home/hermann/extending-lilypond:/home/hermann/git-cl:/home/hermann/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin" [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/lily.scm] Using (ice-9 curried-definitions) module [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/lily-library.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/output-lib.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/markup-macros.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/parser-ly-from-scheme.scm] [/home/hermann/lilypond-git/build/out/share/lilypond/current/scm/lily/file-cache.scm] [/hom
Re: More about stencil
On 2022-02-13 11:43 am, Rip _Mus wrote:
Hello everyone,
thanks to your many suggestions, I was able to get a little into the
perspective of modifying the stencils.
I created a stencil modification that adds a small arrow (sort of a
glissando) to the left of the note or accident.
However, I cannot understand why the ascending arrows let the stem no
longer attached to the notehead. Do you have any ideas?
Modifying the NoteHead stencil as you are doing changes its extents,
thus affects the attachment point. One option is to add the arrow to
the final stencil but preserve the original extents:
(ly:stencil-outline
(ly:stencil-combine-at-edge arr X RIGHT note 0)
note)
(The above approach might result in collisions.)
Another option would be to utilize Fingering as a host grob, as that
already handles alignment with notes whether or not accidentals are
present:
(Below also I show an alternate method for defining the arrows, so that
a shared symbol is simply rotated. Custom extents are specified so that
the arrows align as desired.)
double-right-arrow =
#(ly:stencil-add
(make-line-stencil 0.1 -0.9 0.1 -0.1 0.1)
(make-line-stencil 0.1 -0.9 -0.1 -0.1 -0.1)
(make-line-stencil 0.15 -0.3 0.3 0 0)
(make-line-stencil 0.15 -0.3 -0.3 0 0))
glis-su-arrow =
#(ly:make-stencil
(ly:stencil-expr
(ly:stencil-rotate double-right-arrow 45 RIGHT CENTER))
'(-0.7 . -0.2) '(-0.3 . 0.7))
glis-giu-arrow =
#(ly:make-stencil
(ly:stencil-expr
(ly:stencil-rotate double-right-arrow -45 RIGHT CENTER))
'(-0.7 . -0.2) '(-0.7 . 0.3))
glis-giu =
#(define-music-function
(note) (ly:music?)
(ly:music-set-property! note 'articulations
(cons
(make-music 'FingeringEvent 'digit 1
'tweaks (list (cons (quote stencil) glis-giu-arrow)))
(ly:music-property note 'articulations '(
#{ \once \set fingeringOrientations = #'(left)
#(make-event-chord (list note)) #})
glis-su =
#(define-music-function
(note) (ly:music?)
(ly:music-set-property! note 'articulations
(cons
(make-music 'FingeringEvent 'digit 1
'tweaks (list (cons (quote stencil) glis-su-arrow)))
(ly:music-property note 'articulations '(
#{ \once \set fingeringOrientations = #'(left)
#(make-event-chord (list note)) #})
\new Staff {
\relative c' {
\once \override Score.FootnoteItem.annotation-line = ##f
\footnote "*" #'(-0.2 . -1) "* glissando at the end of previous
note" NoteHead
\stemDown \glis-giu f2 \glis-su b |
\glis-giu fis4 \glis-su bes2.
\glis-giu c32 \glis-su c c c c c c c
\glis-giu c \stemUp \glis-giu c
}
}
Since Fingerings must be inside a chord (i.e. <>) construct in order to
respect fingeringOrientations, the music functions above have to do some
manipulation of the argument. Depending on how you intend on using
these arrows in context, it might be worth the time to invent a custom
grob instead rather than cannibalize something built-in.
-- Aaron Hill
Re: More about stencil
Hello Rip, the problem is that you are modifying the stencil of the NoteHead, thus changing its dimensions. Take a look at this old Lilypond Blog post: https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/2013/08/ adding-ornamentations-to-note-heads-part-1/[1] In there a new Event and Grob for Head ornamentation is added, which would probably be better suited for your demands. Cheers, Valentin Am Sonntag, 13. Februar 2022, 20:43:07 CET schrieb Rip _Mus: > Hello everyone, > thanks to your many suggestions, I was able to get a little into the > perspective of modifying the stencils. > I created a stencil modification that adds a small arrow (sort of a > glissando) to the left of the note or accident. > However, I cannot understand why the ascending arrows let the stem no > longer attached to the notehead. Do you have any ideas? > > Rip_mus [1] https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/2013/08/ adding-ornamentations-to-note-heads-part-1/ signature.asc Description: This is a digitally signed message part.
\repeat segno (Was re: LilyPond 2.23.6 released)
On 2/8/2022 8:07 AM, Jonas Hahnfeld via Discussions on LilyPond development wrote: We are happy to announce the release of LilyPond 2.23.6. Thank you, especially for the new `\repeat segno` code. Works beautifully. It’ll take a little getting used to, figuring out when & when not to use `\alternative` in a `\repeat segno` block, but it’s already made my code much cleaner. Between `\repeat segno`, `\fine`, `\section` and `\sectionLabel`, most of the non-music formatting commands I’d used can be eliminated from my code. —Joel
Re: More about stencil
Hello Rip, also for a more recent version that is compatible with 2.22 check out the nenuvar-side- ornementations.ily from https://github.com/nsceaux/nenuvar-lib[1] This is not compatible with the latest versions of Lilypond for now. The amazing Jean quite recently fixed the magnetic-snap thingy, which had the same problem. To apply his fix to your situation replace the definition of define-grob-definition in line 7 by #(define (define-grob-definition grob-name grob-entry) (set! all-grob-descriptions (cons ((@@ (lily) completize-grob-entry) (cons grob-name grob-entry)) all-grob-descriptions))) Cheers, Valentin Am Sonntag, 13. Februar 2022, 22:51:25 CET schrieb Valentin Petzel: > Hello Rip, > > the problem is that you are modifying the stencil of the NoteHead, thus > changing its dimensions. > > Take a look at this old Lilypond Blog post: > https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/2013 > /08/ adding-ornamentations-to-note-heads-part-1/[1] > > In there a new Event and Grob for Head ornamentation is added, which would > probably be better suited for your demands. > > Cheers, > Valentin > > Am Sonntag, 13. Februar 2022, 20:43:07 CET schrieb Rip _Mus: > > Hello everyone, > > thanks to your many suggestions, I was able to get a little into the > > perspective of modifying the stencils. > > I created a stencil modification that adds a small arrow (sort of a > > glissando) to the left of the note or accident. > > However, I cannot understand why the ascending arrows let the stem no > > longer attached to the notehead. Do you have any ideas? > > > > Rip_mus > > > [1] > https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/201 > 3/08/ adding-ornamentations-to-note-heads-part-1/ [1] https://github.com/nsceaux/nenuvar-lib signature.asc Description: This is a digitally signed message part.
Blind and visually impaired users learning LilyPond
Hello, I am a proud blind musician and composer. I first tried
LilyPond in 2017; I found it after Googling things like "text-based
music generator" and "text-based music format", because that was a
lifelong dream of mine, to edit MIDI in a text editor-friendly format
and then convert to standard MIDI. I didn't start seriously using
LilyPond until 2019, but one of my computers had it installed for a
few days in 2017. Now, I know that LilyPond is a text-based format,
therefore it is much preferred over graphical score editors by blind
people, but there's one thing that seems to discourage blind users.
By default, if you just start your file with a version statement and
then put some notes in some braces, there is no audio output! It makes
the log file, uses the engraver and makes a PDF, and that's it. So
when I first learned LilyPond, I knew that, as a blind person, I
needed audio output; we obviously can't read score PDFs. Now, as a
beginner in 2017, I obviously started from the first page of the
manual, but all examples at the beginning had PDF output, no MIDI
output. So I had to jump ahead in the manual, doing a search in the
file for the word MIDI, until I found the \midi { } command. And then,
when I started putting \layout { } \midi { } at the end of my files, I
got an error, so I looked more closely at the examples containing this
command, and noticed there was a \score brace, and therefore I made
sure that \layout and \midi came before that final closing brace of
\score. Then I went back to the beginning of the manual and tried all
the beginner code examples, this time inside a \score brace, with
\layout and \midi at the end, so every time I engraved, a MIDI also
came out so I can actually listen to what I'm typing. So do you think
the default configuration is biased against people with visual
disabilities? Either that, or the manual is. The manual doesn't teach
you the \score command until later, but I needed it to get the \midi
command to work properly, which is a command that blind people need.
But the \midi command, let alone the \score command, aren't taught
until later in the book, so were they not thinking of blind people? I
actually associate text-based music writing with blind people; it
seems like all the people with eyesight that I know use graphical
editors, leaving the text-based formats for us blind people. But no,
the basic code only compiles to a PDF, no MIDI. And yes, I repeated
the experiment this year on new stable release version 2.22.1, and
yes, it's the same as when I tried it on 2.18.2 all those years ago.
I'm helping someone, another blind user, learn LilyPond because she
likes to experiment with music, and being blind, even semi-accessible
programs like Noteworthy Composer can be difficult especially in the
editing department, so I'm guiding her through LilyPond and that's
when I repeated the experiment from 2017. Only this time I remembered
the \score bracket, so I put my example in that, put \layout and \midi
just before the final brace, and there, we were able to listen to all
our examples every time we engraved. I'm glad I was determined enough
to find the \midi command; I have read about other blind composers, I
keep thinking there's a famous one from China who used LilyPond, but
do you think that, in general, LilyPond or at least the manual isn't
blind friendly? I feel bad for anyone who had to do what I do; a
beginner who's supposed to be reading the beginning examples needing
to flip to the middle of the book just to find out how to use the
\midi command just to go back to the beginning to try the simple
examples; \midi command should be taught at the beginning if the
program is as blind accessible as I thought, which I thought a
text-based music format would be. Anyway, once I got the MIDI command
in the right place, I have since written full piano pices, short
jingles using multiple orchestral instruments, and even three or four
songs with lyrics perfectly aligned on the score. If there are any
blind users on the list, I hope to hear what you think about PDF only
being the default, and learning how to make it compile to MIDI coming
much later in the manual. I wouldn't wish for any beginner to flip to
the advanced section of the manual just to grab an accessible command;
the accessible command should be taught early or be default; it would
probably be easier to just teach people the MIDI command early on;
LilyPond is the perfect solution for blind people who want to compose,
as long as they get that command at the beginning.
Re: Font kerning
On 2/7/2022 11:53 AM, Francesco Napoleoni wrote:
How can I adjust (if possible) such property in a markup block?
namely I would like to “shrink” the “V.° I.°” and the “V.° 2.°” text like the
attached screenshot.
I wonder whether you’re using the wrong symbol, and using the correct
one might help a little. Your code is using the degree sign “°” U+B0,
when by context this should probably be the masculine ordinal indicator
“º” U+BA.
(Some fonts display this symbol as a superscript “o” like “ᵒ”; some add
an underline to it like “̵ᵒ”; some add an underdot that I can’t easily
imitate by abusing other Unicode characters; and your source material is
using a full-stop “.” kerned in pretty tightly.)
I’m also pretty sure this is a font with old-style figures, where the
numeral “1” looks like a small-caps “ɪ”; and so the v’s should be
lower-case.
So the actual text should be “vº1º” & “vº2º” or “v.º1.º” & “v.º2.º”:
{
c''1^\markup {
\override #'(font-name . "TeX Gyre Schola")
\override #'(font-features . ("onum"))
{ "vº1º2º" }
}
c''^\markup \concat {
\override #'(font-name . "TeX Gyre Termes")
\override #'(font-features . ("onum"))
{ "v." \hspace #-0.4 "º" "1." \hspace #-0.6 "º" "2." \hspace #-0.6
"º" }
}
}
—Joel
Re: Blind and visually impaired users learning LilyPond
Hello Tyler, Are the defaults biased against people with visual disabilities? I’d say no. They are maybe not perfect, but there is surely no intent to make it harder for people with visual disabilities to use it. If just has never been a major concern for the small set of developers. Also I think Lilypond’s way is not really that suitable for such needs. Lilypond’s syntax is all about being quite powerful with what you can do with it, and less about being easy to parse. I suppose many of the structures Lilypond has will be quite hard to use, considering they can be quite hard to read with perfect eyesight. This approach allows us to have lots of power, but often this power is not really nescessary. Thus what I’d suggest is to have a sort of wrapper language that relies on text for structure, making it easier to navigate by stuff like TTS. We surely could have something like a command line option to create midi for each score, but I feel like default Lilypond is not really the most adequate solution for this problem. Concerning the documentation I’d say: Rather than shifting some elements to be earlier or later we could have a dedicated point in the documentation for this matter, with all of the information especially relevant for visually impaired users in one place. I’m sure no one here would oppose doing reasonable things to make Lilypond more accessible, but for most people here this is not an issue, and most people here do not know a lot about what is important in such cases. So we also need your help to know what things are important, and what can be done better. Best, Valentin signature.asc Description: This is a digitally signed message part.
Re: Blind and visually impaired users learning LilyPond
Greetings Tyler, I would gently suggest that, when asking for help or making critical suggestions, not to simultaneously accuse people whom you do not know of cardinal faults. Likewise, it is not wise to assume that all people in a certain situation operate or think in the same way; I too am unable to see but have never, until now, identified as such to the LilyPond community. The VERY first subsubsection of the Learning Manual, 1.1.1, indicates that examples in the manual may not always reflect the way they should be written in order to successfully compile. And a quick look into the Table of Contents would have shown you where to find the relevant midi sections. Your and Valentin's suggestions are certainly warranted. I prefer Valentin's, simply because it is much more streamlined and works nicely with the way the manuals are already structured. Hwaen Ch'uqi On 2/13/22, Valentin Petzel wrote: > Hello Tyler, > > Are the defaults biased against people with visual disabilities? I’d say no. > > They are maybe not perfect, but there is surely no intent to make it harder > > for people with visual disabilities to use it. If just has never been a > major > concern for the small set of developers. > > Also I think Lilypond’s way is not really that suitable for such needs. > Lilypond’s syntax is all about being quite powerful with what you can do > with > it, and less about being easy to parse. I suppose many of the structures > Lilypond has will be quite hard to use, considering they can be quite hard > to > read with perfect eyesight. > > This approach allows us to have lots of power, but often this power is not > really nescessary. Thus what I’d suggest is to have a sort of wrapper > language > that relies on text for structure, making it easier to navigate by stuff > like > TTS. We surely could have something like a command line option to create > midi > for each score, but I feel like default Lilypond is not really the most > adequate solution for this problem. > > Concerning the documentation I’d say: Rather than shifting some elements to > be > earlier or later we could have a dedicated point in the documentation for > this > matter, with all of the information especially relevant for visually > impaired > users in one place. > > I’m sure no one here would oppose doing reasonable things to make Lilypond > more accessible, but for most people here this is not an issue, and most > people here do not know a lot about what is important in such cases. So we > also need your help to know what things are important, and what can be done > > better. > > Best, > Valentin
Re: Blind and visually impaired users learning LilyPond
Of possible interest: MusicXML to braille music conversion (sent to this mailing list Jan 2020) https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00418.html and also: Braille music translation system (BrailleMUSE v5.62pp20210208) from MusicXML to Braille score https://braillemuse.net/BrailleMUSE/en2/Input-e-b2-lyricP.jsp
Re: Blind and visually impaired users learning LilyPond
A lot of good points. I rather like the idea of there being a section in the documentation for visually impaired users; I would even be willing to help contribute to such a section. On 2/13/22, Kevin Cole wrote: > Of possible interest: > > MusicXML to braille music conversion (sent to this mailing list Jan 2020) > https://lists.gnu.org/archive/html/lilypond-user/2020-01/msg00418.html > > and also: > > Braille music translation system (BrailleMUSE v5.62pp20210208) from > MusicXML to Braille score > https://braillemuse.net/BrailleMUSE/en2/Input-e-b2-lyricP.jsp >
Re: Blind and visually impaired users learning LilyPond
> I rather like the idea of there being a section in the documentation > for visually impaired users; I would even be willing to help > contribute to such a section. Excellent, and thanks for the offer. If you find time to write such a section, simply send your suggested text to this list, indicating where to insert it. We will then discuss it and do the integration into the documentation. Werner
Re: Blind and visually impaired users learning LilyPond
Another approach could be to add a new first chapter, maybe named “Discovering LilyPond”, containing a handful of examples without much commentary. Those could illustrate various features such as <<…>> without a \score around, \score, \book, chords and lyrics, as well as PDF, SVG and MIDI output. JM > Le 14 févr. 2022 à 06:21, Werner LEMBERG a écrit : > > >> I rather like the idea of there being a section in the documentation >> for visually impaired users; I would even be willing to help >> contribute to such a section. > > Excellent, and thanks for the offer. If you find time to write such a > section, simply send your suggested text to this list, indicating > where to insert it. We will then discuss it and do the integration > into the documentation. > > >Werner >
Re: Blind and visually impaired users learning LilyPond
Greetings Jacques, Admittedly, I cannot find it at the moment, but is there not already a Templates section? Perhaps these additions could be added to that? HC On 2/14/22, Jacques Menu wrote: > Another approach could be to add a new first chapter, maybe named > “Discovering LilyPond”, containing a handful of examples without much > commentary. > > Those could illustrate various features such as <<…>> without a \score > around, \score, \book, chords and lyrics, as well as PDF, SVG and MIDI > output. > > JM > >> Le 14 févr. 2022 à 06:21, Werner LEMBERG a écrit : >> >> >>> I rather like the idea of there being a section in the documentation >>> for visually impaired users; I would even be willing to help >>> contribute to such a section. >> >> Excellent, and thanks for the offer. If you find time to write such a >> section, simply send your suggested text to this list, indicating >> where to insert it. We will then discuss it and do the integration >> into the documentation. >> >> >>Werner >> > > >
Re: LilyPond 2.23.6 released
Am Sonntag, dem 13.02.2022 um 22:37 +0100 schrieb Thomas Morley: > Am So., 13. Feb. 2022 um 16:02 Uhr schrieb Jonas Hahnfeld via LilyPond > user discussion : > > > > Am Samstag, dem 12.02.2022 um 20:43 +0800 schrieb Jinsong Zhao: > > > On 2022/2/12 18:48, Jonas Hahnfeld wrote: > > > > Am Mittwoch, dem 09.02.2022 um 20:39 +0100 schrieb Jonas Hahnfeld via > > > > LilyPond user discussion: > > > > > Am Mittwoch, dem 09.02.2022 um 12:07 +0800 schrieb Jinsong Zhao: > > > > > > Hello developers, > > > > > > > > > > > > Thanks a lot for the transition towards Guile 2.2. I've switched to > > > > > > 2.23.6/guile 2.2 on Windows 10. > > > > > > > > > > > > The only issue I have currently encountered is when the filename is > > > > > > in > > > > > > Chines, for example "中文.ly", then lilypond could not generate PDF > > > > > > file. It could generate corrected "中文.midi", and also could generate > > > > > > correct ps and svg file, but the filenames are unreadable > > > > > > characters. > > > > > > > > > > I can confirm it's not working with the version using Guile 2.2 - > > > > > however I remember that I tested this in the past and made it work, > > > > > after fixing something in the LilyPond code. I'll have to dig up > > > > > details and figure out what broke / changed... > > > > > > > > Yep, I remembered correctly that there was a general issue with special > > > > character filenames: https://gitlab.com/lilypond/lilypond/-/issues/6089 > > > > The problem was fixed quite some time ago in > > > > https://gitlab.com/lilypond/lilypond/-/merge_requests/612 and this > > > > works, ie LilyPond produces the correct filenames and correctly encoded > > > > contents. What doesn't work is Ghostscript converting the generated > > > > Postscript to PDF, which I suspect is a packaging / cross-compilation > > > > error on our side since it works with the official Windows binaries > > > > from ghostscript.com and the older version of Ghostscript from GUB... > > > > > > > > Tracked in https://gitlab.com/lilypond/lilypond/-/issues/6282, I'll > > > > have to investigate how to solve this. > > > > > > Thanks a lot for your efforts on this issue. > > > > > > In my case, LilyPond 2.23.6/guile 2.2 does not produce the correct > > > filenames but correctly encoded contents. The only correct filename > > > produced by LilyPond is the MIDI file. However, LilyPond 2.23.6/guile > > > 1.8 produced all correct filenames. > > > > > > The following is the output in CMD terminal. You will find that > > > filenames of ps and svg are not correct. However the content are correct. > > > > Okay, interesting. So there actually may be multiple problems on > > Windows, again working fine on Linux... > > Not for me, being on Ubuntu 20.04 > > Compiling > \markup \override #'(font-name . "思源黑体 HW Bold") "中文" > returns: > ERROR: In procedure ly:text-interface::interpret-markup: > Invalid read access of chars of wide string: "思源黑体 HW Bold 3.8662109375" > > For both setups (see my recent mail on devel), i.e. self-compiled > 2.23.6 and the GitLab-archive Yes, that's a different problem (not related to filenames), reported in a different email thread. I also reproduced this on Linux yesterday, but didn't reply yet since I don't know what is at fault here (I presume some string conversion in our font handling). signature.asc Description: This is a digitally signed message part
Re: More about stencil
Good morning, thank you, thank you very much! The level of customization of lilypond seems incredible to me: I will have to deepen a lot, especially as regards the definition of new engravers. Nenuvar utilities are great! The only "problem" is that the side ornamentation, in case of altered notes, is placed between the accidental and the note. If I set the "is-inside" property to ## f, the ornamentation is printed before the accident, but there is a collision problem with previous notes. I'll have to figure out how to do it a bit. Thanks again! Rip_mus Il giorno dom 13 feb 2022 alle ore 23:17 Valentin Petzel ha scritto: > Hello Rip, > > also for a more recent version that is compatible with 2.22 check out the > nenuvar-side-ornementations.ily from > https://github.com/nsceaux/nenuvar-lib > > This is not compatible with the latest versions of Lilypond for now. The > amazing Jean quite recently fixed the magnetic-snap thingy, which had the > same problem. To apply his fix to your situation replace the definition of > define-grob-definition in line 7 by > > #(define (define-grob-definition grob-name grob-entry) > >(set! all-grob-descriptions > > (cons ((@@ (lily) completize-grob-entry) > > (cons grob-name grob-entry)) > >all-grob-descriptions))) > > Cheers, > > Valentin > > Am Sonntag, 13. Februar 2022, 22:51:25 CET schrieb Valentin Petzel: > > > Hello Rip, > > > > > > the problem is that you are modifying the stencil of the NoteHead, thus > > > changing its dimensions. > > > > > > Take a look at this old Lilypond Blog post: > > > > https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/2013 > > > /08/ adding-ornamentations-to-note-heads-part-1/[1] > > > > > > In there a new Event and Grob for Head ornamentation is added, which > would > > > probably be better suited for your demands. > > > > > > Cheers, > > > Valentin > > > > > > Am Sonntag, 13. Februar 2022, 20:43:07 CET schrieb Rip _Mus: > > > > Hello everyone, > > > > thanks to your many suggestions, I was able to get a little into the > > > > perspective of modifying the stencils. > > > > I created a stencil modification that adds a small arrow (sort of a > > > > glissando) to the left of the note or accident. > > > > However, I cannot understand why the ascending arrows let the stem no > > > > longer attached to the notehead. Do you have any ideas? > > > > > > > > Rip_mus > > > > > > > > > [1] > > > > https://web.archive.org/web/20200221133054/https://www.lilypondblog.org/201 > > > 3/08/ adding-ornamentations-to-note-heads-part-1/ > > >
