Term rendering with concept mentions broken in style, instead of issuing warning of missing reference

[ronaldtse]

Notice how the "scene graph" term has its definition messed up.

==== scene graph

Encoded graph that contain information about {{scene,scenes}}, {{hyperspace asset,assets}}, {{authority,authorities}} and {{action,actions}}.


==== scene graph server

Server that contains primary and subordinate {{scene graph,scene graphs}}.

NOTE: Different servers may contain different parts of the same scene (for instance, the Earth scene, which hosts any form of augmented reality scenes, has potentially millions of scenes broken down by nested geopolitical regions or corporate environments). Unmoored scenes (such as those associated with game or simulation worlds that aren't based on real Earth location) may be similarly segmented.

related:seealso[scene graph]

[opoudjis]

The bug involves four cross references. You have not provided any of them. I therefore cannot debug this.

This issue will be ignored until you provide the source document. Your ongoing failure to provide sufficient information for actionable issues is going to continue to get the same response.

[ronaldtse]

https://github.com/metanorma/SWF-Corpus_and_IEEEP2874-D2

Check it here.

[ronaldtse]

I forgot to mention that PDF layout works perfectly.

[opoudjis]

There is no such term as "hyperspace asset".

AsciiDoc Input: (XML Line 000794): Error: Term reference to `hyperspace-asset` missing: "hyperspace-asset" is not defined in document

[opoudjis]

We should break rendering, as with Standoc:

Error: Term reference to `#{target}` missing: "#{target}" is not defined in document

Need to establish why this isn't happening in IEEE.

[opoudjis]

This is happening because we left it open when a term is not cited in an IEEE document, that it might be cited from the IEEE online dictionary.

But concept markup should not be used for such external references, when it presupposes for concept markup that the term is defined internally by default (which is what is happening here). If a cross-reference is given to a term, it should be explicit. So an error still needs to be displayed.

[opoudjis]

No, changed my mind again. Those pending definitions to external and absent terms are legit.

[opoudjis]

Need to get rid of intrusive spaces around concepts, inherited from pretty-printing.

[opoudjis]

Removed redundant spaces from the wrong place. They are being introduced in termdefinition processing.

[opoudjis]

to_xml as invoked in isodoc needs to use Nokogiri::XML::Node::SaveOptions::AS_XML a lot more, to prevent XML from being rendered with carriage returns between tags.

[opoudjis]