Re: weird error engraving two files with 2.23.14
Le 01/11/2022 à 23:16, Han-Wen Nienhuys a écrit : Some PDF metadata features are missing, IIRC. Off the top: -dembed-source-code, and PDF outlines. There are also some obscure font features like -dgs-load-lily-fonts.
Re: weird error engraving two files with 2.23.14
On Thu, Oct 13, 2022 at 1:28 PM Kevin Barry wrote: > > It works great using the cairo backend! > > I wanted to test it so I think I'll set it as default for all my scores. > > What are the current drawbacks? There's any page in the docs about cairo? > > It looks like there was some kind of mixup adding info about cairo to > the changes doc. I can see the doc code in this diff: > https://gitlab.com/lilypond/lilypond/-/merge_requests/1651/diffs?commit_id=1df07dd726ff8bf16e60501080fcbd47b82ae6d4 > but it looks like that merge request somehow didn't end up including > that. I'll see about preparing a patch for it. > > To summarise what's there: it should be an improvement over ghostscript, > but it's still experimental and doesn't implement all of the features of > the other backends (I can't remember what, if anything, is missing). Some PDF metadata features are missing, IIRC. Also, raw PostScript only works if you export to PS, but not for PDF/PNG/SVG. -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
Re: weird error engraving two files with 2.23.14
Il giorno lun 17 ott 2022 alle 20:45:01 +, Werner LEMBERG
ha scritto:
\column \override #'(font-name . "Arial Bold") {
D A F♯ D A D
}
Using `font-name` is 'absolute', that is, it overrides any LilyPond
font switching mechanism. This means that `\number` doesn't work.
There are two solutions: Either set up a font tree so that you can use
standard commands like `\bold` (and `\number`), or switch manually to
the `Emmentaler` font. An example for the latter is
```
\column \override #'(font-name . "Arial Bold")
{
D A \concat { F
\override #'(font-name . "Emmentaler-16") \small
♯ } D A D
}
```
This is beautiful, thank you!
Re: weird error engraving two files with 2.23.14
> \column \override #'(font-name . "Arial Bold") {
>D A F♯ D A D
> }
Using `font-name` is 'absolute', that is, it overrides any LilyPond
font switching mechanism. This means that `\number` doesn't work.
There are two solutions: Either set up a font tree so that you can use
standard commands like `\bold` (and `\number`), or switch manually to
the `Emmentaler` font. An example for the latter is
```
\column \override #'(font-name . "Arial Bold")
{
D A \concat { F
\override #'(font-name . "Emmentaler-16") \small
♯ } D A D
}
```
Werner
Re: weird error engraving two files with 2.23.14
Le 17/10/2022 à 22:13, Federico Bruni a écrit :
Sorry, I should have not put that link, as it only works in 2.22 and
no longer in 2.23.
Here's a minimal example:
\version "2.23.14"
tuningOpenD = \markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D A F♯ D A D
}
}
\new TabStaff {
\set TabStaff.stringTunings = #guitar-open-d-tuning
\set TabStaff.instrumentName = \markup { " " \tuningOpenD }
\set TabStaff.shortInstrumentName = \markup \tuningOpenD
d,8 a, d fis a d'
}
Well, the ♯ is inside \override #'(font-name . "Arial Bold"), which
is basically a sledgehammer to override all font selection logic.
Try
\version "2.23.14"
tuningOpenD = \markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D A \concat { F \override #'(font-name . #f) \fontsize #-3 \number ♯
} D A D
}
}
\new TabStaff {
\set TabStaff.stringTunings = #guitar-open-d-tuning
\set TabStaff.instrumentName = \markup { " " \tuningOpenD }
\set TabStaff.shortInstrumentName = \markup \tuningOpenD
d,8 a, d fis a d'
}
Re: weird error engraving two files with 2.23.14
On 2022-10-17 1:13 pm, Federico Bruni wrote:
Sorry, I should have not put that link, as it only works in 2.22 and no
longer in 2.23.
Here's a minimal example:
\version "2.23.14"
tuningOpenD = \markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D A F♯ D A D
}
}
\new TabStaff {
\set TabStaff.stringTunings = #guitar-open-d-tuning
\set TabStaff.instrumentName = \markup { " " \tuningOpenD }
\set TabStaff.shortInstrumentName = \markup \tuningOpenD
d,8 a, d fis a d'
}
For the line break issue, you need to join the F and # together,
otherwise each markup expression is treated as its own line within
\column.
So, something like " \concat { F \number ♯ } ".
-- Aaron Hill
Re: weird error engraving two files with 2.23.14
Il giorno dom 16 ott 2022 alle 21:07:22 +0200, Jean Abou Samra
ha scritto:
Le 16/10/2022 à 20:54, Federico Bruni a écrit :
Il giorno dom 16 ott 2022 alle 12:19:46 +0200, Jean Abou Samra
ha scritto:
Le 14/10/2022 à 22:19, Federico Bruni a écrit :
I also had to replace # with ♯ (utf8) to specify sharp notes in
a tuning, otherwise I got a Guile error.
LilyPond likely interpreted # as introducing Scheme code.
Was this something that used to work in 2.22? If so, what
is the code?
Yes, it worked for sure in 2.22 (using Guile 1.8).
You can adapt this snippet (add # to one note):
https://lsr.di.unimi.it/LSR/Item?id=658
utf8 character is even prettier.
You can also use
\number ♯
in order to take the glyph from Feta instead of some
text font.
I tried it but it looks the same glyph to me, see attached files.
For both of the above, can you provide MWEs please? Sorry for being
annoying, but I am tired and it is much easier to understand problems
if you don't have to guess what exactly is meant by descriptions of
source code in English.
Sorry, I should have not put that link, as it only works in 2.22 and no
longer in 2.23.
Here's a minimal example:
\version "2.23.14"
tuningOpenD = \markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D A F♯ D A D
}
}
\new TabStaff {
\set TabStaff.stringTunings = #guitar-open-d-tuning
\set TabStaff.instrumentName = \markup { " " \tuningOpenD }
\set TabStaff.shortInstrumentName = \markup \tuningOpenD
d,8 a, d fis a d'
}
Re: weird error engraving two files with 2.23.14
Le 16/10/2022 à 20:54, Federico Bruni a écrit : Il giorno dom 16 ott 2022 alle 12:19:46 +0200, Jean Abou Samra ha scritto: Le 14/10/2022 à 22:19, Federico Bruni a écrit : I also had to replace # with ♯ (utf8) to specify sharp notes in a tuning, otherwise I got a Guile error. LilyPond likely interpreted # as introducing Scheme code. Was this something that used to work in 2.22? If so, what is the code? Yes, it worked for sure in 2.22 (using Guile 1.8). You can adapt this snippet (add # to one note): https://lsr.di.unimi.it/LSR/Item?id=658 utf8 character is even prettier. You can also use \number ♯ in order to take the glyph from Feta instead of some text font. I tried it but it looks the same glyph to me, see attached files. For both of the above, can you provide MWEs please? Sorry for being annoying, but I am tired and it is much easier to understand problems if you don't have to guess what exactly is meant by descriptions of source code in English. Thanks, Jean
Re: weird error engraving two files with 2.23.14
Le 14/10/2022 à 22:19, Federico Bruni a écrit : I also had to replace # with ♯ (utf8) to specify sharp notes in a tuning, otherwise I got a Guile error. LilyPond likely interpreted # as introducing Scheme code. Was this something that used to work in 2.22? If so, what is the code? utf8 character is even prettier. You can also use \number ♯ in order to take the glyph from Feta instead of some text font. There is also \markup \musicglyph "accidentals.sharp" which works in 2.22, but it uses a different glyph. The one \number gives you is specifically meant for text and was added by Werner in 2.23.
Re: weird error engraving two files with 2.23.14
Il giorno ven 14 ott 2022 alle 12:38:55 +0200, Thomas Morley
ha scritto:
Thanks for the files.
The culprit seems to be:
tuningOpenBb =
\markup {
\with-dimensions #'(0 . 0.8) #'(0 . 1.0)
\postscript "/Arial-Bold findfont
1.3 scalefont
setfont -0.5 3.6 moveto
(D) show -0.5 2.0 moveto
(C) show -0.5 0.6 moveto
(F) show -0.5 -0.8 moveto
(D) show -0.5 -2.2 moveto
(Bb) show -0.5 -3.6 moveto
(F) show
stroke"
}
It is no longer possible to specify fonts like above.
https://lists.gnu.org/archive/html/lilypond-devel/2022-04/msg00018.html
I suggest to do instead:
tuningOpenBb =
\markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D C F D Bb F
}
}
Many thanks Harm!
Now I can compile all my scores even with Ghostscript.
I also had to replace # with ♯ (utf8) to specify sharp notes in a
tuning, otherwise I got a Guile error. utf8 character is even prettier.
Re: weird error engraving two files with 2.23.14
Am Do., 13. Okt. 2022 um 14:08 Uhr schrieb Thomas Morley
:
>
> Am Do., 13. Okt. 2022 um 01:09 Uhr schrieb Federico Bruni
> :
> > These two files are copyrighted and I can't share them here, but I will
> > send privately to anyone interested in debugging this issue.
>
> Hi Federico,
>
> I'd offer to have a look.
>
> Cheers,
> Harm
Thanks for the files.
The culprit seems to be:
tuningOpenBb =
\markup {
\with-dimensions #'(0 . 0.8) #'(0 . 1.0)
\postscript "/Arial-Bold findfont
1.3 scalefont
setfont -0.5 3.6 moveto
(D) show -0.5 2.0 moveto
(C) show -0.5 0.6 moveto
(F) show -0.5 -0.8 moveto
(D) show -0.5 -2.2 moveto
(Bb) show -0.5 -3.6 moveto
(F) show
stroke"
}
It is no longer possible to specify fonts like above.
https://lists.gnu.org/archive/html/lilypond-devel/2022-04/msg00018.html
I suggest to do instead:
tuningOpenBb =
\markup {
\fontsize #-4
\override #'(baseline-skip . 1.5)
\column \override #'(font-name . "Arial Bold") {
D C F D Bb F
}
}
HTH,
Harm
Re: weird error engraving two files with 2.23.14
Am Do., 13. Okt. 2022 um 01:09 Uhr schrieb Federico Bruni : > > Hi folks > > I've recently used convert-ly to update my private music sheet library > and test version 2.23.14 (official binaries). > Two files are failing with the same error message: > > Drawing systems... > Converting to `foo.pdf'... > warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH > -dAutoRotatePages=/None -dPrinted=false /tmp/lilypond-tmp-9384021)' > failed (256) > > /var/home/fede/.local/lilypond/lilypond-2.23.14/share/lilypond/2.23.14/ly/init.ly:65:2: > error: Guile signaled an error for the expression beginning here > # > (let ((book-handler (if (defined? 'default-toplevel-book-handler) > Throw to key `ly-file-failed' with args `()'. > > > Any idea about the cause? I'm using a different font for tablature > numbers, but commenting that line still triggers this error. > These two files are copyrighted and I can't share them here, but I will > send privately to anyone interested in debugging this issue. Hi Federico, I'd offer to have a look. Cheers, Harm > > Thanks > Federico > > PS > Here's the --verbose log: > > GPL Ghostscript 9.56.1 (2022-04-04) > Copyright (C) 2022 Artifex Software, Inc. All rights reserved. > This software is supplied under the GNU AGPLv3 and comes with NO > WARRANTY: > see the file COPYING for details. > Querying operating system for font files... > Can't find (or can't open) font file %rom%Resource/Font/%rom%Resou. > Can't find (or can't open) font file Arial-Bold. > Didn't find this font on the system! > Substituting font Helvetica-Bold for Arial-Bold. > Can't find (or can't open) font file %rom%Resource/Font/%rom%Resource/F. > Can't find (or can't open) font file NimbusSans-Bold. > Can't find (or can't open) font file %rom%Resource/Font/%rom%Resource/F. > Can't find (or can't open) font file NimbusSans-Bold. > Didn't find this font on the system! > Unable to substitute for font. > Error: /invalidfont in findfont > Operand stack: >Arial-Bold > Execution stack: >%interp_exit .runexec2 --nostringval-- .findfontop --nostringval-- 2 > %stopped_push --nostringval-- .findfontop .findfontop false 1 > %stopped_push 1974 1 3 %oparray_pop 1973 1 3 %oparray_pop 1961 1 3 > %oparray_pop 1817 1 3 %oparray_pop --nostringval-- %errorexec_pop > .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push > --nostringval-- 1974 1 3 %oparray_pop 1973 1 3 %oparray_pop 1961 1 3 > %oparray_pop 1817 1 3 %oparray_pop --nostringval-- %errorexec_pop > .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push > --nostringval-- 1909 1 3 %oparray_pop > Dictionary stack: >--dict:761/1123(ro)(G)-- --dict:0/20(G)-- --dict:115/200(L)-- > Current allocation mode is local > Last OS error: Permission denied > Current file position is 915685 > GPL Ghostscript 9.56.1: Unrecoverable error, exit code 1 > warning: `(gs -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH > -dAutoRotatePages=/None -dPrinted=false /tmp/lilypond-tmp-2513976)' > failed (256) > > /var/home/fede/.local/lilypond/lilypond-2.23.14/share/lilypond/2.23.14/ly/init.ly:65:2: > error: Guile signaled an error for the expression beginning here > # > (let ((book-handler (if (defined? 'default-toplevel-book-handler) > 14 # > In > /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/lily.scm: >876:16 13 (lilypond-main _) > 905:4 12 (lilypond-all _) > In srfi/srfi-1.scm: > 640:9 11 (for-each # ?) > In > /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/lily.scm: > 915:9 10 (_ _) > In ice-9/boot-9.scm: > 829:9 9 (catch _ _ # ?) > In unknown file: >8 (ly:parse-file "Close-to-Heaven.ly") >7 (apply-smob/1 #) >6 (ly:book-process # #< Output_def> #< Output_def> #) > In > /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/backend-library.scm: > 319:4 5 (postprocess-output #< Output_def> # ?) > In srfi/srfi-1.scm: > 640:9 4 (for-each # ?) > In > /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/backend-library.scm: > 139:4 3 (postscript->pdf _ _ _ _ #f) > 57:4 2 (ly:gs-cli _ _) > In ice-9/boot-9.scm: >751:25 1 (dispatch-exception 0 ly-file-failed ()) > In unknown file: >0 (apply-smob/1 # #) > Throw to key `ly-file-failed' with args `()'. > > > >
Re: weird error engraving two files with 2.23.14
> I tried 2.23.12 and I got the same error. Do you remember what version it last worked with? > It works great using the cairo backend! > I wanted to test it so I think I'll set it as default for all my scores. > What are the current drawbacks? There's any page in the docs about cairo? It looks like there was some kind of mixup adding info about cairo to the changes doc. I can see the doc code in this diff: https://gitlab.com/lilypond/lilypond/-/merge_requests/1651/diffs?commit_id=1df07dd726ff8bf16e60501080fcbd47b82ae6d4 but it looks like that merge request somehow didn't end up including that. I'll see about preparing a patch for it. To summarise what's there: it should be an improvement over ghostscript, but it's still experimental and doesn't implement all of the features of the other backends (I can't remember what, if anything, is missing). Kevin
Re: weird error engraving two files with 2.23.14
Il giorno gio 13 ott 2022 alle 10:06:47 +, Kevin Barry
ha scritto:
Hi Federico,
On Thu, Oct 13, 2022 at 01:06:17AM +0200, Federico Bruni wrote:
Hi folks
I've recently used convert-ly to update my private music sheet
library and
test version 2.23.14 (official binaries).
Two files are failing with the same error message:
Did this work with 2.23.13? Or what was the last version it worked on?
I tried 2.23.12 and I got the same error.
Any idea about the cause? I'm using a different font for tablature
numbers,
but commenting that line still triggers this error.
These two files are copyrighted and I can't share them here, but I
will send
privately to anyone interested in debugging this issue.
On the surface it looks like a problem with ghostscript, but it's not
clear. If you remove all font changes does the error still occur? Can
you send on the verbose log for that?
Also, if you are willing to try it, see if adding the option
-dbackend=cairo (which should avoid calling ghostscript) also fails
(you
may need libcairo or some such installed on your system for this).
It works great using the cairo backend!
I wanted to test it so I think I'll set it as default for all my
scores. What are the current drawbacks? There's any page in the docs
about cairo?
$ git grep -ni cairo Documentation/en/
Documentation/en/web/introduction.itexi:1435:a score editor based on
the @uref{https://www.cairographics.org,Cairo}
Re: weird error engraving two files with 2.23.14
Hi Federico, On Thu, Oct 13, 2022 at 01:06:17AM +0200, Federico Bruni wrote: > Hi folks > > I've recently used convert-ly to update my private music sheet library and > test version 2.23.14 (official binaries). > Two files are failing with the same error message: Did this work with 2.23.13? Or what was the last version it worked on? > Any idea about the cause? I'm using a different font for tablature numbers, > but commenting that line still triggers this error. > These two files are copyrighted and I can't share them here, but I will send > privately to anyone interested in debugging this issue. On the surface it looks like a problem with ghostscript, but it's not clear. If you remove all font changes does the error still occur? Can you send on the verbose log for that? Also, if you are willing to try it, see if adding the option -dbackend=cairo (which should avoid calling ghostscript) also fails (you may need libcairo or some such installed on your system for this). Kevin
weird error engraving two files with 2.23.14
Hi folks I've recently used convert-ly to update my private music sheet library and test version 2.23.14 (official binaries). Two files are failing with the same error message: Drawing systems... Converting to `foo.pdf'... warning: `(gs -q -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false /tmp/lilypond-tmp-9384021)' failed (256) /var/home/fede/.local/lilypond/lilypond-2.23.14/share/lilypond/2.23.14/ly/init.ly:65:2: error: Guile signaled an error for the expression beginning here # (let ((book-handler (if (defined? 'default-toplevel-book-handler) Throw to key `ly-file-failed' with args `()'. Any idea about the cause? I'm using a different font for tablature numbers, but commenting that line still triggers this error. These two files are copyrighted and I can't share them here, but I will send privately to anyone interested in debugging this issue. Thanks Federico PS Here's the --verbose log: GPL Ghostscript 9.56.1 (2022-04-04) Copyright (C) 2022 Artifex Software, Inc. All rights reserved. This software is supplied under the GNU AGPLv3 and comes with NO WARRANTY: see the file COPYING for details. Querying operating system for font files... Can't find (or can't open) font file %rom%Resource/Font/%rom%Resou. Can't find (or can't open) font file Arial-Bold. Didn't find this font on the system! Substituting font Helvetica-Bold for Arial-Bold. Can't find (or can't open) font file %rom%Resource/Font/%rom%Resource/F. Can't find (or can't open) font file NimbusSans-Bold. Can't find (or can't open) font file %rom%Resource/Font/%rom%Resource/F. Can't find (or can't open) font file NimbusSans-Bold. Didn't find this font on the system! Unable to substitute for font. Error: /invalidfont in findfont Operand stack: Arial-Bold Execution stack: %interp_exit .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- .findfontop .findfontop false 1 %stopped_push 1974 1 3 %oparray_pop 1973 1 3 %oparray_pop 1961 1 3 %oparray_pop 1817 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- 1974 1 3 %oparray_pop 1973 1 3 %oparray_pop 1961 1 3 %oparray_pop 1817 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- .findfontop --nostringval-- 2 %stopped_push --nostringval-- 1909 1 3 %oparray_pop Dictionary stack: --dict:761/1123(ro)(G)-- --dict:0/20(G)-- --dict:115/200(L)-- Current allocation mode is local Last OS error: Permission denied Current file position is 915685 GPL Ghostscript 9.56.1: Unrecoverable error, exit code 1 warning: `(gs -dNODISPLAY -dNOSAFER -dNOPAUSE -dBATCH -dAutoRotatePages=/None -dPrinted=false /tmp/lilypond-tmp-2513976)' failed (256) /var/home/fede/.local/lilypond/lilypond-2.23.14/share/lilypond/2.23.14/ly/init.ly:65:2: error: Guile signaled an error for the expression beginning here # (let ((book-handler (if (defined? 'default-toplevel-book-handler) 14 # In /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/lily.scm: 876:16 13 (lilypond-main _) 905:4 12 (lilypond-all _) In srfi/srfi-1.scm: 640:9 11 (for-each # ?) In /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/lily.scm: 915:9 10 (_ _) In ice-9/boot-9.scm: 829:9 9 (catch _ _ # ?) In unknown file: 8 (ly:parse-file "Close-to-Heaven.ly") 7 (apply-smob/1 #) 6 (ly:book-process # #< Output_def> #< Output_def> #) In /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/backend-library.scm: 319:4 5 (postprocess-output #< Output_def> # ?) In srfi/srfi-1.scm: 640:9 4 (for-each # ?) In /home/lily/lilypond-2.23.14/release/binaries/lilypond/build/out/share/lilypond/current/scm/lily/backend-library.scm: 139:4 3 (postscript->pdf _ _ _ _ #f) 57:4 2 (ly:gs-cli _ _) In ice-9/boot-9.scm: 751:25 1 (dispatch-exception 0 ly-file-failed ()) In unknown file: 0 (apply-smob/1 # #) Throw to key `ly-file-failed' with args `()'.
