Skip to content
This repository has been archived by the owner on Oct 9, 2023. It is now read-only.

Ruby clarification on specs #4

Open
r12a opened this issue Aug 21, 2015 · 3 comments
Open

Ruby clarification on specs #4

r12a opened this issue Aug 21, 2015 · 3 comments
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.

Comments

@r12a
Copy link

r12a commented Aug 21, 2015

http://www.w3.org/TR/2015/WD-dpub-css-priorities-20150820/#ruby

issue 18 asks whether the spec is stable, but there are two specs for ruby support: the HTML5 spec, which handles the markup and for which browsers tend to provide basic positioning by default, and the CSS ruby spec, which provides fine control over the display. Issue 18 should make it clear that there are more than one spec involved.

for HTML, you can find information about implementation support at
http://www.w3.org/International/tests/repo/results/ruby-html

@r12a r12a added the i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on. label Jul 21, 2016
@r12a
Copy link
Author

r12a commented Jul 21, 2016

fwiw, there's also a new article available from i18n WG:

Ruby Markup
https://www.w3.org/International/articles/ruby/markup

there's another in development

Ruby Styling (draft!)
https://w3c.github.io/i18n-drafts/articles/ruby/styling.en

@xfq
Copy link
Member

xfq commented Mar 27, 2020

Here are more tests for ruby:

The most prominent issues are the lack of bopomofo ruby support, tabular markup support, and ruby alignment (and other styling) support. The relevant HTML and CSS standards are relatively mature, but some text is not clear enough or not interoperable, and some requirements in Chinese/Japanese are not written into the specs yet. I'm happy to contribute some text to this section if needed.

@himorin
Copy link

himorin commented Jan 29, 2021

Note: W3C i18n WG closed our tracker that we've noticed target document of this issue no longer maintained, and is ok to close this issue.
(please not remove i18n-needs-resolution label which is used by our bot and tracking system)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
i18n-needs-resolution Issue the Internationalization Group has raised and looks for a response on.
Projects
None yet
Development

No branches or pull requests

3 participants