Re: ghostscript 9.56.1 in lilypond 2.23.14 no longer finds font Helvetica-Bold, but gs in 2.22.1 did

[Jean Abou Samra]

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
>         2.23.12
>         https://lists.gnu.org/archive/html/lilypond-user/2022-08/msg00364.html
>         but cairo isn't mentioned at all in the changes doc.



This is intentional. One reason is that no all users will be able to run 
with Cairo, because in 2.23.80, support for Cairo is optional when 
compiling LilyPond, and not all GNU/Linux distributions compile LilyPond 
with this option.

It will be mentioned in the changes for version 2.26, where compiling 
LilyPond with Cairo becomes mandatory.


>      o
>
>
>
>   * \bar ".|:-|"
>       o This is what convert-ly did to my 2.22 instances of \bar ".|:"
>         , which isn't even in the 2.23 NR.


All bar lines are now in the NR, here:

https://lilypond.org/doc/v2.23/Documentation/notation/list-of-bar-lines


>      o
>
>
>
>       o It's especially curious since the 2.23 changes doc uses the
>         2.22 form unchanged elsewhere:
>           + "The solution is to place \bar inside the music for each
>             staff, as is usual with most commands.
>             <<
>               \new Staff { \bar ".|:" c' }
>               \new Staff { \bar ".|:" c' }
>             >>


\bar ".|:" is still valid, just different. \bar ".|:-|" is equivalent
to what was formerly \bar ".|:". The difference between \bar ".|:" and
\bar ".|:-|" is only visible when the bar line is at the end of a system.
Therefore, it doesn't make a difference in this example.

Best,
Jean

OpenPGP_signature
Description: OpenPGP digital signature