Changeset 5192
- Timestamp:
- 01/21/08 23:35:28 (10 months ago)
- Files:
-
- 1 modified
-
docs/m-takagi/CodeGen_PECL/trunk/manual.xml (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
docs/m-takagi/CodeGen_PECL/trunk/manual.xml
r5189 r5192 1986 1986 1987 1987 <chapter> 1988 <title>XML input parsing</title>1989 1990 <section> 1991 <title> Includes</title>1992 <para> 1993 The XML parser used by <literal>CodeGen_PECL</literal> supports inclusion 1994 of additional source files using three different ways:1988 <title>XML ���Υѡ���</title> 1989 1990 <section> 1991 <title>���롼��/title> 1992 <para> 1993 <literal>CodeGen_PECL</literal> ����Ѥ��Ƥ���ML �ѡ����ϡ� 1994 ������ˡ�dz���ե��������롼�ɤݡ��Ȥ��Ƥ��ޤ��� 1995 1995 <itemizedlist> 1996 <listitem><simpara> external entities</simpara></listitem>1997 <listitem><simpara> a subset of XInclude</simpara></listitem>1998 <listitem><simpara> the <literal>source</literal> attribute of <literal><code></literal> tags</simpara></listitem>1996 <listitem><simpara>���������ƥ�</simpara></listitem> 1997 <listitem><simpara>XInclude �Υ��֥��å�/simpara></listitem> 1998 <listitem><simpara><literal><code></literal> ������<literal>source</literal> °�</simpara></listitem> 1999 1999 </itemizedlist> 2000 2000 </para> 2001 2001 2002 2002 <section> 2003 <title>External entities</title> 2004 <para> 2005 In SGML and early XML system entites were the only 2006 include mechanism availabe. System entities have to 2007 be defined in the documents DOCTYPE header, later on 2008 in the document the entity can be used to include 2009 the specified file: 2003 <title>���������ƥ�</title> 2004 <para> 2005 SGML ����L �Ǥϡ� 2006 �����ƥ२����ƥ��ˤ����롼�ɤ�ͣ����ȤߤǤ����� 2007 �����ƥ२����ƥ��ϡ��ɥ������DOCTYPE 2008 �إå������������������ 2009 �����ơ����ɥ����������Υ�����ƥ������ 2010 ��ꤷ���ե��������롼�ɤ��뤳�Ȥ��Ǥ��ޤ��� 2010 2011 </para> 2011 2012 <example> 2012 <title> System Entities</title>2013 <title>�����ƥ२����ƥ�</title> 2013 2014 <programlisting> 2014 2015 <![CDATA[ … … 2030 2031 <title>XInclude</title> 2031 2032 <para> 2032 The <literal>CodeGen</literal> XML parser supports a simple2033 subset of XInclude, it is possible to include additional2034 specification files using the <literal>href=...</literal>2035 attribute of the <literal><include></literal> tag:2033 <literal>CodeGen</literal> ��XML �ѡ����ϡ� 2034 XInclude ��������֥��åȤݡ��Ȥ��Ƥ��ޤ��� 2035 <literal><include></literal> ������ <literal>href=...</literal> °���Ѥ��ơ� 2036 ��ä������������롼�ɤǤ������ˤʤ����� 2036 2037 </para> 2037 2038 <example> … … 2048 2049 </example> 2049 2050 <para> 2050 The <literal>parse=...</literal> attirbute is also supported, 2051 using <literal><include parse='text' href='...'/></literal> it is possible to 2052 include arbitrary data without parsing it as XML. 2051 <literal>parse=...</literal> °��⥵�ݡ��Ȥ��Ƥ��ޤ��� 2052 <literal><include parse='text' href='...'/></literal> 2053 �Ȥ�����Ǥ�դΥǡ�����ML �Ȥ��Ʋ�����ˤ��Τޤ� 2054 ���롼�ɤǤ������ˤʤ����� 2053 2055 </para> 2054 2056 <example> 2055 <title> VerbatimXInclude</title>2057 <title>���Τޤޤξ�Ǥ�XInclude</title> 2056 2058 <programlisting> 2057 2059 <![CDATA[ … … 2065 2067 </example> 2066 2068 <para> 2067 Other <literal><include></literal> features and the <literal><fallback></literal> 2068 tag are not supported yet, and most of them won't make sense in this context anyway. 2069 <literal><include></literal> �Τ������ε�ǽ�� <literal><fallback></literal> �����ˤĤ��ƤϤޤ���ݡ��Ȥ��Ƥ��ޤ��� ��������ˤĤ��Ƥϡ����ξ��ǻȤäƤ�����ʤ��Ǥ��� 2069 2070 </para> 2070 2071 </section> 2071 2072 2072 2073 <section> 2073 <title><literal><code></literal> tags</title>2074 <para> 2075 In most places the <literal><code></literal> tag supports loading of2076 its content using its <literal>src=...</literal> attribute:2074 <title><literal><code></literal> ����</title> 2075 <para> 2076 �ۤȤ�ξ��ǡ�<literal><code></literal> 2077 ���������iteral>src=...</literal> °������ɤ߹��ळ�Ȥ��Ǥ��ޤ��� 2077 2078 </para> 2078 2079 <example> 2079 <title> Using <literal><code src="..."></literal></title>2080 <title><literal><code src="..."></literal> �λ���title> 2080 2081 <programlisting> 2081 2082 <![CDATA[ … … 2091 2092 2092 2093 <section> 2093 <title>Verbatim text data</title> 2094 <para> 2095 C code usually contains quite a few <literal>></literal>, 2096 <literal><</literal> and <literal>&</literal> characters 2097 all of which need to be escaped in XML. This can be done by either 2098 converting them into entities all over the place or by embedding 2099 the code into CDATA sections: 2094 <title>���Τޤޤξ�Υƥ����ȥǡ���</title> 2095 <para> 2096 C �Υ����ɤˤϡ���� <literal>></literal> �� <literal><</literal>��������<literal>&</literal> 2097 ���ޤޤ����ޤ������������ML ��Ǥϥ��������פ��ʤ����ʤ����� �����Ƥϡ�����������٤ƥ�����ƥ���Ѵ����뤫�� 2098 ���뤤�ϥ����ɤ�ATA ����������˵��Ҥ��ޤ��� 2100 2099 </para> 2101 2100 <example> 2102 <title>CDATA sections</title>2101 <title>CDATA ��������</title> 2103 2102 <programlisting> 2104 2103 <code> … … 2110 2109 </example> 2111 2110 <para> 2112 Typing <literal><![CDATA[</literal> can become rather annoying 2113 over time (esp. on a german keyboard), so i introduced the 2114 <literal><?data</literal> processing instruction into the 2115 <literal>CodeGen</literal> XML parser as an alternative to CDATA: 2111 ����ⲿ���literal><![CDATA[</literal> �ȥ����פ�������Ǥ� 2112 (��˥ɥ��ĸ������ܡ��ɤ���ݤǤ�)�������ǡ� 2113 <literal>CodeGen</literal> ��XML �ѡ����ˤϽ�̿� 2114 <literal><?data</literal> ��ä��뤳�Ȥˤ��ޤ����� 2115 ���� CDATA ������褦�˻Ȥ����ΤǤ��� 2116 2116 </para> 2117 2117 <example> 2118 <title><literal><?data</literal> processing instruction</title>2118 <title><literal><?data</literal> ��̿�</title> 2119 2119 <programlisting> 2120 2120 <![CDATA[
![(please configure the [header_logo] section in trac.ini)](/share/chrome/site/your_project_logo.png)