You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
STL2SLTXML: Mapping of TTI blocks containing comments #27
In the current scf verison 0.2.8, TTI blocks from an STL file that contain comments are ignored when transforming from STL to STLXML. These comments should be mapped as well in order to achieve a "better" XML representation of the STL file.
CF set to 00h --> TTI Block contains subtitle data
CF set to 01h --> TTI Block contains comments
The mapping of the text field (TF) of a comment should be handled is the same way that a normal subtitle is.
The description of the requirement no. 214 "Comment Flag mapping" should be updated accordingly.
Comments should be mapped from STLXML to EBU-TT according to EBU-TT Part 2:
"The text content of a comment TTI block in an STL file may be placed into an ebuttExt:comment element. The ebuttExt:comment element must itself be a child element of a tt:metadata element, which must be the first child element of the containing tt:p element. The TTI block containing the comment may be associated with subtitle text in another TTI block (by having matching TCI and TCO values or SN value), or may be independently timed, as below: [...]" Page 35
Activity
braincoded commentedon Feb 5, 2017
+1 A very good point!
pthopesch commentedon Feb 7, 2017
Comments should be mapped from STLXML to EBU-TT according to EBU-TT Part 2:
"The text content of a comment TTI block in an STL file may be placed into an ebuttExt:comment element. The ebuttExt:comment element must itself be a child element of a tt:metadata element, which must be the first child element of the containing tt:p element. The TTI block containing the comment may be associated with subtitle text in another TTI block (by having matching TCI and TCO values or SN value), or may be independently timed, as below: [...]" Page 35
nigelmegitt commentedon Feb 7, 2017
I think we will probably be deprecating
ebuttExtand will just make this metadata inebuttm, to be confirmed.