dev

.github/workflows/adoc_build.yml

@@ -57,7 +57,7 @@ jobs:
       with:
         shellcommand: 'asciidoctor --verbose ${FINAL_TAG} -a docprodtime=$(date -u ${DATE_FMT}) cf-conventions.adoc -D conventions_build; cp -r images conventions_build'
     # Patch the cfconventions.org link
-    - run: sed -E -i 's+(https://cfconventions.org)+<a href="\1" target="_blank">\1</a>+' ./conventions_build/cf-conventions.html
+    #    - run: sed -E -i 's+(https://cfconventions.org)+<a href="\1" target="_blank">\1</a>+' ./conventions_build/cf-conventions.html
     # Build cf-conventions.pdf using the Analog-inc asciidoctor-action
     - name: Build cf-conventions.pdf
       uses: Analog-inc/[email protected]

ch03.adoc

@@ -97,7 +97,7 @@ The description may define rules on the variable type, attributes and coordinate
 
 When appropriate, the table entry also contains the corresponding GRIB parameter code(s) (from ECMWF and NCEP) and AMIP identifiers.
 
-The standard name table is located at https://cfconventions.org/Data/cf\-standard\-names/current/src/cf\-standard\-name\-table.xml[test], written in compliance with the XML format, as described in <<standard-name-table-format>>.
+The standard name table is located at https://cfconventions.org/Data/cf-standard-names/current/src/cf-standard-name-table.xml[test], written in compliance with the XML format, as described in <<standard-name-table-format>>.
 Knowledge of the XML format is only necessary for application writers who plan to directly access the table.
 A formatted text version of the table is provided at link:$$https://docs.unidata.ucar.edu/cf_standard_name_table.html$$[test2] NO COMMA link:$$https://docs.unidata.ucar.edu/nug/current/md_types.html$$[netCDF external data types] and this table may be consulted in order to find the standard name that should be assigned to a variable.
 Some standard names (e.g. **`region`** and **`area_type`**) are used to indicate quantities which are permitted to take only certain standard values.