> Then, the two font files, one from 2.23.7 and the good one from
> 2.23.10, are conflicting under the name "Emmentaler 11" for being
> embedded in the PS file. [...]
Could you try to apply the effects of
https://gitlab.com/lilypond/lilypond/-/merge_requests/1758
to the two problematic inst
>> What about adding
>>
>> ```
>> .../lilypond/XX.YY.ZZ/fonts/otf
>> ```
>>
>> at the top of `00-lilypond-fonts.conf`? According to the
>> maintainer of FontConfig, first directory gets served first, and
>> the `00-*` file is read before anything else.
>
> I already tried this and it didn't work
Here is the current countdown report.
The next countdown will begin on December 14th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
No patches in Push at this time.
Countdown:
!1578 New margins by d
Le 12/12/2022 à 23:33, Lukas-Fabian Moser a écrit :
Yes, I kept a backup. I attach the .ly file and the ps file generated
by 2.23.10.
Thanks. I think this finishes to explain what is happening.
In the big blob of data that embeds the emmentaler-11 font in the PS
file, there is the string "2.
Le 12/12/2022 à 23:22, Lukas-Fabian Moser a écrit :
This solves the problem.
OK, we're getting closer to the root of the problem.
There is one more thing I'd like to know before I go to bed: can you
restore a failing setup (I hope you kept a backup of the fonts in
~/.local? ...) and send th
Am 12.12.22 um 23:17 schrieb Jean Abou Samra:
Ha:
[... ... ...]
(utf-8-string "emmentaler-11 3.9453125" "6" (translate-stencil (0.0 .
0.0) (glyph-string
# "Emmentaler-11" 3.9443359375 #f
((0.785296062992126 (0.0 . 1.1225612496924213)
0.0 0.0 "six")) "/home/lukas/.local/share/fonts/emmentaler
Le 12/12/2022 à 23:02, Werner LEMBERG a écrit :
Masamichi-san, can you advise a solution? Would it be possible and
would make it sense to add a directory specifier to
`00-lilypond-fonts.conf`?
I didn't find a way to do it in the configuration file directly,
[...]
What about adding
```
.../l
Ha:
[... ... ...]
(utf-8-string "emmentaler-11 3.9453125" "6" (translate-stencil (0.0 .
0.0) (glyph-string
# "Emmentaler-11" 3.9443359375 #f
((0.785296062992126 (0.0 . 1.1225612496924213)
0.0 0.0 "six")) "/home/lukas/.local/share/fonts/emmentaler-11.otf"
<<<== Whoops again ...
[... ... ..
Again, thanks for "holding my hands" while searching for the cause; I
try to follow your suggestions precisely, but am not able to "start
thinking for myself" at the moment:
Am 12.12.22 um 22:57 schrieb Jean Abou Samra:
Yet another question.
Can you try this:
\markup \override #'(font-featu
>> Masamichi-san, can you advise a solution? Would it be possible and
>> would make it sense to add a directory specifier to
>> `00-lilypond-fonts.conf`?
>
> I didn't find a way to do it in the configuration file directly,
> [...]
What about adding
```
.../lilypond/XX.YY.ZZ/fonts/otf
```
at
Am 12.12.22 um 22:46 schrieb Jean Abou Samra:
Ah, another question, Lukas: what does the "locale" command give you?
Call me paranoid, but the accidental characters are obviously
non-ASCII, so the Unicode handling might go wrong somewhere.
lukas@Aquarium:~$ locale
LANG=de_DE.UTF-8
LANGUAGE=de_
Hi,
OK. What do you get with
\version "2.23.82"
\new FiguredBass \figuremode {
\override BassFigure.stencil =
#(grob-transformer
'stencil
(lambda (grob orig)
(pretty-print (ly:stencil-expr orig) (current-error-port))
orig))
<6> <_+> <_-> <_!>
}
?
Thanks f
Le 12/12/2022 à 22:43, Jean Abou Samra a écrit :
Le 12/12/2022 à 22:33, Lukas-Fabian Moser a écrit :
For me,
\version "2.23.82"
\markup
$(markup-lambda (layout props x) (markup?)
(let ((stil (interpret-markup layout props x)))
(pretty-print (ly:stencil-expr stil) (current-error-port))
> The question is, do we consider this a problem important enough to
> not release 2.24.0?
IMHO, this is not important enough to delay 2.24.0.
Werner
Ah, another question, Lukas: what does the "locale" command give you?
Call me paranoid, but the accidental characters are obviously non-ASCII,
so the Unicode handling might go wrong somewhere.
OpenPGP_signature
Description: OpenPGP digital signature
Le 12/12/2022 à 22:33, Lukas-Fabian Moser a écrit :
Am 12.12.22 um 01:36 schrieb Jean Abou Samra:
Le 12/12/2022 à 01:20, Jean Abou Samra a écrit :
Werner will know about this better than me, but I am still curious.
What does this give you?
\version "2.23.82"
#(ly:message "~s" (ly:font-config
Le 12/12/2022 à 22:35, Lukas-Fabian Moser a écrit :
I would very strongly suspect 2.23.10 with
https://gitlab.com/lilypond/lilypond/-/merge_requests/1409
New data: The problem starts with 2.23.8, incidentally the same
release that contain's Werner's modifications to bass figure glyph
sizes.
I would very strongly suspect 2.23.10 with
https://gitlab.com/lilypond/lilypond/-/merge_requests/1409
New data: The problem starts with 2.23.8, incidentally the same
release that contain's Werner's modifications to bass figure glyph sizes.
I'm sorry, stupid mistake: Make that 2.23.10. (I'm j
Am 12.12.22 um 01:36 schrieb Jean Abou Samra:
Le 12/12/2022 à 01:20, Jean Abou Samra a écrit :
Werner will know about this better than me, but I am still curious.
What does this give you?
\version "2.23.82"
#(ly:message "~s" (ly:font-config-get-font-file "emmentaler-20"))
\markup "♯"
Sorry
Am 12.12.22 um 22:26 schrieb Jean Abou Samra:
Le 12/12/2022 à 22:11, Lukas-Fabian Moser a écrit :
I'm sorry not to have been more prompt in my replies, as I'm still
quite swamped.
To my knowledge, I have no globally installed lilypond. I don't
remember installing one, and there is no global
Le 12/12/2022 à 22:11, Lukas-Fabian Moser a écrit :
I'm sorry not to have been more prompt in my replies, as I'm still
quite swamped.
To my knowledge, I have no globally installed lilypond. I don't
remember installing one, and there is no globally available "lilypond"
command on my system.
On Mon, 2022-12-12 at 22:05 +0100, Jean Abou Samra wrote:
> Le 12/12/2022 à 21:23, Jonas Hahnfeld a écrit :
> > On Mon, 2022-12-12 at 01:36 +0100, Jean Abou Samra wrote:
> > > Note the path in /usr/share/fonts/lilypond, which is a folder
> > > provided by the lilypond package from my Fedora system
Hi all,
Anyway, this doesn't explain Lukas' original problem on Mint.
My conjecture was that Lukas has 2.22 installed globally like I have
2.23, and this would lead to characters not being found because the
2.22 Emmentaler doesn't have those new characters. Of course, we
need Lukas to tell more
Il giorno lun 12 dic 2022 alle 17:34:27 +0100, Jean Abou Samra
ha scritto:
Le 12/12/2022 à 12:24, Karlin High a écrit :
No, it is Linux. (Docker in Alpine in ProxMox.)
If a macOS machine is wanted, I have a MacBook Air which could help,
although its capacities are unremarkable.
OK. What
Le 12/12/2022 à 21:23, Jonas Hahnfeld a écrit :
On Mon, 2022-12-12 at 01:36 +0100, Jean Abou Samra wrote:
Note the path in /usr/share/fonts/lilypond, which is a folder
provided by the lilypond package from my Fedora system
This should be reported, it's not how Fedora is supposed to package
Lily
On Mon, 2022-12-12 at 01:36 +0100, Jean Abou Samra wrote:
> Note the path in /usr/share/fonts/lilypond, which is a folder
> provided by the lilypond package from my Fedora system
This should be reported, it's not how Fedora is supposed to package
LilyPond...
On Mon, 2022-12-12 at 17:54 +0100, Jea
Le 12/12/2022 à 12:16, Werner LEMBERG a écrit :
Masamichi-san, can you advise a solution? Would it be possible and
would make it sense to add a directory specifier to
`00-lilypond-fonts.conf`?
I didn't find a way to do it in the configuration file directly, but
using this:
https://docs.gt
>
> From: Karlin High
> Subject: Re: New CI runner
> Date: 12 December 2022 at 12:24:06 CET
> To: Jean Abou Samra
> Cc: lilypond-devel
>
>
> No, it is Linux. (Docker in Alpine in ProxMox.)
>
> If a macOS machine is wanted, I have a MacBook Air which could help,
> although its capacities are
On 12/12/2022 10:34 AM, Jean Abou Samra wrote:
What version of macOS does this MacBook Air have?
It is also in end-of-life, but is able to get to macOS Catalina 10.15.7
Details:
MacBook Air (11-inch, mid-2012)
Intel Core i5-3317U 1.7-2.6 GHz (2 cores, 4 threads)
4 GB RAM
I keep this thing ar
Le 12/12/2022 à 17:44, Werner LEMBERG a écrit :
I think
https://gitlab.com/lilypond/lilypond/-/merge_requests/1758
will help in the future.
Interesting, but for me, LilyPond 2.22 also reads from /usr/share.
OpenPGP_signature
Description: OpenPGP digital signature
>> "/usr/share/fonts/lilypond/emmentaler-20.otf" <<<== Whoops
>
> Yes, whoops!
>
>> I don't even understand how that can work. How is Fontconfig finding
>> the Emmentaler fonts in the LilyPond package?
I think
https://gitlab.com/lilypond/lilypond/-/merge_requests/1758
will help in the futu
Le 12/12/2022 à 12:24, Karlin High a écrit :
No, it is Linux. (Docker in Alpine in ProxMox.)
If a macOS machine is wanted, I have a MacBook Air which could help,
although its capacities are unremarkable.
OK. What version of macOS does this MacBook Air have? The main goal
would be to find a
No, it is Linux. (Docker in Alpine in ProxMox.)
If a macOS machine is wanted, I have a MacBook Air which could help,
although its capacities are unremarkable.
--
Karlin High
Missouri, USA
> OK, I have found something that looks bad on my system, although I
> can't reproduce Lukas' problem: for me, this:
>
> ```
> \version "2.23.82"
>
> \markup
> $(markup-lambda (layout props x) (markup?)
> (let ((stil (interpret-markup layout props x)))
> (pretty-print (ly:stencil-expr st
> \markup \override #'(font-name . "Nonexistent Bold") "ABC"
>
> With 2.22, this compiles without warning, and the resulting PDF
> contains the font "DejaVuSans-Bold" (according to pdffonts).
>
> With 2.23.82, it gives me
>
> GNU LilyPond 2.23.82 (running Guile 2.2)
> Processing `unfound-font.
Am I understanding it correctly that the new runner provided by Karlin is a
macOS machine? If so, what macOS version? (Context: planning a Frescobaldi
release.)
Thanks,
Jean
36 matches
Mail list logo
