The #extent-measure designation includes the value auto.

[palemieux]

The value auto should be removed from #extent-measure since auto is supported in TTML1, and presumably prohibiting #extent-measure is intended to achieve parity with TTML1

[skynavga]

@palemieux the value auto in a measure expression is not the same thing as the value auto for tts:extent. The former is defined in section 10.4.24, while the latter is defined in 10.2.16.

[nigelmegitt]

Specifically with regards to tts:extent a single <measure> is not permitted, so it is syntactically unambiguous whether an auto corresponds to a possible value of <extent> or to one of a pair of <measure>s separated by <lwsp>.

[cconcolato]

That means that auto would not be equivalent to auto auto! One of the auto should probably be renamed to avoid confusion.

[skynavga]

That's correct. I think the best we can do is add a note pointing out this oddity.

…

On Mon, Mar 12, 2018 at 7:52 AM, Cyril Concolato ***@***.***> wrote: That means that auto would not be equivalent to auto auto! One of the auto should probably be renamed to avoid confusion. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#690 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAXCbw3TtiS_WD2yOhXXo3FOlhXP7D2Iks5tdn2ggaJpZM4SfpPk> .

[nigelmegitt]

Tracing through auto and auto auto on tts:extent for each element it can apply to, I think they actually do resolve to the same thing. They wouldn't for tt:tt@tts:extent however auto auto is an illegal value there, so the situation doesn't arise.

[skynavga]

@palemieux @nigelmegitt is any further action required on this issue? if not, then please close

[palemieux]

@skynavga Apologies for the delay. I have been busy with IMSC and TTML1. Will get back to this soon. Is it blocking anything?

[skynavga]

@palemieux no, not blocking at this time

[nigelmegitt]

@palemieux if you are happy to close this, that would be fine for me - I don't believe any action is needed.

[skynavga]

@palemieux ping (see @nigelmegitt comment)

[palemieux]

That's correct. I think the best we can do is add a note pointing out this oddity.

That would be good, and address my concern.

[css-meeting-bot]

The Working Group just discussed The #extent-measure designation includes the value auto. ttml2#690, and agreed to the following:

• RESOLUTION: Add a note as per the comments in the issue.

The full IRC log of that discussion

<nigel> Topic: The #extent-measure designation includes the value auto. ttml2#690
<nigel> github: https://github.com//issues/690
<nigel> Glenn: Looks like Pierre responded...
<nigel> Pierre: Yes, the note would really help. This was caused by the fact that the terms are
<nigel> .. identical but mean something different depending on the context.
<nigel> Glenn: OK
<nigel> RESOLUTION: Add a note as per the comments in the issue.