Make coq stdlib html's documentation readable offline

[SnarkBoojum]

In the Debian build script, I build and make the stdlib documentation available using:

        dune build @stdlib-html --display=verbose
	# all the html files point to the same logo - ship it and point to it
	cp ide/coqide/coq.png _build/default/doc/stdlib/html/logo.png
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/files/barron_logo.png,logo.png,g"
	# all the html files point to some remote css - but they can be local too
	cp doc/common/styles/html/coqremote/modules/node/node.css _build/default/doc/stdlib/html/
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/modules/node/node.css,node.css,g"
	cp doc/common/styles/html/coqremote/modules/system/defaults.css _build/default/doc/stdlib/html/
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/modules/system/defaults.css,defaults.css,g"
	cp doc/common/styles/html/coqremote/modules/system/system.css _build/default/doc/stdlib/html/
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/modules/system/system.css,system.css,g"
	cp doc/common/styles/html/coqremote/modules/user/user.css _build/default/doc/stdlib/html/
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/modules/user/user.css,user.css,g"
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/sites/all/themes/coq/coqdoc.css,coqdoc.css,g"
	cp tools/coqdoc/style.css _build/default/doc/stdlib/html/
	find _build/default/doc/stdlib/html/ -name "*.html" | xargs sed -i -e "s,//coq.inria.fr/sites/all/themes/coq/style.css,style.css,g"

so I put needed files with the html files and make the links use it, so that the docs look right even offline. You'll notice that it isn't a serious patch, but a hack to work around the issue.

In addition, you'll notice that the links I'm fixing look like "//coq.inria.fr/foo/bar/baz", which means they're lacking "https:" -- there must be something fishy about it too.

[ejgallego]

I can reproduce, that's an easy fix for someone willing to dig into the code.

[SkySkimmer]

In addition, you'll notice that the links I'm fixing look like "//coq.inria.fr/foo/bar/baz", which means they're lacking "https:" -- there must be something fishy about it too.

That's the "network-path reference" syntax https://stackoverflow.com/questions/4071117/uri-starting-with-two-slashes-how-do-they-behave
It means use whatever protocol the main page used to load the resource.