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.

Sign up for GitHub

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

Jump to bottom

Informative text on text direction handling #1753

Closed
egekorkan opened this issue Dec 1, 2022 · 0 comments · Fixed by #2026
Closed

Informative text on text direction handling #1753

egekorkan opened this issue Dec 1, 2022 · 0 comments · Fixed by #2026
Assignees
@egekorkan
Labels
Defer to TD 2.0 Editorial Issues with no technical impact on implementations Human Readability

Comments

@egekorkan
Copy link
Contributor

As suggested in yesterday's call, it would be nice to explain text direction handling informatively with a list as well (in addition to assertions):

  • String-specific metadata (we will not have it until T2.0)
  • File-level metadata (currently the @direction and @language)
  • (optional) guess from language
  • first-strong (i.e. using dir=auto in HTML or FSI/PDI controls around the string)
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Dec 1, 2022
@egekorkan egekorkan added Human Readability by REC publication and removed needs-triage Automatically added to new issues. TF should triage them with proper labels labels Dec 7, 2022
@mjkoster mjkoster added the Editorial Issues with no technical impact on implementations label Feb 8, 2024
@egekorkan egekorkan self-assigned this May 8, 2024
@egekorkan egekorkan mentioned this issue May 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@egekorkan egekorkan

Labels
Defer to TD 2.0 Editorial Issues with no technical impact on implementations Human Readability
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Informative steps to implement text direction parsing in Consumers w3c/wot-thing-description
2 participants
@mjkoster @egekorkan