Re: GSoC 2026 / contributing

Hi again,

I am still trying to wrap my head around the lilypond program
structure. As such, sorry in advance for some possibly stupid
questions.

1. When going through the source files, I find that the MIDI uses a
kind of extended Translator_group interface called Performer_group.
What are the main differences between the two, and which one would be
more suitable for generalizing?
2. Would a new output format defined the way you suggest require
writing new performers/translators that are tailored for xml/mnx - or
could the old ones be reused somehow? Could the new
performers/translators be done in scheme in line with the format
definition?
3. How would a scheme definition of a format look like? In general, how
would this kind of definition differ from the c++ midi stream and
walker?

Hjalmar

mån 2025-12-01 klockan 11:45 -0500 skrev Saul Tobin:
> If I might make a suggestion, IMHO it would be a good idea to
> approach this by generalizing the Translator_group interface to allow
> for new output formats written in Scheme. This sort of project would
> be best approached by paralleling the way Lilypond itself does MIDI
> output. Trying to do it in Python will require effectively copying
> the whole parsing and translation process into a separate program,
> which seems like a lot of extra work and maintenance burden.
> 
> On Mon, Dec 1, 2025, 7:24 AM Werner LEMBERG <[email protected]> wrote:
> > 
> > > I did not find any public email address for Peter Bjuhr, would
> > any of
> > > you know how to reach him?
> > 
> > In the Frescobaldi git repository his commits are tagged with
> > <[email protected]> (his last commit is almost three years old).
> > 
> > > I tried reaching out on the active frescobaldi list, but I did
> > not get
> > > an answer there either.
> > > 
> > > https://groups.google.com/g/frescobaldi
> > 
> > Federico Bruni is also reading this list, so maybe he knows more.
> > 
> > 
> >     Werner
> >