I don't think enabling trivial modifications at the expense of creating an immense amount of manual labor is the right trade-off.On 12/08/13 19:15, Benoit Jacob wrote:On the one hand, we have markup language that make it easy to write documents. On the other hand we have XML which gives automation but is a pain to write by hand. The only document writing system that combines convenient markup with good large-document-structuration-and-automation features, that I know of, is LaTeX. From the looks of the OpenGL [ES] PDF spec, it seems that it's made in LaTeX, for example (maybe someone can confirm). But compared to a wiki, this will increase the barrier to entry quite a bit.
https://cvs.khronos.org/svn/repos/ogl/trunk/ecosystem/public/sdk/docsIf you look in e.g., man4 for example, you can see the source xml files. The output files are in, e.g., man4/xhtml.
If it wasn't for the issue that a lot of information will be duplicated between this and the OpenGL ES man pages and the related issue that the WebGL spec is not a complete standalone specification, I'd say go for it.
Currently, the IDL file is extracted from the spec (see https://github.com/KhronosGroup/WebGL/blob/master/specs/latest/extract-idl.py). Seems like the text for man pages could be similarly extracted. This might involve tagging additional elements in the spec, or adding some hidden elements with additional data. Then maybe the simplest thing to do would be to add this text to the IDL in Doxygen format so we can use those tools to generate various formats of man pages?
NOTE: This electronic mail message may contain confidential and privileged information from HI Corporation. If you are not the intended recipient, any disclosure, photocopying, distribution or use of the contents of the received information is prohibited. If you have received this e-mail in error, please notify the sender immediately and permanently delete this message and all related copies.