Monthly Archives: May 2021
Updated article: Inline markup and bidirectional text in HTML
An update for the article Inline markup and bidirectional text in HTML has just been published.
This article tells you how to write HTML where text with different writing directions is mixed within a paragraph or other HTML block (ie. inline or phrasal content).
The worked examples and the descriptions of markup have been moved to a new page: Inline bidi markup examples. This and various small edits, including a new set of examples with links to live versions, are intended to make it easier to read the main article and make its advice clearer.
Send any comments via GitHub.
For review: Structural markup and right-to-left text in HTML
The article Structural markup and right-to-left text in HTML is out for wide review. We are looking for comments by Thursday 13 May.
This article looks at ways of handling text direction for structural markup in HTML, ie. at the document level and for elements like paragraphs, tables and forms. The article has been largely rewritten to take into account recent developments in HTML and CSS. A section was added to describe the use of logical properties. The text was make more concise.
Please send any comments as github issues by clicking on this link, or on “Leave a comment” at the bottom of the article. (This will add some useful information to your comment.)
Article published: Can we derive base direction from language?
Sometimes people wonder whether it’s possible to obtain a definitive list of language tags which indicate a RTL base direction, so that there would be no need for separate direction metadata. This article looks into whether that is really feasible. (Spoiler: The W3C Internationalization Working Group believes it is not.)
To comment on this article, raise a GitHub issue.
Article published: Use cases for bidi and language metadata on the Web
Information about text direction and language needs to be associated with strings used on the Web. This article explores use cases that support that need.
To send a comment, raise a GitHub issue.
W3C® liability, trademark and permissive license rules apply.
Questions or comments? firstname.lastname@example.org