Excellent job! It kinda makes sense for one person to decode the commands and share it with everyone instead of everyone who ever used mathopd to do it. I haven't found any glaring errors (in my 30 second scan) and I can't see the harm in publishing it. I would add a couple line blurb at the beginning explaining how mathopd reads the configuration file because that can be a major hurtle (I've never seen a program that takes its config file from STDIN, but it does make it very convenient). Lots of programs have manuals written by users instead of the author. And, I don't see anything wrong with placing this file on the mathopd home page with just a quick comment that it's from a user and unverified. Even if 10% of it is wrong, users are still 90% further than they are without it.
Anyway, well done! I already had to decode several commands and this makes it easy to figure out the rest. Tim > Hi, > > I subscribed to this mailing list only a week ago, and I have > already seen quite some messages about the mathopd config file. > The author admits that there is no documentation describing the > mathopd config file. > So, I took the opportunity to fill that information gap, > reverse engineered the config.c and browsed the other source files > to produce my version of such a syntax description. > I have sent it to Michiel Boland, but he replied that unfortunately > he is too busy at the moment to verify the contents. > > At last I have decided to publish the document anyhow, but remember : > This is my *personal* understanding of the syntax and semantics of the > mathopd config file. It is by no means complete or even correct. > Please also take into consideration that English is not my native tongue. > USE IT AT YOUR OWN RISK.
