Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling non-kana text for rubyAlign with spaceAround or spaceBetween #320

Closed
r12a opened this issue Feb 8, 2017 · 8 comments
Closed

Handling non-kana text for rubyAlign with spaceAround or spaceBetween #320

r12a opened this issue Feb 8, 2017 · 8 comments
Labels
recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. s:ttml https://w3c.github.io/ttml2/ wg:timed-text https://www.w3.org/groups/wg/timed-text

Comments

@r12a
Copy link
Contributor

r12a commented Feb 8, 2017

§ w3c/ttml2#251

@r12a r12a added pending Issue not yet sent to WG, or raised by tracker tool & needing labels. s:ttml https://w3c.github.io/ttml2/ labels Feb 8, 2017
@r12a r12a removed the pending Issue not yet sent to WG, or raised by tracker tool & needing labels. label Feb 16, 2017
@r12a
Copy link
Contributor Author

r12a commented Feb 14, 2018

discussion ongoing...

@r12a
Copy link
Contributor Author

r12a commented Oct 9, 2018

The TTML WG conclusion was:

We will create tests to verify this behaviour and will be open to implementation feedback based on the results of those tests during CR.

That would mean that for spaceBetween you'd see

|j a y  c h o u|

rather than

|jay    chou| 

I have requested information about what feedback was received during CR.

My expectation is that people working with pinyin (or, i suppose, other word-separated writing systems) will normally use the centre value, rather than spaceBetween or spaceAround, so this may be a non-issue.

@r12a r12a added close? The related issue was closed by the Group but open here recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. labels Oct 9, 2018
@KatyMawhood
Copy link

Since @r12a appears happy with the conclusion of the TTML WG, I propose to close this issue.

@r12a r12a removed the close? The related issue was closed by the Group but open here label Apr 4, 2019
@r12a r12a closed this as completed Apr 4, 2019
@r12a
Copy link
Contributor Author

r12a commented Apr 4, 2019

Bring this up again for the next version of the spec.

@KatyMawhood
Copy link

@r12a Is there a basic timeline for spec versions that we can use as a prompt?

@aphillips
Copy link
Contributor

@KatyMawhood Except in exceptional cases (cough CSS cough) there usually isn't a pre-determined next version. But any next version of a spec will become visible to us at FPWD. That would seem to be a logical place to review any holdovers?

@KatyMawhood
Copy link

Sounds like this is already set up via the recycle label. :)

@r12a
Copy link
Contributor Author

r12a commented Apr 11, 2019

Indeed. That's what that label is for.

@w3cbot w3cbot added the wg:timed-text https://www.w3.org/groups/wg/timed-text label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
recycle Attach to closed items where the issue needs to be ressurected for a next version of the spec. s:ttml https://w3c.github.io/ttml2/ wg:timed-text https://www.w3.org/groups/wg/timed-text
Projects
None yet
Development

No branches or pull requests

4 participants