Closed matmat closed 10 months ago
TI's spec document has this, though, in A.1 DTD Specification:
<!ELEMENT LoadFont EMPTY>
If I read it correctly the prose in 2.7 LoadFont differs from Chapter 3's example differs from A.1 DTD.
Feeling hesitant to take xs:simpleContent on board ... convince me? [ducks]
@wolfgangw You are right. Feel free to close this. The example DCP I was referencing is clearly doing it wrong.
@matmat yes, I agree.
Fwiw, I'm not aware of systems in the field which would choke over content in LoadFont
, though. But, I reckon, we have to stick to the ground truth as best as we can.
I will modify the language around Error/Hint/Info (there's a wiki page with a chapter on the distinction) to mention that Error may merely be a violation of a given standard, with no practical consequences in the field. Right now, it says that Error will result in playback failure, iirc. (it's ok, kind of had that already)
The spec says "The LoadFont element has only attributes, and no values, so it can be specified as an empty tag (...)". So it seems that this is not required.
Today I encountered an DCSubtitle file with the following:
dcp_inspect throws the following error:
And in fact the example on page 31 of http://www.dlp.com/downloads/pdf_dlp_cinema_cinecanvas_rev_c.pdf contains the similar:
So this does indeed seem legit.
The following patch allows for a
xs:string
as content of the LoadFont element. Also tested successfully on DCSubtitle files with empty LoadFont elements.