TEIC
symlinks/binaries should be expanded a bit
The teitohtml5 symlink/script appears to process both regular TEI documents to web versions, and also ODD files to HTML documentation, based on a parameter. It would be much clearer if there were also an oddtohtml5 binary that did this without any extra knowledge being required. There may be other processes where it's ambiguous whether a regular TEI file is being passed in or an ODD file. Script names which distinguish this clearly would be a good idea.
@ebeshero and I wonder whether there should now only be a conversion to HTML5 (i.e. XHTML5 should be the output from any HTML conversion, and there should only be one symlink).
@sydb I think this could be easily accomplished; *tohtml5 should still work, but produce a warning to the effect that it's just the same as *tohtml and the latter is preferred, while the oddtohtml symlink just needs to be added, with handling for it in the script.