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
It is related to empty spaceS, but not necessarily “indentation”. The problem seems to be with line breaking. Depending on where the line is a break (in order to format the XML thus adding indentation), a new node (type text) is appended to the element.
Removing just indentation doesn't solve the problem.
<CHRONPROSE>
<NAME STANDARD="Johnson, Pauline" REF="https://commons.cwrc.ca/orlando:7a7be083-1459-4879-aee3-7b6fecbed81f">PJ</NAME> was born at the family home, <PLACE>
<PLACENAME>Chiefswood</PLACENAME>, on the <REGION REG="Ontario">Six Nations Reserve</REGION>
<GEOG REG="Canada"/>
</PLACE> near <PLACE>
<SETTLEMENT>Brantford</SETTLEMENT>, <REGION>Ontario</REGION>
<GEOG REG="Canada"/>
</PLACE>.</CHRONPROSE>
The problem is solved when the line breaking is removed with the indentation.
<CHRONSTRUCT RELEVANCE="SELECTIVE" CHRONCOLUMN="WRITINGCLIMATE" RESP="JSC">
<DATE VALUE="1861-03-10">10 March 1861</DATE>
<CHRONPROSE>
<NAME STANDARD="Johnson, Pauline" REF="https://commons.cwrc.ca/orlando:7a7be083-1459-4879-aee3-7b6fecbed81f">PJ</NAME> was born at the family home, <PLACE>
<PLACENAME>Chiefswood</PLACENAME>, on the <REGION REG="Ontario">Six Nations Reserve</REGION>
<GEOG REG="Canada"/>
</PLACE> near <PLACE>
<SETTLEMENT>Brantford</SETTLEMENT>, <REGION>Ontario</REGION><GEOG REG="Canada"/></PLACE>.
</CHRONPROSE>
Note that the “.” is on the same line as and now.
Since we don’t know where the line breakings are, the only way is to do this for sure is to remove all the (empty?) spaces. That is, having the XML as a single string. Not sure if this is a good idea, though.
see as example: https://cwrc.ca/islandora/object/orlando%3Ajohnp2
transformed using xslt property
indent="no"
: https://cwrc.ca/islandora/object/cwrc%3Aa8541aa9-8aaa-43d2-a4fd-c81ee724ff80seems to fix most of the extra spaces popping up
The text was updated successfully, but these errors were encountered: