Closed DavidFLOR closed 4 years ago
@DavidFLOR , the entry point for the document is standard_document.adoc
In each CDB volume repo, the entry point for the document is standard_document.adoc
So to generate the standard, please use asciidoctor -a stem=latexmath --safe -a data-uri -o standard_document.html standard_document.adoc
NOTE: The file with the name beginning with 15-113r5 is an output of one of the processing steps. It can be deleted.
As you know we have our standard and best practices spread out over multiple repos. Not everyone will be using github. We will need to be posting to our OGC portal CDB project .html and .pdf conversions. Do I understand your comment to mean the WG's using these repos can't change the 'standard_document' to a specific name for each repo?
The repo holds the code/elements that are needed to generate the HTML and PDF files.
In order to generate the HTML file, the following command has to be ran asciidoctor -a stem=latexmath --safe -a data-uri -o standard_document.html standard_document.adoc
In order to generate the PDF file, the following command has to be ran asciidoctor-pdf -a stem=latexmath --safe -a data-uri -o standard_document.pdf standard_document.adoc
After generating the HTML or PDF file using the above commands, the output file can be uploaded to the OGC Portal.
Files uploaded to the OGC Portal are given the title of the artefact as names. So it is not necessary to change the name of standard_document.
I"ve seen the syntax of those command line instructions. A more specific document name can easily be substituted to replace 'standard_document' in those command lines. A more specific document name is of value to the WG when we have 19 github repos active. Besides knowing we have to substitute the more specific document name is there some other reason why the WG can't change the document name.
After changing the 'source-highlighter', the windows errors using asciidoctor conversion scripts have been cleared up