- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Mon, 03 Feb 2020 13:21:46 +0000
- To: public-i18n-archive@w3.org
r12a has just created a new issue for https://github.com/w3c/jlreq: == Tabular markup not supported for ruby == The basic pattern of 'tabular' markup is <code>ruby-base ruby-base ... ruby-text ruby-text ...</code>. An advantage to this approach is that it enables you to style the ruby text to appear inline in such a way that all the ruby text for a word follows that word together. Inline styling can be useful in space-constrained situations, where it would be too difficult to read small ruby characters. <a href="https://w3c.github.io/i18n-drafts/articles/ruby/markup.en.html#tabular">Read more</a>. This also makes certain applications of double-sided ruby impossible when the ruby on each side of the base spans a different set of base characters. When text is marked up in mono-ruby way, searching may not work well. If you have the following markup <code><p><ruby>漢<rt>かん</rt>字<rt>じ</rt></ruby></p></code> and search for the base text "漢字" in a browser, you will not get a result. Tabular markup could solve this problem. Only <span class="pass">Firefox</span> supports tabular ruby markup. <span class="fail">Chrome</span>, <span class="fail">Safari</span>, & <span class="fail">legacy Edge</span> do not. See <a href="https://w3c.github.io/i18n-drafts/articles/ruby/markup-data/eg_tabular">a test</a>. See more <a href="https://w3c.github.io/i18n-tests/results/ruby-html">tests for ruby in HTML markup</a></p> <p>For creation of HTML with jukugo ruby this is advanced in impact, however there are other implications when tabular markup is not supported that have a more important impact. Please view or discuss this issue at https://github.com/w3c/jlreq/issues/175 using your GitHub account
Received on Monday, 3 February 2020 13:21:48 UTC