Hello, and thanks for the reply, Sorry for the confusion, I am of course talking about GSoC 2026.
I looked up the MNX format. Compared with musicxml, it seems like its syntax is more similar to that of LilyPond. Features such as chord grouping and propertizing duration dots and beam properties seems to simplify conversion. This, along with with its use of json, seems to make MNX export smoother to use and easier to implement. One could write a more robust and flexible MNX export with python json handling, refactoring and building upon the xml-MNX-agnostic functionality from musicxml.py. Maybe this would even be easier than improving the xml export itself for next year's GSoC. Does this seem like a suitable project? I am unsure of how widely spread and implemented the MNX format has become yet. Still, with active development of MNX, MNX-implementations and MNX-converters (https://github.com/w3c/mnxconverter?tab=readme-ov-file), it looks like it's worth it looking into. Hjalmar lör 2025-11-15 klockan 10:50 +0000 skrev Werner LEMBERG: > Hello Hjalmar! > > > > I am wondering if the lilypond project plan on having projects for > > > this year's Google Summer of Code, especially regarding the project > > > for extending support for exporting to MusicXML, listed on your > > > website: https://lilypond.org/google-summer-of-code.html > > > You mean next year's GSoC, right? GSoC 2025 ends in two days... > > Since you have raised your hand, we might consider to apply for GSOC > 2026 – there wasn't any interest in the previous years. > > Making LilyPond emit MusicXML would be quite an important feature. > On > the other hand, the future is MNX (https://w3c.github.io/mnx/docs/), > the successor format for MusicXML that is under active development. > Ideally, LilyPond should support both output formats. > > > Werner
