Should I go ahead and edit these files to move the constraintSpecs in dev? I've done that with moduleRef already, and I can just do the others. Then we could cherry-pick those commits into a released branch if you all think this merits a quick fix point-release. Cheers, Martin On 2021-02-25 10:15 a.m., Martin Holmes wrote:

Hi all,

I think this is perhaps worth a quick point-release update, I'm sorry to say. The problem occurs in four specs:

moduleRef variantEncoding citeStructure rt

Two of these are new and likely to get attention (citeStructure and rt). The problem can be solved easily by moving the constraints up to the elementSpec level -- I've tested with moduleRef and actually committed that change in dev. Whatever is causing it, it'll be deep in the Stylesheets, so I don't think we can fix the actual problem without a lot of work, but we can just move the constraintSpecs and make the pages work properly without any side-effects.

Cheers, Martin

On 2021-02-25 9:25 a.m., Martin Holmes wrote:

...

Hi all,

Just clicking around in the various types of Guidelines outputs, and I noticed this:

<https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html>

Take a look at the content model. It's the same in the ebook; it's slightly different but I think also borked in the PDF (p. 1402).

I don't think it's urgent, because it was the same in 4.1.0. I'll raise a ticket and start investigating.

Cheers, Martin

-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre