Open skynavga opened 5 years ago
@skynavga we'd like to be able to resolve this before or during Thursday's call if possible.
but div
is not image
Applying itts:forcedDisplay
to the parent div
of an image
has the effect as applying it to image
(for Image Profile document).
ok, but an author should be able to apply it to the image
itself alone, yes?
ok, but an author should be able to apply it to the image itself alone, yes?
Not necessary in IMSC, and itts:forcedDisplay
is an IMSC extension.
My overriding suggestion is to avoid making any change to the Image Profile unless absolutely necessary.
ok, but an author should be able to apply it to the
image
itself alone, yes?
@skynavga It'd be helpful to know what's driving this request - for example are there users or practitioners who have been in touch with you to complain about this omission? If it's a point of principle alone, I don't disagree that in an ideal world the semantic makes more sense if we could apply forcedDisplay
directly to the image
, but I would also back @palemieux 's thinking that we have a way to achieve the same effect and that making changes to the Image Profile is something we should be super reluctant to do without a strong motive, i.e. I'd also do nothing.
No, there was no external input. This came up during work on TTV support for IMSC1.1 and review of upcoming IMSC1.2 semantics w.r.t. semantic symmetry and consistency.
The Timed Text Working Group just discussed itts:forcedDisplay should apply to image element in image profile imsc#493
, and agreed to the following:
RESOLUTION: We will not address this in IMSC 1.2 but leave on the backlog for potentially fixing in some future version.
itts:forcedDisplay
already applies todiv
so I do not think this is necessary.