Issue 938 in lilypond: building lilypond omf files: what, why, how, etc

[lilypond]

Status: Accepted
Owner: percival.music.ca
Labels: Type-Other Priority-Postponed Maintainability Frog

New issue 938 by percival.music.ca: building lilypond omf files: what, why,  
how, etc
http://code.google.com/p/lilypond/issues/detail?id=938

We build .omf files from the main manual .texi / .tely files.
- what are these, how are they used?
- are they being generated correctly?
- do we still want to bother with them?
- does it make sense to generate them from .texi files, or could they be
defined in another file?  For that matter, might it make sense just to
write the xml file directly in git?  why do have have a .pdf.omf and
.html.omf ?  are we generating them for all the manuals?

Don't start this before 2.14, but it would be nice somebody knew WTF was up
with these files before we start the new build system.


(and no, don't reply with "this means opendata meta format, you idiot who
couldn't do a 10-second google search"; I already did that, but it doesn't
answer the above questions)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings