- From: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
- Date: Fri, 5 Jul 2013 10:55:45 +0900
- To: "Phillips, Addison" <addison@lab126.com>
- Cc: "www-international@w3.org" <www-international@w3.org>
>When we refer here to fallback, we mean what happens when a browser >doesn't support ruby. If a browser doesn't support ruby, the content of the > ruby element will be produced as ordinary characters, in the order in which >they appear inside the ruby element. I have a comment on the above paragraph in the draft. Some browsers do now know anything about <ruby> and other tags, and they just handle their contents while ignoring start and end tags. Other browsers know these tags and they provide ruby formatting. So far so good. But I can imagine that yet other browsers know these tags but do not provide ruby formatting. Rather, they just put an open parenthesis, ruby text, and a close parenthesis as text after the ruby base. I would say that such browsers also do "fallback". How about "ruby-aware fallback" and "ruby-unaware fallback"? Regards, Makoto 2013/6/3 Phillips, Addison <addison@lab126.com>: > The Internationalization Working Group is preparing [1] to publish a new "Note" status document "Use Cases & Exploratory Approaches for Ruby Markup". This email serves as a "Last Call" for comments on the document. > > The current draft is located here: > > http://www.w3.org/International/docs/ruby/ > > This document was designed to support discussion about what is needed in the HTML5 specification, and possibly other markup vocabularies, to adequately support ruby markup. It describes a number of use cases associated with ruby usage, and then examines a number of possible ruby markup approaches for each use case, listing pros and cons for each approach. > > Please send any comments to this list (www-international@w3.org) as soon as possible. This last call ends 12 June 2013. > > Addison > > [1] http://www.w3.org/2013/05/30-i18n-minutes.html#item06 > [2] http://www.w3.org/International/track/actions/230 > > Addison Phillips > Globalization Architect (Amazon Lab126) > Chair (W3C I18N WG) > > Internationalization is not a feature. > It is an architecture. >
Received on Friday, 5 July 2013 01:56:11 UTC