As of now, it does only insert the actual version in the generated PDFs, not the HTML output (or at least not all of it).
Probably, instead of inserting the version in PDF and HTML, we should already add it in the Markdown that ends up under build/gen_sources/, as it then works for all possible generated outputs, and also because that markdown might be considered an output by its self, and might be distributed as the documentation for a specific version by its self.
NOTE: use sed orawk` for adding/replacing the version in the markdown. IT is by far the easiest and probably the cleanest way to get there.
NOTE: I already started working on this locally (NOTE to self: in the local OSEG/ohs repo).
hoijui
commented
2 years ago
As of now, it does only insert the actual version in the generated PDFs, not the HTML output (or at least not all of it).
Probably, instead of inserting the version in PDF and HTML, we should already add it in the Markdown that ends up under
build/gen_sources/, as it then works for all possible generated outputs, and also because that markdown might be considered an output by its self, and might be distributed as the documentation for a specific version by its self.NOTE: use
sed orawk` for adding/replacing the version in the markdown. IT is by far the easiest and probably the cleanest way to get there.NOTE: I already started working on this locally (NOTE to self: in the local OSEG/ohs repo).