- From: Robin Berjon <robin@w3.org>
- Date: Fri, 06 Sep 2013 12:56:18 +0200
- To: public-digipub-ig-comment@w3.org
- CC: Richard Ishida <ishida@w3.org>
[Ivan kindly pointed out to me that I'd used the wrong list for this, so
reposting. Sorry, for those of you who are seeing this twice. You can
see the discussion thread at
http://lists.w3.org/Archives/Public/public-digipub/2013Sep/thread.html]
Dear all,
I was perusing the report from the eBooks & i18n workshop[0] that took
place in Tokyo last June and I noticed that Ruby support rated close to
as high as it possibly could.
One thing that it does not clearly state however is which features from
ruby are needed, or at what level of priority.
The current HTML5 specification does have some support for Ruby[1], but
some concerns have been raised about limitations in its support for a
number of features, notably jukugo and double-sided ruby, as well as
inline ruby.
As a result of those concerns, I have put together a specification that
is aimed at replacing the current HTML5 Ruby support in order to add
those features. You can read it at:
http://darobin.github.io/html-ruby/
At this stage, several implementers have expressed interest, but they
are unsure as to how much interest there is in the feature. So in order
to make progress in pushing this forward (or, on the contrary, to simply
drop it if there isn't enough support for it) it would be most useful to
benefit from the digital publishing community's feedback in this area as
I believe you are likely to have strong and informed opinions on the topic.
Thanks a lot!
[0] https://www.w3.org/2013/06/ebooks/report.php
[1]
http://www.w3.org/html/wg/drafts/html/master/text-level-semantics.html#the-ruby-element
--
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Friday, 6 September 2013 10:56:26 UTC