(VB6) Component Documenter

[Eduardo-]

JSON, XML are useful standards to use, they can be picked up by other tools, potentially useful in migration.

Yes, I have thought about that after considering xiaoyiao's proposal of exporting to JSON.
That could be useful to import the data into a third party reporting tool.
But the point is that the alleged reporting tool would expect the data no only in JSON (or XML), but in some specific way, unless it is very versatile and configurable.
So, if I don't know what the tool expect, I cannot output it in the right expected format. And BTW, they must exist, but I'm not aware of such tools.

Anyway, until a practical real case is presented, someone that don't like how this program outputs the information, and wants to just to use it to generate the data for later export to another reporting tool, we are talking about assumptions, and I won't spend days working on assumptions.

If you had a tool that could describe all of a forms' controls properties in XML using standard descriptions for x, y position &c then with just a little tweaking a design could be pulled into any forms designer that can read XML.

It does not describe forms, it is for components interfaces.
I think you are misunderstanding this program.

As far as being human-readable is concerned I have found no problems so far with XML.

Yes, you can also read pure html files's code if you want. But for "human readable" I was talking about like the format of a manual, or what msdn has on the web (not if you could figure the content).