W3C home > Mailing lists > Public > www-validator@w3.org > October 2022

Re: Ruby RB is no error?

From: Jens Oliver Meiert <jens@meiert.org>
Date: Wed, 05 Oct 2022 09:54:50 +0000
To: www-validator@w3.org, "Jukka K. Korpela" <jukkakk@gmail.com>
Cc: Andreas Prilop <aprilop@freenet.de>
Message-ID: <OCV29KBDxjoo8cTpfF9aO8l4rZNO8GTpxe8cgA5fJJ7kEe8JnGC632BYA4eET663MJndd2Oa0e-DQK0UpRZtVAyf-IvWyLGDjLESBXUpUIc=@meiert.org>
> > This is probably due to https://www.w3.org/TR/ruby/, which specifies this element.
> 
> But why would a W3C recommendation that is over 20 years old affect validation against “living HTML”?

I suppose one could view Ruby similar to SVG and MathML. And yet this case looks odd, because HTML handles Ruby differently—it does not leave it at making only <ruby> an element of the spec, and referring to the Ruby spec for the rest.

(I vaguely recall Ruby was moved to HTML—but I’m not sure. The specs don’t help clear that up.)

For the validator, it doesn’t only accept <rb>, but also <rtc> and <rt>. However, <rbc> itself is invalid. Try with the following snippet:

<!DOCTYPE html>
<title>Ruby Validation Test</title>
<ruby>
  <rbc>
    <rb>Foo
  <rtc>
    <rt>Bar
</ruby>

It would be great if the validator team could look into this, and interesting to learn more about how Ruby exactly relates to HTML.

--
Jens Oliver Meiert
https://meiert.com/en/ · https://twitter.com/j9t
Received on Wednesday, 5 October 2022 09:55:17 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 5 October 2022 09:55:17 UTC