Jon Leech

@bashbaug I pushed a big update to #950 which, among other things, tries to pull in as much of this to the XML as possible, then uses those tags to...

The cl_khr_fp16 one is particularly egregious because there are just so many of them (and also see my issues in #1044 regarding this extension and the current C spec). In...

Realistically speaking the 1.0-1.2 stuff is unlikely to get fixed. That's using the old toolchain that had a tendency to create incredibly chopped up documents with tiny bits of HTML...

Yes, just a typo in the document markup for the link to the main spec. Not sure why I thought the registry index was at fault.

BTW, I've been looking at similar issues since James brought up the report for the Vulkan registry. There are a bunch of causes in our case including the refpage extractor...

Also, the internal links are trivial to check in the generated HTML without running a link-checker on the website - this find almost all of the problems for us without...

BTW @rpavlik I'm not sure if you're aware, but a while back we went through an exercise in the Vulkan spec to make sure that every use of 'undefined' was...

Thanks! I'll try to describe what my intended use cases are. For reference I'm the release manager for the Vulkan specification (KhronosGroup/Vulkan-Docs on github, but much of our work is...

N.b. I unfortunately am not at all familiar with Go, so probably not in a position to assist much with this - if it happens that my use case is...

I like #3. I've been doing REUSE compliance for some repositories which import multiple other repos which are *not* REUSE-compliant and aren't likely to be, so globbing is important.