You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the metadata.xsl we had JATS-journalpublishing1.dtd which should be a local file, although we do not have the schema in the generated folder.
NLM maintains the DTD in a CDN manner, which can be automatically extracted for validation.
Another solution would be to copy the DTD from the runtime folder to each generated NLM folder, which may add extra storage, what I thought users would not like.
Additionally, I added two namespaces, xlink and mml, which are common in JATS files so that an automated validation is possible, even though some files may not have mml.
Sorry for the MASSIVE delay here, but this is giving me some very weird results on test 510 and 513: XTDE0820: Invalid element name. Invalid QName {2} among others.
Starting test: Tests.Section Headers.510 Complex headings
20200102 17:30:08.874 : INFO :
Starting process:
python ../bin/meTypeset.py docx ComplexHeadings.docx ./510 -d --nogit
20200102 17:30:08.876 : INFO : Waiting for process to complete.
20200102 17:30:09.043 : INFO : Process completed.
20200102 17:30:09.044 : INFO : ${result} = <result object with rc 1>
20200102 17:30:09.045 : INFO :
20200102 17:30:09.045 : INFO :
Traceback (most recent call last):
File "../bin/meTypeset.py", line 43, in
from frontmatterparser import *
File "/home/Mounts/linuxfilesssd/Documents/Programming/meTypeset/bin/frontmatterparser.py", line 45
print guess2score.iteritems()
^
SyntaxError: invalid syntax
20200102 17:30:09.046 : FAIL : IOError: [Errno 2] No such file or directory: u'./510/nlm/out.xml'
20200102 17:30:09.047 : INFO : Directory '/home/Mounts/linuxfilesssd/Documents/Programming/meTypeset/tests/510' does not exist.
Ending test: Tests.Section Headers.510 Complex headings
Starting test: Tests.Section Headers.513 Renesting mechanism
20200102 17:30:09.048 : INFO :
Starting process:
python ../bin/meTypeset.py docx Renesting.docx ./513 -d --nogit
20200102 17:30:09.051 : INFO : Waiting for process to complete.
20200102 17:30:09.107 : INFO : Process completed.
20200102 17:30:09.108 : INFO : ${result} = <result object with rc 1>
20200102 17:30:09.109 : INFO :
20200102 17:30:09.109 : INFO :
Traceback (most recent call last):
File "../bin/meTypeset.py", line 43, in
from frontmatterparser import *
File "/home/Mounts/linuxfilesssd/Documents/Programming/meTypeset/bin/frontmatterparser.py", line 45
print guess2score.iteritems()
^
SyntaxError: invalid syntax
20200102 17:30:09.110 : FAIL : IOError: [Errno 2] No such file or directory: u'./513/nlm/out.xml'
20200102 17:30:09.111 : INFO : Directory '/home/Mounts/linuxfilesssd/Documents/Programming/meTypeset/tests/513' does not exist.
Ending test: Tests.Section Headers.513 Renesting mechanism
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @MartinPaulEve ,
In the metadata.xsl we had JATS-journalpublishing1.dtd which should be a local file, although we do not have the schema in the generated folder.
NLM maintains the DTD in a CDN manner, which can be automatically extracted for validation.
Another solution would be to copy the DTD from the runtime folder to each generated NLM folder, which may add extra storage, what I thought users would not like.
Additionally, I added two namespaces, xlink and mml, which are common in JATS files so that an automated validation is possible, even though some files may not have mml.
Best wishes,
Dulip