Chris Maloney

Well, I have to say, I think reverting the fix in master was a bad idea. I remember that I only needed this fix when I upgraded to the latest...

+1

+1 Any chance this will get fixed? Also, I'd think it should complain about empty-string keys: ``` { "": "foo" } ```

Sorry I was a little hasty submitting this. Please use this commit: https://github.com/Klortho/MathJax-dev/commit/6be1361f3e69b27af41d2a5703d3391eb4d475bc See this compare view for all of the changes since when I forked: https://github.com/Klortho/MathJax-dev/compare/f20e729c46e729e0c736045d7139ffe1b2aae039...6be1361f3e69b27af41d2a5703d3391eb4d475bc

My turn: oh dear, I never noticed your comment above. @pkra , if you guys are still using this tool, then yes, absolutely, this is still relevant. If not, then...

One more enhancement that is really essential, I think: It has to do with the trailing commas and the pretty-printing. Those two features are almost impossible to get working robustly...

I implemented these in the [dtd-diagram](https://github.com/klortho/dtd-diagram) project, and they are currently integrated with the [alternative tag libraries](http://jatspan.org/niso/archiving-1.1/#p=elem-aff), but they are not integrated with DtdDocumentor yet.

I made a first stab at this. The dtdschematron scripts are in place and they correctly invoke the XSLT transformation, and output what looks like a reasonable document, when I...

A good bit of this documentation is in this comment: https://github.com/NCBITools/DtdAnalyzer/issues/3#issuecomment-9016049

Still need to document the XSLTs, that don't have their own command-line scripts. Where are they (xslt directory)? How do you run them? Give examples in "Quick start", and give...