I am currently in the process of developing a commandline utility to quickly convert ecf files into a readable json format. I stress readable because I did find one other utility that does this, but it appears to use jsonpickle, and the resulting output is mangled quite a lot. The primary use case for such a utility would be ingesting the config files into an application or database for display / reference or whatever else. I don't currently have any plans to allow for converting from json back into ecf so it's really for read-only purposes. Mainly because I've never been able to find any kind of specification as to what is and is not allowed in the file format. From the huge inconsistencies I've been seeing between the various files I'm starting to think that's because no such specification exists. Some strings are in quotations, others are not, some comments use #, others are using /* and */ it seems to be all over the place. In any case, if there's any interest, I'll post the tool here when I'm done. It's basically done when I can get it to read all the various variations of ecf files. So far it handles about half.
