For what it's worth, I have submitted a patch to clearly document why
\postscript should be a last resort.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1735
Best,
Jean
OpenPGP_signature
Description: OpenPGP digital signature
One more thing ...
Le 13/11/2022 à 01:35, Jeff Olson a écrit :
I've done #(ly:font-config-display-fonts) as directed in the 2.23 NR
(thanks for adding that), and it lists
family Times New Roman
Times New Roman:style=Bold,Negreta, ...
But the MWE above with all those variations still
Le 15/11/2022 à 05:29, Jeff Olson a écrit :
That's it exactly! What a relief to know a fix is coming.
For a start, version 2.23.81 is supposed to be better in
this respect, although the problem remains in very intensive
situations.
Best,
Jean
OpenPGP_signature
Description: OpenPGP digital
On 11/14/2022 1:53 PM, Jean Abou Samra wrote:
Meanwhile I've got to get back to making an MWE to explore why
2.23.14 (but not 2.22.1) is crashing with a segmentation fault when I
put too many scores in a bookpart (clearly another thread).
If it is something like "exited with return code -107374
Le 14/11/2022 à 21:33, Jeff Olson a écrit :
Yes! It is excellent and I highly recommend it. Especially after you
incorporated my 7/12/2022 off-list suggestions concerning named let
and various presentation formatting issues (self-promotion 😉)!
I am notoriously bad with remembering names
On 11/13/2022 1:24 PM, Jean Abou Samra wrote:
[Self-promotion:] Have you tried to read this?
https://scheme-tutorial.readthedocs.io
(It originates in a presentation that some people found clear, which
is the reason why I wrote it down.)
Yes! It is excellent and I highly recommend it. Espec
Le 12/11/2022 à 05:45, Jeff Olson a écrit :
Would be nice if lilypond had a way to load a resource into the
postscript file without having to produce this extra output, or sledge
hammer the bold/italic styles.
That's not my view. LilyPond is meant to be extensible in Scheme, not in
Posts
Hi,
I'll react to most of this off-list on the samples you sent to me, but:
Le 12/11/2022 à 06:43, Jeff Olson a écrit :
I did most of this 5+ years ago in 2.18.2 before I knew any scheme,
and my scheme attempts since then have not built my confidence.
[Self-promotion:] Have you tried to read
> On 13 Nov 2022, at 10:54, Jean Abou Samra wrote:
>
> Le 12/11/2022 à 05:27, Jeff Olson a écrit :
>> On 11/7/2022 6:58 AM, Hans Åberg wrote:
In 2.22 you successfully get "Hello, World!" at top of page.
>>> This example works in LilyPond 2.23.80 (MacPorts), on MacOS 13.0.
>>
>> Interestin
Le 13/11/2022 à 01:56, Jeff Olson a écrit :
Thanks, Jean.
While we're at it, there are two other changes that I don't see listed
in https://lilypond.org/doc/v2.23/Documentation/changes-big-page.html
* -dbackend=cairo
o Jonas invited users to try this out in the announcement for
Le 12/11/2022 à 05:27, Jeff Olson a écrit :
On 11/7/2022 6:58 AM, Hans Åberg wrote:
In 2.22 you successfully get "Hello, World!" at top of page.
This example works in LilyPond 2.23.80 (MacPorts), on MacOS 13.0.
Interesting. This must mean that Helvetica-Bold is available as a
system font on
On 11/10/2022 4:50 AM, Jean Abou Samra wrote:
For your information, I have submitted a merge request to mention this
change in LilyPond's Changes document
(https://gitlab.com/lilypond/lilypond/-/merge_requests/1719).
Also, the red herring in init.ly is now tracked in
https://gitlab.com/lilypo
On 11/12/2022 1:51 AM, Hans Åberg wrote:
On 12 Nov 2022, at 05:27, Jeff Olson wrote:
On 11/7/2022 6:58 AM, Hans Åberg wrote:
In 2.22 you successfully get "Hello, World!" at top of page.
This example works in LilyPond 2.23.80 (MacPorts), on MacOS 13.0.
Interesting. This must mean that Helve
> On 12 Nov 2022, at 05:27, Jeff Olson wrote:
>
> On 11/7/2022 6:58 AM, Hans Åberg wrote:
>>> In 2.22 you successfully get "Hello, World!" at top of page.
>>>
>> This example works in LilyPond 2.23.80 (MacPorts), on MacOS 13.0.
> Interesting. This must mean that Helvetica-Bold is available as
On 11/7/2022 11:58 PM, Jean Abou Samra wrote:
By the way, what are you using PostScript code for more precisely?
It is not possible for you to switch to regular markup? (If
it's lots of paths, for example, that could be partly automated.)
Jean,
I did most of this 5+ years ago in 2.18.2 before
On 11/7/2022 11:58 PM, Jean Abou Samra wrote:
Surprises (2)-(4) happen because font-name is meant to be a
sledgehammer that overrides all font selection logic. In
particular, it makes \bold and \italic have no effect.
You have to use font-style instead.
On 11/8/2022 12:07 AM, Jean Abou Samra wr
On 11/7/2022 6:58 AM, Hans Åberg wrote:
In 2.22 you successfully get "Hello, World!" at top of page.
This example works in LilyPond 2.23.80 (MacPorts), on MacOS 13.0.
Interesting. This must mean that Helvetica-Bold is available as a
system font on MacOS, so even our stripped down ghostscript
On 11/7/2022 6:46 AM, Timothy Lanfear wrote:
Could it be sufficient to install the full Ghostscript and set the
environment variable GS_FONTPATH to point to that Ghostscript
version's font directory? (e.g. export GS_FONTPATH=/usr/share/fonts).
The LilyPond Ghostscript will then search that di
Hi,
For your information, I have submitted a merge request to mention this
change in LilyPond's Changes document
(https://gitlab.com/lilypond/lilypond/-/merge_requests/1719).
Also, the red herring in init.ly is now tracked in
https://gitlab.com/lilypond/lilypond/-/issues/6459
Best,
Jean
Le 08/11/2022 à 06:59, Jeff Olson a écrit :
Excellent! Thank you three times for your examples and patient
explanations!
So part of the trick is discovering which lilypond font-name to
specify in order to embed the desired font in lilypond's postscript.
My target is /Helvetica-Bold in pos
On 11/7/2022 12:02 AM, Jean Abou Samra wrote:
\version "2.23.80"
\markup {
\postscript "
/NimbusSans-Regular findfont
4 scalefont setfont
(Hello, World!) show
"
}
\markup
\override #'(font-name . "Nimbus Sans")
\translate #'(100 . 0)
"abcxyz"
...
N.B. The way I found "Nimbus
> On 6 Nov 2022, at 06:12, Jeff Olson wrote:
>
> This MWE works in 2.22.1 but fails in 2.23.14 (running via Frescobaldi 3.1.1
> on up-to-date Windows 10):
> \version "2.22.1"
> \markup {
> \postscript #"
> /Helvetica-Bold findfont
> 4 scalefont setfont
> (Hello, World!) show
>
On 07/11/2022 07:02, Jean Abou Samra wrote:
Le 07/11/2022 à 05:39, Jeff Olson a écrit :
Jean, please help me understand what this implies. The above
lilypond-devel thread basically ends with Harm's statement that
It is no longer possible to specify fonts like above.
https://lists.gnu.or
Le 07/11/2022 à 05:39, Jeff Olson a écrit :
Jean, please help me understand what this implies. The above
lilypond-devel thread basically ends with Harm's statement that
It is no longer possible to specify fonts like above.
https://lists.gnu.org/archive/html/lilypond-devel/2022-04/msg
On 11/6/2022 1:05 AM, Jean Abou Samra wrote:
Can someone explain (a) why Helvetical is no longer in 2.23.14's gs
and (b) the syntax for specifying Nimbus Sans L properly in my MWE?
Thanks for wading through all this with me. I've been on a very big
lilypond project for 6 years now, and it i
> Le 6 nov. 2022 à 06:14, Jeff Olson a écrit :
>
>
> This MWE works in 2.22.1 but fails in 2.23.14 (running via Frescobaldi 3.1.1
> on up-to-date Windows 10):
>
> \version "2.22.1"
> \markup {
> \postscript #"
> /Helvetica-Bold findfont
> 4 scalefont setfont
> (Hello, World!)
This MWE works in 2.22.1 but fails in 2.23.14 (running via Frescobaldi
3.1.1 on up-to-date Windows 10):
\version "2.22.1"
\markup {
\postscript #"
/Helvetica-Bold findfont
4 scalefont setfont
(Hello, World!) show
"
}
In 2.22 you successfully get "H
27 matches
Mail list logo
