(URGENT) Failure when building document inside container

ronaldtse commented 4 years ago

@camobap795 can you help fix this? Thanks!

docker run -v $(pwd):/metanorma -it metanorma/metanorma metanorma sources/iso-24229.adoc
PlantUML not installed
PlantUML not installed
PlantUML not installed
Cache relaton/cache/iso/: version is obsolete and cache is cleared.
Cache relaton/cache/cn/: version is obsolete and cache is cleared.
[relaton-iso] ("ISO 5127") fetching...
[relaton-iso] ("ISO 5127") found ISO 5127 (all parts)
[relaton-iso] ("ISO 15924") fetching...
^CTraceback (most recent call last):
    81: from /usr/local/bundle/bin/metanorma:23:in `<main>'
    80: from /usr/local/bundle/bin/metanorma:23:in `load'
    79: from /usr/local/bundle/bundler/gems/metanorma-cli-1c0cc29c0a77/exe/metanorma:20:in `<top (required)>'
...

docker run -v $(pwd):/metanorma -it metanorma/metanorma bash
# in container
make clean all published
Running locally...
Cache relaton/cache/iso/: version is obsolete and cache is cleared.
Cache relaton/cache/cn/: version is obsolete and cache is cleared.
[relaton-iso] ("ISO 5127") fetching...
[relaton-iso] ("ISO 5127") found ISO 5127 (all parts)
[relaton-iso] ("ISO 15924") fetching...
[relaton-iso] ("ISO 15924") found ISO 15924:2004
bundler: failed to load command: metanorma (/usr/local/bundle/bin/metanorma)
Errno::ENOENT: No such file or directory @ rb_sysopen - ./images/plantuml/plantuml20200207-220-szwff1.png
  /usr/local/bundle/gems/metanorma-standoc-1.3.16/lib/asciidoctor/standoc/inline.rb:162:in `initialize'
  /usr/local/bundle/gems/metanorma-standoc-1.3.16/lib/asciidoctor/standoc/inline.rb:162:in `open'
  /usr/local/bundle/gems/metanorma-standoc-1.3.16/lib/asciidoctor/standoc/inline.rb:162:in `datauri'
  /usr/local/bundle/gems/metanorma-standoc-1.3.16/lib/asciidoctor/standoc/inline.rb:172:in `image_attributes'

Clearly the failure is due to PlantUML not useable from within Metanorma.

However, if I go into the container, the plantuml command works:

root@f05200466649:/metanorma# plantuml -h
Usage: java -jar plantuml.jar [options] -gui
    (to execute the GUI)
    or java -jar plantuml.jar [options] [file/dir] [file/dir] [file/dir]
    (to process files or directories)

You can use the following wildcards in files/dirs:
    *   means any characters but '/'
    ?   one and only one character but '/'
    **  means any characters (used to recurse through directories)
...

CAMOBAP commented 4 years ago

In progress

CAMOBAP commented 4 years ago

This is how we call plantuml for the code, examples:

"plantuml /tmp/plantuml20200207-682-ewdu3l.pml"
"plantuml /tmp/plantuml20200207-682-1v5zccz.pml"
"plantuml /tmp/plantuml20200207-682-1x47b2i.pml"

As results images created in /tmp directory then by our logic they moved to plantuml directory which created at the same level where adoc placed

After this we have bad logic which adds wrong 'prefix' to it,

to be continued ...

CAMOBAP commented 4 years ago

Here are my research results

https://github.com/metanorma/metanorma-standoc/blob/master/lib/asciidoctor/standoc/macros.rb#L192 - here we hardcoded "plantuml" image directory and it doesn't respect :imagesdir: for adoc
according to the comment to this method it should care about :imagesdir:

PR https://github.com/metanorma/metanorma-standoc/pull/204

ronaldtse commented 4 years ago

PR metanorma/metanorma-standoc#204 is now merged.

The docker images will still crash with PlantUML until @opoudjis makes a new release of metanorma-standoc. Let's close this once the new release of metanorma-standoc is up and docker containers are updated.

This shows that it is important to only release a docker container after testing on documents. We need to do this.

CAMOBAP commented 4 years ago

@ronaldtse I have tested the fix by patching gem inside of docker, but I agree that we should follow the process

ronaldtse commented 4 years ago

@CAMOBAP795 we don't even have this part of the process 😢

This shows that it is important to only release a docker container after testing on documents. We need to do this.

opoudjis commented 4 years ago

Metanorma release has happened

CAMOBAP commented 4 years ago

@ronaldtse it works for me, I think we can close this one

docker run -v $(pwd):/metanorma -it metanorma/metanorma metanorma sources/iso-24229.adoc

``` asciidoctor: ERROR: sources/sections/a3-codes.adoc: line 6: include file not found: /metanorma/sources/data/codes.adoc [relaton-iso] ("ISO 24614-1") fetching... [relaton-iso] ("ISO 24614-1") found ISO 24614-1:2010 [relaton-iso] ("ISO 24614-2") fetching... [relaton-iso] ("ISO 24614-2") found ISO 24614-2:2011 [relaton-iso] ("ISO 639") fetching... [relaton-iso] ("ISO 639") found ISO 639 (all parts) [relaton-iso] ("ISO 639-1") fetching... [relaton-iso] ("ISO 639-1") found ISO 639-1:2002 [relaton-iso] ("ISO 639-2") fetching... [relaton-iso] ("ISO 639-2") found ISO 639-2:1998 [relaton-iso] ("ISO 639-3") fetching... [relaton-iso] ("ISO 639-3") found ISO 639-3:2007 [relaton-iso] ("ISO 639-5") fetching... [relaton-iso] ("ISO 639-5") found ISO 639-5:2008 [relaton-iso] ("ISO 3166-1") fetching... [relaton-iso] ("ISO 3166-1") found ISO 3166-1:2013 [relaton-iso] ("ISO/IEC TR 15285") fetching... [relaton-iso] ("ISO/IEC TR 15285") found ISO/IEC TR 15285:1998 [relaton-iso] ("ISO 9") fetching... [relaton-iso] ("ISO 9") found ISO 9:1995 [relaton-iso] ("ISO 233") fetching... [relaton-iso] ("ISO 233") found ISO 233 (all parts) [relaton-iso] ("ISO 233-2") fetching... [relaton-iso] ("ISO 233-2") found ISO 233-2:1993 [relaton-iso] ("ISO 233-3") fetching... [relaton-iso] ("ISO 233-3") found ISO 233-3:1999 [relaton-iso] ("ISO 259") fetching... [relaton-iso] ("ISO 259") found ISO 259 (all parts) [relaton-iso] ("ISO 259-2") fetching... [relaton-iso] ("ISO 259-2") found ISO 259-2:1994 [relaton-iso] ("ISO 843") fetching... [relaton-iso] ("ISO 843") found ISO 843:1997 [relaton-iso] ("ISO 3602") fetching... [relaton-iso] ("ISO 3602") found ISO 3602:1989 [relaton-iso] ("ISO 7098") fetching... [relaton-iso] ("ISO 7098") found ISO 7098:2015 [relaton-iso] ("ISO 9984") fetching... [relaton-iso] ("ISO 9984") found ISO 9984:1996 [relaton-iso] ("ISO 9985") fetching... [relaton-iso] ("ISO 9985") found ISO 9985:1996 [relaton-iso] ("ISO 11940") fetching... [relaton-iso] ("ISO 11940") found ISO 11940 (all parts) [relaton-iso] ("ISO 11940-2") fetching... [relaton-iso] ("ISO 11940-2") found ISO 11940-2:2007 [relaton-iso] ("ISO 15919") fetching... [relaton-iso] ("ISO 15919") found ISO 15919:2001 [relaton-iso] ("ISO 20674-1") fetching... [relaton-iso] ("ISO 20674-1") found ISO 20674-1:2019 BGN/PCGN Romanization Systems does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN Romanization Systems does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1956 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1956 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1979 Agreement does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1979 Agreement does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1993 Agreement does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1993 Agreement does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1981 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN 1981 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ALA-LC Romanization Tables does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ALA-LC Romanization Tables does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. UNGEGN Working Group on Romanization Systems does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. UNGEGN Working Group on Romanization Systems does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Fifth United Nations Conference on the Standardization of Geographical Names does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Fifth United Nations Conference on the Standardization of Geographical Names does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. System of Romanization for Japanese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. System of Romanization for Japanese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ICI Standard Orthography does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ICI Standard Orthography does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. National Institute of Korean Language — Romanization of Korean does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. National Institute of Korean Language — Romanization of Korean does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transliteration and Translation System for Nepal does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transliteration and Translation System for Nepal does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Report on Cartography and Reproduction of Eastern Nepal Topographic Mapping Project does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Report on Cartography and Reproduction of Eastern Nepal Topographic Mapping Project does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. The Linguistic Society of Hong Kong Cantonese Romanisation Scheme does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. The Linguistic Society of Hong Kong Cantonese Romanisation Scheme does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Rules of transliteration from Hebrew into Latin letters does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Rules of transliteration from Hebrew into Latin letters does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transliteration system for the Names of Geographical Features of Georgia into the Latin Alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transliteration system for the Names of Geographical Features of Georgia into the Latin Alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BDS 1596 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BDS 1596 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Geographic Department Transcription System for Khmer does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Geographic Department Transcription System for Khmer does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Yale Romanization does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Yale Romanization does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Myanmar Language Commission Transcription System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Myanmar Language Commission Transcription System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Maldives Official Romanization System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Maldives Official Romanization System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Royal Thai General System of Transcription does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Royal Thai General System of Transcription does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. fetching GB/T 16159-2012... fetching GB/T 15834-2011... fetching GB/T 28039-2011... Scheme for the Chinese Phonetic Alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Scheme for the Chinese Phonetic Alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Chinese Phonetic Alphabet Spelling Rules for Chinese Geographical Names does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Chinese Phonetic Alphabet Spelling Rules for Chinese Geographical Names does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ICAO Doc 9303: Machine Readable Travel Documents does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ICAO Doc 9303: Machine Readable Travel Documents does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST 7.79 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST 7.79 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST R 52535.1 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST R 52535.1 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST R 7.0.34 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GOST R 7.0.34 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GUGK Order No.231 of 13.05.1983 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. GUGK Order No.231 of 13.05.1983 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 1460 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 1460 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 1460-2 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 1460-2 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31634 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31634 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31635 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31635 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31635 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31635 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31636 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 31636 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32706 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32706 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32707 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32707 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32708 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 32708 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 33903 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 33903 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 33904 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. DIN 33904 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Guideline to the Romanization of Korean does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Guideline to the Romanization of Korean does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transcription of Chinese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Transcription of Chinese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ELOT 743 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ELOT 743 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ELOT 743 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ELOT 743 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. YIVO Yiddish Alef-Beys does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. YIVO Yiddish Alef-Beys does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Systeme de transcription des caracteres ethiopiens adopte par la BIULO does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Systeme de transcription des caracteres ethiopiens adopte par la BIULO does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Bulgaria system for transliteration of Bulgarian geographical names with Roman letters does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Bulgaria system for transliteration of Bulgarian geographical names with Roman letters does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Bulgaria Transliteration Act does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Republic of Bulgaria Transliteration Act does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. UN Romanization System In Bulgaria does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. UN Romanization System In Bulgaria does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN Romanization Agreement — Bulgarian (2013) does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BGN/PCGN Romanization Agreement — Bulgarian (2013) does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Toponymic Guidelines for Antarctica does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Toponymic Guidelines for Antarctica does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Streamlined Romanization system for Russian Cyrillic does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Streamlined Romanization system for Russian Cyrillic does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Chinese-English Dictionary does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Chinese-English Dictionary does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Dictionary of Spoken Chinese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Dictionary of Spoken Chinese does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Macedonian Latin alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Macedonian Latin alphabet does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. IS 13194 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. IS 13194 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Unicode Transliteration Guidelines does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Unicode Transliteration Guidelines does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 2979 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 2979 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 4280 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 4280 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 4812 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 4812 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 7014 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS 7014 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS PD 6505 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BS PD 6505 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Arabic DMG 1936 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Arabic DMG 1936 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Perso-Arabic DMG 1969 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Perso-Arabic DMG 1969 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Armenian Hübschmann-Meillet 1913 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Armenian Hübschmann-Meillet 1913 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ANSI Z39.11 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ANSI Z39.11 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Ministry of Foreign Affairs Passport Standard does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Ministry of Foreign Affairs Passport Standard does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Hyōjun-shiki Romaji does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Hyōjun-shiki Romaji does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Railway Notice Regulations does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Railway Notice Regulations does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Japanese and English Dictionary: with an English and Japanese Index does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Japanese and English Dictionary: with an English and Japanese Index does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Japanese-English And English-Japanese Dictionary does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. A Japanese-English And English-Japanese Dictionary does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Romanization of Geographical Names in Japan does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Romanization of Geographical Names in Japan does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Road Association Road Sign Establishment Standard does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japan Road Association Road Sign Establishment Standard does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Nippon-no-Rômazi-Sya Rômazi no tuzurikata Nihon-siki does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Nippon-no-Rômazi-Sya Rômazi no tuzurikata Nihon-siki does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Nihon-siki Rômazi does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Nihon-siki Rômazi does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese Modified Hepburn 1954 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese Modified Hepburn 1954 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese Modified Hepburn 1974 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese Modified Hepburn 1974 System does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese, The Spoken Language does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Japanese, The Spoken Language does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. The transliteration of Ottoman Turkish does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. The transliteration of Ottoman Turkish does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. IAST 1912 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. IAST 1912 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BULAC 2010 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. BULAC 2010 does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Hong Kong Government Cantonese Romanisation does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. Hong Kong Government Cantonese Romanisation does not have a recognised prefix: CN, IEC, IETF, ISO, ITU, NIST, OGC, CC. See https://github.com/relaton/relaton/ for instructions on prefixing and wrapping document identifiers to disambiguate them. ISO style: WARNING (Line 59): Foreword may contain requirement: ISO shall not be held responsible for identifying any or all such patent rights ISO style: WARNING (Line 59): Foreword may contain permission: Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights ISO style: WARNING (Line 59): Foreword may contain recommendation: In particular the different approval criteria needed for the different types of ISO documents should be noted ISO style: WARNING (Line 134): Hanging paragraph in clause ISO style: WARNING (Line 147): Hanging paragraph in clause ISO style: WARNING (Line 158): Hanging paragraph in clause ISO style: WARNING (Line 163): Hanging paragraph in clause ISO style: WARNING (Line 210): Hanging paragraph in clause ISO style: WARNING (Line 232): Hanging paragraph in clause ISO style: WARNING (Line 232): Hanging paragraph in clause ISO style: WARNING (Line 246): Hanging paragraph in clause ISO style: WARNING (Line 286): Hanging paragraph in clause ISO style: WARNING (Line 291): Hanging paragraph in clause ISO style: WARNING (Line 380): Hanging paragraph in clause ISO style: WARNING (Line 380): Hanging paragraph in clause ISO style: WARNING (Line 394): Hanging paragraph in clause ISO style: WARNING (Line 457): Hanging paragraph in clause ISO style: WARNING (Line 495): Hanging paragraph in clause ISO style: WARNING (Line 536): Hanging paragraph in clause ISO style: WARNING (Line 575): Hanging paragraph in clause ISO style: WARNING (Line 322): number not broken up in threes: 2013 ISO style: WARNING (Line 322): number not broken up in threes: 2013 ISO style: WARNING (Line 403): number not broken up in threes: 2012 ISO style: WARNING (Line 403): number not broken up in threes: 2012 ISO style: WARNING (Line 406): number not broken up in threes: 1995 ISO style: WARNING (Line 406): number not broken up in threes: 1995 ISO style: WARNING (Line 423): number not broken up in threes: 1993 ISO style: WARNING (Line 437): number not broken up in threes: 2015 ISO style: WARNING (Line 440): number not broken up in threes: 1460 ISO style: WARNING (Line 440): number not broken up in threes: 1982 ISO style: WARNING (Line 440): number not broken up in threes: 1460 ISO style: WARNING (Line 440): number not broken up in threes: 1982 ISO style: WARNING (Line 532): number not broken up in threes: 1912 ISO style: WARNING (Line 81): possible decimal point: 3.1 ISO style: WARNING (Line 85): possible decimal point: 3.1 ISO style: WARNING (Line 93): possible decimal point: 3.1 ISO style: WARNING (Line 97): possible decimal point: 3.1 ISO style: WARNING (Line 117): possible decimal point: 3.2 ISO style: WARNING (Line 121): possible decimal point: 3.8 ISO style: WARNING (Line 323): number not broken up in threes: 2013 ISO style: WARNING (Line 323): number not broken up in threes: 2013 ISO style: WARNING (Line 404): number not broken up in threes: 2012 ISO style: WARNING (Line 404): number not broken up in threes: 2012 ISO style: WARNING (Line 407): number not broken up in threes: 1995 ISO style: WARNING (Line 407): number not broken up in threes: 1995 ISO style: WARNING (Line 424): number not broken up in threes: 1993 ISO style: WARNING (Line 438): number not broken up in threes: 2015 ISO style: WARNING (Line 441): number not broken up in threes: 1460 ISO style: WARNING (Line 441): number not broken up in threes: 1982 ISO style: WARNING (Line 441): number not broken up in threes: 1460 ISO style: WARNING (Line 441): number not broken up in threes: 1982 ISO style: WARNING (Line 533): number not broken up in threes: 1912 ISO style: WARNING (Line 154): Figure should have title ISO style: WARNING (Line 212): Figure should have title ISO style: WARNING (Line 293): Figure should have title ISO style: WARNING (Line 608): Table should have title element "clause" incomplete; expected element "admonition", "bookmark", "clause", "dl", "example", "figure", "formula", "hr", "note", "ol", "p", "pagebreak", "permission", "pre", "quote", "recommendation", "requirement", "review", "sourcecode", "table" or "ul" @ 196:10 ```

ronaldtse commented 4 years ago

Let’s close. Thanks!

metanorma / metanorma-docker

(URGENT) Failure when building document inside container #55