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

Remove application of tts:unicodeBidi to tt:p element. #1212

Open
nigelmegitt opened this issue Oct 8, 2020 · 4 comments
Open

Remove application of tts:unicodeBidi to tt:p element. #1212

nigelmegitt opened this issue Oct 8, 2020 · 4 comments
Assignees
Labels
agenda i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. substantive

Comments

@nigelmegitt
Copy link
Contributor

Arising from #1211 clarify the application of unicodeBidi and direction on the p element (only).

Suggest matching CSS text direction.

  • direction sets the paragraph embedding level
  • unicodeBidi values plaintext and bidi-override have specific effects
  • other values have no specific effect
@nigelmegitt nigelmegitt added i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. substantive labels Oct 8, 2020
@skynavga skynavga changed the title Clarify application of unicodeBidi and direction on p Remove application of tts:unicodeBidi to tt:p element. Oct 8, 2020
@palemieux
Copy link
Contributor

direction sets the paragraph embedding level

@nigelmegitt To make sure, the idea is that tts:direction sets the paragraph embedding level in addition to potentially altering the inline progression direction per #1213.

unicodeBidi values plaintext and bidi-override have specific effects
other values have no specific effect

@nigelmegitt What is the intent of the above if tts:unicodeBidi does not apply to p?

@nigelmegitt
Copy link
Contributor Author

direction sets the paragraph embedding level

@nigelmegitt To make sure, the idea is that tts:direction sets the paragraph embedding level in addition to potentially altering the inline progression direction per #1213.

Altering the inline progression direction is in addition, but yes, I think this is what we intended.

unicodeBidi values plaintext and bidi-override have specific effects
other values have no specific effect

@nigelmegitt What is the intent of the above if tts:unicodeBidi does not apply to p?

Hmm, I'm not sure about that now. We created this issue jointly during the call and nobody called this out! @fantasai can you recall?

@palemieux
Copy link
Contributor

@nigelmegitt It looks like bidiOverride has an effect on p: https://www.w3.org/TR/css-writing-modes-4/#unicode-bidi

@palemieux
Copy link
Contributor

See discussion at #1214 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda i18n-tracker Group bringing to attention of Internationalization, or tracked by i18n but not needing response. substantive
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants