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.
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
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
> \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
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 .
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
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 ♯
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.
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
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
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
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
> 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
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
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
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
16 matches
Mail list logo
