Update of /cvsroot/perl-xml/perl-xml-faq
In directory usw-pr-cvs1:/tmp/cvs-serv22640
Modified Files:
perl-xml-faq.xml
Log Message:
- integrated patch from Per Einar Ellefsen
Index: perl-xml-faq.xml
===================================================================
RCS file: /cvsroot/perl-xml/perl-xml-faq/perl-xml-faq.xml,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- perl-xml-faq.xml 31 Mar 2002 20:00:56 -0000 1.1.1.1
+++ perl-xml-faq.xml 2 Apr 2002 21:42:35 -0000 1.2
@@ -53,6 +53,10 @@
<listitem><para><ulink
url="http://www.xml.com/pub/a/2001/06/13/perlxml.html">Perl XML
Quick Start: Convenience Modules</ulink></para></listitem>
+
+ <listitem><para><ulink
+ url="http://www.xml.com/pub/a/2001/11/14/xml-libxml.html">XML::LibXML
+ - An XML::Parser Alternative</ulink></para></listitem>
<listitem><para><ulink
url="http://www.xml.com/pub/au/83">List of all Kip's articles</ulink>
@@ -117,6 +121,12 @@
ActivePerl</guisubmenu></menuchoice>. If your distribution does not
include the HTML files, you can create them using
<command>pod2html</command></para></listitem>
+
+ <listitem><para>HTML documentation for various Perl modules is also
+ provided on various Internet sites. You can try searching for XML on
+ <ulink url="http://www.perldoc.com/">Perldoc.com</ulink> or on <ulink
+ url="http://search.cpan.org">search.cpan.org</ulink> for a list of XML
+ documentation.</para></listitem>
<listitem><para>If all else fails, you can locate the module and open
it directly in a text editor. Once again, using
@@ -370,10 +380,11 @@
</question>
<answer>
- <para>Enno Derksen's <classname>XML::DOM</classname> implements the W3C
- DOM Level 1 tree structure and API (DOM Level 1 does not include
- namespace support). Although you can find nodes in the tree by tag name,
- you can't use XPath expressions.</para>
+ <para>Enno Derksen's <classname>XML::DOM</classname> implements the
+ <ulink url="http://www.w3.org/TR/REC-DOM-Level-1/">W3C DOM Level 1</ulink>
+ tree structure and API (DOM Level 1 does not include namespace support).
+ Although you can find nodes in the tree by tag name, you can't use XPath
+ expressions.</para>
<para>The distribution includes
<classname>XML::DOM::ValParser</classname> which performs validation
@@ -1008,7 +1019,7 @@
<answer id="perl_5_6_tr">
<formalpara>
- <title>Perl 5.6 tr/// operator - deprecated</title>
+ <title>Perl 5.6 tr/// operator (deprecated)</title>
<para>Perl 5.6 offers a way of converting between UTF-8 and Latin1 8 bit
byte strings using the 'tr' operator. This will no longer work in
@@ -1508,7 +1519,7 @@
</formalpara>
<programlisting><![CDATA[
-item name="widget"></item>
+<item name="widget"></item>
]]></programlisting>
<para>while this would not:</para>
@@ -1568,12 +1579,39 @@
in your DTD or in an 'internal subset' of a DTD. For example:</para>
<programlisting><![CDATA[
-FIXME: Internal DTD subset example
+<!DOCTYPE doc [
+ <!ENTITY eacute "é" >
+ <!ENTITY euro "€" >
+]>
+
+<doc>Combien avez-vous payé? 125 €</doc>
]]></programlisting>
<para>You can find the definitions for <ulink
url="http://www.w3.org/TR/xhtml-modularization/dtd_module_defs.html#a_module_XHTML_Latin_1_Character_Entities"
>HTML Latin 1 characters entities</ulink> on the W3c Site.</para>
+
+ <para>You can include all these character entities into your DTD, so that
+ you won't have to worry about it anymore:</para>
+
+ <programlisting><![CDATA[
+<!DOCTYPE doc [
+<!ENTITY % HTMLlat1 PUBLIC
+ "-//W3C//ENTITIES Latin 1 for XHTML//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">
+%HTMLlat1;
+
+<!ENTITY % HTMLspecial PUBLIC
+ "-//W3C//ENTITIES Special for XHTML//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml-special.ent">
+%HTMLspecial;
+
+<!ENTITY % HTMLsymbol PUBLIC
+ "-//W3C//ENTITIES Symbols for XHTML//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml-symbol.ent">
+%HTMLsymbol;
+]>
+ ]]></programlisting>
</answer>
</qandaentry>
|
