7890 / oscdoc

create HTML documentation for OSC unit descriptions that comply with oschema

oscdoc

create HTML documentation for OSC unit descriptions that comply with oschema

see https://github.com/7890/oschema

oscdoc's Issues

Add Better Display For Paths With Multiple Accepted Argument Types

Right now if there is one OSC path which can receive different arguments (eg "f" or "") these are not distinguished in the display of the path with the htmlized documentation links. Either some display update or some way to include this information in the oscscheme would be useful.

Excessive CPU Usage of oschema2html.xsl

Testing with moderate sized inputs (~2.5k line input xml) an excessive amount of time is spent in this stage of processing.
xsltproc --profile indicated that most of the time was spent in base64encoder.
For http://fundamental-code.com/tmp/test-osc.xml this stage takes about 40 seconds at the moment.
After removing the base64encoder calls, this time is reduced to 0.05 seconds.
Is there a cheaper way to get a UID though a less expensive hash function or something?

entity_de_esc Failure

On running oscdoc, the script fails at entity_de_esc
The output of sed on my system is:

sed: -e expression #1, char 46: Invalid range end

Missing License

I was just whipping up a quick manpage for oscdoc and I noticed that there does not seem to be any mention of a license in any of the oscdoc/oschema code.
Could you add one? (just a simple COPYING file would be fine with me)