libdcp/src/smpte_subtitle_asset.cc, branch utf8

Be explicit about the version of SMPTE 428-7 that is used for subtitles,

2023-02-17T23:35:01Z

and default to writing the 2014 namespace.

In Deluxe's "Specifications for Digital Cinema Source and DCP Content Delivery"

2023-02-02T00:37:16Z

they say that subtitle must be of the form yyyy-mm-ddThh:mm:ss They don't explain it, and the standards don't say this (as far as I can see) but as usual their QC fails that don't meet this "spec" so here we are. See also: https://dcpomatic.com/forum/viewtopic.php?t=2069

Fix some ambiguous shared_ptrs, seen on Arch Linux.

2022-12-04T20:52:29Z

Nearly pretty-print subtitle XML (though not in nodes).

2022-03-20T20:20:58Z

This is an attempt to fix DoM bug #2205.

Make the former dcst namespace default for SMPTE subtitles.

2021-10-03T20:18:56Z

In DoM bug #2061 it is reported that Easy DCP gives the error "XML Document has default root namespace prefix: dcst. Default namespace should not use prefix for root or root namespace child nodes." with SMPTE subtitle files written by DCP-o-matic, and that the correct fix is to make the former dcst: namespace the default and then remove the dcst: qualifiers from everything. I'm not sure I agree with the error; AFAICS the subtitle files written by previous versions did not have a default root namespace prefix, since it was specified by xmlns:dcst and not just xmlns alone, so I think they were valid. However, using a default NS also seems fine, slightly simplifies the code and produces more compact subtitle files, so we change that here. It should also stop Easy DCP complaining, which is always marginally preferable to sticking to our guns and getting the blame for it.

Make similar changes to the previous commit for _xml_id.

2021-05-27T12:25:17Z

This is also unavailable if the asset is encrypted.

Tidy handling of _raw_xml.

2021-05-27T12:25:17Z

Before this if we tried to get the XML of an encrypted asset we would just get an empty string. Now we get a boost::none which means the verifier can avoid trying to check details of the XML (and instead raise a warning that you are trying to verify data that it cannot decrypt).

Read the bits we can from the MXF header even when it is encrypted.

2021-05-27T09:45:11Z

Fix/hide some warnings.

2021-04-13T23:00:05Z

Don't set the MXF _id from the XML tag.

2021-04-08T00:05:04Z

They should not be the same, so it's unhelpful to make them so. parse_xml() sets up _xml_id anyway.