Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info

I can confirm that replacing scm_write_line (ly_string2scm (str), port); with scm_c_write (port, str.c_str (), str.length ()); fixes the issue on my end. I’d be happy to make a merge request for this. > On Jan 13, 2024, at 6:19 PM, Jean Abou Samra wrote: > >> I don't have the time to check t

Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info

> Can you make your example code generic and report it to the Guile people? Done. > How shall we proceed? Because this issue occurs with a macOS system font, it it likely to impact most (possibly all) LilyPond users on macOS. Consequently, it may be necessary to revert commit c3f2dddaa2b1623

Re: Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info

Thanks for making the merge request. Unfortunately, it didn’t fix the issue, although it really seems like it should have. I’m starting to think this may be a bug in Guile. With the patch applied, running `lilypond -dshow-available-fonts` outputs: GNU LilyPond 2.25.12 (running Guile 3.0) ERROR:

Using -dshow-available-fonts with LilyPond v2.25.12 throws error with non–UTF-8 encoded font info

Hi there, At commit c3f2dddaa2b16231bc2f786fba7421f03f7da7af , All_font_metrics::display_fonts was changed

PDF bookmark issues

Thanks for all your work on LilyPond! PDF bookmark support was added in LilyPond 2.22, but there seems to be a number of issues. • If several bookmarks occur on the same page, the order of the bookmarks is reversed. • Bookmarks always seems to be placed at the top of the page on which they oc

In TabStaff, \grace with \override misbehaves when it’s the first note

Hi there, Thanks for all your work on LilyPond! In a TabStaff, if a grace note is the first note and the \grace contains overrides, the overrides seem to be applied to whatever follows the grace note (instead of the grace note itself). Here’s an example that illustrates the behavior: ``` \ver

Tuplet numbers collide with articulations when notes are slurred

Hi there, Thanks for all your work on LilyPond! When notes in a tuplet are slurred, tuplet numbers can collide with articulations that appear above notes. When notes in a tuplet aren’t slurred, tuplet numbers appear above articulations. Here’s an example that illustrates the behavior: ``` \ve

Re: 64 bit MacOS version + Apple Silicon version

Hi, For Homebrew users, I have a Homebrew tap for building and installing LilyPond from source (apologies for self-promotion): https://github.com/nwhetsell/homebrew-lilypond This is tested on macOS 10.15 Catalina and 11 Big Sur (Intel-only). Best wishes, Nate __

Setting Slur.positions to 0s can still move slurs

Hi there, Thank you for all your work on LilyPond! Setting Slur.positions to #'(0 . 0) appears to still move slurs. Here’s an example that illustrates the behavior: ``` \version "2.22.0" { \override Beam.auto-knee-gap = #8 % This makes the example clearer but isn't needed c8( c'') c( c'')

Assertion failure when using Melody_engraver and CueVoice

Hi there, Thank you for all your work on LilyPond! It appears to be impossible to use a Melody_engraver in a Voice that also includes a CueVoice. Here’s a LilyPond example that illustrates the issue: ``` \version "2.22.0" \new Voice \with { \consists "Melody_engraver" \override Stem.neutral

Incorrect example in documentation

Hi there, Thank you for all your work on LilyPond! The syntax for \revert-ing certain properties appears to have changed after LilyPond 2.18, which makes the “Altering the length of beamed stems” example in the documentation slightly incorrect. At http://lilypond.org/doc/v2.18/Documentation/sn

Multi-measure rests not compressed when \partial is used in middle of score

Hi there, First, thank you for all your work on LilyPond. Within \compressMMRests, if a multi-measure rest is preceded by a \partial that’s not at the beginning of the score, it appears that the multi-measure rest isn’t compressed. Here’s a LilyPond example that illustrates the issue: ``` \ver