I realized Lilypond files were just TeX,
... makes mistakes ...
many people operate under the assumption that if it saved as as TeX/XML/CSV/relational data, therefore it must follow the concepts of Tex/XML/CSV/rel.data. A famous example of such an ill-conceived format is the use of XML in Ant - a custom language would have been a much better choice.
Because examples have to be exhaustive in order for the format to be "understood". Without direct knowledge, there is no way to know if any selection of "example" files are exhaustive.
Hope, because lasconic's .nwctxt -> MusicXML converter makes mistakes when multiple lyric lines use voices to change rhythms on a man additional verse. Without that bug fixed (and it doesn't look likely), my users will be unable to import the content they created in NWC unless I write an importer from scratch. And without proper documentation on what might appear in the file, interpreting my users files will be "best guess" instead of reliable.
I don't think my users will know how to extract a binary deflate stream and inflate it.
..., they may as well buy Finale (churches get a 42% discount!),... to enable that content to be usable in my app.
So here I am ..., trying hard to solve the biggest problem my users will ever face (content acquisition) with things I can do, like writing an importer for other popular file formats.
Page created in 0.040 seconds with 24 queries.