--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ 13¾ð·ÐÂè1154¹æ¡Ë Êó¹ð½ñ </TITLE>
+<META NAME="description" CONTENT="2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ 13¾ð·ÐÂè1154¹æ¡Ë Êó¹ð½ñ ">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node1.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html30"
+ HREF="node1.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up_g.png">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev_g.png">
+<BR>
+<B> Next:</B> <A NAME="tex2html31"
+ HREF="node1.html">ÌÜŪ</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+
+<P>
+<H1 ALIGN="CENTER"><FONT SIZE="+2">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È</FONT>
+<BR> <BR>
+<BR>
+ ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯
+<BR> ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ
+<BR> <FONT SIZE="+1">¡Ê·ÀÌóÈÖ¹æ 13¾ð·ÐÂè1154¹æ¡Ë
+<BR>
+<BR></FONT>
+<BR> Êó¹ð½ñ
+<BR> <BR>
+<BR>
+<BR>
+<BR></H1>
+<P ALIGN="CENTER"><STRONG>³«È¯¼Ô¡§¼é²¬ ÃÎɧ, Christian Wittern</STRONG></P>
+
+<P>
+
+<P>
+
+<P>
+<BR><HR>
+<!--Table of Child-Links-->
+<A NAME="CHILD_LINKS"></A>
+
+<UL>
+<LI><A NAME="tex2html32"
+ HREF="node1.html">ÌÜŪ</A>
+<LI><A NAME="tex2html33"
+ HREF="node2.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</A>
+<LI><A NAME="tex2html34"
+ HREF="node3.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</A>
+<LI><A NAME="tex2html35"
+ HREF="node4.html">ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<LI><A NAME="tex2html36"
+ HREF="node5.html">Topic Maps ¤Ë´ð¤Å¤¯Âç°èʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<LI><A NAME="tex2html37"
+ HREF="node6.html">ʸ½ñÊÔ½¸·Ï¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÅý¹ç</A>
+<LI><A NAME="tex2html38"
+ HREF="node7.html">Bibliography</A>
+<!-- <LI><A NAME="tex2html39" -->
+<!-- HREF="node8.html">About this document ...</A> -->
+</UL>
+<!--End of Table of Child-Links-->
+<BR><HR>
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>ÌÜŪ</TITLE>
+<META NAME="description" CONTENT="ÌÜŪ">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node2.html">
+<LINK REL="previous" HREF="main.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node2.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html48"
+ HREF="node2.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html46"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html40"
+ HREF="main.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html49"
+ HREF="node2.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</A>
+<B> Up:</B> <A NAME="tex2html47"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html41"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+
+<H1><A NAME="SECTION00100000000000000000">
+ÌÜŪ</A>
+</H1>
+
+<P>
+¼¡À¤Âå¤Î¿¸À¸ìʸ½ñ½èÍýµ»½Ñ¤Î´ðÁäȤ·¤Æ¡¢Ê¸»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»ú¥ª
+¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤ò¸¦µæ¡¦³«È¯¤¹¤ë¡£¤³¤ÎÌÜŪ¤Î¤¿¤á¤Ë¡¢¸Ä¿ÍÍÑ¡¢¥µ¥¤¥ÈÍÑ¡¢¥¤
+¥ó¥¿¡¼¥Í¥Ã¥ÈÍѤÎʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥·¥¹¥Æ¥à¤È¤½¤Î¥³¥ó¥Æ¥ó¥Ä¡¢¤ª¤è¤Ó¡¢¤³
+¤ì¤é¤òÍѤ¤¤ë¥¯¥é¥¤¥¢¥ó¥È¡¦¥·¥¹¥Æ¥à¤ò³«È¯¤¹¤ë¡£
+
+<P>
+·×»»µ¡¤Ë¤ª¤±¤ëʸ»úɽ¸½µ»½Ñ¤Ï·×»»µ¡¤Ë¤ª¤±¤ë¤µ¤Þ¤¶¤Þ¤Ê¥Ç¡¼¥¿É½¸½¤Î´ðÈפÇ
+¤¢¤ê¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ë¤ª¤±¤ë¿ºÌ¤Ê¥³¥ó¥Æ¥ó¥Ä¤âʸ»úɽ¸½µ»½Ñ¤Ë°Í¤Ã¤Æ¤¤¤ë¡£
+¸½ºß¡¢·×»»µ¡¤Ë¤ª¤±¤ëʸ»úɽ¸½¤Ï¤¹¤Ù¤ÆÉä¹æ²½Ê¸»úµ»½Ñ¤Ë´ð¤Å¤¤¤Æ¤¤¤ë¡£¤³¤ì
+¤Ïʸ»ú¤òÂбþ¤¹¤ëÈÖ¹æ¤Çɽ¸½¤¹¤ëÊýË¡¤Ç¤¢¤ë¡£
+
+<P>
+¤³¤ÎÊýË¡¤Ç¤Ïʸ»ú¤ÈÈÖ¹æ¤ÎÂбþµ¬Â§¤Ç¤¢¤ëÉä¹æ²½Ê¸»ú½¸¹ç¡Êʸ»úÉä¹æ¡Ë¤òξ¼Ô
+¤¬¶¦Í¤·¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¡£¤µ¤â¤Ê¤¯¤Ðʸ»ú²½¤±¤¬À¸¤¸¤ë¡£¤Þ¤¿¡¢Éä¹æ²½Ê¸»ú
+½¸¹ç¤Ë´Þ¤Þ¤ì¤ëʸ»ú¤Ï͸¤Ǥ¢¤ê¡¢¤½¤³¤Ë¸ºß¤·¤Ê¤¤Ê¸»ú¤Ïɽ¸½¤Ç¤¤Ê¤¤¡£¤³
+¤Î¤¿¤á¡¢½¾Íè¡¢¸ò´¹²ÄǽÀ¤ò¤¢¤¤é¤á¤Æ³°»ú¤òÍѤ¤¤ëÊýË¡¤ä¡¢¸¡º÷¤Ê¤É¤ÎÉä¹æ
+²½Ê¸»ú¤È¤·¤Æ¤ÎÍøÊØÀ¤ò¤¢¤¤é¤á¤Æ²èÁü¤òÍѤ¤¤ëÊýË¡¤¬ºÎ¤é¤ì¤Æ¤¤¿¡£¤Þ¤¿¡¢
+¤³¤¦¤·¤¿ÌäÂê¤òÈò¤±¤ë¤¿¤á¤Ë¡¢Ê¸»úÉä¹æ¤Îµ¬³Ê¤Ë¿¿ô¤Îʸ»ú¤ÎÄɲäò¹Ô¤¦Æ°¤
+¤â¤¢¤ë¤¬¡¢¤³¤ì¤Ë¤âµ»½ÑŪ¡¦À¯¼£ÅªÌäÂ꤬¤¢¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤ÊÌäÂê¤òÈ´ËÜŪ¤Ë²ò·è¤·¡¢Æü¾ïŪ¤Êʸ½ñ¤Î¤ß¤Ê¤é¤ºÎò»ËŪ¤Êʸ½ñ¤ä¾
+ÍèÀ¸¤¸¤ëʸ½ñ¤âɽ¸½²Äǽ¤Ç¡¢¤«¤Ä¡¢³Æʸ½ñ¤Î±Ê³À¤òÊݾڤ¹¤ë¤¿¤á¤Ë¤Ï¡¢Éä¹æ
+²½Ê¸»ú½¸¹ç¤Ë°Í¸¤·¤Ê¤¤¼¡À¤Âå¤Î¿¸À¸ìʸ½ñ½èÍýµ»½Ñ¤Î³ÎΩ¤¬É¬ÍפǤ¢¤ë¤È¹Í
+¤¨¤ë¡£
+
+<P>
+¤³¤Î¤¿¤á¤Ë¤Ïʸ½ñɽ¸½¤Ë¤ª¤±¤ë¤¢¤é¤æ¤ëÍ×ÁǤòµ¡³£²ÄÆɤÊÊýË¡¤ÇÀë¸ÀŪ¤Ëµ½Ò
+²Äǽ¤Ë¤¹¤ëɬÍפ¬¤¢¤ë¡£¤¹¤Ç¤Ë¡¢Ê¸»ú¤è¤êÂ礤Êñ°Ì¤ÎÍ×ÁǤËÂФ·¤Æ¤Ï¡¢
+SGML/XML ¤Ê¤É¤Ë¤â¤È¤Å¤¯¥Þ¡¼¥¯¥¢¥Ã¥×¼êË¡¤¬ÍѤ¤¤é¤ì¤Æ¤¤¤ë¡£¤½¤³¤Ç¡¢²æ¡¹
+¤Ïʸ»ú¤ËÂФ·¤ÆƱÍͤμêË¡¤ò»î¤ß¤Æ¤¤¤ë¡£
+
+<P>
+ʸ»ú¤Îµ¡³£²ÄÆɤʵ½Ò¤Ë´ð¤Å¤¯¼¡À¤Âåʸ½ñ½èÍýµ»½Ñ¤ò³ÎΩ¤·¡¢¼ÂÍѲ½¤¹¤ë¤¿¤á
+¤Ë¤ÏÈÆÍÑŪ¤Êʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥·¥¹¥Æ¥à¤ª¤è¤Ó¥¯¥é¥¤¥¢¥ó¥È¡¦¥·¥¹¥Æ¥à¤Î¸ú
+ΨŪ¤Ê¼Â¸½¤¬·ç¤«¤»¤Ê¤¤¡£¤Þ¤¿¡¢¤³¤ì¤é¤Î¾å¤ÇÍøÍѲÄǽ¤Êʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î
+¥³¥ó¥Æ¥ó¥Ä¤â¤Ê¤¯¤Æ¤Ï¤Ê¤é¤Ê¤¤¡£
+
+<P>
+¥¤¥ó¥¿¡¼¥Í¥Ã¥È¤Ç¤ÎÉáµÚ¤ò¹Í¤¨¤ë¤Ê¤é¤Ð¡¢¤³¤¦¤·¤¿µ»½Ñ¤Î¾¯¤Ê¤¯¤È¤âÃæ³Ë¤Ï¼«
+ͳ¤ËÍøÍѲÄǽ¤Ê¥×¥í¥°¥é¥à¤È¥Ç¡¼¥¿¤Ç¹½À®¤µ¤ì¤ëɬÍפ¬¤¢¤ë¡£¤è¤Ã¤Æ¡¢¼«Í³¥½
+¥Õ¥È¥¦¥§¥¢¡¦¥Ç¡¼¥¿¤ò³èÍѤ·¡¢´õ˾¤¹¤ë¤â¤Î¤¬¼«Í³¤ËÍøÍѤ·¤¿¤ê³«È¯¤Ë»²²Ã¤Ç
+¤¤ë¤è¤¦¤Ê·Á¤Ç¥×¥í¥¸¥§¥¯¥È¤ò¹Ô¤¦¡£
+
+<P>
+<BR><HR>
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</TITLE>
+<META NAME="description" CONTENT="ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node3.html">
+<LINK REL="previous" HREF="node1.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node3.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html58"
+ HREF="node3.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html56"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html50"
+ HREF="node1.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html59"
+ HREF="node3.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</A>
+<B> Up:</B> <A NAME="tex2html57"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html51"
+ HREF="node1.html">ÌÜŪ</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+<!--Table of Child-Links-->
+<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
+
+<UL>
+<LI><A NAME="tex2html60"
+ HREF="#SECTION00210000000000000000">½¾Íè¤Îʸ»úɽ¸½¤ÎÆÃħ¤ÈÌäÂêÅÀ</A>
+<LI><A NAME="tex2html61"
+ HREF="#SECTION00220000000000000000">Éä¹æ²½Ê¸»ú½¸¹ç¤Ë°Í¸¤·¤Ê¤¤Ê¸»úɽ¸½¤Ø</A>
+</UL>
+<!--End of Table of Child-Links-->
+<HR>
+
+<H1><A NAME="SECTION00200000000000000000">
+ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</A>
+</H1>
+
+<P>
+
+<H1><A NAME="SECTION00210000000000000000">
+½¾Íè¤Îʸ»úɽ¸½¤ÎÆÃħ¤ÈÌäÂêÅÀ</A>
+</H1>
+
+<P>
+
+<H2><A NAME="SECTION00211000000000000000">
+Éä¹æ²½Ê¸»ú¥â¥Ç¥ë</A>
+</H2>
+
+<P>
+¸½ºß¡¢Â¿¤¯¤Îʸ»ú½èÍý·Ï¤Ç¤Ï¡¢Ê¸»ú¤½¤Î¤â¤Î¤ò°·¤¦Âå¤ï¤ê¤Ë¡¢Ê¸»ú¤Ë¸ÇͤÎÈÖ
+¹æ¤ò¿¶¤Ã¤Æ¡¢¤½¤ÎÈÖ¹æ¤Çʸ»ú¤òɽ¤¹¼êË¡¤òÍѤ¤¤Æ¤¤¤ë¡£¤³¤³¤Ç¡¢Ê¸»ú¤ÈÈÖ¹æ¤Î
+Âбþµ¬Â§¤ò¡ÖÉä¹æ²½Ê¸»ú½¸¹ç¡×(Coded Character Set; CCS) ¤â¤·¤¯¤Ï¡Öʸ»ú
+Éä¹æ¡×(character code) ¤È¸Æ¤Ó¡¢Ê¸»ú¤Ë¿¶¤é¤ì¤¿ÈÖ¹æ¤ò¡ÖÉä¹æ°ÌÃÖ¡×(code
+point) ¤È¸Æ¤Ö¡£¤Þ¤¿¡¢¤³¤Î¤è¤¦¤Ë¡¢Í¸Â¤Îʸ»ú¤Î½¸¹ç¤òÄê¤á¡¢³Æʸ»ú¤Ë¸ÇÍ
+¤ÎÈÖ¹æ¤ò¿¶¤ê¤½¤ÎÈÖ¹æ¤Çʸ»ú¤òɽ¸½¤¹¤ë¼êË¡¤Î¤³¤È¤ò¡¢¤³¤³¤Ç¤Ï¡ØÉä¹æ²½Ê¸»ú
+¥â¥Ç¥ë¡Ù¤È¸Æ¤Ö¤³¤È¤Ë¤¹¤ë¡£
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="fig:coded-char-model"></A><A NAME="98"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 2.1:</STRONG>
+Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Î³µÇ°¿Þ</CAPTION>
+<TR><TD>
+<DIV ALIGN="CENTER">
+<!-- MATH
+ $\scalebox{0.5}{\includegraphics*[0mm,15mm][300mm,155mm]{char-code.eps}}$
+ -->
+<IMG
+ WIDTH="609" HEIGHT="318" ALIGN="BOTTOM" BORDER="0"
+ SRC="img1.png"
+ ALT="\scalebox{0.5}{\includegraphics*[0mm,15mm][300mm,155mm]{char-code.eps}}">
+ <BR>
+</DIV></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+¿Þ <A HREF="node2.html#fig:coded-char-model">2.1.1</A>¤Ë¼¨¤¹¤è¤¦¤Ë¡¢Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Ç¤Ïʸ»ú¤Ï
+ʸ»ú¤Ë¿¶¤é¤ì¤¿ÈÖ¹æ¤Çɽ¸½¤µ¤ì¤ë¡£Ê¸»ú¤Ë´Ø¤¹¤ëÃ챤ÏÉä¹æ²½Ê¸»ú½¸¹ç¤ÎÄêµÁ
+¤ÎÃæ¤Ë¸ºß¤·¡¢Ä̾·×»»µ¡¤ÎÃæ¤Ë¤Ï¸ºß¤·¤Ê¤¤¡£¤³¤Î¤¿¤á¡¢·×»»µ¡¤Ï¾¯¤Ê¤¤
+µ²±Î̤Çʸ»ú¤òɽ¸½¤Ç¤¤ëȾÌÌ¡¢·×»»µ¡¤¬°·¤¦¤³¤È¤¬¤Ç¤¤ëʸ»ú¤Î¼ïÎà¤äʸ»ú
+¤Î³µÇ°¤ÏÉä¹æ²½Ê¸»ú½¸¹ç¤ÎÄêµÁ¤Ë«Çû¤µ¤ì¤ë¡£
+
+<P>
+Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Ë´ð¤Å¤¤¤ÆÄÌ¿®¤ò¹Ô¤Ê¤¦¾ì¹ç¡¢Á÷¿®¼Ô¤È¼õ¿®¼Ô¤Ïʸ»ú¤ÈÈÖ¹æ
+¤ÎÂбþµ¬Â§¤Ç¤¢¤ëʸ»úÉä¹æ¤ò¶¦Í¤·¤Æ¤¤¤ëɬÍפ¬¤¢¤ë¡£¤µ¤â¤Ê¤¯¤Ðʸ»ú²½¤±¤¬
+À¸¤¸¤ë¡£¤¢¤ëʸ»úÉä¹ç¤Çɽ¸½¤Ç¤¤Ê¤¤Ê¸»ú¤¬Â¸ºß¤·¤¿¾ì¹ç¡¢Î¾¼Ô¤¬¹ç°Õ¤·¤ÆÄÌ
+¿®¼ê½ç¤ÇÍѤ¤¤ëʸ»úÉä¹ç¤ò³ÈÄ¥¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£¤·¤«¤·¡¢¥¤¥ó¥¿¡¼¥Í¥Ã¥È
+¤Î¤è¤¦¤ÊÉÔÆÃÄê¿¿ô¤¬»²²Ã¤·¤µ¤Þ¤¶¤Þ¤Ê¼ïÎà¤Îµ¡ºà¤¬Â¸ºß¤¹¤ë¤è¤¦¤ÊÂ絬Ìϳ«
+Êü¥·¥¹¥Æ¥à¤ÇÍѤ¤¤é¤ì¤ëɸ½àŪ¤Êʸ»úÉä¹ç¤ò³ÈÄ¥¤¹¤ë¤³¤È¤Ï¶Ë¤á¤Æº¤Æñ¤Ç¤¢¤ë
+¤È¤¤¤¨¤ë¡£
+
+<P>
+¤³¤Î¤¿¤á¡¢¸½¼ÂŪ¤ÊÊýºö¤È¤·¤Æ¡¢½¾Íè¡¢¸ò´¹²ÄǽÀ¤ò¤¢¤¤é¤á¤Æ³°»ú¤òÍѤ¤¤ë
+ÊýË¡¤ä¡¢¸¡º÷¤Ê¤É¤ÎÉä¹æ²½Ê¸»ú¤È¤·¤Æ¤ÎÍøÊØÀ¤ò¤¢¤¤é¤á¤Æ²èÁü¤òÍѤ¤¤ëÊýË¡
+¤¬ºÎ¤é¤ì¤Æ¤¤¿¡£¤Þ¤¿¡¢¹ñºÝŪ¤Êɸ½àÉä¹ç¤È¤·¤Æ ISO/IEC 10646
+(UCS)/Unicode ¤ò de jure/de fact standard ¤È¤·¤ÆÀ©Äꤷ¡¢¤³¤ì¤òÁ´À¤³¦¤Ç
+¶¦Í¤·¡¢¤Þ¤¿¡¢¤³¤ì¤ò³ÈÄ¥¤¹¤ë¤³¤È¤Ë¤è¤ê¤³¤ÎÌäÂê¤ò²ò·è¤·¤è¤¦¤È¤¹¤ëÅØÎϤ¬
+³¤±¤é¤ì¤Æ¤¤¤ë¤¬¡¢¤³¤ì¤Ë¤âµ»½ÑŪ¡¦À¯¼£ÅªÌäÂ꤬¤¢¤êÍưפǤϤʤ¤¡£
+<A NAME="tex2html2"
+ HREF="footnode.html#foot102"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+<P>
+
+<H2><A NAME="SECTION00212000000000000000">
+Éä¹ç³Èĥˡ ¡½ Mule Êý¼°</A>
+</H2>
+
+<P>
+Á°½Ò¤Î¤è¤¦¤Ë¡¢Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Ç¤Ï¡¢¡ÖÀ¤¤ÎÃæ¤Ë¸ºß¤¹¤ë¤µ¤Þ¤¶¤Þ¤Êʸ»ú¡×
+¤È¡ÖÉä¹æ²½¤µ¤ìÉä¹æ°ÌÃ֤Ȥ¤¤¦ÈÖ¹æ¤ò¿¶¤é¤ì¤¿Ê¸»ú¡×¤Î´Ö¤Î´Ø·¸¤Ï¡¢Éä¹æ²½Ê¸
+»ú½¸¹ç¤Ë¤è¤Ã¤ÆÄêµÁ¤µ¤ì¤Æ¤¤¤ë¡£¤³¤Î¹Í¤¨Êý¤Ç¤Ï¡¢Ê¸»ú¤Î»ý¤Ä¤¤¤í¤¤¤í¤ÊÀ¼Á
+¤Ï¸Ä¡¹¤Îʸ»ú¤Ç¤Ï¤Ê¤¯Éä¹æ²½Ê¸»ú½¸¹ç¤¬»ý¤Ä¤³¤È¤òÁ°Äó¤È¤·¤Æ¤¤¤ë¡£¤Þ¤¿¡¢¤µ
+¤é¤Ë¡¢¤½¤ì¤¾¤ì¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤¬»÷¤¿À¼Á¤Îʸ»ú¤Î½¸¹ç¤Ç¤¢¤ê¡¢ÆÃÄê¤ÎÍÑ»ú
+·Ï (script) ¤ä¸À¸ì¤ÇÍѤ¤¤ëʸ»ú¤Î½¸¹ç¤Ç¤¢¤ë¤È²¾Äê¤Ç¤¤ë¤Ê¤é¤Ð¡¢Éä¹æ²½
+ʸ»ú½¸¹ç¤Î¼ïÎà¤òÆÃÄꤹ¤ë¤³¤È¤Ë¤è¤ê¡¢ÍÑ»ú·Ï¤ä¸À¸ì¤òÆÃÄê¤Ç¤¤ë¤È¤¤¤¨¤ë¡£
+
+<P>
+¤³¤Î²¾Ä꤬¤Ê¤ê¤¿¤Ã¤Æ¤¤¤ì¤Ð¡¢¸Ä¡¹¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤ÏÍÑ»ú·Ï¤ä¸À¸ì¤ò¶á»÷¤¹
+¤ë¤â¤Î¤È¤·¤ÆÍѤ¤¤ë¤³¤È¤¬¤Ç¤¡¢¾¯¤Ê¤¤µ²±ÍÆÎ̤ÇÂçÎ̤Îʸ»ú¤ò°·¤¦¤³¤È¤¬¤Ç
+¤¤ë¡£UCS/Unicode ¤Î¤è¤¦¤Ê¿¿ô¤Î¸À¸ì¤òÂоݤË¿¿ô¤ÎÍÑ»ú·Ï¤ò¼ýÏ¿¤·¤¿Éä¹æ
+²½Ê¸»ú½¸¹ç¤¬ÍøÍѤµ¤ì¤ë¤è¤¦¤Ë¤Ê¤ë¤Þ¤Ç¤Ï¡¢Ã±°ì¤Î¸À¸ì¤äÍÑ»ú·Ï¤òÁÛÄꤷ¤Æºî
+¤é¤ì¤Æ¤¤¤¿Éä¹æ²½Ê¸»ú½¸¹ç¤¬Â¿¤¯¡¢¤³¤ÎÁ°Äó¤Ï¤Û¤ÜËþ¤¿¤µ¤ì¤Æ¤¤¤¿¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ê²¾Äê¤òÁ°Äó¤ËÉä¹æ²½Ê¸»ú½¸¹ç¤òÄɲòÄǽ¤Ë¤·¤¿¥·¥¹¥Æ¥à¤È¤·¤Æ
+Mule [<A
+ HREF="node7.html#Mule">3</A>] ¤¬Â¸ºß¤¹¤ë¡£<A NAME="tex2html3"
+ HREF="footnode.html#foot124"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+<P>
+¤·¤«¤·¡¢Â¿¤¯¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤ÏÄ̾ï¤Îʸ»ú¤À¤±¤Ç¤Ê¤¯¡¢¶çÆÉÅÀ¤Î¤è¤¦¤Êµ¹æ
+¤ò´Þ¤ó¤Ç¤ª¤ê¡¢¤Þ¤¿¡¢JIS X 0208 ¤Î¤è¤¦¤ËÊ£¿ô¤ÎÍÑ»ú·Ï¤ò´Þ¤à¤è¤¦¤ÊÉä¹æ²½
+ʸ»ú½¸¹ç¤ä ISO 8859-1 ¤Î¤è¤¦¤ËÊ£¿ô¤Î¸À¸ì¤ÇÍøÍѤµ¤ì¤ëÉä¹æ²½Ê¸»ú½¸¹ç¤â¿
+¤¯Â¸ºß¤·¤¿¤Î¤Ç¡¢Åö½é¤«¤é¤³¤ì¤Ï¤¢¤¯¤Þ¤Ç¶á»÷¤Ë²á¤®¤Ê¤«¤Ã¤¿¡£
+µÕ¤Ë¡¢Æ±°ì¤Îʸ»ú¤Ç¤â¡¢Éä¹æ²½Ê¸»ú½¸¹ç¤¬°Û¤Ê¤ì¤Ð°ã¤¦Ê¸»ú¤È¤·¤Æ°·¤ï¤ì¤Æ¤·
+¤Þ¤¦¡£Î㤨¤Ð¡¢ISO 8859-1 ¤Î¡Öá¡×¤È ISO 8859-2 ¤Î¡Öá¡×¤ä JIS X
+0208:1978 ¤Î¡Ö¤¢¡×¤È JIS X 0208:1983 ¤Î¡Ö¤¢¡×¤ÏÊ̤Îʸ»ú¤È¤µ¤ì¤ë¡£¤³¤ì
+¤Ç¤Ï¡¢¸¡º÷¤äʸ»ú¤ÎÀ¼Á¤òÄêµÁ¤¹¤ë¾å¤ÇÌäÂ꤬¤ª¤³¤ë¡£À¾²¤¤ÈÅ첤¤Î¤è¤¦¤Ë¡¢
+ÅÁÅýŪ¤Ë¤Ï°Û¤Ê¤ëÉä¹æ²½Ê¸»ú½¸¹ç¤ò»È¤Ã¤Æ¤¤Æ¤ª¤ê¡¢¶áǯ¸òή¤¬À¹¤ó¤Ë¤Ê¤ê¤Ä
+¤Ä¤¢¤ë¤è¤¦¤Ê´Ä¶¤Ç¤Ï¡¢ÆäËÉÔÊؤǤ¢¤ë¡£
+
+<P>
+ʸ»ú¤Î½Å¤Ê¤ê¤¬¤Û¤È¤ó¤É¤Ê¤¤¤³¤È¤òÁ°Äó¤È¤·¤Æ¤¤¤ë½¾Íè¤Î Mule ·¿¤Îʸ»úɽ¸½
+ÊýË¡¤Ï¡¢µ²±»ñ¸»¤¬¹â²Á¤Ç¤¢¤Ã¤¿»þÂå¤Ë¤Ï°ì¼ï¤Î¶á»÷²ò¤È¤·¤Æ¸ú²ÌŪ¤Ç¤¢¤Ã¤¿¡£
+¤·¤«¤·µ²±»ñ¸»¤¬Èæ³ÓŪËÉ٤ˤʤê¤Ä¤Ä¤¢¤ë¸½ºß¡¢¤½¤ÎÍøÅÀ¤è¤ê¤âÊÀ³²¤¬Â¿¤¯
+¤Ê¤Ã¤Æ¤¤¿¡£¤è¤ê¹âÅÙ¤Êʸ»ú½èÍý¤ä¤è¤ê½ÀÆð¤Ê³ÈÄ¥²ÄǽÀ¤ò¼Â¸½¤¹¤ë¤¿¤á¤Ë¤â¡¢
+¤Þ¤¿¡¢¸½ºßÍøÍѤµ¤ì¤Æ¤¤¤ë¤µ¤Þ¤¶¤Þ¤ÊÉä¹æ²½Ê¸»ú½¸¹ç¤ò¤è¤êŬÀÚ¤ËÍøÍѤ¹¤ë¤¿
+¤á¤Ë¤â¡¢Ãø¼Ô¤é¤Ï½¾Íè¤Î Mule ¤ÎÊý¼°¤ËÂå¤ï¤ë¿·¤¿¤Êʸ»úɽ¸½¤Î»ÅÁȤߤò¼Â¸½
+¤¹¤ë¤³¤È¤ò¤á¤¶¤·¤Æ¤¤¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00220000000000000000"></A>
+<A NAME="sec:utf-2000-model"></A>
+<BR>
+Éä¹æ²½Ê¸»ú½¸¹ç¤Ë°Í¸¤·¤Ê¤¤Ê¸»úɽ¸½¤Ø
+</H1>
+
+<P>
+Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Ë´ð¤Å¤«¤º¤Ëʸ»ú¤òɽ¸½¤¹¤ë¤³¤È¡¢¤¹¤Ê¤ï¤Á¡¢¸ÇͤÎÈÖ¹æ¤Ç
+ƱÄꤹ¤ë¤³¤È¤Ê¤·¤Ëʸ»ú¤ò»Ø¤·¼¨¤½¤¦¤È¤¹¤ë¤È¤·¤¿¤é¡¢¤É¤¦¤¹¤ì¤ÐÎɤ¤¤À¤í¤¦
+¤«¡© ¤ª¤½¤é¤¯¤½¤Î°ì¤Ä¤ÎÊýË¡¤Ï»Ø¤·¼¨¤·¤¿¤¤Ê¸»ú¤ÎÀ¼Á¤òÎóµó¤¹¤ë¤³¤È¤À¤í
+¤¦¡£Î㤨¤Ð¡¢¡Ö¤¢¡×¤ò»Ø¤·¼¨¤¹¤È¤¹¤ë¤Ê¤é¤Ð<DL>
+<DT><STRONG>ÍÑ»ú·Ï</STRONG></DT>
+<DD>¤Ò¤é¤¬¤Ê
+
+</DD>
+<DT><STRONG>²»²Á</STRONG></DT>
+<DD>/a/
+
+</DD>
+</DL>
+¤Î¤è¤¦¤Ë¤¹¤ì¤Ð¤è¤¤¤À¤í¤¦¡£<A NAME="tex2html4"
+ HREF="footnode.html#foot114"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A> ´Á»ú¤Î¾ì¹ç¤Ë¤Ï¡¢È¯
+²»¤À¤±¤Ç¤ÏÉÔ½½Ê¬¤Ç¤¢¤ë¡£Î㤨¤Ð¡¢¡Ö»ú¡×¤ò»Ø¤·¼¨¤·¤¿¤¤»þ¤Ë<DL>
+<DT><STRONG>ÍÑ»ú·Ï</STRONG></DT>
+<DD>´Á»ú
+
+</DD>
+<DT><STRONG>²»</STRONG></DT>
+<DD>/¤¸/
+
+</DD>
+</DL>
+¤È¤¹¤ì¤Ð¡¢¡Ö»ú¡×°Ê³°¤Ë¤â¡Ö»þ¡×¤ä¡Ö¼¡¡×¤Ê¤É /¤¸/ ¤È¤¤¤¦²»¤ò»ý¤ÄÁ´¤Æ¤Î´Á
+»ú¤¬´Þ¤Þ¤ì¤Æ¤·¤Þ¤¦¡£Áí²è¿ô¤òÉÕ¤±<DL>
+<DT><STRONG>ÍÑ»ú·Ï</STRONG></DT>
+<DD>´Á»ú
+
+</DD>
+<DT><STRONG>²»</STRONG></DT>
+<DD>/¤¸/
+
+</DD>
+<DT><STRONG>Áí²è¿ô</STRONG></DT>
+<DD>6
+
+</DD>
+</DL>
+¤È¤¹¤ì¤Ð¡¢¡Ö»þ¡×¤ä¡Ö»ö¡×¤Ê¤É¤Ï½ü³°¤µ¤ì¡¢¡Ö»ú¡×¤ä¡Ö¼¡¡×¤ä¡Ö¼ª¡×¤Ê¤É¤ÎÁí
+²è¿ô¤¬£¶²è¤Î /¤¸/ ¤È¤¤¤¦²»¤ò»ý¤ÄÁ´¤Æ¤Î´Á»ú¤Î½¸¹ç¤Ë¸ÂÄꤵ¤ì¤ë¡£¤µ¤é¤ËÉô
+¼ó¡Ö»Ò¡×¤ò»ØÄꤹ¤ì¤Ð¤µ¤é¤Ë¸ÂÄꤵ¤ì¤Æ¤¤¤¯¤À¤í¤¦¤·¡¢Ê¸»ú¤Î¹½Â¤¡Ö¡ØÕß¡Ù¤Î
+²¼¤Ë¡Ø»Ò¡Ù¡×¤ò»ØÄꤷ¤¿¤ê¡¢»úµÁ¤ò»ØÄꤹ¤ì¤Ð¤µ¤é¤Ë¸ÂÄꤵ¤ì¤ë¤À¤í¤¦¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ëʸ»ú¤ò°À¤Î½¸¹ç¤Çɽ¸½¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢Éä¹æ²½Ê¸»úÊý¼°¤Ë°Í¤é
+¤º¤Ëʸ»ú¡Ê¤Ê¤¤¤·¤Ïʸ»ú¤Î½¸¹ç¡Ë¤òɽ¸½¤¹¤ë¤³¤È¤¬²Äǽ¤Ç¤¢¤ë¡£¤Þ¤¿¡¢»ØÄꤹ
+¤ë°À¤ò¿¤¯¤·¤¿¤ê¾¯¤Ê¤¯¤·¤¿¤ê¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æ¡¢É½¸½¤¹¤ëʸ»ú¤ÎÊñÀݵ¬½à
+¤òºÙ¤«¤¯¤·¤¿¤êÁƤ¯¤·¤¿¤ê¤¹¤ë¤³¤È¤¬¤Ç¤¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ê°À¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¤Ë¤ª¤¤¤Æ¤Ï¡¢Ê¸»ú¤ÎÀ¼Á¤Ë´Ø¤¹¤ë¾ðÊó¤Ïʸ»ú
+°À¤È¤·¤Æʸ»úɽ¸½¼«ÂΤ˴ޤޤì¤Æ¤¤¤ë¡£¤è¤Ã¤Æ¡¢ÆÃÄê¤Î½èÍý¤ËɬÍפʾðÊó¤Ï
+ʸ»ú°À¤È¤·¤Æʸ»úɽ¸½¤Ë´Þ¤á¤Æ¤ª¤«¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£Î㤨¤Ð¡¢É½¼¨¤ò¹Ô¤Ê¤¦
+¤Ë¤Ïʸ»ú¤Î»ú·Á¤ò¼¨¤¹¾ðÊó¤¬É¬ÍפǤ¢¤ë¡£µÕ¤Ë¡¢É½¼¨¤È¤¤¤¦½èÍý¤ò¹Ô¤Ê¤ï¤Ê¤¤
+¤³¤È¤òÁ°Äó¤È¤·¤¿Ê¸»úɽ¸½¤Ë¤Ï¡¢»ú·Á¤È¤¤¤¦Â°À¤ÏÉÔÍפȤʤ롣
+
+<P>
+¤³¤Î¤è¤¦¤Ë³Æʸ»ú¤ò¤½¤Îʸ»ú¤¬»ý¤Ä°À¤Î½¸¹ç¤Ë¤è¤Ã¤Æɽ¸½¤·¡¢¤³¤¦¤·¤¿Ê¸»ú
+¤Î°À¤Î½¸¹ç¤ò¥Ç¡¼¥¿¥Ù¡¼¥¹²½¤·¡¢¤½¤ì¤ò»²¾È¤·¤Ê¤¬¤éʸ»ú¤ò½èÍý¤¹¤ëÊý¼°¤ò
+¤³¤³¤Ç¤Ï¡ØUTF-2000 Êý¼°¡Ù¤È¸Æ¤Ö¤³¤È¤Ë¤¹¤ë¡£UTF-2000 Êý¼°¤Ïʸ»ú¤Ë´Ø
+¤¹¤ëÃ챤òľÀÜ¥×¥í¥°¥é¥à¤¹¤ë¤Î¤Ç¤Ï¤Ê¤¯¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹²½¤·¤Æ¤½¤ì¤ò»²¾È¤¹
+¤ëÊýË¡¤Ç¤¢¤ë¤Î¤Ç¡¢·×»»µ¡¤¬°·¤¦¤³¤È¤¬¤Ç¤¤ëʸ»ú¤Î¼ïÎà¤äʸ»ú¤Î³µÇ°¤ÏÉä¹æ
+²½Ê¸»ú½¸¹ç¤ÎÄêµÁ¤Ë«Çû¤µ¤ì¤Ê¤¤¡£»ÈÍѤ¹¤ëʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò¼è¤ê´¹¤¨¤ë¤³
+¤È¤Ë¤è¤Ã¤Æ¡¢ÍưפËʸ»ú¤Î¼ïÎà¤ä³µÇ°¤òÊѹ¹²Äǽ¤Ç¤¢¤ë¡£¤³¤Î¤è¤¦¤Ê¹âÅ٤ʽÀ
+ÆðÀ¤ò»ý¤ÄȾÌÌ¡¢Â¿¿ô¤Îʸ»ú¤ò°·¤¦¾ì¹ç¡¢Â¿Î̤ε²±Î̤¬É¬ÍפȤʤë¤È¹Í¤¨¤é
+¤ì¤ë¡£¤³¤Î¤¿¤á¡¢Ê¸»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò½ÀÆðÀ¤ò»¤Ê¤¦¤³¤È¤Ê¤¯¸úΨŪ¤Ë°·¤¦¤¿
+¤á¤Îµ¡¹½¤¬É¬ÍפȤʤ롣
+
+<P>
+¤È¤³¤í¤Ç¡¢UTF-2000 Êý¼°¼«ÂΤϴû¸¤ÎÉä¹æ²½Ê¸»úµ»½Ñ¤ÈÂÐΩ¤¹¤ë¤â¤Î¤Ç¤Ï¤Ê
+¤¤¡£Éä¹æ²½Ê¸»ú½¸¹ç¤Î¼ïÎà¤ÈÉä¹æ°ÌÃÖ¤Ïʸ»ú°À¤Î°ì¤Ä¤Èª¤¨¤ë¤³¤È¤Ï²Äǽ¤Ç
+¤¢¤ê¡¢ÍøÍѤ·¤¿¤¤Éä¹æ²½Ê¸»ú½¸¹ç¤òʸ»ú°À¤Ë´Þ¤á¤ë¤³¤È¤Ë¤è¤ê¡¢¤½¤ì¤é¤ÎÉä
+¹æ²½Ê¸»ú½¸¹ç¤ÎÀ¤³¦¤È¾ðÊó¸ò´¹¤ò¹Ô¤Ê¤¦¤³¤È¤Ï²Äǽ¤Ç¤¢¤ë¡£
+
+<P>
+
+<P>
+<BR><HR>
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</TITLE>
+<META NAME="description" CONTENT="ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node4.html">
+<LINK REL="previous" HREF="node2.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node4.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html70"
+ HREF="node4.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html68"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html62"
+ HREF="node2.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html71"
+ HREF="node4.html">ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<B> Up:</B> <A NAME="tex2html69"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html63"
+ HREF="node2.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+<!--Table of Child-Links-->
+<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
+
+<UL>
+<LI><A NAME="tex2html72"
+ HREF="#SECTION00310000000000000000">XEmacs UTF-2000</A>
+<LI><A NAME="tex2html73"
+ HREF="#SECTION00320000000000000000">ʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤Èʸ»úɽ¸½</A>
+<LI><A NAME="tex2html74"
+ HREF="#SECTION00330000000000000000">Internal Representation of Character Object</A>
+<LI><A NAME="tex2html75"
+ HREF="#SECTION00340000000000000000">Áȹþ¤ßʸ»ú</A>
+<LI><A NAME="tex2html76"
+ HREF="#SECTION00350000000000000000">coded-charset</A>
+</UL>
+<!--End of Table of Child-Links-->
+<HR>
+
+<H1><A NAME="SECTION00300000000000000000">
+ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</A>
+</H1>
+
+<P>
+²æ¡¹¤Ï <A HREF="node2.html#sec:utf-2000-model">2.2</A> Àá¤Ç½Ò¤Ù¤¿¡ØUTF-2000 Êý¼°¡Ù¤Î¼Â¾Ú
+¤òÌÜŪ¤Ë <B>XEmacs UTF-2000</B> ¤ò³«È¯¤·¤¿¡£
+¤³¤Î¾Ï¤Ç¤Ï¡¢¼ç¤Ë¡¢Ê¸»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï (text editor)
+¤È¤·¤Æ¤Î´ÑÅÀ¤«¤é <B>XEmacs UTF-2000</B> ¤Ë¤Ä¤¤¤Æ³µÀ⤹¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00310000000000000000">
+XEmacs UTF-2000</A>
+</H1>
+
+<P>
+XEmacs-UTF-2000¡Ê¿Þ <A HREF="node3.html#FIG:XEmacs">3.1</A>) ¤Ï <B>XEmacs</B> [<A
+ HREF="node7.html#XEmacs">6</A>]
+¤È¸Æ¤Ð¤ì¤ëÂÐÏ÷¿Åý¹ç´Ä¶¤ò´ð¤Ë¤·¤Æ¤¤¤ë¡£XEmacs ¤Ï <B>GNU Emacs</B>
+[<A
+ HREF="node7.html#GNU-Emacs">4</A>] ¤È¸Æ¤Ð¤ì¤ë³ÈÄ¥²Äǽ¤Ê¥¨¥Ç¥£¥¿¤òÃæ¿´¤È¤·¤¿ÂÐÏ÷¿Åý¹ç´Ä
+¶¤òÀ°Íý¡¦³ÈÄ¥¤·¡¢³¨¤Ê¤É¤â°·¤¨¤ë¤è¤¦¤Ë¤·¤¿¤â¤Î¤Ç¤¢¤ë<A NAME="tex2html5"
+ HREF="footnode.html#foot187"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>¡£°ìÊý¡¢<B>Mule</B>
+(MULtilingual enhancement of GNU Emacsen) [<A
+ HREF="node7.html#Mule">3</A>] ¤ÏÅŻҵ»½ÑÁí¹ç¸¦
+µæ½ê¤ÎȾÅÄ·õ°ì»á¤¬Ãæ¿´¤È¤Ê¤Ã¤Æ³«È¯¤·¤Æ¤¤¤ë GNU Emacs ¤Î¿¸À¸ì³ÈÄ¥¤Ç¡¢
+¸½ºß¤Ï GNU Emacs ¤ËÅý¹ç¤µ¤ì¤Æ¤¤¤ë¡£¤³¤Î Mule µ¡Ç½¤ò XEmacs ¤ËÅý¹ç¤·¤¿
+XEmacs-Mule ¤Î³«È¯¤â¿Ê¤á¤é¤ì¤Æ¤ª¤ê¡¢XEmacs ¤Î°ìÉô¤È¤·¤ÆÇÛÉÛ¤µ¤ì¤Æ¤¤¤ë¡£
+XEmacs UTF-2000 ¤Ï¤³¤Î XEmacs-Mule ¤ò´ð¤ËÂçÉý¤Ë²þÊѤ·¤¿¤â¤Î¤Ç¤¢¤ë¡£
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="FIG:XEmacs"></A><A NAME="193"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 3.1:</STRONG>
+XEmacs UTF-2000</CAPTION>
+<TR><TD><!-- MATH
+ $\scalebox{0.5}{\includegraphics{xe-u2k-cd.eps}}$
+ -->
+<IMG
+ WIDTH="690" HEIGHT="796" ALIGN="BOTTOM" BORDER="0"
+ SRC="img2.png"
+ ALT="\scalebox{0.5}{\includegraphics{xe-u2k-cd.eps}}"></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+GNU Emacs ¤ª¤è¤Ó XEmacs ¤Ï Emacs Lisp ¸À¸ì¤ò»È¤Ã¤Æµ¡Ç½¤ò³ÈÄ¥¤¹¤ë¤³¤È¤¬
+¤Ç¤¡¢¼ÂºÝ¤Ë Emacs Lisp ¤Çµ½Ò¤µ¤ì¤¿¤µ¤Þ¤¶¤Þ¤Ê¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤¬ºîÀ®¤µ
+¤ìÍøÍѤµ¤ì¤Æ¤¤¤ë¡£Î㤨¤Ð¡¢GNU Emacs/XEmacs ¤ÎÃæ¤ÇÅŻҥ᡼¥ë¤ä¥Í¥Ã¥È¥Ë¥å¡¼
+¥¹¤òÆɤ߽ñ¤¤¹¤ë¤³¤È¤¬¤Ç¤¤ë¤· WWW ÊǤò¸«¤ë¤³¤È¤¬¤Ç¤¤ë¡£¤·¤«¤·¡¢¤³¤ì
+¤é¤Ï¸µ¡¹ Latin-1 (ISO-8859-1) ¤Ê¤É¤Î 1 byte ¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤Ç¤·¤«ÍøÍÑ
+²Äǽ¤Ç¤Ï¤Ê¤«¤Ã¤¿¡£
+
+<P>
+¤³¤ì¤ËÂФ·¡¢Mule ¤Ï GNU Emacs/XEmacs ¤ÎÍøÊØÀ¡¦³ÈÄ¥²ÄǽÀ¤ò¤½¤Î¤Þ¤Þ¤Ë¡¢
+ÍøÍѤǤ¤ëÉä¹æ²½Ê¸»ú½¸¹ç¤òÂçÉý¤Ë³ÈÄ¥¤·¤¿¤â¤Î¤Ç¤¢¤ê¡¢¤µ¤Þ¤¶¤Þ¤Êʸ»ú¤òɽ
+¼¨¤¹¤ëµ¡Ç½¤È³Æ¼ï¸À¸ìÍѤÎÆþÎϵ¡Ç½¤ò¤Ï¤¸¤á¤È¤¹¤ë¿¸À¸ì²½µ¡Ç½¤òÄ󶡤¹¤ë¡£
+Mule µ¡Ç½¤ò»ý¤Ã¤¿ GNU Emacs/XEmacs ¤Ç¤Ï GNU Emacs/XEmacs ¤Îµ¡Ç½¤¬¤µ¤Þ
+¤¶¤Þ¤Êʸ»ú¡¦¸À¸ì¤ÇÍøÍѲÄǽ¤È¤Ê¤ë¡£<A NAME="tex2html7"
+ HREF="footnode.html#foot196"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+<P>
+Mule ¤Ç¤Ïʸ»ú¤ÏÉä¹æ²½Ê¸»ú½¸¹ç¤Î¼ïÎà¤òɽ¤¹ <B>charset-id</B>
+¤ÈÉä¹æ°ÌÃ֤ΠÁȤÇɽ¸½¤µ¤ì¤ë¡£charset-id ¤ÏºÇÂç 128
+¸Ä¤¬Æ±»þ¤ËÍøÍѲÄǽ¤Ç¤¢¤ë¡£Ã¢¤·¡¢ ÍøÍѲÄǽ¤ÊÉä¹æ²½Ê¸»ú½¸¹ç¤Ï ISO 2022
+[<A
+ HREF="node7.html#ISO-2022">1</A>] ¤Î 94 ʸ»ú½¸¹ç¡¢96 ʸ»ú½¸¹ç¡¢94¡ß94 ʸ»ú½¸¹ç¡¢96¡ß96
+ʸ»ú½¸¹ç¤Ë¸Â¤é¤ì¤ë¡£Big5 ¤Î¤è¤¦¤Ê ISO 2022
+¤Î¿Þ·Áʸ»ú½¸¹ç¤Î¹½Â¤¤ËŬ¹ç¤·¤Ê¤¤¤â¤Î¤Ï ISO 2022 ¤Î¹½Â¤¤Ë¹ç¤¦
+¤è¤¦¤ËÊÑ´¹¤·¤Æ°·¤¦É¬Íפ¬¤¢¤ë¡£¤Þ¤¿¡¢Ê¸»úɽ¸½¶õ´Ö¤Ï 19 bit ¤Ç¤¢¤ê¡¢´û¤Ë
+ÍøÍѲÄǽ¤Ê¶õ´Ö¤¬¸Ï³é¤·¤Æ¤¤Æ¤¤¤ë¡£¤µ¤é¤Ë¡¢Mule ¤Ç¤Ïʸ»ú¤Ï charset-id
+¤ÈÉä¹æ°ÌÃÖ¤ÎÁȤÇɽ¸½¤µ¤ì¤ë¤Î¤Ç¡¢Éä¹æ²½Ê¸»ú½¸¹ç¤¬°Û¤Ê¤ì¤ÐËÜÍèƱ¤¸Ê¸»ú¤Ç
+¤¢¤Ã¤Æ¤â°Û¤Ê¤ëʸ»ú¤È¤·¤Æ°·¤ï¤ì¤Æ¤·¤Þ¤¦¤È¤¤¤¦ÌäÂê¤â¤¢¤ë¡£
+
+<P>
+XEmacs UTF-2000 ¤Ï GNU Emacs, XEmacs, Mule ¤ÎÍøÅÀ¤ò·Ñ¾µ¤·¤Ä¤Ä¡¢¤³¤ì¤é
+¤ÎÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë°Ê²¼¤Ë½Ò¤Ù¤ë¤è¤¦¤Ê³ÈÄ¥¡¦²þÊѤò¹Ô¤Ã¤¿¡£
+
+<P>
+
+<H1><A NAME="SECTION00320000000000000000">
+ʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤Èʸ»úɽ¸½</A>
+</H1>
+
+<P>
+XEmacs UTF-2000 ¤Ï¡¢Ê¸»ú°À¤Î½¸¹ç¤Ë¤è¤ëʸ»úɽ¸½¤È¤¤¤¦¥â¥Ç¥ë¤Ë´ð¤Å¤¤¤Æ¡¢
+ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»²¾È¤¹¤ë¤³¤È¤Ë¤è¤Ã¤Æʸ»ú¤ò½èÍý¤¹¤ë¡£¤³¤Î¤¿¤á¡¢Ê¸»ú¥Ç¡¼
+¥¿¥Ù¡¼¥¹¤òÍøÍѤ·¤ä¤¹¤¤¤è¤¦¤ËÆâÉôɽ¸½¤òÊѹ¹¤·¤Æ¤¤¤ë¡£Ê¸»úɽ¸½¶õ´Ö¤ò 30
+bit ¤Ë³ÈÂ礷¤¿¤¿¤á¡¢Æ±»þ¤ËÍøÍѤǤ¤ëʸ»ú¿ô¤ÏÂçÉý¤ËÁý¤¨¤Æ¤¤¤ë¡£Ê¸»ú¤Ï¡¢
+<I>ʸ»ú id</I>¤È¸Æ¤Ð¤ì¤ëʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤Î id ¤ÇÆâÉôŪ¤Ëɽ¸½¤µ¤ì¡¢¤³¤Î
+ʸ»ú id ¤òÍѤ¤¤Æʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤ò»²¾È¤·¤Æ¡¢½èÍý¤¬¹Ô¤Ê¤ï¤ì¤ë¡£
+
+<P>
+ʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤Ïʸ»ú°À¤Î½¸¹ç¤È¤·¤ÆÄêµÁ¤µ¤ì¡¢¸ÇͤΡÖʸ»ú id¡×¤¬³ä
+¤êÅö¤Æ¤é¤ì¤ë¡£Ê¸»ú¤òÄêµÁ¤¹¤ë¤¿¤á¤Ë XEmacs UTF-2000 ¤Ç¤Ï define-char ¤È
+¤¤¤¦Áȹþ¤ß´Ø¿ô¤òÍÑ°Õ¤·¤Æ¤¤¤ë¡£
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>define-char</B> (<I>attributes</I>)
+
+<BLOCKQUOTE>
+ʸ»ú°À <I>attributes</I> ¤Çɽ¸½¤µ¤ì¤ëʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤òÄêµÁ¤·¡¢
+ ¤½¤Îʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤òÊÖ¤¹¡£
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>ʸ»ú°À <I>attributes</I> ¤ÏÏ¢Áۥꥹ¥È¤Ç¤¢¤ë¡£
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+<P><DL>
+<DT><STRONG>¡ÎÎã¡Ï</STRONG></DT>
+<DD><PRE>
+(define-char
+ '((name . "CJK RADICAL SECOND TWO")
+ (general-category symbol other) ; Informative Category
+ (bidi-category . "ON")
+ (mirrored . nil)
+ (total-strokes . 1)
+ (<-radical
+ ((ucs . #x4E5A)
+ ))
+ (ideograph-cdp . -21)
+ (chinese-big5-cdp . #x8C5D)
+ (ucs . #x2E83)
+ ))
+</PRE>
+
+</DD>
+</DL>
+
+<P>
+¤³¤Î¾¡¢Ê¸»ú¤äʸ»ú°À¤ò°·¤¦¤¿¤á¤Ë¼¡¤Î¤è¤¦¤Ê´Ø¿ô¤òÍÑ°Õ¤·¤Æ¤¤¤ë¡§
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>get-char-attribute</B>
+ (<I>character</I> <I>attribute</I>)
+
+<BLOCKQUOTE>
+ʸ»ú¥ª¥Ö¥¸¥§¥¯¥È <I>character</I> ¤Î°À <I>attribute</I> ¤ÎÃÍ
+ ¤òÊÖ¤¹¡£
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+<P><DL>
+<DT><STRONG>¡ÎÎã¡Ï</STRONG></DT>
+<DD><PRE>
+(get-char-attribute ?¤¢ 'name)
+¢ª "HIRAGANA LETTER A"
+</PRE>
+</DD>
+</DL><BLOCKQUOTE>
+
+
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>put-char-attribute</B>
+ (<I>character</I> <I>attribute</I> <I>value</I>)
+
+<BLOCKQUOTE>
+ʸ»ú¥ª¥Ö¥¸¥§¥¯¥È <I>character</I> ¤Î°À <I>attribute</I> ¤ÎÃÍ
+ ¤ò <I>value</I> ¤ËÀßÄꤹ¤ë¡£
+
+</BLOCKQUOTE>
+ </BLOCKQUOTE><DL>
+<DT><STRONG>¡ÎÎã¡Ï</STRONG></DT>
+<DD><PRE>
+(get-char-attribute ?¤¢ 'foo)
+¢ªnil
+(put-char-attribute ?¤¢ 'foo 1)
+¢ª1
+(get-char attribute ?¤¢ 'foo)
+¢ª1
+</PRE>
+</DD>
+</DL>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>find-char</B>
+ (<I>attributes</I>)
+
+<BLOCKQUOTE>
+In order to find a character object by a character attribute, a
+ builtin function <TT>find-char</TT> may be convenient. This function
+ retrieves the character that has specified attributes.
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>map-char-attribute</B>
+ (<I>function</I> <I>attribute</I> &optional <I>range</I>)
+
+<BLOCKQUOTE>
+A map function for character attributes is also available. This
+ function is useful in finding characters with a character
+ attribute, or processing by a character attribute,
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>This function maps <I>function</I> over entries in <I>attribute</I>,
+
+calling it with two arguments, each key and value in the table.
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE><I>Range</I>
+ specifies a subrange to map over and
+
+is in the same format as the
+ range argument to
+ 'put-range-table'. If omitted or t, it defaults to
+ the entire table. See Fig <A HREF="node3.html#fig:map-char-attribute">3.2</A>
+
+for an example using this function.
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>char-attribute-alist</B>
+ (<I>character</I>)
+
+<BLOCKQUOTE>
+You can get every attributes of a character as an association-list
+ by a built-in function <TT>char-attribute-alist</TT>.
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>This function returns the alist of attributes of character.
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>char-attribute-list</B> ()
+
+<BLOCKQUOTE>
+You can get the list of character attributes by a builtin function
+ <TT>char-attribute-list</TT>.
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>This function returns the list of all existing character
+ attributes.
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+¤Ê¤ª¡¢Ê¸»ú°À¤Ë´Ø¤·¤Æ¤Ï <A HREF="node4.html#cha:char-db">4</A> ¾Ï¤Ç¾ÜÀ⤹¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00330000000000000000">
+Internal Representation of Character Object</A>
+</H1>
+
+<P>
+XEmacs UTF-2000 processes characters based on the UTF-2000 model,
+that is, it operates on character objects and their attributes stored in
+its character database. For this purpose, XEmacs UTF-2000 modifies
+and extends the internal character and string representations.
+
+<P>
+In Mule, its internal representation depends on the structure of
+graphic character set<A NAME="tex2html8"
+ HREF="footnode.html#foot289"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A> of
+ISO/IEC 2022 [<A
+ HREF="node7.html#ISO-2022">1</A>]. In this paper, such kind of CCS used for the
+internal representation of Mule is called <B>Mule-charset</B>.
+Each character is represented by a pair of Mule-charset and its code
+point. The internal character representation is separated by
+7bit-segments. It is designed to use bit calculus, and thus very
+sparse. The internal string representation is a kind of multi-byte
+encoding. ASCII characters are represented by ASCII code points.
+Other characters are represented by 2 to 4 bytes sequence. For this
+case, the first byte called <B>leading-byte</B> specifies a CCS. The
+following bytes indicate a code point<A NAME="tex2html9"
+ HREF="footnode.html#foot293"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>. Every valid multi-byte sequence can be
+mapped to a corresponding character representation, however possible
+character representation may not be mapped to any multi-byte sequence.
+The code space is limited by two parameters: charset-id (basically
+same with leading-byte) and characters representation. Number of
+charset-ids has to be smaller than 128. Each character is represented
+by 19-bit integer 14 bit can be used for code point and 5 bit can be
+used for charset-id of 2-bytes-set. However full 14-bit cannot be
+used for a code point. As the character representation has to satisfy
+the structure of ISO/IEC graphic character set, 33 to 126 or 32 to 127
+can be used for each 7-bit segment (octet) .
+
+<P>
+The character and string representation of Mule is too limited to
+implement a large character database. It is better to guarantee
+1-to-1 mapping between character representation and string
+representation, and they should not depend on any coded character
+sets. Perhaps a simple, non-segmented, linear space is better than
+complex, segmented, sparse space. In addition, a 19-bit code space
+seems too narrow even for UCS [<A
+ HREF="node7.html#BMP">2</A>] (Unicode [<A
+ HREF="node7.html#Unicode">5</A>]). To
+support UCS, at least a 21-bit code space is required. Therefore, we
+decided to change the internal representation.
+
+<P>
+In the XEmacs UTF-2000, each character object has a character-id.
+Each character-id is represented by a 30-bit integer. In strings or
+buffers, each character object is represented by a multi-byte sequence
+that is a character-id encoded in UTF-8 [<A
+ HREF="node7.html#BMP">2</A>]. It is wide enough
+to represent various kind of characters at the same time. It can
+support every Unicode character. In addition, user can define a lot
+of other characters.
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="fig:map-char-attribute"></A><A NAME="298"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 3.2:</STRONG>
+Example of map-char-attribute</CAPTION>
+<TR><TD></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+
+<H1><A NAME="SECTION00340000000000000000">
+Áȹþ¤ßʸ»ú</A>
+</H1>
+
+<P>
+XEmacs UTF-2000 ¤Ç¤Ï¡¢Ê¸»ú¤Ï´Ø¿ô define-char ¤Çʸ»ú°À¤Î½¸¹ç¤ò»ØÄꤹ
+¤ë¤³¤È¤Ë¤è¤Ã¤ÆÄêµÁ¤µ¤ì¤ë¡£¤·¤«¤·ºÇ½é¤Ëʸ»ú¤òÄêµÁ¤¹¤ë»þ¤Ë²¿¤âʸ»ú¤¬Â¸ºß
+¤·¤Ê¤¤¤È¤¹¤ì¤Ð¡¢Ê¸»ú¤ÎÄêµÁ¥×¥í¥°¥é¥à¤òʸ»úÎó¤Çɽ¸½¤Ç¤¤Ê¤¤¤³¤È¤Ë¤Ê¤ë¡£
+¤³¤ì¤Ç¤ÏÉÔÊؤǤ¢¤ë¤Î¤Ç¡¢´Ø¿ô define-char ¤Çʸ»ú¤òÄêµÁ¤¹¤ëÁ°¤«¤é¤¢¤é¤«
+¤¸¤áÄêµÁ¤µ¤ì¤Æ¤¤¤ëʸ»ú¤òÀߤ±¤Æ¤¤¤ë¡£¤³¤ì¤ò<I>Áȹþ¤ßʸ»ú</I>
+(builtin character)¤È¸Æ¤Ö¡£
+
+<P>
+ÁȤ߹þ¤ßʸ»ú¤Ï¡¢Ê¸»ú°À¤ò°ìÀÚ»ý¤¿¤Ê¤¤¤³¤È¤ò½ü¤±¤Ð¡¢°ì¼ï¤Îʸ»ú¥ª¥Ö¥¸¥§
+¥¯¥È¤È¤·¤Æ°·¤ï¤ì¤ë¡£³ÆÁȤ߹þ¤ßʸ»ú¤Ï¡¢Ê¸»ú°À¤ò°ìÀÚ»ý¤¿¤Ê¤¤¤Ë¤â´Ø¤ï¤é
+¤º¡¢¤¢¤ëÉä¹æ²½Ê¸»ú½¸¹ç¤ÎÉä¹ç°ÌÃÖ¤òʸ»ú°À¤È¤·¤Æ»ý¤Ã¤Æ¤¤¤ë¤è¤¦¤Ë²ò¼á¤µ
+¤ì¤ë¡£¤³¤Î¤è¤¦¤Ê»ÅÁȤߤòÍѤ¤¤ë¤³¤È¤Ë¤è¤ê¡¢XEmacs UTF-2000 ¤Ï¥Ö¡¼¥È¥¹¥È
+¥é¥Ã¥×½èÍý¤Ë¤ª¤¤¤Æʸ»úÄêµÁ¤Ê¤·¤ËÉä¹æ²½Ê¸»úÎó¤òÆɤ߹þ¤à¤³¤È¤¬¤Ç¤¤ë¡£
+
+<P>
+¤Ê¤ª¡¢Ê¸»úÄêµÁ¤Ë¤è¤Ã¤ÆÄêµÁ¤µ¤ì¤¿Ê¸»ú¤ÈƱÍͤˡ¢ÁȤ߹þ¤ßʸ»ú¤ËÂФ·¤Æ¤â¡¢
+ʸ»ú°À¤òÉղ乤뤳¤È¤Ï²Äǽ¤Ç¤¢¤ê¡¢¤½¤Î¾ì¹ç¡¢¤½¤ÎÁȤ߹þ¤ßʸ»ú¤ÏÉղäµ
+¤ì¤¿Ê¸»ú°À¤ò»ý¤Ã¤¿Ä̾ï¤Îʸ»ú¤È¤·¤ÆºÆÄêµÁ¤µ¤ì¤ë¡£
+
+<P>
+¤È¤³¤í¤Ç¡¢ÄêµÁ¥×¥í¥°¥é¥à¤òɽ¸½¤¹¤ë¤¿¤á¤ÎÁȹþ¤ßʸ»ú¤È¤·¤Æ¤Ç¤¢¤ì¤Ð¡¢ISO
+8859-1 ¤Îʸ»ú¤¬Â¸ºß¤¹¤ì¤Ð½½Ê¬¤¢¤ë¡£¤·¤«¤·¡¢ÂçÎ̤Îʸ»úÄêµÁ¤Ê¤·¤Ë¡¢¾¯¤Ê
+¤¯¤È¤â»ú·Á¤¬³Îǧ¤Ç¤¤ë¤è¤¦¤Ë¡¢UCS ¤Îʸ»ú¤ä ISO 2022 ¤Î¿Þ·Áʸ»ú½¸¹ç¤Îʸ
+»ú¡¢Ê¸»ú¶À¤Îʸ»ú¤Ê¤É¤òÁȹþ¤ßʸ»ú¤È¤·¤Æ¤¤¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00350000000000000000"></A>
+<A NAME="sec:coded-charset"></A>
+<BR>
+coded-charset
+</H1>
+
+<P>
+XEmacs UTF-2000 ¤Ç¤Ï¡¢Ê¸»ú¤ÏÉä¹æ²½Ê¸»ú½¸¹ç¤Ë¤è¤Ã¤Æɽ¸½¤µ¤ì¤Æ¤Ï¤¤¤Ê¤¤¡£¤³
+¤Î¤¿¤á¡¢Mule ¤Ë¤ª¤±¤ë¤è¤¦¤Ê°ÕÌ£¤Ç¤Î Mule-charset ¤ÏɬÍפʤ¤¡£¤·¤«¤·¡¢
+´û¸¤Îʸ»úÉä¹æ¤ÎÀ¤³¦¤È¾ðÊó¸ò´¹¤·¤¿¤ê¡¢´û¸¤Î¥Õ¥©¥ó¥È¤òÍøÍѤ·¤¿¤ê¡¢
+´û¸¤Î¼ÂÁõ¤È¤Î¸ß´¹À¤ò¼Â¸½¤·´û¸¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤òÍøÍѤ¹
+¤ë¤¿¤á¤Ë¡¢¤Ä¤Þ¤ê²ÄÈÂÀ¤ÎÌ̤«¤é¡¢Mule-charset ¤ËÁêÅö¤¹¤ë¤â¤Î¤¬¤¢¤ë¤ÈÊØ
+Íø¤Ç¤¢¤ë¡£¤½¤³¤Ç¡¢XEmacs UTF-2000 ¤Ç¤ÏÉä¹æ²½Ê¸»ú½¸¹ç¤ÎÃê¾Ý¤·¤¿¤â¤Î¤È¤·¤Æ
+<I>coded-charset</I>¤òÀߤ±¤Æ¤¤¤ë¡£
+
+<P>
+XEmacs UTF-2000 ¤Î coded-charset ¤Ë´Ø¤¹¤ë API ¤Ï XEmacs-Mule ¤Ë¤ª¤±¤ë
+Mule-charset ¤Ë´Ø¤¹¤ë API ¤Î¾å°Ì¸ß´¹¤Ë¤Ê¤ë¤è¤¦¤ËÀ߷פµ¤ì¤Æ¤¤¤ë¡£
+XEmacs-Mule ¤Ë¤ª¤±¤ë Mule-charset ¤ÈƱÍͤˡ¢charset ·¿¤¬Â¸ºß¤·¡¢
+charset ·¿¥ª¥Ö¥¸¥§¥¯¥È¤Ï¥·¥ó¥Ü¥ë¤Çɽ¸½¤µ¤ì¤ë̾Á°¤ò»ý¤Ä¡£Mule ¤Ç¤Ï
+Mule-charset ¤Ïʸ»ú¤ÎÆâÉôɽ¸½¤Ë°Í¸¤·¤Æ¤ª¤ê¡¢¤½¤Î¹½Â¤¾å¡¢
+94 ʸ»ú½¸¹ç¡¢
+96 ʸ»ú½¸¹ç¡¢
+94¡ß94 ʸ»ú½¸¹ç¡¢
+96¡ß96 ʸ»ú½¸¹ç¤Î£´¼ïÎà
+¤Ë¸ÂÄꤵ¤ì¤Æ¤¤¤¿¡£°ìÊý¡¢XEmacs UTF-2000 ¤Ç¤Ï¤½¤Î¤è¤¦¤ÊÀ©Ìó¤Ï¸ºß¤·¤Ê¤¤
+¤¿¤á¡¢
+<!-- MATH
+ $\{94|96|128|256\}^{1 ¡Á 4}$
+ -->
+<IMG
+ WIDTH="138" HEIGHT="36" ALIGN="MIDDLE" BORDER="0"
+ SRC="img4.png"
+ ALT="$\{94\vert 96\vert 128\vert 256\}^{1 ¡Á 4}$"> ʸ»ú½¸¹ç¤Ë³ÈÄ¥¤µ¤ì¡¢Éä¹æ°ÌÃÖ¤¬ 4 byte
+°Ê²¼¤Çɽ¸½¤Ç¤¤µ¤¨¤¹¤ì¤Ð¡¢Ç¤°Õ¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤òÍøÍѤǤ¤ë¡£¤¿¤È¤¨
+¤Ð¡¢UCS ¤Î´ðËÜ¿¸À¸ìÌÌ (BMP) [<A
+ HREF="node7.html#BMP">2</A>] ¤Ï 256¡ß256 ʸ»ú½¸¹ç¤Çɽ¸½¤Ç¤
+¡¢UCS-4 Á´ÂΤâ¤Þ¤¿ <IMG
+ WIDTH="35" HEIGHT="16" ALIGN="BOTTOM" BORDER="0"
+ SRC="img5.png"
+ ALT="$256^4$"> ʸ»ú½¸¹ç¤Çɽ¸½¤Ç¤¤ë¡£
+
+<P>
+XEmacs UTF-2000 ¤Î coded-charset ¤Ïʸ»ú¤ÎÆâÉôɽ¸½¤ÈľÀÜ´Ø·¸¤·¤Ê¤¤¤¿¤á¡¢
+coded-charset ¤Ë¼ýÏ¿¤µ¤ì¤¿³Æʸ»ú¤È¤½¤Î coded-charset ¤Ë¤ª¤±¤ëÉä¹æ°ÌÃÖ
+¤ÎÂбþɽ¤Ë¤è¤Ã¤Æ¡¢Ê¸»ú¤ÈÉä¹æ°ÌÃ֤δط¸¤òɽ¸½¤¹¤ëɬÍפ¬¤¢¤ë¡£¤³¤ÎÂбþɽ
+¤È¤·¤Æ¡¢Éä¹æ°ÌÃÖ¤«¤éʸ»ú¤òÆÀ¤ë¤¿¤á¤Î<I>decoding-table</I>¤È¡¢Ê¸»ú¤«¤éÉä
+¹æ°ÌÃÖ¤òÆÀ¤ë¤¿¤á¤Î<I>encoding-table</I>¤Î£²¼ïÎà¤òÀߤ±¤Æ¤¤¤ë¡£¤³¤Î¤¦¤Á¡¢
+¸å¼Ô¤Ïʸ»ú°À¤Î°ì¼ï¤È¤·¤Æ¡¢¤¹¤Ê¤ï¤Á¡¢coded-charset ¤Î̾¾Î¤ò
+°À̾¤È¤¹¤ëʸ»ú°À¤Ï encoding-table ¤ÎÍ×ÁǤȸ«Ê蘆¤ì¤ë¤è¤¦¤Ë¤Ê¤Ã
+¤Æ¤¤¤ë¡£´Ø¿ô define-char ¤â¤·¤¯¤Ï´Ø¿ôput-char-attribute ¤Ç
+coded-charset ¤Î̾¾Î¤ò»ý¤Äʸ»ú°À¤ò»ØÄꤹ¤ë¤È¡¢¤½¤ÎÃͤϻØÄꤵ¤ì¤¿
+coded-charset ¤ÎÉä¹æ°ÌÃ֤Ȥߤʤµ¤ì¡¢»ØÄꤵ¤ì¤¿coded-charset ¤Î
+decoding-table ¤âƱ»þ¤ËÀßÄꤵ¤ì¤ë¡£¤³¤Î»ÅÁȤߤˤè¤ê¡¢ÍÛ¤ËÊÑ´¹É½
+¤ò»ØÄꤷ¤¿¤ê¡¢ÆâÉôɽ¸½¤Ë¸ÀµÚ¤·¤¿¤ê¤»¤º¤Ë¡¢
+¤µ¤Þ¤¶¤Þ¤ÊÉä¹æ²½Ê¸»ú½¸¹ç¤òɽ¸½²Äǽ¤Ç¤¢¤ë¡£
+
+<P>
+
+<P>
+<HR>
+<!--Navigation Panel-->
+<A NAME="tex2html70"
+ HREF="node4.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html68"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html62"
+ HREF="node2.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html71"
+ HREF="node4.html">ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<B> Up:</B> <A NAME="tex2html69"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html63"
+ HREF="node2.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸»úɽ¸½¥â¥Ç¥ë</A>
+<!--End of Navigation Panel-->
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹</TITLE>
+<META NAME="description" CONTENT="ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node5.html">
+<LINK REL="previous" HREF="node3.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node5.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html84"
+ HREF="node5.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html82"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html76"
+ HREF="node3.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html85"
+ HREF="node5.html">Topic Maps ¤Ë´ð¤Å¤¯Âç°èʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<B> Up:</B> <A NAME="tex2html83"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html77"
+ HREF="node3.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+<!--Table of Child-Links-->
+<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
+
+<UL>
+<LI><A NAME="tex2html86"
+ HREF="#SECTION00410000000000000000">ʸ»ú°À̾¤Î̿̾µ¬Ìó</A>
+<LI><A NAME="tex2html87"
+ HREF="#SECTION00420000000000000000">Éä¹ç°ÌÃÖ°À</A>
+<LI><A NAME="tex2html88"
+ HREF="#SECTION00430000000000000000">¢Íucs °À</A>
+<LI><A NAME="tex2html89"
+ HREF="#SECTION00440000000000000000">¢ªdecomposition °À</A>
+<LI><A NAME="tex2html90"
+ HREF="#SECTION00450000000000000000">´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¾ðÊó</A>
+</UL>
+<!--End of Table of Child-Links-->
+<HR>
+
+<H1><A NAME="SECTION00400000000000000000"></A>
+<A NAME="cha:char-db"></A>
+<BR>
+ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹
+</H1>
+
+<P>
+¤³¤ì¤Þ¤Ç½Ò¤Ù¤Æ¤¤¿¤è¤¦¤Ë¡¢¡ØUTF-2000 Êý¼°¡Ù¤Î¼ÂÁõ¡Ê°Ê²¼¤Ç¤Ï¡ØUTF-2000
+¼ÂÁõ¡Ù¤È¸Æ¤Ö¡Ë¤Ç¤Ïʸ»ú¤Ë¤ËÂФ·¤Æ²¿¤é¤«¤Î½èÍý¤ò¹Ô¤Ê¤¦»þ¤ËÂоݤȤʤëʸ»ú
+¤Î½èÍý¤ËɬÍפÊ°À¤ò»²¾È¤¹¤ëɬÍפ¬¤¢¤ë¡£¤³¤Î¤¿¤á¡¢³Æʸ»ú¤Î°À¤òµ¡³£²Ä
+ÆɤʷÁ¤Ç³ÊǼ¤·¤¿¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬É¬ÍפȤʤ롣
+
+<P>
+¤³¤Î¤¿¤á¡¢²æ¡¹¤Ï define-char ·Á¼°¤Çɽ¸½¤µ¤ì¤ëʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò³«
+ȯÃæ¤Ç¤¢¤ë¡£¤³¤ì¤Ï¡¢UTF-2000 µ»½Ñ¤Î¼Â¾Ú¤òÌÜŪ¤È¤¹¤ë¤È¤È¤â¤Ë¡¢¾Íè¤Ë¤ª
+¤±¤ë UTF-2000 µ»½Ñ¤Ë´ð¤Å¤¯Ê¸»ú¾ðÊó¸ò´¹¤Î¥Ù¡¼¥¹¤È¤Ê¤ëɸ½àŪ¤Ê¥Ç¡¼¥¿¥Ù¡¼
+¥¹¤ò¹½ÃÛ¤¹¤ë¤³¤È¤â»ëÌî¤ËÃÖ¤¤¤Æ¤¤¤ë¡£
+
+<P>
+¸½ºß¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï
+
+<UL>
+<LI>Unicode Database
+</LI>
+<LI>CNS 11643 ¤È½ô¶¶Âç´Áϼŵ¤ÎÂоÈɽ <A NAME="tex2html11"
+ HREF="footnode.html#foot437"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+</LI>
+<LI>CDP (Chinese Document Processing) ¥Ç¡¼¥¿¥Ù¡¼¥¹ <A NAME="tex2html12"
+ HREF="footnode.html#foot438"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+</LI>
+<LI>CBETA (Chinese Buddhist Electronic Text Association) ³°»ú¥Ç¡¼¥¿
+ ¥Ù¡¼¥¹
+</LI>
+<LI>CHINA3 ³°»ú¥Ç¡¼¥¿¥Ù¡¼¥¹ <A NAME="tex2html13"
+ HREF="footnode.html#foot439"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>
+</LI>
+<LI>³«È¯¼Ô¤¬¤³¤ì¤Þ¤ÇºîÀ®¤·¤Æ¤¤¿¤½¤Î¾¤Î»¨Â¿¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹
+</LI>
+</UL>
+Åù¤òÅý¹ç¤·¡¢¸ß¤¤¤ÎÌ·½âÅÀ¤ò½¤Àµ¤¹¤ë¤â¤Î¤Ç¤¢¤ë¡£¤Þ¤À¸í¤ê¤â¿¤¯¡¢ÉʼÁ¤Ï¹â
+¤¯¤Ï¤Ê¤¤¤¬¡¢¸½»þÅÀ¤ÇÌó 7 Ëü»úʬ¤ÎÄêµÁ¤¬Â¸ºß¤¹¤ë¡£
+
+<P>
+¤³¤Îɸ½àʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ç¤Ï¡¢Èó´Á»ú¤Ë´Ø¤·¤Æ¤Ï¤ª¤ª¤à¤Í Unicode
+[<A
+ HREF="node6.html#Unicode">5</A>] ¤ÎÄêµÁ¤Ë¤Î¤Ã¤È¤Ã¤Æ¤¤¤ë°ìÊý¡¢´Á»ú¤Ë´Ø¤·¤Æ¤ÏÈù¾®¤Ê»úÂκ¹
+¤â¶èÊ̤·¤Æ¤¤¤ë¡£´Á»ú¤Î³Æʸ»ú¡Ê»úÂΡˤÎÆâ¡¢Âç´Áϼŵ¤ÈƱ¤¸»úÂΤǤʤ¤¤â
+¤Î¤Ë¤Ä¤¤¤Æ¤Ï¡¢ <TT>morohashi-daikanwa</TT> ¤È¤¤¤¦Â°À¤ÎÃͤȤ·¤Æ¡¢Âç´ÁÏÂÈÖ
+¹æ¤Èº¹°Û¤ÎÅٹ礪¤è¤ÓÀ°ÍýÈÖ¹æ¤ò»ý¤¿¤»¤Æ¤¤¤ë¡£¤Þ¤¿¡¢<I>The Unicode
+Standard</I> [<A
+ HREF="node6.html#Unicode">5</A>] ¤ÎÎ㼨»úÂΤÈƱ¤¸»úÂΤǤʤ¤¤â¤Î¤ËÂФ·¤Æ¤Ï¡¢ÂÐ
+±þ¤¹¤ë Unicode ¤ÎÉä¹æ°ÌÃÖ¤ò <code>=>ucs</code> <A NAME="tex2html14"
+ HREF="footnode.html#foot445"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A> ¤È¤¤¤¦Â°À¤ÎÃͤȤ¹¤ë¡£
+
+<P>
+UTF-2000 ¼ÂÁõ¤Ë¤È¤Ã¤Æ¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï¼ÂÁõ¤ÎµóÆ°¤òÄêµÁ¤¹¤ë¤â¤Î
+¤Ç¤¢¤ë¤Î¤Ç¡¢½èÍý¤ËɬÍפÊʸ»ú°À¤È UTF-2000 ¼ÂÁõ¤ÎµóÆ°¤òÂбþÉÕ¤±¤ëɬÍ×
+¤¬¤¢¤ë¡£¤¹¤Ê¤ï¤Á¡¢¾¯¤Ê¤¯¤È¤â½èÍý¤ËÍѤ¤¤ëʸ»ú°À¤ËÂФ·¤Æ¤Ï¡¢Ì¾Á°¤ä·¿¤ä
+°ÕÌ£¤òÄêµÁ¤¹¤ëɬÍפ¬¤¢¤ë¤È¤¤¤¨¤ë¡£¤Þ¤¿¡¢¿Í´Ö¤¬¤³¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò»ú½ñ¤È
+¤·¤ÆÍѤ¤¤ë¾ì¹ç¤ä¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥á¥ó¥Æ¥Ê¥ó¥¹¤ò¹Ô¤Ê¤¦¾å¤Ç¤âʸ»ú°À¤Î·Á¼°
+¤ä°ÕÌ£¤òµ¬Äꤹ¤ë¤³¤È¤Ï½ÅÍפǤ¢¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ê´ÑÅÀ¤Ë´ð¤Å¤¡¢XEmacs UTF-2000 ¤òÂоݤ˴ö¤Ä¤«¤Îʸ»ú°À¤Î̿̾
+µ¬Ìó¤È´ö¤Ä¤«¤Îʸ»ú°À¤Î·Á¼°¡¦°ÕÌ£¤òµ¬Äꤷ¡¢¤½¤ì¤Ë´ð¤Å¤¯Ê¸»ú°À¥Ç¡¼¥¿
+¥Ù¡¼¥¹¤ò³«È¯¤·¤Æ¤¤¤ë¡£¤³¤Î¾Ï¤Ç¤Ïʸ»ú°À¤Ë´Ø¤¹¤ëµ¬Ìó¤Èʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼
+¥¹¤Ë¤Ä¤¤¤Æ³µÀ⤹¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00410000000000000000"></A>
+<A NAME="sec:attribute-naming"></A>
+<BR>
+ʸ»ú°À̾¤Î̿̾µ¬Ìó
+</H1>
+
+<P>
+UTF-2000 ¥â¥Ç¥ë¤Ï XEmacs UTF-2000 ¤Ï¸½ºß¤Î¤È¤³¤í¡¢
+<A HREF="node4.html#sec:coded-charset">4.2</A> Àá¤Ç½Ò¤Ù¤ë¡ØÉä¹ç°ÌÃÖ°À¡Ù¤È
+<A HREF="node4.html#sec:decomposition">4.4</A> Àá¤Ç½Ò¤Ù¤ë ¡Ø<code>->decomposition</code> °À¡Ù¤ò½ü
+¤¡¢Ê¸»ú°À¤Î°ÕÌ£¤òµ¬Äꤷ¤Æ¤¤¤Ê¤¤¡£¤·¤«¤·¤Ê¤¬¤é¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹
+¤ò¹½ÃÛ¡¦¥á¥ó¥Æ¥Ê¥ó¥¹¤·¤¿¤ê¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÍøÍѤ¹¤ë¥¢¥×¥ê¥±¡¼¥·¥ç
+¥ó¡¦¥×¥í¥°¥é¥à¤ò¼Â¸½¤¹¤ë¾å¤Ç¤Ï°ìÄê¤Îµ¬Ì󤬤¢¤Ã¤¿Êý¤¬Ë¾¤Þ¤·¤¤¤È¤¤¤¨¤ë¡£
+¤½¤³¤Ç¡¢·Ð¸³Åª¤Ëʸ»ú°À¤Î̿̾µ¬Ìó¤òÀ°È÷¤·¡¢Ê¸»ú°À¤Î̾¾Î¤Î¥Ñ¥¿¡¼¥ó¤È
+Âç¤Þ¤«¤Ê·Á¼°¤ª¤è¤Ó°ÕÌ£¤òÂбþÉÕ¤±¤è¤¦¤È¤·¤Æ¤¤¤ë¡£
+
+<P>
+
+<H2><A NAME="SECTION00411000000000000000">
+ʸ»ú´Ö¤Î´Ø·¸¤Ë´Ø¤¹¤ë°À</A>
+</H2>
+
+<P>
+¤¢¤ëʸ»ú <IMG
+ WIDTH="18" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
+ SRC="img6.png"
+ ALT="$C$"> ¤ËÂФ·¤Æ´Ø·¸ <I>foo</I> ¤ò»ý¤Äʸ»ú <IMG
+ WIDTH="18" HEIGHT="28" ALIGN="MIDDLE" BORDER="0"
+ SRC="img7.png"
+ ALT="$\gamma_i$"> ¤¬Â¸ºß¤¹
+¤ë»þ¡¢Ê¸»ú <IMG
+ WIDTH="18" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
+ SRC="img6.png"
+ ALT="$C$"> ¤Î°À <code>-></code><I>foo</I> ¤ÏÃͤγÆÍ×ÁÇ <IMG
+ WIDTH="18" HEIGHT="28" ALIGN="MIDDLE" BORDER="0"
+ SRC="img7.png"
+ ALT="$\gamma_i$"> ¤¬
+<IMG
+ WIDTH="18" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
+ SRC="img6.png"
+ ALT="$C$"> ¤Î<I>foo</I> ¤Ç¤¢¤ë¤³¤È¤ò°ÕÌ£¤¹¤ë¡£¤³¤³¤Ç¡¢<code>-></code><I>foo</I>
+¤ÎÃÍ <!-- MATH
+ $\gamma_1 ... \gamma_n$
+ -->
+<IMG
+ WIDTH="51" HEIGHT="28" ALIGN="MIDDLE" BORDER="0"
+ SRC="img8.png"
+ ALT="$\gamma_1 ... \gamma_n$"> ¤Ï¥ê¥¹¥È¤Ç¤¢¤ë¡£
+
+<P>
+ƱÍͤˡ¢<IMG
+ WIDTH="18" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
+ SRC="img6.png"
+ ALT="$C$"> ¤Î°À <code><-</code><I>foo</I> ¤Ïʸ»ú <IMG
+ WIDTH="18" HEIGHT="14" ALIGN="BOTTOM" BORDER="0"
+ SRC="img6.png"
+ ALT="$C$"> ¤¬ÃͤγÆÍ×ÁÇ
+<IMG
+ WIDTH="19" HEIGHT="28" ALIGN="MIDDLE" BORDER="0"
+ SRC="img9.png"
+ ALT="$\gamma_j$"> ¤Î <I>foo</I> ¤Ç¤¢¤ë¤³¤È¤ò°ÕÌ£¤¹¤ë¡£<code>-></code><I>foo</I>
+¤ÈƱÍͤˡ¢<code><-</code><I>foo</I> ¤ÎÃÍ <!-- MATH
+ $\gamma_1 ... \gamma_m$
+ -->
+<IMG
+ WIDTH="54" HEIGHT="28" ALIGN="MIDDLE" BORDER="0"
+ SRC="img10.png"
+ ALT="$\gamma_1 ... \gamma_m$"> ¤â¥ê¥¹¥È
+¤Ç¤¢¤ë¡£
+
+<P>
+<DL>
+<DT><STRONG>Îã</STRONG></DT>
+<DD>¾®Ê¸»ú¤òɽ¤¹´Ø·¸¤ò <B>lowercase</B> ¤È¤¹¤ë»þ¡¢
+ <DL>
+<DT><STRONG>(a)</STRONG></DT>
+<DD>ʸ»ú <B>A</B> ¤Î°À <code>(->lowercase ?a)</code> ¤Ï¡¢Ê¸»ú
+ <B>a</B> ¤¬Ê¸»ú <B>A</B> ¤Î¾®Ê¸»ú¤Ç¤¢¤ë¤³¤È¤òɽ¤·¤Æ¤¤¤ë¡£
+
+</DD>
+<DT><STRONG>(b)</STRONG></DT>
+<DD>ʸ»ú <B>a</B> ¤Î°À <code>(<-lowercase ?A)</code> ¤Ï¡¢Ê¸»ú
+ <B>a</B> ¤¬Ê¸»ú <B>A</B> ¤Î¾®Ê¸»ú¤Ç¤¢¤ë¤³¤È¤òɽ¤·¤Æ¤¤¤ë¡£
+
+</DD>
+</DL>
+</DD>
+</DL>
+
+<P>
+
+<H2><A NAME="SECTION00412000000000000000"></A>
+<A NAME="Character_Specification"></A>
+<BR>
+ʸ»ú»ØÄê·Á¼°
+</H2>
+
+<P>
+UTF-2000 ¼ÂÁõ¤ÎÃæ¤Ç¤Ïʸ»ú¤Ï¥ª¥Ö¥¸¥§¥¯¥È¤Î°ì¼ï¤È¤·¤ÆÉä¹æ²½¤»¤º¤Ë°·¤¦¤³
+¤È¤¬¤Ç¤¤ë¤¬¡¢UTF-2000 ¼ÂÁõ¤Î³°¤ÎÀ¤³¦¤È¤Î´Ö¤Ç¤Ï¤Ê¤ó¤é¤«¤ÎËÝÌõ¼êË¡¤¬É¬
+ÍפȤʤ롣
+
+<P>
+¤³¤Î¤È¤¡¢¤â¤·Éä¹æ²½Ê¸»ú½¸¹ç¤¬ÍøÍѲÄǽ¤Ç¤«¤Äɽ¸½¤·¤¿¤¤Ê¸»ú¤ò½½Ê¬¤Ëɽ¸½
+²Äǽ¤Ç¤¢¤ë¤Ê¤é¡¢¤½¤ÎÉä¹æ²½Ê¸»ú½¸¹ç¤ÎÉä¹ç°ÌÃÖ¤ò»È¤Ã¤Æ¤½¤Îʸ»ú¤òɽ¸½¤¹¤ë
+¤³¤È¤¬¤Ç¤¤ë¡Ê¤³¤ÎÌÜŪ¤Î¤¿¤á¤Ë XEmacs UTF-2000 ¤Ï
+<A HREF="node4.html#sec:coded-charset">4.2</A> Àá¤Ç½Ò¤Ù¤¿ <I>coded-charset</I> µ¡Ç½¤òÍÑ°Õ¤·¤Æ
+¤¤¤ë¡Ë¡£¤·¤«¤·¤Ê¤¬¤é¡¢É½¸½¤·¤¿¤¤Ê¸»ú¤¬ÍøÍѲÄǽ¤ÊÉä¹æ²½Ê¸»ú½¸¹ç¤Ë¼ýÏ¿¤µ
+¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤ä¡¢Âбþ¤¹¤ëʸ»ú¤¬¼ýÏ¿¤µ¤ì¤Æ¤¤¤Æ¤â¤½¤³¤Çµ¬Äꤵ¤ì¤¿Ãê¾Ýʸ
+»ú¤Èɽ¸½¤·¤¿¤¤Ê¸»ú¤È¤Îº¹°Û¤¬µöÍƤǤ¤Ê¤¤¾ì¹ç¡¢Éä¹æ²½Ê¸»ú½¸¹ç¤òÍѤ¤¤ë¤³
+¤È¤Ï¤Ç¤¤Ê¤¤¡£
+
+<P>
+¤½¤Î¤è¤¦¤ÊÌäÂê¤ò²ò·è¤¹¤ë¤¿¤á¤Ë¤Ï UTF-2000 Êý¼°¤Ë´ð¤Å¤Ê¸»ú¥ª¥Ö¥¸¥§¥¯¥È
+¤ÎÀ¼Á¤òÎóµó¤¹¤ë¤è¤¦¤Ê·Á¼°¤¬¤¢¤ì¤ÐÎɤ¤¡£¤³¤¦¤·¤¿¤â¤Î¤È¤·¤Æ XEmacs
+UTF-2000 ¤Ç¤Ï<I>ʸ»ú»ØÄê (character-specification; char-spec)</I>·Á¼°
+¤òµ¬Äꤷ¤Æ¤¤¤ë¡£
+
+<P>
+ʸ»ú»ØÄê¤Î·Á¼°¤Ï Lisp ¤ÎÏ¢Áۥꥹ¥È (association-list) ¤Ç¡¢¥ê¥¹¥È¤Î³ÆÍ×
+ÁǤ¬³Æʸ»ú°À¤òɽ¸½¤¹¤ë¡£Ï¢Áۥꥹ¥È¤Î¸° (key) Éô¡Ê³ÆÍ×ÁǤÎÀèƬ (car)
+Éô¡Ë¤¬Â°À̾¤òɽ¤·¡¢Ï¢Áۥꥹ¥È¤ÎÃÍ (value) Éô¡Ê³ÆÍ×ÁǤλĤê (cdr) Éô¡Ë
+¤¬Â°ÀÃͤòɽ¤¹¡£
+
+<P>
+ʸ»ú»ØÄ꤬ɽ¤¹°ÕÌ£¤Ï¤½¤ÎÀ¼Á¤òͤ¹¤ëÃê¾Ýʸ»ú¡Ê¶ñ¾Ýʸ»ú¡Ê½ñ¤«¤ì¤¿Ê¸»ú¡Ë
+¤Î½¸¹ç¡Ë¤Ç¤¢¤ë¡£
+
+<P>
+¤Ê¤ª¡¢¤³¤Î·Á¼°¤Ï´Ø¿ô define-char ¤Î°ú¿ô¤Ç»ØÄꤵ¤ì¤ë¤â¤Î¤ÈƱ¤¸¤Ç¤¢¤ë¡£
+
+<P>
+
+<H2><A NAME="SECTION00413000000000000000">
+ʸ»ú»²¾È·Á¼°</A>
+</H2>
+
+<P>
+ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë¤ª¤¤¤Æʸ»ú´Ö¤Î´Ø·¸¤òµ½Ò¤¹¤ë¤è¤¦¤Ê¾ì¹ç¡¢Ãͤ˵ºÜ¤¹¤ë
+ʸ»ú¤Î¾¤Ëʸ»ú´Ö¤Î´Ø·¸¤Ë¤â°À¤òÉÕ¤±¤¿¤¤¾ì¹ç¤¬¤¢¤ë¡£Î㤨¤Ð¡¢Ê¸»ú¤ÎÀµµ¬
+²½¤ò¹Ô¤Ê¤¦¾ì¹ç¡¢¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë¤è¤Ã¤ÆÀµµ¬²½µ¬Â§¤¬°Û¤Ê¤ë¤Î¤Ç¡¢¤³¤Î¤¿
+¤á¤Î°ÛÂλú¥Ç¡¼¥¿¥Ù¡¼¥¹¤òºî¤ë¾ì¹ç¡¢¤É¤ÎÀµµ¬²½µ¬Â§¤òÍѤ¤¤Æ¤¤¤ë¤«¤òµºÜ¤¹
+¤ëɬÍפ¬¤¢¤ë¡£¤Þ¤¿¡¢³Ø½ÑŪ¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹¤òºî¤ë¾ì¹ç¤Ë¤ª¤¤¤Æ¡¢Ê¸»ú³Ø¾å¤Î
+³ØÀ⤬°Û¤Ê¤ë¾ì¹ç¤Ë½Ðŵ¤ä¤É¤Î³ØÀâ¤òÍѤ¤¤Æ¤¤¤ë¤«¤Ê¤É¤òµºÜ¤¹¤ëɬÍפ¬¤¢¤ë¡£
+¤³¤Î¾¡¢ÃÎŪºâ»º¸¢¤Î´ÉÍý¤ò¹Ô¤Ê¤¦¾ì¹ç¤Ë¤â¥Ç¡¼¥¿¤Î½Ðŵ¤ä¸¢Íø¾ðÊó¤òµÏ¿¤¹
+¤ëɬÍפ¬¤¢¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤ÊÌÜŪ¤Î¤¿¤á¤Ë¡¢XEmacs UTF-2000 ¤Ç¤Ï<I>ʸ»ú»²¾È
+(character-reference; char-ref)</I> ·Á¼°¤òµ¬Äꤷ¤Æ¤¤¤ë¡£
+
+<P>
+ʸ»ú»²¾È¤Î·Á¼°¤Ï Lisp ¤Î°À¥ê¥¹¥È (property-list) ¤Ç¤¢¤ë¡£¤³¤³¤Ç¤ÏǤ
+°Õ¤Î°À¤¬ÍøÍѲÄǽ¤Ç¤¢¤ë¤¬¡¢´ö¤Ä¤«¤Î°À̾¤ËÂФ·¤Æ¤Ï¤½¤Î°ÕÌ£¤¬Í½¤áµ¬Äê
+¤µ¤ì¤Æ¤¤¤ë¡£
+
+<P>
+°Ê²¼¤Ë°ÕÌ£¤¬µ¬Äꤵ¤ì¤Æ¤¤¤ë°À¤Ë¤Ä¤¤¤ÆÀâÌÀ¤¹¤ë¡§
+
+<P>
+<DL>
+<DT><STRONG>:char</STRONG></DT>
+<DD>»²¾È¤µ¤ì¤ëʸ»ú
+
+<P>
+[·¿] ʸ»ú¡¢¤â¤·¤¯¤Ï¡¢Ê¸»ú»ØÄê
+
+<P>
+</DD>
+<DT><STRONG>:source</STRONG></DT>
+<DD>½Ðŵ¡¦ÅµµòÅù
+
+<P>
+[·¿] ½Ðŵ¡¦Åµµò¤òɽ¤¹¥·¥ó¥Ü¥ë¡Ê½Ðŵ¥·¥ó¥Ü¥ë¡Ë¤Î¥ê¥¹¥È¡£
+
+<P>
+°Ê²¼¤Ë XEmacs UTF-2000 ¤Î´ðËÜʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÇÍѤ¤¤Æ¤¤¤ë½Ðŵ¥·¥ó¥Ü¥ë
+¤òÎóµó¤¹¤ë¡£²æ¡¹¤Ï´ÁÀÒ¤ª¤è¤Ó¸½ÂåÃæ¹ñʸ¸¥¤ËÂФ¹¤ë½Ðŵ¥·¥ó¥Ü¥ë¤Ï¹ñºÝŪ¤Ë
+ÍѤ¤¤é¤ì¤Æ¤¤¤ëÃæ¹ñ¸ì¤Î¥Ô¥ó¥¤¥óɽµ¤òºÎÍѤ¹¤ë¤³¤È¤Ë¤·¤¿¤¬¡¢Îò»ËŪ»ö¾ð¤«
+¤éÆüËܸì¥í¡¼¥Þ»úɽµ¤Î¤â¤Î¤â¸ºß¤·¤Æ¤¤¤ë¡£É½ <A HREF="node4.html#tab:source-symbol">4.1.3</A>
+¤Ç¤Ï¡¢º£¸åÍѤ¤¤Æ¤¤¤¯½Ðŵ¥·¥ó¥Ü¥ë̾¤ò¡Ö̾Á°¡×¤ËµºÜ¤·¡¢Îò»ËŪ»ö¾ð¤«¤é¸½
+ºßÍѤ¤¤Æ¤¤¤ëÆüËܸì¥í¡¼¥Þ»úɽµ¤Î½Ðŵ¥·¥ó¥Ü¥ë¤ò¡ÖÂåÂØ̾¾Î¡×¤ËµºÜ¤·¤Æ¤¤
+¤ë¡£
+
+<P>
+<BR><P></P>
+<DIV ALIGN="CENTER">
+ <A NAME="tab:source-symbol"></A> <DIV ALIGN="CENTER">
+ </DIV>
+<P>
+<BR>
+<DIV ALIGN="CENTER"> <A NAME="481"></A>
+<TABLE CELLPADDING=3 BORDER="1">
+<CAPTION><STRONG>Table 4.1:</STRONG>
+ʸ»ú»²¾È¤Ë¤ª¤±¤ë :source °À</CAPTION>
+<TR><TD ALIGN="LEFT">̾Á°</TD>
+<TD ALIGN="LEFT">ÂåÂØ̾¾Î</TD>
+<TD ALIGN="LEFT">ÆâÍÆ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">chuuka-daijiten</TD>
+<TD ALIGN="LEFT">Ãæ²ÚÂç»úŵ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">doubun-tsuukou</TD>
+<TD ALIGN="LEFT">ƱʸÄ̹Í</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">gyokuhen</TD>
+<TD ALIGN="LEFT">¶ÌÊÔ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">henkai</TD>
+<TD ALIGN="LEFT">ÊÓ³¤</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">inkai</TD>
+<TD ALIGN="LEFT">±¤²ñ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">inkaiho</TD>
+<TD ALIGN="LEFT">±¤²ñÊá</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">jii</TD>
+<TD ALIGN="LEFT">»ú×Ã</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">jiiho</TD>
+<TD ALIGN="LEFT">»ú×ÃÊá</TD>
+</TR>
+<TR><TD ALIGN="LEFT">jiyun</TD>
+<TD ALIGN="LEFT">shuuin</TD>
+<TD ALIGN="LEFT">½¸±¤</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">kaihen</TD>
+<TD ALIGN="LEFT">³¤ÊÓ</TD>
+</TR>
+<TR><TD ALIGN="LEFT">kangxi</TD>
+<TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">¹¯ô¦»úŵ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">kouin</TD>
+<TD ALIGN="LEFT">¹±¤</TD>
+</TR>
+<TR><TD ALIGN="LEFT">morohashi-daikanwa</TD>
+<TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">Âç´Áϼŵ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">ruishuu-meigishou</TD>
+<TD ALIGN="LEFT">ÎàæÜ̾µÁ¾¶</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">seiin</TD>
+<TD ALIGN="LEFT">Àµ±¤</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">seiji-tsuu</TD>
+<TD ALIGN="LEFT">Àµ»úÄÌ</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">setumon-tuukun-teisei</TD>
+<TD ALIGN="LEFT">ÀâʸÄÌ·±ÄêÀ¼</TD>
+</TR>
+<TR><TD ALIGN="LEFT">shouwen</TD>
+<TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">Àâʸ²ò»ú</TD>
+</TR>
+<TR><TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">sougen-irai-zokujifu</TD>
+<TD ALIGN="LEFT">Á׸µ°ÊÍ读úÉè</TD>
+</TR>
+<TR><TD ALIGN="LEFT">yuquan</TD>
+<TD ALIGN="LEFT"> </TD>
+<TD ALIGN="LEFT">¶ÌÀô</TD>
+</TR>
+</TABLE></DIV>
+</DIV>
+<BR>
+
+<P>
+</DD>
+</DL>
+
+<P>
+
+<H1><A NAME="SECTION00420000000000000000"></A>
+<A NAME="sec:coded-charset"></A>
+<BR>
+Éä¹ç°ÌÃÖ°À
+</H1>
+
+<P>
+<A HREF="node4.html#sec:coded-charset">4.2</A> Àá¤Ç½Ò¤Ù¤¿¤è¤¦¤Ë¡¢XEmacs UTF-2000 ¤Ç¤Ï
+coded-charset ¤Î̾Á°¤ò°À̾¤È¤¹¤ëʸ»ú°À¤Ï coded-charset ¤Ë¤ª¤±¤ëÉä
+¹ç°ÌÃÖ¤òɽ¤¹ÆÃÊ̤Êʸ»ú°À¤Ç¤¢¤ë¡£¤³¤Î°À¤Ë´Ø¤¹¤ë¾ðÊó¤Ï¡¢¥Õ¥¡¥¤¥ëÆþ½Ð
+ÎϤʤɤˤª¤±¤ëʸ»úÉä¹ç¤ÎÊÑ´¹½èÍý¤Ë¤ª¤¤¤ÆÍøÍѤµ¤ì¤ë¡£
+
+<P>
+Éä¹ç°ÌÃÖ°À¤ÎÃͤηÁ¼°¤ÏÀ°¿ô¤Ç¤¢¤ë¡£À°¿ôÃͤΤȤêÆÀ¤ëÈϰϤÏÂбþ¤¹¤ë
+coded-charset ¤Ë¤è¤Ã¤ÆÀ©Ì󤵤ì¤ë¡£
+
+<P>
+¤È¤³¤í¤Ç¡¢¸½ºß¤Î¤È¤³¤í¡¢¤¢¤ëʸ»ú°À̾¤¬Éä¹ç°ÌÃÖ°À̾¤Ç¤¢¤ë¤«¤É¤¦¤«¤Ï¡¢
+¤½¤Î°À̾¤ò̾Á°¤È¤¹¤ë coded-charset ¤¬Â¸ºß¤¹¤ë¤«¤Ë¤è¤Ã¤Æ¤¤¤ë¡£¤¹¤Ê¤ï
+¤Á¡¢Éä¹ç°ÌÃÖ°À¤òɽ¤¹Â°À̾¤Î̿̾µ¬Ìó¤Ïº£¤Î¤È¤³¤í¸ºß¤·¤Æ¤ª¤é¤º¡¢Â°À
+̾¤À¤±¤Ç¤Ï¤½¤Îʸ»ú°À¤¬Éä¹ç°ÌÃÖ°À¤«¤É¤¦¤«¤òµ¡³£Åª¤Ë·èÄꤹ¤ë¤³¤È¤¬¤Ç
+¤¤Ê¤¤¡£¸½ºß¤Î XEmacs UTF-2000 ¤Ë¤ª¤¤¤Æ¤ÏÊÌ¤Ë coded-charset ¤¬ÄêµÁ¤µ¤ì
+¤ë¤¿¤á¤Ë¤³¤ì¤ÇÌäÂê¤Ï¤Ê¤¤¤Î¤Ç¤¢¤ë¤¬¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤È¤·¤Æ¤Ï²¿¤é¤«
+¤Îµ¬Ì󤬤¢¤Ã¤¿Êý¤¬Îɤ¤¤«¤âÃΤì¤Ê¤¤¡£
+
+<P>
+
+<H1><A NAME="SECTION00430000000000000000">
+¢Íucs °À</A>
+</H1>
+
+<P>
+The attribute named <code>=>ucs</code> is used to indicate a UCS code point of
+a character. If a user would not like to unify characters that are
+unified in UCS, or would like to define a character that is not
+included in UCS, this attribute is available to specify the nearest
+UCS code point.
+
+<P>
+If a user need to refer a code point of UCS, the user can use
+<BLOCKQUOTE>
+<TT>(or (get-char-attribute CHAR 'ucs)
+ (get-char-attribute CHAR '<code>=>ucs</code>))</TT>
+
+</BLOCKQUOTE>
+instead of <TT>(get-char-attribute CHAR 'ucs)</TT>.
+
+<P>
+The information of <code>=>ucs</code> attributes are stored in the internal
+variants database,
+and users can find variant characters corresponding
+to a UCS code point by the following function:
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>char-variants</B> (<I>character</I>)
+
+<BLOCKQUOTE>
+This function returns variants of <I>character</I>.
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>Perhaps there are another kind of variant relations, so we are
+ planning to extend this feature more generally.
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+
+<H1><A NAME="SECTION00440000000000000000"></A>
+<A NAME="sec:decomposition"></A>
+<BR>
+¢ªdecomposition °À
+</H1>
+
+<P>
+The attribute named <code>->decomposition</code> is used to specify combining
+sequences of composite (precomposed) characters. The value of
+<code>->decomposition</code> attribute is a list of characters or
+character-specifications <A HREF="node4.html#Character_Specification">4.1.2</A>, which means
+that a character defined with a <code>->decomposition</code> attribute can be
+interpreted as the sequence of characters specified by the value of
+the attribute.
+For example, if <B>á</B> has an attribute
+<TT>(<code>->decomposition</code> ?a ?´)</TT>,
+ the sequence <TT>(?a ?´)</TT> can be composed into <B>á</B>.
+
+<P>
+This information can be used in the coding-system features, which is
+code-conversion features of the Mule API <A NAME="tex2html16"
+ HREF="footnode.html#foot511"><SUP><IMG ALIGN="BOTTOM" BORDER="1" ALT="[*]"
+ SRC="/usr/share/latex2html/icons/footnote.png"></SUP></A>.
+
+<P>
+In addition, there is a builtin function to find a precomposed
+character from a list of combining sequence.
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>get-composite-char</B> (<I>list</I>)
+
+<BLOCKQUOTE>
+This function returns a character composed from elements of the
+ <I>list</I>.
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>Each element is a character, an integer or a
+ character-specification. If an element is an integer, it is
+ interpreted as a code point of UCS character.
+
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+
+<H1><A NAME="SECTION00450000000000000000">
+´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¾ðÊó</A>
+</H1>
+
+<P>
+¿¤¯¤Î´Á»ú¤ÏÊФÈÚդʤɤÎÉôÉʤÎÁȤ߹ç¤ï¤»¤Ë¤è¤Ã¤Æ¹½À®¤µ¤ì¤Æ¤¤¤ë¡£¤·¤«¤·
+¤Ê¤¬¤é¡¢½¾Íè¤Î¿¤¯¤ÎÉä¹æ²½ÊýË¡¤Ç¤ÏÁȤ߹ç¤ï¤µ¤ì¤¿´Á»ú¤òñ°Ì¤Ë¤·¤Æ°·¤ï¤ì
+¤Æ¤ª¤ê¡¢´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¹½Â¤¤Ë´Ø¤¹¤ë¾ðÊó¤ÏÉä¹æ²½¤ÎÂоݤȤʤé¤Ê¤¤¤³
+¤È¤¬Â¿¤«¤Ã¤¿¡£¤³¤Î¤¿¤á¡¢¼«Í³¤ËÍøÍѲÄǽ¤Ê¥Ç¡¼¥¿¤ÎÃßÀѤâÉÔ½½Ê¬¤Ç¤¢¤ë¡£
+
+<P>
+ËÜ¥×¥í¥¸¥§¥¯¥È¤Ç¤Ï´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¾ðÊó¤òÍøÍѤ¹¤ë¤¿¤á¤Ë
+<A HREF="node4.html#sec:ideographic-structure">4.5.5</A> Àá¤Ç½Ò¤Ù¤ë
+<B>ideographic-structure °À</B>¤òÄêµÁ¤·¡¢XEmacs UTF-2000 ¤Ë¤ª¤¤¤Æ
+¤³¤Î°À¤ò°·¤¨¤ë¤è¤¦¤Ë¤·¤¿¡£
+
+<P>
+¤Þ¤¿¡¢´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¾ðÊó¤Ë´Ø¤¹¤ë¤³¤ì¤Þ¤Ç¤Î»î¤ß¤òÄ´ºº¤·¡¢¼«Í³¤ËÍø
+ÍѲÄǽ¤Ê¤â¤Î¤ËÂФ·¤Æ¤Ï ideographic-structure ·Á¼°¤ËÊÑ´¹¤¹¤ë¤¿¤á¤Î¥×¥í
+¥°¥é¥à¤òºîÀ®¤·¤¿¡£
+
+<P>
+
+<H2><A NAME="SECTION00451000000000000000">
+What are glyph expressions</A>
+</H2>
+
+<P>
+Kanji characters are very visibly composed not of atomic units, but of
+a relatively small number of components. The tradition of defining a
+character by its components is as old as the script itself. Encoding
+of Kanji in computers, however, has so far failed to take advantage of
+this structural feature and treated every Kanji as an atomic unit. To
+make Kanji encoding more efficient, it has been suggested to encode
+these parts and compose the characters on the fly. This will make the
+rendering process more complex and potentially less appealing. The
+feasability of this will depend on the applictions available for
+rendering and certainly will require more research. Even if not used
+as the primary encoding in text, however, such a character component
+database will still serve an important purpose for classifying,
+analysing and retrieving characters.
+
+<P>
+Since the 1970's, research concerning such an analytic encoding has
+been conducted in Taiwan, China, Japan and elsewhere. One of the most
+important and thoroughly researched proposal has been that of Hsieh
+Ching-chun (¼ÕÀ¶½Ó) of Academia Sinica, Taiwan. Building on previous
+results, he started in 1990 to build a database of the structure of
+Kanji characters. Since this work was carried out at his `Chinese
+Document Processing' lab, it came to be known as the CDP database.
+Christian Wittern has been involved with this project since 1994.
+Currently, the database contains glyph expressions of more than 55500
+characters, including all characters contained in the <I>´Á¸ìÂç¼Åµ</I>.
+The database has been developed on the Traditional Chinese version of
+Windows using Access as the database engine. The user interface only
+runs on versions of Chinese Windows from Windows 95 up to Windows ME.
+Professor Hsieh graciously gave permission to port the content of the
+CDP database to the UTF-2000 project and release it under the GPL.
+
+<P>
+
+<H2><A NAME="SECTION00452000000000000000">
+The CDP database</A>
+</H2>
+
+<P>
+The expressions in the CDP database are based on Big5, the local
+encoding for Kanji characters mostly used in Taiwan. For the purpose
+of expressing the parts of characters, that are not characters
+themselves, more than 2000 codepoints from the private use area (PUA)
+of Big5 had been used. Furthermore, the CDP database uses a set of
+only three operators for connecting the characters, although in
+practice, this has been expanded to 11 due to the introduction of
+shortcut operators for handling multiple occurrences of the same
+component in one character. Figure <A HREF="node4.html#fig:mitou-report01">4.5.2</A> shows a
+list of these operators. There are three more operator-like
+characters, which are used when embedding glyph expressions into
+running text.
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="fig:mitou-report01"></A><A NAME="533"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 4.1:</STRONG>
+The connecting operators used in the CDP</CAPTION>
+<TR><TD>
+<DIV ALIGN="CENTER">
+<!-- MATH
+ $\scalebox{0.5}{\includegraphics{mitou-report01.eps}}$
+ -->
+<IMG
+ WIDTH="212" HEIGHT="327" ALIGN="BOTTOM" BORDER="0"
+ SRC="images/mitou-report01.jpg"
+ ALT="\scalebox{0.5}{\includegraphics{mitou-report01.eps}}">
+</DIV></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+
+<H2><A NAME="SECTION00453000000000000000">
+The CBETA database</A>
+</H2>
+
+<P>
+Another database of Chinese characters and glyph expressions, if
+somewhat smaller than the CDP with around 13000 characters at the
+moment, is the database developed by the Chinese Buddhist Electronic
+Text Association (CBETA). This is a sideproduct of CBETA's
+groundbreaking work of creating an electronic version of Chinese
+Buddhist scriptures. So far, more than 80 million characters of text
+have been input, carefully proofread and marked up in XML according to
+the Guidelines of the Text Electronic Initiative. The base character
+set used for this is again Big5. Characters that could not be found
+in Big5 have been collected and expressed with glyph expressions. The
+CBETA database again uses a simple system of three basic connecting
+operators, expressed with ASCII interpunction as follows:
+
+<P>
+<BR><P></P>
+<DIV ALIGN="CENTER">
+ <A NAME="tab:cbeta-op"></A> <DIV ALIGN="CENTER">
+ </DIV>
+<P>
+<BR>
+<DIV ALIGN="CENTER"> <A NAME="539"></A>
+<TABLE CELLPADDING=3 BORDER="1">
+<CAPTION><STRONG>Table 4.2:</STRONG>
+The operators used in the CBETA character database</CAPTION>
+<TR><TD ALIGN="LEFT">operator</TD>
+<TD ALIGN="LEFT">meaning</TD>
+</TR>
+<TR><TD ALIGN="LEFT">/</TD>
+<TD ALIGN="LEFT">top/bottom connection</TD>
+</TR>
+<TR><TD ALIGN="LEFT"><IMG
+ WIDTH="12" HEIGHT="13" ALIGN="BOTTOM" BORDER="0"
+ SRC="img12.png"
+ ALT="$*$"></TD>
+<TD ALIGN="LEFT">left/right connection</TD>
+</TR>
+<TR><TD ALIGN="LEFT">@</TD>
+<TD ALIGN="LEFT">enclosure connection</TD>
+</TR>
+</TABLE></DIV>
+</DIV>
+<BR>
+
+<P>
+The CBETA character database avoids the reliance on characters from
+the PUA. Instead, character components are expressed by using
+arithmetic operators - and + for deletion and replacement of
+characters. In this manner, a glyph exression for the character Ãþ
+could thus be constructed as: [Á×-ÌÚ+ζ], here the part ÌÚ is replaced
+with ζ. Using this simple arithmetic, a surprisingly large number of
+characters can be expressed without much effort. Some expressions do
+however get more complicated, for example
+[((((\8f¶¹-¸ý)-¾®)-Æü+(¹©/½½))*»Ù)/»®].
+
+<P>
+Since Christian Wittern has been involved with the CBETA project for
+some time, it has been possible to gain permission to include the
+CBETA character database into the UTF-2000 character database. This
+is especially interesting, since the CBETA data are derived directly
+from text input and sources for the characters are easily determined,
+quite contrary to dictionaries and standard documents, where it is not
+easy to find real world examples for some of the characters.
+
+<P>
+
+<H2><A NAME="SECTION00454000000000000000"></A>
+<A NAME="sec:ideographic-structure"></A>
+<BR>
+ideographic-structure °+</H2>
+
+<P>
+´Á»ú¤ÎÉôÉÊÁȤ߹ç¤ï¤»¹½Â¤¤Ë´Ø¤¹¤ë¾ðÊó¤ò XEmacs UTF-2000 ¤ÇÍøÍѤ¹¤ë¤¿¤á
+¤Ë<B>ideographic-structure °À</B>¤òÄêµÁ¤·¤¿¡£
+
+<P>
+ideographic-structure °À¤Î·¿¤Ï¡¢Ê¸»ú¡¢Ê¸»ú»ØÄê¤Þ¤¿¤Ïʸ»ú»²¾È¤Î¥ê¥¹¥È
+¤Ç¤¢¤ë¡£
+
+<P>
+ideographic-structure °À¤ÎÃͤÎÍ×ÁǤȤ·¤Æ»ØÄꤵ¤ì¤¿Ê¸»ú¡Ê¤ª¤è¤Óʸ»ú»Ø
+Äê¡¢¤Þ¤¿¤Ï¡¢Ê¸»ú»²¾È¤Î :char °À¤Ç»ØÄꤵ¤ì¤¿Ê¸»ú¡¦Ê¸»ú»²¾È¡Ë¤Ï
+ideographic-structure °À¤ò¼è¤ë¤³¤È¤¬¤Ç¤¤ë¡£¤³¤ì¤Ë¤è¤ê¡¢
+ideographic-structure °À¤ÏÆþ¤ì»Ò¹½Â¤¤ò¼è¤ë¤³¤È¤¬¤Ç¤¤ë¡£
+
+<P>
+
+<H2><A NAME="SECTION00455000000000000000">
+Extending the UTF-2000 character database</A>
+</H2>
+
+<P>
+The Unicode Standard introduced in version 3.0 a set of socalled
+`IDEOGRAPHIC DESCRIPTION CHARACTER' (IDC) to allow the construction of
+Kanji glyph sequences. This set of operators followed a proposal from
+China, based on research done there and describes 12 operators. For
+the purpose of using glyph expressions in the UTF-2000 character
+database, we decided to use the operator set from Unicode/ISO 10646.
+This set is shown in Figure <A HREF="node4.html#fig:mitou-report02">4.5.4</A>.
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="fig:mitou-report02"></A><A NAME="554"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 4.2:</STRONG>
+The IDC from Unicode/ISO 10646</CAPTION>
+<TR><TD>
+<DIV ALIGN="CENTER">
+<!-- MATH
+ $\scalebox{0.5}{\includegraphics{mitou-report02.eps}}$
+ -->
+<IMG
+ WIDTH="462" HEIGHT="619" ALIGN="BOTTOM" BORDER="0"
+ SRC="images/mitou-report02.gif"
+ ALT="\scalebox{0.5}{\includegraphics{mitou-report02.eps}}">
+</DIV></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+The adaption of the CDP and CBETA database and subsequent inclusion in
+the UTF-2000 character database thus involved the following steps:
+
+<P>
+
+<OL>
+<LI>Converting the underlying character code from Big5 to Unicode
+</LI>
+<LI>Mapping of entries for characters outside of the reference
+encoding Big5 to Unicode
+</LI>
+<LI>Mapping of the characters from the PUA to Unicode
+where possible
+</LI>
+<LI>Where the previous step did not produce a mapping,
+a recursive use of IDC was applied where possible
+</LI>
+<LI>Modify the glyph expressions to adjust for the
+different scope of the operators
+</LI>
+<LI>Add new glyph expressions for characters not in CDP
+</LI>
+</OL>
+
+<P>
+Apart from this, some related supporting tasks were also necessary.
+Since it is difficult to input unknown and rare Kanji characters, a
+new input method had to be devised. For this purpose, a table of
+input keys of the Four Corner system originally created by Christian
+Wittern for the Kanji characters in CNS-11642:1992 as part of the
+`KanjiBase' has been ported and adopted so that it could be used
+within UTF-2000. Additionally, input keys for Kanji radicals in
+different shapes and other characters from Unicode that where not yet
+covered (essentially, characters with less than 7 strokes) have been
+added. This newly expanded input table contains now more than 50000
+input keys and will be part of the UTF-2000 character database.
+
+<P>
+Quite a different problem, that requires further attention is the way
+the glyph expressions are composed. The CDP database uses a
+`intuitive' approach and splits characters where the most logical
+cut-off line is. This is, however not always the ethymological
+correct way of splitting. In the UTF-2000 character database, we
+prefer to have ethymological splitting and new expressions are added
+in this way. The task of systematically identifying and changing the
+intuitive splittings has not yet been done.
+
+<P>
+The whole process, which is not yet fully completed, involved a
+tedious and time consuming task of meticulously checking the accuracy
+of every single entry for more than 70000 characters. At the time of
+this writing, the porting and checking is done in a first go for more
+than 40000 characters. This is an important and fundamental addition
+to the UTF-2000 character database.
+
+<P>
+
+<P></P>
+<DIV ALIGN="CENTER"><A NAME="fig:mitou-report03"></A><A NAME="564"></A>
+<TABLE>
+<CAPTION ALIGN="BOTTOM"><STRONG>Figure 4.3:</STRONG>
+A table of glyph expressions in XEmacs UTF-2000</CAPTION>
+<TR><TD>
+<DIV ALIGN="CENTER">
+<!-- MATH
+ $\scalebox{0.5}{\includegraphics{mitou-report03.eps}}$
+ -->
+<IMG
+ WIDTH="610" HEIGHT="487" ALIGN="BOTTOM" BORDER="0"
+ SRC="images/mitou-report03.jpg"
+ ALT="\scalebox{0.5}{\includegraphics{mitou-report03.eps}}">
+</DIV></TD></TR>
+</TABLE>
+</DIV><P></P>
+
+<P>
+
+<H2><A NAME="SECTION00456000000000000000">
+Additional benefits</A>
+</H2>
+
+<P>
+As has been mentioned above, a table of input keys for the Four Corner
+method has been ported to UTF-2000 to be used as input keys. Since
+the Four Corner numbers are systematically assigned to the four
+corners of a character, it is possible to generate new Four Corner
+values based on existing characters, if the composition of characters
+is known. Since this information is exactly the content of the glyph
+expressions, new Four Corner input keys can automatically be
+generated, thus covering the whole 70000 Unicode characters. This
+provides also an additional method for proofreading both the glyph
+expression data and the Four Corner input codes.
+
+<P>
+
+<P>
+<HR>
+<!--Navigation Panel-->
+<A NAME="tex2html84"
+ HREF="node5.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html82"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html76"
+ HREF="node3.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html85"
+ HREF="node5.html">Topic Maps ¤Ë´ð¤Å¤¯Âç°èʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<B> Up:</B> <A NAME="tex2html83"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html77"
+ HREF="node3.html">ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯Ê¸½ñÊÔ½¸·Ï</A>
+<!--End of Navigation Panel-->
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<html>
+ <!--THIS FILE IS GENERATED FROM AN XML MASTER.
+ DO NOT EDIT-->
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+
+ <title>Mitou project: Model and implementation of a Character
+ Object Database
+ </title>
+ </head>
+ <body>
+ <h2>Contents</h2>
+ <ul class="toc">
+ <li class="toc">5. <a class="toc" href="#mitou-report1-div-d0e75">Topic Maps</a><ul class="toc">
+ <li class="toc">5.1. <a class="toc" href="#mitou-report1-div-d0e80">The topic map paradigm</a></li>
+ <li class="toc">5.2. <a class="toc" href="#mitou-report1-div-d0e130">The character database as a topic map</a></li>
+ <li class="toc">5.3. <a class="toc" href="#mitou-report1-div-d0e251">A Topic Map engine with Zope</a><ul class="toc">
+ <li class="toc">5.3.1. <a class="toc" href="#mitou-report1-div-d0e256">Why Zope?</a></li>
+ <li class="toc">5.3.2. <a class="toc" href="#mitou-report1-div-d0e268">Requirements for a Topic Map engine</a></li>
+ <li class="toc">5.3.3. <a class="toc" href="#mitou-report1-div-d0e301">Implementation details</a></li>
+ <li class="toc">5.3.4. <a class="toc" href="#mitou-report1-div-d0e363">A browser-based interface to the Topic Map engine</a></li>
+ <li class="toc">5.3.5. <a class="toc" href="#mitou-report1-div-d0e446">The interface to XEmacs UTF-2000</a></li>
+ <li class="toc">5.3.6. <a class="toc" href="#mitou-report1-div-d0e569">Evaluation</a></li>
+ </ul>
+ </li>
+ <li class="toc">5.4. <a class="toc" href="#mitou-report1-div-d0e582">Other possibilities</a></li>
+ </ul>
+ </li>
+ </ul>
+
+ <div class="teidiv">
+ <h2><a name="mitou-report1-div-d0e75"></a>5. Topic Maps
+ </h2>
+
+
+ <div class="teidiv">
+ <h3><a name="mitou-report1-div-d0e80"></a>5.1. The topic map paradigm
+ </h3>
+
+
+ <p><a name="d0e85"></a>The Topic Map Standard
+ ‘provides a standardized notation
+ for interchangeably representing information about the
+ structure of information resources used to define topics,
+ and the relationships between topics. ’
+ A set of one or more
+ interrelated documents that employs the notation defined
+ by this International Standard is called a `topic map'. In
+ general, the structural information conveyed by topic maps
+ includes:
+ <ol>
+ <li><a name="d0e95"></a>groupings of addressable information objects
+ around `topics' (`occurrences'), and
+ </li>
+ <li><a name="d0e104"></a>relationships between
+ topics (`associations').
+ </li>
+ </ol>
+
+ </p>
+
+ <p><a name="d0e111"></a>A topic map defines a
+ multidimensional topic space — a space in which the
+ locations are topics, and in which the distances between
+ topics are measurable in terms of the number of
+ intervening topics which must be visited in order to get
+ from one topic to another, and the kinds of relationships
+ that define the path from one topic to another, if any,
+ through the intervening topics, if any. (from the document
+ defining Topic Maps as ISO/IEC 13250:2000)
+ </p>
+
+ <p><a name="d0e114"></a>The standard as published in 2000 includes a
+ serialization format specification in form of a Document
+ Type Definition (DTD) originally using HyTime (ISO/IEC
+ 10744:1992) Architectural Forms and a SGML (ISO/IEC
+ 8879:1986) based syntax. An independent group of vendors
+ started development of a XML based version, which was
+ published as XTM 1.0 in December 2000 and per ballot
+ adopted as an amendment to the ISO standard in December
+ 2001. The development here is based on the XML syntax,
+ which has also quite different elements and structure.
+ </p>
+
+ <p><a name="d0e117"></a>Since SGML/XML based formats are overly verbose
+ (especially XTM 1.0) and awkward to work with, other
+ formats have been suggested, including the `Asymptotic Topic Map Notation, Authoring'
+ (AsTMA, by Robert Barta) and `Linear Topic Map
+ Notation' (LTM, by Lars Marius Garshol). Both
+ are essentially line
+ based and can be easily edited in UTF-2000 and other
+ editors.
+ </p>
+
+ <p><a name="d0e126"></a>Besides defining a serialization format for the exchange of
+ information, the Topic Map standard also includes
+ constructs that are intended to faciliate exchange of
+ information. One of the most important tasks is to
+ reliably identify identical pieces of information across
+ different sources. Towards this end, rules for subsetting
+ and merging of topic maps are laid down in the standard.
+ Topics can be defined with reference to Published Subject
+ Indicators (PSI), which function in a similar way to XML
+ Namespaces.
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h3><a name="mitou-report1-div-d0e130"></a>5.2. The character database as a topic map
+ </h3>
+
+
+
+ <p><a name="d0e137"></a>Characters are used in scripts for the writing of
+ languages, languages are distributed in different areas.
+ The exact form of these characters, as well as their
+ phonetic representation changes over time and area. The
+ adaption of the Topic Map paradigm in a character database
+ tries to use these different axes to organise them in a way
+ that is appropriate to the domain they are encountered
+ in. Characters are thus not only objects in their own
+ right, but these objects are organized in a hierarchy of
+ `super-class / sub-class' and
+ `class / instance' hierarchies.
+ </p>
+
+ <p><a name="d0e146"></a></p>
+
+ <p><a name="d0e148"></a>The topic map currently contains information along the
+ following axes:
+
+ <ul>
+ <li><a name="d0e152"></a>abstract character
+ </li>
+ <li><a name="d0e155"></a>character instances
+ </li>
+ <li><a name="d0e158"></a>variant shapes
+ </li>
+ <li><a name="d0e161"></a>character structure
+ </li>
+ <li><a name="d0e164"></a>language
+ </li>
+ <li><a name="d0e167"></a>readings
+ </li>
+ <li><a name="d0e170"></a>meanings
+ </li>
+ <li><a name="d0e173"></a>time
+ </li>
+ <li><a name="d0e176"></a>space
+ </li>
+ <li><a name="d0e179"></a>frequency of usage
+ </li>
+ <li><a name="d0e182"></a>mappings to coded character sets
+ </li>
+ <li><a name="d0e185"></a>references to dictionaries
+ </li>
+ </ul>
+ </p>
+
+ <p><a name="d0e189"></a>While most of these are organized as occurrences of the
+
+ </p>
+
+ <p><a name="d0e192"></a>It might be appropriate to illustrate this with an
+ example. The character attributes for the character
+ U+03432 when viewed within the UTF-2000 framework
+ might have attributes similar to those shown in <a class="ptr" href="#what-char">Figure 4</a>.
+ </p>
+
+ <p><a name="d0e197"></a><a name="what-char"></a><img src="images/mitou-report04.jpg" alt="The character U+03432 displayed with
 the function."><p>
+ Figure 4
+
+ The character U+03432 displayed with
+ the `what-char-definition' function.
+
+ </p>
+ </p>
+
+ <p><a name="d0e210"></a>Transformed to the topic map notation, the attributes of
+ the same character will look similar to <a class="ptr" href="#tm-examp1">Figure 5</a>
+ content has not changed, only the notation, within the
+ <tt><occurrence></tt> element, the attributes are similar to
+ key / value pairs. What is not visible here, however, is
+ the underlying structure, which has been used to define the
+ topic map.
+ </p>
+
+ <p><a name="d0e218"></a>
+ <a name="tm-examp1"></a><img src="images/mitou-report05.jpg" alt=" The attributes of character U+03432
 in Topic Map notation."><p>
+ Figure 5
+
+ The attributes of character U+03432
+ in Topic Map notation.
+
+ </p>
+ It should also be noted, that the attributes under
+ `ideographic-structure' are not listed
+ as occurences. These attributes are expressed using
+ separate topics for the character components and the
+ <tt><association></tt> element to connect them, as shown in
+ <a class="ptr" href="#tm-examp2">Figure 6</a>.
+ </p>
+
+ <p><a name="d0e238"></a>
+ <a name="tm-examp2"></a><img src="images/mitou-report06.jpg" alt=" The ideographic-structure of character U+03432
 in Topic Map notation."><p>
+ Figure 6
+
+ The ideographic-structure of character U+03432
+ in Topic Map notation.
+
+ </p>
+
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h3><a name="mitou-report1-div-d0e251"></a>5.3. A Topic Map engine with Zope
+ </h3>
+
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e256"></a>5.3.1. Why Zope?
+ </h4>
+
+
+ <p><a name="d0e261"></a>Zope (Zope Object Publishing Environment) is an
+ object-oriented Web-Application server developped by Zope
+ Corporation (former Digital Creations) using a
+ community-based open-source development model. It is
+ written in Python, with only a few critical parts in C.
+ Although it is mostly considered as an environment for rapid
+ development of dynamic Web content, it is originally and
+ formostly an environment for publishing objects. The
+ underlying storage is a object oriented database, which
+ makes it uniquely suited for storing hierarchical data
+ structures like a Topic Map.
+ </p>
+
+ <p><a name="d0e264"></a>Since Zope acts as a Web-Server, it can also be seen as a
+ networked database. It can be accessed through the HTTP
+ protocol, but also through WebDAV and XML-RPC. One of the
+ advantages of using a Zope based implementation is thus that
+ it can also be used as a distributed editing environment and
+ at the same time act as a backend to be accessed from XEmacs
+ UTF-2000.
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e268"></a>5.3.2. Requirements for a Topic Map engine
+ </h4>
+
+
+ <p><a name="d0e273"></a>Since some of the concepts of Topic Maps are quite new
+ and not yet fully fleshed out in the Topic Map community
+ (for example is the Topic Maps Query Language TMQL still
+ in the stage of requirements and no consensus has been
+ reached, what it will mean to query a topic map), some of
+ the more arcane features will not be covered by this
+ prototype. Instead of more demanding Topic Map queries,
+ which might involve inferences and other Topic Map calculus, searches
+ will directly access the data in the Topic Map. Merging
+ directives, which are problematic among other things
+ because of the `Topic Map Basename
+ Constraint' (TMBC) are not initially supported.
+ </p>
+
+ <p><a name="d0e279"></a>The prototype should be able to :
+
+ <ul>
+ <li><a name="d0e283"></a>Import and export data from XEmacs UTF-2000
+ </li>
+ <li><a name="d0e286"></a>Use a network based communiction protocol to communicate
+ </li>
+ <li><a name="d0e289"></a>Provide access to the Topic Map (read/write
+ topics, occurrences and associations)
+ </li>
+ <li><a name="d0e292"></a>Be designed for generic Topic Maps, not for
+ specific data types
+ </li>
+ <li><a name="d0e295"></a>Allow an assessment of the feasability of this approach.
+ </li>
+ </ul>
+
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e301"></a>5.3.3. Implementation details
+ </h4>
+
+
+ <p><a name="d0e306"></a>Zope is extended in functionality by developing add-on
+ modules, called `Products' in
+ Zope-speach. Products can be developped within the
+ Zope-Database based on ZClasses or as file-system based
+ Python classes. In a first implementation, ZClasses
+ have been used.
+ </p>
+
+ <p><a name="d0e312"></a>In this implementation, four classes have been used to
+ represent the different objects of a Topic Map:
+ <ul>
+ <li><a name="d0e316"></a>topicmap: The container item for all the other classes
+ </li>
+ <li><a name="d0e319"></a>topic: Container item for occurrences
+ </li>
+ <li><a name="d0e322"></a>occurrence: Holds the key / value pairs of occurrences
+ </li>
+ <li><a name="d0e325"></a>association: Information about the type, role
+ and value of the members is hold in instance attributes
+ </li>
+ </ul>
+ This data structure was closely modelled on the underlying
+ data structure of the Topic Map serialization format, as
+ realized in the XTM 1.0 DTD. The built-in Zope search
+ engine ZCatalog was used to built indices and access the
+ different information axes. <a class="ptr" href="#zope-man">Figure 7</a>
+ shows a screenshot from the Zope development interface
+ showing the classes being developed.
+ </p>
+
+ <p><a name="d0e332"></a>
+ <a name="zope-man"></a><img src="images/mitou-report07.jpg" alt="The Zope Management screen with the ZClasses
 under development"><p>
+ Figure 7
+
+ The Zope Management screen with the ZClasses
+ under development
+
+ </p>
+
+ </p>
+
+ <p><a name="d0e344"></a>This approach turned out to induce a large overhead for
+ the data and proved problematic for Topic Maps with more
+ than approximately 1000 topics and associations. For this
+ reasons, this approach has been given up.
+ </p>
+
+ <p><a name="d0e347"></a>The next logical step was to use a native Python
+ Product, insted of the ZClasses. This should give better
+ performance, since less overhead is involved, it also
+ allows greater flexibility in the data structures. An
+ additional advantage is that a more efficient development
+ environment could be used due to the fact that the source
+ is on the file system and not in the Zope database.
+ </p>
+
+ <p><a name="d0e350"></a>Performance was slightly improved, but not as much as
+ hoped for. It also turned out that some flaws in the
+ data structure defined for the Python classes did not
+ allow the full expressive power that was required for
+ Topic Maps in XTM 1.0.
+ </p>
+
+ <p><a name="d0e353"></a>Around this time, development activity started once
+ again in the Zope ParsedXML product, which is the Zope
+ product that provides XML functionality. Since an XML
+ Document Object Model (DOM) tree shares some similiarity
+ to the Zope DOM (ZDOM) used to store the Zope objects, it
+ was expected that this approach might scale better. An
+ additional advantage was that Zope procedures could be
+ used to directly expose XML elements in DTML (Document
+ Template Markup Language). For this reason, it was
+ decided to start once again, this time with ZClasses using
+ the ParsedXML product.
+ </p>
+
+ <p><a name="d0e356"></a>Development of this prototype had progressed quite some
+ while, when it was realized that the support for Unicode
+ in Zope, which was introduced in Zope 2.4.0 had some
+ flaws. While UTF-8 could be used with out problems in
+ previous versions, the partial support for Unicode meant
+ that Python UnicodeStrings in some cases could be cast as
+ AsciiStrings, which would crash the process. While some
+ patches became available and development of the Zope core
+ continued to adress this problem, it remained acute even
+ with the recent 2.5.0 release and will probably only
+ resolved in the upcoming Zope 3.0 release, which will be a
+ major rewrite.
+ </p>
+
+ <p><a name="d0e359"></a>While the improvement of the support for Unicode within
+ Zope is important, it remains outside of the scope and
+ timeframe of this project. As a temporary fix therefore,
+ no Unicode characters can be used in the TopicMap engine.
+ While this is unfortunate, since the XML standard
+ explicitly requires conformant XML processors to support
+ at least UTF-8 and UTF-16, there is nothing that can be
+ done about this at the moment, this situation will improve
+ with the arrival of a fully Unicode compliant version of
+ Zope.
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e363"></a>5.3.4. A browser-based interface to the Topic Map engine
+ </h4>
+
+
+ <p><a name="d0e368"></a>When a new Topic Map has been created or imported into
+ the Zope Topic Map engine, it can be explored on the
+ Topic Map overview screen, as shown in <a class="ptr" href="#ztm-overview">Figure 8</a></p>
+
+ <p><a name="d0e372"></a><a name="ztm-overview"></a><img src="images/mitou-report08.jpg" alt="The Topic Map overview screen"><p>
+ Figure 8
+
+ The Topic Map overview screen
+
+ </p>
+
+ </p>
+
+ <p><a name="d0e383"></a>This screen is divided in several parts. The top frame
+ provides a general interface to manage the display of the
+ Topic Map, it also here that other Topic Maps can be
+ selected. This part allows also the addition of new
+ topics as well as global searches over the Topic Map. The
+ frame on the left is for navigating the Topic Map. By
+ default, it shows a list of topics in the topic map.
+ Since this list can be potentially very long, the default
+ length is set to 20, if there are more topics, the list
+ will be displayed in batches. The list can be limited
+ down in various ways:
+ <ul>
+ <li><a name="d0e387"></a>by using the scopes (or themes) defined in the
+ Topic Map
+ </li>
+ <li><a name="d0e390"></a>by searching the Topic Map; this will limit the
+ list to the search results
+ </li>
+ <li><a name="d0e393"></a>by defining new scopes (if the user has the
+ appropriate rights, these can also be stored in the Topic
+ Map and be used in the future)
+ </li>
+ </ul>
+
+ </p>
+
+ <p><a name="d0e398"></a>The main frame shows a short information about this
+ Topic Map engine, this will be used to display the topic
+ details as shown in <a class="ptr" href="#tm-details">Figure 9</a></p>
+
+ <p><a name="d0e402"></a><a name="tm-details"></a><img src="images/mitou-report09.jpg" alt="The details of a topic"><p>
+ Figure 9
+
+ The details of a topic
+
+ </p>
+
+ </p>
+
+ <p><a name="d0e413"></a>The Topic Map engine can not only be used to browse the
+ Topic Map, but also to add or edit new topics, occurrences
+ or associations. A click on the `Add'
+ button in the upper right area of <a class="ptr" href="#ztm-overview">Figure 8</a> will lead to the entry screen
+ in <a class="ptr" href="#tm-add-topic">Figure 10</a></p>
+
+ <p><a name="d0e422"></a>
+ <a name="tm-add-topic"></a><img src="images/mitou-report10.jpg" alt="The entry form for new topics"><p>
+ Figure 10
+
+ The entry form for new topics
+
+ </p>
+
+ </p>
+
+ <p><a name="d0e434"></a>Occurences for topics can be added from the topic
+ details screen as shown in <a class="ptr" href="#tm-details">Figure 9</a>,
+ associations can be added by checking the topics to be
+ associated in the list of topics on the left frame and
+ then clicking on the `Add
+ Association' button.
+ </p>
+
+ <p><a name="d0e442"></a>The interface to the Topic Map as developed here is
+ generic and rather primitive. It does however however to
+ develop and maintain Topic Maps in a distributed way.
+ Because of its generic nature, it is cumbersome to use
+ for specific Topic Maps, since it is not aware of topics
+ that might be defined as Topic Map templates. Since
+ there is not yet a standardized way to define Topic Map
+ templates, automatic generation of a customized user
+ interface for specific Topic Maps will have to wait
+ until such a definition is finalized.
+
+ </p>
+
+ </div>
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e446"></a>5.3.5. The interface to XEmacs UTF-2000
+ </h4>
+
+
+ <p><a name="d0e451"></a>Beside the browser based user interface described in
+ the previous section, the Zope Topic Map engine can also
+ be interfaced from XEmacs UTF-2000. This can be done
+ through XML-RPC, WebDAV or HTTP. The format of the
+ returned values can be either in XML, HTML or in a list
+ formatted in LISP syntax.
+ </p>
+
+ <p><a name="d0e454"></a>Currently, the following commands are implemented
+ (parameters are key/value pairs that are submitted using
+ the appropriate syntax):
+
+ <p><em>Retrieval</em></p>
+ <ul>
+ <li><a name="d0e461"></a><em>tm-topics</em>: Lists topics. Parameters are:
+ <ul>
+ <li><a name="d0e467"></a>scope: string that specifies the scoping topics
+ </li>
+ <li><a name="d0e470"></a>name: string that will be used to search for
+ the <tt><baseName></tt> of topics
+ </li>
+ <li><a name="d0e476"></a>display: scope to be used to select a name
+ to return
+ </li>
+ <li><a name="d0e479"></a>occurences: type or scope of the occurrences
+ to be returned
+ </li>
+ <li><a name="d0e482"></a>format: `XML',
+ `HTML' or `LISP'.
+ </li>
+ </ul>
+
+ </li>
+ <li><a name="d0e496"></a><em>tm-members</em>: Lists associations that
+ have members as specified in the query. Parameters
+ are:
+ <ul>
+ <li><a name="d0e502"></a>scope: string that specifies the members to
+ look for
+ </li>
+ <li><a name="d0e505"></a>display: scope to be used to select a name
+ to return
+ </li>
+ <li><a name="d0e508"></a>occurences: type or scope of the occurrences
+ to be returned for the members
+ </li>
+ <li><a name="d0e511"></a>format: `XML',
+ `HTML' or `LISP'.
+ </li>
+ </ul>
+
+ </li>
+ </ul>
+
+ <p><em>Maintenance</em></p>
+ <ul>
+ <li><a name="d0e533"></a><em>tm-add</em>: This command will add a new
+ topic. If the topic already exists, it will replace
+ or add <tt><occurrence></tt> or <tt><baseName></tt>
+ elements as specified in the request. It can also
+ be used to change the list of scoping topics. Parameters:
+
+ <ul>
+ <li><a name="d0e545"></a>args: A string that gives the items to be
+ added as key/value pairs
+ </li>
+ </ul>
+
+ </li>
+ <li><a name="d0e550"></a><em>tm-delete</em>: This command will delete
+ the specified topic.
+ <ul>
+ <li><a name="d0e556"></a>topic: the topic to be deleted
+ </li>
+ </ul>
+
+ </li>
+ </ul>
+
+ </p>
+
+ <p><a name="d0e563"></a>This is a very low-level interface that will need to be
+ complemented with higher-level commands to integrate it
+ with the oeverall workings of XEmacs and the XEmacs
+ UTF-2000 character database.
+ </p>
+
+
+ </div>
+
+ <div class="teidiv">
+ <h4><a name="mitou-report1-div-d0e569"></a>5.3.6. Evaluation
+ </h4>
+
+
+ <p><a name="d0e574"></a>The goal of developping a complete Topic Map engine
+ based on Zope has not been reached. This has been partly
+ due to the development process, which had to confront some
+ fundamental issues of processing Topic Maps, which had not
+ been solved so far. While the goal of developing a
+ generic Topic Map engine is worthwhile and important, it
+ proved to be too ambitious for the context of this
+ project. We therefore had to settle to a solution that
+ works well for this context and are confident that it will
+ be possible to generalize from there.
+ </p>
+
+ <p><a name="d0e577"></a>It has also been realized that Zope is maybe not a
+ suitable platform for holding the potentially very large
+ data of a Topic Map. Using a database for this approach
+ would be better.
+ </p>
+
+ </div>
+
+ </div>
+
+ <div class="teidiv">
+ <h3><a name="mitou-report1-div-d0e582"></a>5.4. Other possibilities
+ </h3>
+
+
+ <p><a name="d0e587"></a>The current model of implementing the Topic Map engine
+ and interfacing it with XEmacs UTF-2000 is
+ based on a two way connection.
+ </p>
+
+ <p><a name="d0e590"></a>Storing the Topic Map in the Zope object database proved
+ to be a performance bottleneck. The logical way to solve
+ this problem is to move the data to an external storage. To
+ test the feasability of this approach, the Topic Map
+ datastructure has been mapped to a set of relational
+ database tables and a Topic Map has been imported into the database
+ Postgresql.
+ </p>
+
+ <p><a name="d0e593"></a>The connection between XEmacs UTF-2000, the
+ Topic Map engine within Zope and the storage backend can now
+ be established in a triangular way as shown in <a class="ptr" href="#pg-u2k-zope">Figure 12</a>. The red arrows symbolize updates to
+ the database, while the green arrows stand for data that are
+ retrieved from the databases. Both, XEmacs UTF-2000 and the
+ Zope Topic Map engine will be able to commit updates and
+ retrieve data. While the model employed so far
+ assumed a direct communication between XEmacs UTF-2000 and
+ the Zope Topic Map engine, this model provides a far more
+ flexible way of communication by introducing another layer
+ between them. This model is also extendible, since more
+ partners can be connected to the database through a set of
+ well defined interfaces and a cascade of such layers can be
+ built in a distributed way.
+ </p>
+
+ <p><a name="d0e598"></a><a name="pg-u2k-zope"></a><img src="images/mitou-report12.jpg" alt="Communication between XEmacs UTF-2000, Zope and
 the PostgreSQL database"><p>
+ Figure 12
+
+ Communication between XEmacs UTF-2000, Zope and
+ the PostgreSQL database
+
+ </p>
+
+ </p>
+
+ <p><a name="d0e609"></a>
+ While time did not permit to properly change the backend
+ of the Topic Map engine,
+ this will be a straightforward task that is not expected to
+ require changes to the other layers of the program.
+ </p>
+
+ </div>
+
+ </div>
+
+ <hr>
+ <address>Date: Time-stamp: "02/02/13 17:30:32 chris"
+ Author: Christian Wittern.
+ <br>
+ <!--
+Generated from mitou-report1using an XSLT version 1 stylesheet
+based on /pfiles/xml/xsl/tei/teihtml.xsl
+processed using SAXON 6.4.4 from Michael Kay--></address>
+ </body>
+</html>
\ No newline at end of file
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>ʸ½ñÊÔ½¸·Ï¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÅý¹ç</TITLE>
+<META NAME="description" CONTENT="ʸ½ñÊÔ½¸·Ï¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÅý¹ç">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node7.html">
+<LINK REL="previous" HREF="node5.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node7.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html114"
+ HREF="node7.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html112"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html106"
+ HREF="node5.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html115"
+ HREF="node7.html">Bibliography</A>
+<B> Up:</B> <A NAME="tex2html113"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html107"
+ HREF="node5.html">Topic Maps ¤Ë´ð¤Å¤¯Âç°èʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<BR>
+<BR>
+<!--End of Navigation Panel-->
+<!--Table of Child-Links-->
+<A NAME="CHILD_LINKS"><STRONG>Subsections</STRONG></A>
+
+<UL>
+<LI><A NAME="tex2html116"
+ HREF="#SECTION00610000000000000000">´ðËܹ½Â¤</A>
+<LI><A NAME="tex2html117"
+ HREF="#SECTION00620000000000000000">Berkeley DB ¤òÍѤ¤¤¿¼ÂÁõ</A>
+<LI><A NAME="tex2html118"
+ HREF="#SECTION00630000000000000000">³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò°·¤¦¤¿¤á¤Î API</A>
+<LI><A NAME="tex2html119"
+ HREF="#SECTION00640000000000000000">ɾ²Á</A>
+</UL>
+<!--End of Table of Child-Links-->
+<HR>
+
+<H1><A NAME="SECTION00600000000000000000">
+ʸ½ñÊÔ½¸·Ï¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÅý¹ç</A>
+</H1>
+
+<P>
+UTF-2000 ¼ÂÁõ¤Ç¤Ï½èÍýÂоݤȤ¹¤ë¤¹¤Ù¤Æ¤Îʸ»ú¤ÎÃ챤òʸ»ú°À¤È¤·¤ÆÊÝ»ý
+¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¤¿¤á¤Ë¡¢Éä¹æ²½Ê¸»ú¥â¥Ç¥ë¤Ë´ð¤Å¤¯½¾Íè·¿¤Îʸ»ú½èÍý·Ï¤Ë
+Èæ¤Ù¤Æ¿¤¯¤Îµ²±»ñ¸»¤òɬÍפȤ¹¤ë¡£
+
+<P>
+XEmacs UTF-2000 ¤Ç¤Ïʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï define-char ·Á¼°¤Î Emacs
+Lisp ¥×¥í¥°¥é¥à¤È¤·¤Æɽ¸½¤µ¤ì¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹Á´ÂΤòÆɤ߹þ¤ó¤À¾õ
+Â֤ε²±¥¤¥á¡¼¥¸¤ò¥À¥ó¥×¤·¤¿¼Â¹Ô·Á¼°¤òºî¤ê¡¢¤½¤Î¥À¥ó¥×¤µ¤ì¤¿¼Â¹Ô·Á¼°¤ò
+ÍѤ¤¤ë¡£¤³¤Î¤¿¤á¡¢XEmacs UTF-2000 ¤Î¥À¥ó¥×¸å¤Î¼Â¹Ô·Á¼°¤ÎÂ礤µ¤È¸µ¤È¤Ê¤Ã
+¤¿ XEmacs-Mule ¤Î¼Â¹Ô·Á¼°¤ÎÂ礤µ¤Îº¹¤Ïʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÊÝ»ý¤¹¤ë
+¤¿¤á¤Îµ²±»ñ¸»¤ÎÂ礤µ¤ò°ÕÌ£¤·¤Æ¤¤¤ë¡£
+
+<P>
+½é´ü¤Î XEmacs UTF-2000 ¤Ïʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÊÝ»ý¤¹¤ë¤¿¤á¤Îµ¡¹½¤Î¸ú
+Ψ²½¤¬½½Ê¬¤Ç¤Ê¤«¤Ã¤¿¤³¤È¤â¤¢¤ê¡¢i386 ¥¢¡¼¥¥Æ¥¯¥Á¥ã¾å¤Î Linux ¤Ë¤ª¤¤¤Æ
+Åö»þ¤ÎXEmacs-Mule ¤Î¼Â¹Ô·Á¼°¤¬Ìó 10 MB ¤Ç¤¢¤Ã¤¿¤Î¤ËÂФ·¡¢Ìó5Ëü»úʬ¤Îʸ
+»ú¥Ç¡¼¥¿¤òÊÝ»ý¤·¤¿¾õÂ֤Ǽ¹ԷÁ¼°¤¬ 40 MB ¤ò±Û¤¨¤ë¤è¤¦¤Ë¤Ê¤Ã¤¿¡£¤½¤Î¸å¡¢
+ʸ»ú¥Ç¡¼¥¿¤òÊÝ»ý¤¹¤ëµ¡¹½¤ò²þÎɤ·¡¢µ²±¸úΨ¤ò¸þ¾å¤·¤¿¤¿¤á¡¢ºÇ¶á¤ÎXEmacs
+UTF-2000 ¤Ç¤ÏÌó7Ëü»úʬ¤Îʸ»ú¥Ç¡¼¥¿¤òÊÝ»ý¤·¤¿¾õÂ֤Ǽ¹ԷÁ¼°¤ÏÌó27 MB ¤È
+¤Ê¤Ã¤Æ¤¤¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ë¡¢¼çµ²±¾å¤Ëʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÊÝ»ý¤¹¤ëÊýË¡¤Ï¿¤¯¤Îµ²±»ñ
+¸»¤òÍפ¹¤ë¤È¤¤¤¦ÅÀ¤ÇÌäÂ꤬¤¢¤ë¡£¤½¤·¤Æ¡¢Ä̾ï¤ÎÍøÍѤÇɬÍפȤʤëʸ»ú¤Ï¿ô
+É´¤«¤é¿ôÀé¤Ç¤¢¤ê¡¢É¬ÍפȤ¹¤ëʸ»ú°À¤â¸Â¤é¤ì¤Æ¤¤¤ë¤È¤¤¤¦¤³¤È¤ò¹Í¤¨¤ë¤È¡¢
+ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹Á´ÂΤò¥À¥ó¥×¤¹¤ë¤È¤¤¤¦ÊýË¡¤Ï˾¤Þ¤·¤¯¤Ê¤¤¤È¹Í¤¨¤é¤ì
+¤ë¡£
+
+<P>
+ʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹Á´ÂΤò¥À¥ó¥×¤¹¤ëÊýË¡¤Î¤â¤¦°ì¤Ä¤ÎÌäÂêÅÀ¤Ï¡¢UTF-2000
+¼ÂÁõ¤Èʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬ÉÔ²Äʬ¤Ë¤Ê¤Ã¤Æ¤·¤Þ¤¦¤³¤È¤Ç¤¢¤ë¡£¤Ä¤Þ¤ê¡¢°Û
+¤Ê¤ë UTF-2000 ¼ÂÁõ´Ö¤Çʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬¶¦Í¤Ç¤¤Ê¤¤¤³¤È¤ò°ÕÌ£¤¹¤ë¡£
+¤Þ¤¿¡¢UTF-2000 ¼ÂÁõ¤Î³«È¯¤Èʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥á¥ó¥Æ¥Ê¥ó¥¹¤ÏÈó¾ï¤Ë
+À¼Á¤Î°Û¤Ê¤ëºî¶È¤Ç¤¢¤ë¤Ë¤â´Ø¤ï¤é¤º¡¢Î¾¼Ô¤òÅý¹ç¤·¤¿·Á¤Ç¥½¡¼¥¹¥Õ¥¡¥¤¥ë¤ò
+´ÉÍý¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ê¤³¤È¤ò¹Í¤¨¤ë¤È¡¢UTF-2000 ¼ÂÁõ¤Èʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÏʬΥ¤·
+¤¿Êý¤¬Îɤ¤¤È¹Í¤¨¤é¤ì¤ë¡£¤¹¤Ê¤ï¤Á¡¢Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï UTF-2000 ¼ÂÁõ
+¤Î³°Éô¤Ë¤¢¤ë¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊÝ»ý¤·¡¢UTF-2000 ¼ÂÁõ¤Ë¤ª¤¤¤Æ³°Éô¥Ç¡¼¥¿¥Ù¡¼
+¥¹¤«¤é½èÍý¤ËɬÍפÊʬ¤À¤±¥Ç¡¼¥¿¤ò¥í¡¼¥É¤¹¤ë¤è¤¦¤Ë¤¹¤ëÌõ¤Ç¤¢¤ë¡£
+
+<P>
+¤³¤Î¤è¤¦¤Ê¹Í¤¨¤ËΩ¤Á¡¢ËÜ¥×¥í¥¸¥§¥¯¥È¤Ç¤Ï XEmacs UTF-2000 ¤Ë¤ª¤¤¤Æ³°Éô
+¤Îʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤òÍøÍѤ¹¤ë¤¿¤á¤Îµ¡¹½¤ò³«È¯¤·¤¿¡£ËܾϤǤϤ³¤Îµ¡¹½¤Ë´Ø
+¤·¤Æ³µÀ⤹¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00610000000000000000">
+´ðËܹ½Â¤</A>
+</H1>
+
+<P>
+¸½ºß¤Î XEmacs UTF-2000 ¤Ç¤Ïʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ï°ÀËè¤Î¥Ç¡¼¥¿¹½Â¤
+(char-id-table) ¤Ëʬ¤±¤ÆÊÝ»ý¤µ¤ì¤Æ¤¤¤ë¡£¤³¤Îchar-id-table ¤Ïʸ»ú id ¤«
+¤é°ÀÃͤòº÷¤¯¤¿¤á¤Î¥Ç¡¼¥¿¹½Â¤¤Ç¤¢¤ê¡¢Â°ÀÃͤȤ·¤ÆǤ°Õ¤Î Lisp ¥ª¥Ö¥¸¥§
+¥¯¥È¤¬³ÊǼ¤Ç¤¤ë¡£Ê¸»ú°À̾¤È char-id-table ¤ÎÂбþ¤Ï¥Ï¥Ã¥·¥åɽ¤Ë¤è¤Ã
+¤Æ´ÉÍý¤µ¤ì¤Æ¤ª¤ê¡¢¤³¤ì¤Ë¤è¤êʸ»ú°À̾¤«¤é¤½¤Î°ÀÃͤòº÷¤¯¤³¤È¤¬¤Ç¤¤ë¡£
+
+<P>
+<A HREF="node4.html#sec:coded-charset">4.2</A> Àᤪ¤è¤Ó <A HREF="node4.html#sec:coded-charset">4.2</A> Àá¤Ç½Ò¤Ù¤¿¤è
+¤¦¤Ë¡¢Éä¹ç°ÌÃÖ°À¤Ï coded-charset ¤Ç¤ÎÉü¹æ½èÍý¤ËÍøÍѤµ¤ì¤ë¤¬¡¢¤³¤ì¤Ï
+char-id-table ¤òµÕº÷¤¤¹¤ë¤³¤È¤ËÁêÅö¤¹¤ë¡£Éü¹æ½èÍý¤Ï½ÅÍפʽèÍý¤Ç¤¢¤ê¤³
+¤Î¹â®²½¤Î¤¿¤á¤Ë¡¢coded-charset ¤Ç¤ÎÉä¹ç°ÌÃÖ¤«¤éʸ»ú¥ª¥Ö¥¸¥§¥¯¥È¤òº÷¤¯
+¤¿¤á¤Î¥Ç¡¼¥¿¹½Â¤ (decoding-table) ¤âÍÑ°Õ¤·¤Æ¤¤¤ë¡£¤³¤ì¤Ï 1 byte Ëè¤Ëʬ
+³ä¤·¤¿Éä¹ç°ÌÃÖ¤òÍѤ¤¤¿Æþ¤ì»Ò¾å¤ÎÇÛÎó¤Ç¼Â¸½¤µ¤ì¤Æ¤¤¤ë¡£
+
+<P>
+XEmacs UTF-2000 ¤Ë¤ª¤¤¤Æ³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤éɬÍפʻþ¤Ë¾ðÊó¤ò³ÍÆÀ¤¹¤ë¤³
+¤È (lazy-loading) ¤ò¤¹¤ë¤¿¤á¤Ë¤Ï¡¢char-id-table ¤ª¤è¤Ó decoding-table
+¤ËÃͤ¬Â¸ºß¤·¤Ê¤¤¤³¤È¤ò¼¨¤¹°õ¤¬É¬ÍפǤ¢¤ë¡£¤³¤Î¤¿¤á¤Ë¡¢µ²±¶õ´ÖÃæ¤ËÃͤ¬
+¸ºß¤·¤Ê¤¤¤³¤È¤ò¼¨¤¹ÆÃÊÌ¤Ê Lisp ¥ª¥Ö¥¸¥§¥¯¥È <B>Qunloaded</B> ¤òƳÆþ
+¤·¤¿¡£¤¹¤Ê¤ï¤Á¡¢char-id-table ¤ª¤è¤Ó decoding-table ¤òº÷¤¤¤¿»þ¤ËÆÀ¤é¤ì
+¤¿Ãͤ¬ Qunloaded ¤Ç¤¢¤ì¤Ð³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤é¾ðÊó¤ò³ÍÆÀ¤·¤Ê¤±¤ì¤Ð¤Ê¤é
+¤Ê¤¤¤³¤È¤¬¤ï¤«¤ë¡£¤½¤·¤Æ¡¢¤³¤Î»þ¡¢³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤é¾ðÊó¤ò³ÍÆÀ¤¹¤ë¤³
+¤È¤¬¤Ç¤¤ì¤Ð¡¢Qunloaded ¤ò¤½¤Î·ë²Ì¤ÇÃÖ¤´¹¤¨¤ë¤È¤È¤â¤Ë¡¢¤½¤Î³ÍÆÀ¤·¤¿ÃÍ
+¤òÊÖ¤¹Ìõ¤Ç¤¢¤ë¡£
+
+<P>
+
+<H1><A NAME="SECTION00620000000000000000">
+Berkeley DB ¤òÍѤ¤¤¿¼ÂÁõ</A>
+</H1>
+
+<P>
+XEmacs ¤Ï Berkeley DB ¤Î¤è¤¦¤Ê°ÀÃͤòÊÝ»ý¤¹¤ë¤¿¤á¤Îñ½ã¤Ê¥Ç¡¼¥¿¥Ù¡¼¥¹
+¤òÃê¾Ý²½¤·¤¿ <B>database</B> µ¡Ç½¤ò»ý¤Ã¤Æ¤¤¤ë¡£ËÜ¥×¥í¥¸¥§¥¯¥È¤Ç¤Ï¤³
+¤Îµ¡Ç½¤òÍøÍѤ·¤¿Ê¸»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î³°Éô²½µ¡Ç½¤ò¼Â¸½¤·¤¿¡£¸½ºß¤Î¤È¤³
+¤í¡¢Æ°ºî³Îǧ¤Ï Debian GNU/Linux (sid) ¤Ë¤ª¤±¤ë Berkeley DB Version 3
+¤Ç¤Î¤ß¹Ô¤Ê¤Ã¤Æ¤¤¤ë¡£
+
+<P>
+
+<H2><A NAME="SECTION00621000000000000000">
+¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥Õ¥¡¥¤¥ë¤È¤ÎÂбþ¤Å¤±</A>
+</H2>
+
+<P>
+char-id-table ¤ª¤è¤Ó decoding-table ¤Ï
+<BLOCKQUOTE>
+<I>¡Øʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥ë¡¼¥È¡Ù</I>/<I>¡Ø¸°¤Î¼ïÎà¡Ù</I>/<I>¡ØÃͤμïÎà¡Ù</I>
+
+</BLOCKQUOTE>
+¤È¤¤¤¦¥Õ¥¡¥¤¥ë̾¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÂбþÉÕ¤±¤é¤ì¤ë¡£
+
+<P>
+¤³¤³¤Ç¡¢<I>¡Ø¸°¤Î¼ïÎà¡Ù</I> ¤Ï¤½¤Î¾ðÊó¤Î¸°¤ÎÉä¹æ²½Ë¡¤òɽ¤¹¡£Î㤨¤Ð¡¢
+char-id-table ¤Î¾ì¹ç¡¢¸°¤ÎÉä¹æ²½Ë¡¤Ï XEmacs UTF-2000 ¤Îʸ»ú id ¤Ê¤Î¤Ç¡¢
+¤½¤ì¤òɽ¤¹Ì¾Á° <TT>system-char-id</TT> ¤¬ <I>¡Ø¸°¤Î¼ïÎà¡Ù</I> ¤È¤Ê¤ë¡£
+decoding-table ¤Î¾ì¹ç coded-charset ¤Î̾Á°¤¬ <I>¡Ø¸°¤Î¼ïÎà¡Ù</I> ¤È¤Ê
+¤ë¡£Î㤨¤Ð¡¢<TT>ascii</TT> ¤Î¾ì¹ç <I>¡Ø¸°¤Î¼ïÎà¡Ù</I> ¤Ï
+<TT>ascii</TT> ¤È¤Ê¤ë¡£
+
+<P>
+<I>¡ØÃͤμïÎà¡Ù</I> ¤Ï¤½¤Î°À¤Î̾Á°¤ËÂбþÉÕ¤±¤é¤ì¤ë¡£char-id-table ¤Î
+¾ì¹ç¡¢Ê¸»ú°À¤Î̾Á°¤¬ÍѤ¤¤é¤ì¤ë¡£¤¿¤À¤·¡¢Â°À̾¤Ë¥Õ¥¡¥¤¥ë̾¤È¤·¤ÆÍѤ¤
+¤ë¤³¤È¤¬¤Ç¤¤Ê¤¤Ê¸»ú¤¬´Þ¤Þ¤ì¤Æ¤¤¤¿¾ì¹ç¡¢Emacs Lisp ¤Ë¤ª¤±¤ë
+<code>\</code>-quoting ¤ò¹Ô¤Ê¤¦¡£¤Þ¤¿¡¢decoding-table ¤Î¾ì¹ç¡¢
+<TT>system-char-id</TT> ¤òÍѤ¤¤ë¡£
+
+<P>
+°Ê²¼¤Ë´ö¤Ä¤«Îã¤ò¼¨¤¹¡§
+<BLOCKQUOTE>
+<I>¡Øʸ»ú°À¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥ë¡¼¥È¡Ù</I> ¤ò
+ <TT>/usr/local/libexec/char-db/</TT> ¤È¤¹¤ë»þ¡¢
+ </BLOCKQUOTE><DL>
+<DT><STRONG>Îã1</STRONG></DT>
+<DD>ʸ»ú°À ideographic-structure ¤Ï
+ <TT>/usr/local/libexec/char-db/system-char-id/ideographic-structure</TT>
+ ¤ËÂбþ¤¹¤ë¡£
+
+</DD>
+<DT><STRONG>Îã2</STRONG></DT>
+<DD>ascii ¤Î decoding-table ¤Ï
+ <TT>/usr/local/libexec/char-db/ascii/system-char-id</TT> ¤ËÂбþ¤¹
+ ¤ë¡£
+
+</DD>
+</DL>
+
+<P>
+
+<H1><A NAME="SECTION00630000000000000000">
+³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò°·¤¦¤¿¤á¤Î API</A>
+</H1>
+
+<P>
+³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤é¤Îʸ»ú¥Ç¡¼¥¿¤Î³ÍÆÀ¤ÏɬÍפʻþ¤Ë¼«Æ°Åª¤Ë¹Ô¤Ê¤ï¤ì¤ë¤¬¡¢
+µ²±¶õ´ÖÃæ¤Îʸ»ú¥Ç¡¼¥¿¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÆþ½ÐÎϤòÀ©¸æ¤¹¤ë¤¿¤á¤Ë´ö¤Ä¤«
+¤Î API ¤ò³ÈÄ¥¤·¤¿¡£
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>save-char-attribute-table</B> (<I>attribute</I>)
+
+<BLOCKQUOTE>
+ʸ»ú°À <I>attribute</I> ¤Î¤¹¤Ù¤Æ¤ÎÃͤò¤³¤Î°À¤ËÂбþÉÕ¤±¤é¤ì¤¿
+ ³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ËÊݸ¤¹¤ë¡£
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>ÂбþÉÕ¤±¤é¤ì¤¿³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¡¢²¿¤â¤·¤Ê¤¤¡£
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>save-charset-mapping-table</B>) (<I>coded-charset</I>)
+
+<BLOCKQUOTE>
+<I>coded-charset</I> ¤Î decoding-table ¤òÂбþÉÕ¤±¤é¤ì¤¿³°Éô¥Ç¡¼
+ ¥¿¥Ù¡¼¥¹¤ËÊݸ¤¹¤ë¡£
+</BLOCKQUOTE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><BLOCKQUOTE>ÂбþÉÕ¤±¤é¤ì¤¿³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬Â¸ºß¤·¤Ê¤¤¾ì¹ç¡¢²¿¤â¤·¤Ê¤¤¡£
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+<BLOCKQUOTE>
+
+ ´Ø¿ô <B>reset-char-attribute-table</B> (<I>attribute</I>)
+
+<BLOCKQUOTE>
+ʸ»ú°À <I>attribute</I> ¤ËÂбþÉÕ¤±¤é¤ì¤¿³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤¬Â¸ºß
+ ¤¹¤ë»þ¡¢¤¹¤Ù¤Æ¤Î°ÀÃͤò¾Ãµî¤·¡¢³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤«¤éÆɤ߹þ¤á¤ë¾õÂÖ
+ ¤Ë¤¹¤ë¡£
+
+</BLOCKQUOTE>
+</BLOCKQUOTE>
+
+<P>
+
+<H1><A NAME="SECTION00640000000000000000">
+ɾ²Á</A>
+</H1>
+
+<P>
+TM 5800 ¾å¤Î Debian GNU/Linux (sid) ¤Ë¤ª¤¤¤Æ¡¢Ìó7Ëü»ú¤Î¤Îʸ»úÄêµÁ¤ò»ý¤Ä
+XEmacs 21.2.43 UTF-2000 ¤Î¥À¥ó¥×¸å¤Î¼Â¹Ô·Á¼°¤ÎÂ礤µ¤¬ 27 MB (strip ¸å
+22 MB) ¤Ç¤¢¤ë¤Î¤ËÂФ·¤Æ¡¢lazy-loading ÈǤμ¹ԷÁ¼°¤ÎÂ礤µ¤Ï 15 MB
+(strip ¸å 10 MB) ¤È¤Ê¤Ã¤¿¡£¤Á¤Ê¤ß¤Ë¡¢XEmacs 21.2.43¡Êmule ÉÕ¤¡Ë¤Î¼Â¹Ô
+·Á¼°¤ÎÂ礤µ¤Ï 10 MB (strip ¸å 6 MB) ¤Ç¤¢¤ë¡£
+
+<P>
+lazy-loading ÈǤμ¹ԷÁ¼°¤ÎÂ礤µ¤¬¤Ê¤ª XEmacs-Mule ¤è¤ê¤â 5 MB ÄøÂç¤
+¤¤¤Î¤Ï¡¢XEmacs-Mule ¤«¤é°ú¤·Ñ¤¤¤À Emacs Lisp code ¤Ë¤ª¤¤¤Æ¡¢
+coded-charset ¤ò¸°¤È¤·¤¿ char-table ¤¬Â¿ÍѤµ¤ì¤Æ¤¤¤ë¤»¤¤¤À¤È¹Í¤¨¤é¤ì¤ë¡£
+XEmacs UTF-2000 ¤Ç¤Ï char-table ¤Ï char-id-table ¤Ç¼ÂÁõ¤µ¤ì¤Æ¤ª¤ê¡¢
+coded-charset ¤ò¸°¤Ë¤·¤ÆÃͤòÀßÄꤷ¤¿¾ì¹ç¡¢¤½¤Î coded-charset ¤Ë°¤¹¤ë
+¤¹¤Ù¤Æ¤Îʸ»ú¤ËÂФ·¤ÆÃͤòÀßÄꤹ¤ë¤è¤¦¤Ë¤Ê¤Ã¤Æ¤¤¤ë¤¿¤á¡¢É¬Íפʵ²±Î̤¬ËÄ
+¤é¤à¤È¹Í¤¨¤é¤ì¤ë¡£¤Þ¤¿¡¢char-table ¤Ïʸ»ú°À¤È°Û¤Ê¤ê³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹
+¤ËÂбþÉÕ¤±¤é¤ì¤Æ¤¤¤Ê¤¤¤¿¤á¡¢lazy-loading ¤¬¤Ç¤¤Ê¤¤¤Î¤Ç¤¢¤ë¡£¤è¤Ã¤Æ¡¢
+¤³¤ÎÅÀ¤ò²þÎɤ¹¤ì¤Ð lazy-loading ÈÇ XEmacs UTF-2000 ¤Î¼Â¹Ô·Á¼°¤ÎÂ礤µ
+¤ò XEmacs-Mule ¤ÈƱÄøÅ٤ˤ¹¤ë¤³¤È¤¬¤Ç¤¤ë¤È¹Í¤¨¤é¤ì¤ë¡£
+
+<P>
+
+<P>
+<HR>
+<!--Navigation Panel-->
+<A NAME="tex2html114"
+ HREF="node7.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html112"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html106"
+ HREF="node5.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html115"
+ HREF="node7.html">Bibliography</A>
+<B> Up:</B> <A NAME="tex2html113"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html107"
+ HREF="node5.html">Topic Maps ¤Ë´ð¤Å¤¯Âç°èʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹</A>
+<!--End of Navigation Panel-->
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+
+<!--Converted with LaTeX2HTML 2K.1beta (1.48)
+original version by: Nikos Drakos, CBLU, University of Leeds
+* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
+* with significant contributions from:
+ Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
+<HTML>
+<HEAD>
+<TITLE>Bibliography</TITLE>
+<META NAME="description" CONTENT="Bibliography">
+<META NAME="keywords" CONTENT="main">
+<META NAME="resource-type" CONTENT="document">
+<META NAME="distribution" CONTENT="global">
+
+<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=euc-jp">
+<META NAME="Generator" CONTENT="LaTeX2HTML v2K.1beta">
+<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
+
+<LINK REL="STYLESHEET" HREF="main.css">
+
+<LINK REL="next" HREF="node8.html">
+<LINK REL="previous" HREF="node6.html">
+<LINK REL="up" HREF="main.html">
+<LINK REL="next" HREF="node8.html">
+</HEAD>
+
+<BODY >
+<!--Navigation Panel-->
+<A NAME="tex2html128"
+ HREF="node8.html">
+<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next"
+ SRC="/usr/share/latex2html/icons/next.png"></A>
+<A NAME="tex2html126"
+ HREF="main.html">
+<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up"
+ SRC="/usr/share/latex2html/icons/up.png"></A>
+<A NAME="tex2html120"
+ HREF="node6.html">
+<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous"
+ SRC="/usr/share/latex2html/icons/prev.png"></A>
+<BR>
+<B> Next:</B> <A NAME="tex2html129"
+ HREF="node8.html">About this document ...</A>
+<B> Up:</B> <A NAME="tex2html127"
+ HREF="main.html">2001ǯÅṲ̀Ƨ¥½¥Õ¥È¥¦¥§¥¢ÁϤ»ö¶È ʸ»ú¥Ç¡¼¥¿¥Ù¡¼¥¹¤Ë´ð¤Å¤¯ ʸ»ú¥ª¥Ö¥¸¥§¥¯¥Èµ»½Ñ¤Î¹½ÃÛ ¡Ê·ÀÌóÈÖ¹æ</A>
+<B> Previous:</B> <A NAME="tex2html121"
+ HREF="node6.html">ʸ½ñÊÔ½¸·Ï¤È³°Éô¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎÅý¹ç</A>
+<BR><BR>
+<!--End of Navigation Panel-->
+
+<H2><A NAME="SECTION00700000000000000000">
+Bibliography</A>
+</H2><DL COMPACT><DD><P></P><DT><A NAME="ISO-2022">1</A>
+<DD>
+International Organization for Standardization (ISO).
+<BR><EM>Information technology - Character code structure and extension
+ techniques</EM>, 1994.
+<BR>ISO/IEC 2022:1994 ¡Ê= JIS X 0202,¡Ö¾ðÊó¸ò´¹ÍÑÉä¹æ¤Î³Èĥˡ¡×¡Ë.
+
+<P></P><DT><A NAME="BMP">2</A>
+<DD>
+International Organization for Standardization (ISO).
+<BR><EM>Universal Multiple-Octet Coded Character Set (UCS) - Part 1:
+ Architecture and Basic Multilingual Plane (BMP)</EM>, March 2000.
+<BR>ISO/IEC 10646-1:2000.
+
+<P></P><DT><A NAME="Mule">3</A>
+<DD>
+Mikiko Nishikimi, Ken'ichi Handa, and Satoru Tomura.
+<BR>Mule: MULtilingual Enhancement to GNU Emacs.
+<BR>In <EM>Proc. INET '93</EM>, pages GAB-1-GAB-9, 1993.
+
+<P></P><DT><A NAME="GNU-Emacs">4</A>
+<DD>
+Richard M. Stallman et al.
+<BR>GNU Emacs version 20.7.
+<BR>ftp://ftp.gnu.org/gnu/emacs-20.7.tar.gz, June 2000.
+
+<P></P><DT><A NAME="Unicode">5</A>
+<DD>
+The Unicode Consortium.
+<BR><EM>The Unicode Standard, Version 3.0</EM>, February 2000.
+
+<P></P><DT><A NAME="XEmacs">6</A>
+<DD>
+XEmacs.
+<BR>http://www.xemacs.org/.
+</DL>
+
+<P>
+<BR><HR>
+<ADDRESS>
+MORIOKA Tomohiko
+2002-02-15
+</ADDRESS>
+</BODY>
+</HTML>
projects / www / chise.git / commitdiff
