Rp (Ruby Parenthesis)

Support Key: [2|3|3.2|4] [X1|X1.1] [IE5B2|M|N|O]
What is it?
Tag Example
Parent/Content Model
Tips & Tricks
Browser Peculiarities
= Index DOT Html by Brian Wilson =
Main Index | Element Tree | Element Index | HTML Support History

   Quick Statistics   
End Tag:
Standards Details:
Support beginning in XHTML 1.1 DTD.
XHTML Modules:
CSS 'display' Type:
CSS Mapping:
Default Rendering:
Content ignored if element understood
Official Docs:
XHTML 1.1: Ruby Module

What is it?
A Ruby is part of an annotation pair - a piece of text ("Ruby Text") that is associated with another piece of text known as a "Ruby Base". A common need for such a structure arises in some asian writing systems where a ruby association is used to present helper readings for uncommonly used writing characters.

With a character set as complex as Chinese or Japanese, some characters are used rarely and are thus not as easily recognizable by younger children or possibly many adults. In Japanese writing, for example, the phonetic Hiragana alphabet is used to pair phonetic 'helper' readings (called Furigana or Yomigana in Japanese) with the Chinese character counterpart.

A Ruby text will usually be rendered next to the Base text such that the association between each Base text and Ruby text is clear (often directly above the Base text.) Ruby text is usually also rendered in a smaller font than the Base text to help visually clarify which part is which in the association relationship.

The RP element is a fall-back mechanism for browsers that do not understand the Simple Ruby syntax. It should not be used in Complex Ruby markup. The element semantically denotes content that will be used to clarify the association between a simple RB/RT relationship. Content within the RP element is hidden from browsers that support RUBY, for the express purpose of allowing the insertion of delimiters surrounding RT content to make the RB/RT relationship clear in non-supporting browsers. Although RP stands for Ruby Parenthesis, any characters could be used as RP content, as long as they assist in making this relationship clear.

Simple Rubies
Simple Rubies will often be the only type of annotation mechanism that most authors need. In this type of ruby markup, two main elements exist nested in the RUBY element - the Base text (the RB element), followed by the Ruby text (the RT element.)

For browsers that do not understand the RUBY markup, they will display the content of the RT element directly following the contents of the RB content. Since this sort of fallback may not be enough to distinguish the association relationship between the two content pieces, one final, optional fallback element is provided to make the association clear in non-supporting browser scenarios: the RP element. An RP element containing a single character (usually an open or close parenthesis, depending on the context - RP DOES stand for Ruby Parenthesis...) should be put on either side of the RT element. Ruby-supporting browsers should ignore the RP element completely and not render it in any way; in non-supporting browsers however, the contents of the RP element will surround the RT content to tie the content with the previous RB content.

Common Attributes
[2|3|3.2|4] [X1|X1.1] [IE5B2|M|N|O]
[2|3|3.2|4] [X1|X1.1] [IE|M|N|O]
[2|3|3.2|4] [X1|X1.1] [IE|M|N|O]
[2|3|3.2|4] [X1|X1.1] [IE|M|N|O]
Simple Ruby example:
   <rp>(</rp> <rt>HyperText Markup Language</rt> <rp>)</rp>
Parent Model
Content Model
Tips & Tricks Browser Peculiarities
Boring Copyright Stuff...