Linking errors

[marcoscaceres]

Bikeshed is reporting the following errors, which is preventing this specification from being auto-published:

LINK ERROR: No 'dfn' refs found for 'activation | | | | | | | | behavior'.
<a data-link-type="dfn" data-lt="activation | | | | | | | | behavior">activation |
     |                   |        |          |                |                  |            | behavior</a>
LINK ERROR: No 'dfn' refs found for 'character | | | | value'.
<a data-link-type="dfn" data-lt="character | | | | value">character        |
		 |   |             | value</a>
LINK ERROR: No 'dfn' refs found for 'character | | | | value'.
<a data-link-type="dfn" data-lt="character | | | | value">character   |
		 |   |             | value</a>
LINK ERROR: No 'propdesc' refs found for 'ö'.
'ö'
LINK ERROR: No 'propdesc' refs found for 'ö'.
'Ö'

[garykac]

The section files need to be run through the pre-processor first before passing on to bikeshed.

Here, bikeshed is trying to interpret table formatting as links.

[marcoscaceres]

There is a pre-processor for the pre-processor? 🧐 I was not aware.

[saschanaz]

And that's called prepreprocessor 🤣

[garykac]

There is a pre-processor for the pre-processor? I was not aware.

Yes, the Building section of the Readme covers the details.

The build script ensures that the key and code and glyph values are formatted consistently and it also has special table editing support (so tables are easier to read/edit in the source files).