Example Unicode Plane 1 Usage For Business Applications

Demonstrating Unicode Plane 1 (Supplementary) Characters using NCRs

Here are examples of Unicode Plane 1 Characters encoded as Numeric Character References (NCR).
The page Demonstrating Unicode Plane 1 (Supplementary) Characters Encoded in UTF-8 has the same contents and is encoded using UTF-8. You may find that a browser which displays the plane 1 characters correctly in one page, may not work with the other.

Due to limitations of browsers and operating systems not yet supporting Unicode supplementary characters, the examples for plane 1 are on this page, separate from the Plane 0 (BMP) Unicode example page.

The table displays well on IE 5.5, Mozilla 1.3, Netscape 7.1 and Opera 6 and later versions. (Presuming you have appropriate fonts and your system is configured to support supplementary characters. See the notes after the table.)

Instructions for displaying this page
To display Unicode plane 1 characters, the following has to be done:

• You will need to have appropriate fonts.
  James Kass' CODE2001 font works well and supports all the scripts but Osmanya, and is easy to install.
  For Osmanya, you can use Mark Williamson's ANDAGII font.
  For Linear B, you can use Mark Williamson's PENUTURESU font.
• You can use Microsoft IE 5.0 or later. IE wants plane 1 characters as HTML Numeric Character References (NCRs) (either decimal or hex is ok) to encode the characters, instead of native UTF-8. Or,
• You can use the Opera 6 browser. Opera doesn't care if the text is composed of NCRs or UTF-8 encoded characters.
• The page must be viewed on IE as "User-defined" encoding, not "UTF-8" encoding. To display the page, set the Internet Explorer's encoding manually to "user-defined".
  
  This HTML page is labeled with charset "x-user-defined" not "UTF-8". This is done with the HTML statement:
  <META http-equiv="Content-Type" content="text/html; charset=x-user-defined">
  However, the page is being served by HTTP with charset="UTF-8", so browsers that respect HTTP charset taking precedence over the page setting (as the standard calls for) will interpret the page as UTF-8.
• On Windows NT, 2000, and XP you need to enable support for surrogate code points, to view this page. Instructions to enable surrogates are at Setting Up Microsoft Windows Nt, 2000 Or Windows Xp To Support Unicode Supplementary Characters

Contributor notes
For more info on Etruscan, see: http://www.bdp.it/parco/percorsi/percorso9/ido_labalf.htm

Here are interesting comments on the table's Etruscan text from Marco Cimarosti:

"...the glyphs in James' font are designed for right-to-left display (which is historically correct), but Unicode's old Italic letters are LTR, which is historically not very correct)."

(Note from Tex, 2002年07月12日: This is addressed in the table by using the HTML <BDO> markup, as recommended by both Unicode and W3C consortia.)

Marco continues: Compare the result with the original inscription on the statue: http://www.bdp.it/parco/percorsi/percorso9/immagini/etruscan/ido_aulesin.jpg
The only tiny differences are in the shape of A, T and U -- but these are legitimate font variations.

Finally, a small linguistic note: scholars say that the name is in the dative case, so it actually means "to/for Aulus Metellus" (*). According to Etruscan grammars, this can be turned to nominative by removing the "-s'i" and "-s'" endings: "*Aule *Meteli". But I would not dare to do this, because Etruscan grammars are mostly speculations, and no one can be sure that this particular person's name had a regular declension. This is especially true for the surname (as "Aule" or "Avle" is actually attested in the nominative).

The meaning of the whole inscription is:
"To [the memory of] Aulus Metellus, son of Vel and Vesi, Tenine erected this statue as a votive offer, by will of the people"