Re: Capturing out-of-music markup for music braille

2024-03-29 Thread Maurits Lamers via LilyPond user discussion
Thanks so much for thinking along. In the current setup that would still require users to change their Lilypond code. Your example did give me an idea though: if there would be something like $currentscore, the problem of getting access to the score header would be solved... cheers Maurits

Re: Capturing out-of-music markup for music braille

2024-03-28 Thread Timothy Lanfear
On 27/03/2024 22:03, Maurits Lamers wrote: Hi Timothy, Thanks so much for your answer! With $defaultheader I can indeed get the main/global header fields in the initialize stage of the engraver, which is already a very important step. I looked up where $defaultheader is defined, and tried

Re: Capturing out-of-music markup for music braille

2024-03-27 Thread Maurits Lamers via LilyPond user discussion
Hi Timothy, Thanks so much for your answer! With $defaultheader I can indeed get the main/global header fields in the initialize stage of the engraver, which is already a very important step. I looked up where $defaultheader is defined, and tried toplevel-scores and toplevel-bookparts as well

Re: Capturing out-of-music markup for music braille

2024-03-27 Thread Timothy Lanfear
On 26/03/2024 14:01, Maurits Lamers via LilyPond user discussion wrote: - is there a way to get a listener or callback of some kind to capture out-of-music markup? - is there a way to get access to the global headers and / or score headers (in case of score specific headers)? - is there

Capturing out-of-music markup for music braille

2024-03-26 Thread Maurits Lamers via LilyPond user discussion
Hey all, It has been a while I posted on this mailing-list. As some of you might remember, I have been working on a music braille output system for Lilypond for quite some time now. The update on that front is that I do have a system now that can reliably output (a subset of) music braille