| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
notes (not just the codes).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(DoM #2698).
|
|
#2698).
|
|
|
|
|
|
|
|
The boost test library shipped with Ubuntu 16.04 throws an exception
if you do that.
|
|
|
|
as subs).
|
|
We have a report of Deluxe failing a DCP because of this.
|
|
|
|
|
|
one in the asset map.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I guess originally it was a string mostly because it's not very well defined,
and Interop seemingly does whatever it wants. This basic change also means
that things are checked more carefully, and so we must be more relaxed with
some things seen in the wild that I can't find contradictions for in the
standard (and also with the case of channel IDs, which does seem to be
mentioned in the standard).
|
|
|
|
|
|
Previously we would discard any whitespace subtitle content we found.
This had the side-effect of making a verification test fail (checking
that at least one subtitle is in each reel; blank subtitles are often
used to avoid this warning).
Here we take any subtitle content, whitespace or not, inside a
<Text> or <Image> node which I think is a little more correct.
|
|
|
|
|
|
|
|
It was reported on the forum that files without any <Font> or
<Subtitle> tags fail validation on EasyDCP 3.0.1 and crash
Qubemaster Pro 3.0.15.
|