Hi again,

I wonder if this is what it takes to implement backend support for
musicxml, which hopefully would be more maintainable than an external
python script:

1. Allowing Translator_group::create_child_translator to detect and
adapt to a child Xmlperformer_group.

2. Adapting translator-group-ctors.cc to do the same

3. New Xmlperformer_group child of Translator_group

4. A new xmlperformer suite, loosely based on the musicxml supported
elements: 
https://www.w3.org/2021/06/musicxml40/musicxml-reference/elements/

5. New Score_xmlperformer, calling the suite and creating a performance
object.

6. XML-formatter, written in scheme, parsing this object into an
MusicXML file.

Kind regards, get well soon
Hjalmar

> One additional thought: Guile includes a powerful and convenient
> built-in library for working with XML as native Scheme s-expressions.
> So the actual XML conversion part of this should be relatively simple
> via Scheme.
  • GSoC 2026 / contri... Hjalmar Bjerner via Discussions on LilyPond development
    • Re: GSoC 2026... Werner LEMBERG
      • Re: GSoC ... Hjalmar Bjerner via Discussions on LilyPond development
        • Re: G... Werner LEMBERG
          • R... Hjalmar Bjerner via Discussions on LilyPond development
            • ... Werner LEMBERG
              • ... Saul Tobin
                • ... Hjalmar Bjerner via Discussions on LilyPond development
                • ... Saul Tobin
                • ... Saul Tobin
                • ... Hjalmar Bjerner via Discussions on LilyPond development
                • ... Saul Tobin
                • ... Hjalmar Bjerner via Discussions on LilyPond development

Reply via email to