What did you do?
Created a table with cell values like (copied directly from table cell:
<?xml version="1.0" encoding="UTF-8"?>
<xml xmlns="http://www.wipo.int/classifications/ipc/masterfiles">
<note type="none">
<noteParagraph>
<text>Auxiliary devices attached to machines of a different kind, e.g. harrows attached to ploughs, see relevant groups in <mref endRef="A01B0047000000" ref="A01B0003000000" /> for the machines.</text>
</noteParagraph>
</note>
</xml>What did you expect to see?
In both XML and Text modes the same value above.
What did you see instead?
Copied from value viewer (XML and Text mode alike):
<?xml version='1.0' encoding='UTF-8'?>
<xml xmlns="http://www.wipo.int/classifications/ipc/masterfiles">
<note xmlns="http://www.wipo.int/classifications/ipc/masterfiles" type="none">
<noteParagraph xmlns="http://www.wipo.int/classifications/ipc/masterfiles">
<text xmlns="http://www.wipo.int/classifications/ipc/masterfiles">Auxiliary devices attached to machines of a different kind, e.g. harrows attached to ploughs, see relevant groups in <mref xmlns="http://www.wipo.int/classifications/ipc/masterfiles" ref="A01B0003000000" endRef="A01B0047000000"/> for the machines.</text>
</noteParagraph>
</note>
</xml>This only happens when value is recognized as well-formed XML. If I add a symbol at the beginning in the table cell, the value is no longer recognized as well-formed XML, and all fake "xmlns=..." are gone.
DB4S Version
3.13.1
What OS are you seeing the problem on?
Windows
OS version
Windows 10 LTSC 2019
Relevant log output
Prevention against duplicate issues
- I have searched for similar issues
Reactions are currently unavailable
What did you do?
Created a table with cell values like (copied directly from table cell:
What did you expect to see?
In both XML and Text modes the same value above.
What did you see instead?
Copied from value viewer (XML and Text mode alike):
This only happens when value is recognized as well-formed XML. If I add a symbol at the beginning in the table cell, the value is no longer recognized as well-formed XML, and all fake "xmlns=..." are gone.
DB4S Version
3.13.1
What OS are you seeing the problem on?
Windows
OS version
Windows 10 LTSC 2019
Relevant log output
Prevention against duplicate issues