Upcoming plan for 0.2 release
I have branched ScoreRender for 0.1.x maintenance releases, and started 0.2 release hacking. Right now not much has been done — mainly dropping support for configurable tag markup (I suspect people don’t change it, if anybody is using this plugin at all 
), and allows setting the upper limit of length per fragment.
Here are some of the things I want to achieve in 0.2 release:
- Allows configurable image width limit
- Lilypond chroot support (it really hurts when some Lilypond fragments don’t work because of security issue)
- Allows setting limit of no. of fragment in comment
- Supports more syntax, like MusiXTeX, Philip’s Music Writer and lilypond-book format
- Add button in option page to clear image cache
One thing not quite sure is whether I should implement the feature of covering up error with blank or blanket images. This helps on security side (leaking less info), but blog authors will find it harder to trace error. Still not decided how this can be achieved while satisfying both flexibility and security.