ja-basic.xml

<?xml version="1.0" encoding="utf-8"?>
<!-- $Revision$ -->
<chapter xml:id="mbstring.ja-basic" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
 <title>Basics of Japanese multi-byte encodings</title>
 <para>
  Japanese characters can only be represented by multibyte encodings, 
  and multiple encoding standards are used depending on platform and 
  text purpose. To make matters worse, these encoding standards 
  differ slightly from one another. In order to create a web 
  application which would be usable in a Japanese environment, a 
  developer has to keep these complexities in mind to ensure that the
  proper character encodings are used.
 </para>
 <para>
  <itemizedlist>
   <listitem>
    <simpara>Storage for a character can be up to six bytes</simpara>
   </listitem>
   <listitem>
    <simpara>
     Most Japanese multibyte characters appear twice as wide as
     single-byte characters. These characters are called 
     &quot;zen-kaku&quot; in Japanese, which means 
     &quot;full width&quot;. Other, narrower, characters are called 
     &quot;han-kaku&quot;, which means &quot;half width&quot;. The 
     graphical properties of the characters, however, depends upon 
     the type faces used to display them.
    </simpara>
   </listitem>
   <listitem>
    <simpara>
     Some character encodings use shift(escape) sequences defined
     in ISO-2022 to switch the code map of the specific code area
     (<literal>00h</literal> to <literal>7fh</literal>).
    </simpara>
   </listitem>
   <listitem>
    <simpara>
     ISO-2022-JP should be used in SMTP/NNTP, and headers and entities
     should be reencoded as per RFC requirements. Although those are not
     requisites, it's still a good idea because several popular user
     agents cannot recognize any other encoding methods.
    </simpara>
   </listitem>
   <listitem>
    <simpara>
     Web pages created for mobile phone services such as
     <link xlink:href="&url.imode;">i-mode</link>
     or <link xlink:href="&url.ezweb;">EZweb</link>
     are supposed to use Shift_JIS.
    </simpara>
   </listitem>
   <listitem>
    <simpara>
      Emoji used for mobile phone service such as 
      <link xlink:href="&url.imode;">i-mode</link>
      or <link xlink:href="&url.ezweb;">EZweb</link>
      are supported.
    </simpara>
   </listitem>
  </itemizedlist>
 </para>
</chapter>

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:t
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
indent-tabs-mode:nil
sgml-parent-document:nil
sgml-default-dtd-file:"~/.phpdoc/manual.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:nil
sgml-local-ecat-files:nil
End:
vim600: syn=xml fen fdm=syntax fdl=2 si
vim: et tw=78 syn=sgml
vi: ts=1 sw=1
-->