Tracking Bug for "the lilypondFormat is not yet consulted" about music21 HOT 6 CLOSED

Is anybody working on this or #24 or #25? If not, would a fix be welcomed at this time, or are the relevant modules currently under heavy development at MIT? Thanks!

from music21.

This would be great if you could look into it. We’re revamping how sub formats (things like the “png” in “lilypond.png”) are parsed, but the system for supporting richer communication with .show and .write should be ready very soon and the latest Git commits improve that a lot.

Best,
Myke

On May 12, 2014, at 15:45, Christopher Antila <[email protected]mailto:[email protected]> wrote:

Is anybody working on this or #24#24 or #25#25? If not, would a fix be welcomed at this time, or are the relevant modules currently under heavy development at MIT? Thanks!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-42878755.

from music21.

Thanks, I'll get started!

from music21.

any progress on this? I'm trying to close issues that are not vital so that the (small) team can focus more on ones that have large community interest. Thanks!

from music21.

It looks like this was fixed at some point in May 2014 with the switch to SubConverter objects, but nobody noticed. All three subformats work for me (PDF, PNG, and SVG).

Issues #24 and #25, although they refer to obsolete code that no longer exists, do refer to a standing issue.

from music21.

thanks. SVG was a patch and had a separate bug.

from music21.