mirror of
https://github.com/darlinghq/darling-libxml2.git
synced 2025-01-10 22:46:34 +00:00
do not generate " for " outside of attributes this changes the output
* entities.c: do not generate " for " outside of attributes * result//*: this changes the output of some tests Daniel
This commit is contained in:
parent
8a46917120
commit
8265a18a6a
@ -1,3 +1,8 @@
|
||||
Fri Jun 13 12:03:30 CEST 2003 Daniel Veillard <daniel@veillard.com>
|
||||
|
||||
* entities.c: do not generate " for " outside of attributes
|
||||
* result//*: this changes the output of some tests
|
||||
|
||||
Mon Jun 9 12:28:58 CEST 2003 Daniel Veillard <daniel@veillard.com>
|
||||
|
||||
* parser.c xmlIO.c: trying to fix #114277 about when file
|
||||
|
@ -632,6 +632,7 @@ xmlEncodeEntitiesReentrant(xmlDocPtr doc, const xmlChar *input) {
|
||||
*out++ = 'm';
|
||||
*out++ = 'p';
|
||||
*out++ = ';';
|
||||
#if 0
|
||||
} else if (*cur == '"') {
|
||||
*out++ = '&';
|
||||
*out++ = 'q';
|
||||
@ -639,7 +640,6 @@ xmlEncodeEntitiesReentrant(xmlDocPtr doc, const xmlChar *input) {
|
||||
*out++ = 'o';
|
||||
*out++ = 't';
|
||||
*out++ = ';';
|
||||
#if 0
|
||||
} else if ((*cur == '\'') && (!html)) {
|
||||
*out++ = '&';
|
||||
*out++ = 'a';
|
||||
|
@ -157,9 +157,9 @@ eval("page" + id + " = window.open(URL, '" + id + "', 'toolbars=0, scrollbars=0,
|
||||
| <a href="http://bp6.gamesquad.net/#news_top">top</a></font> <br><font color="black" face="Arial" size="2"><b>Get them now!!</b><br>This is a
|
||||
fixed bp6 wallpaper. In all the popular flavors, err...
|
||||
resolutions.<br><img height="180" src="doc3_files/3-800.jpg" width="240"><br>It's still the Intels Inside one with a spelling
|
||||
change; from "Mothboard" to "Motherboard"<br><br>Thanks to Matt for
|
||||
change; from "Mothboard" to "Motherboard"<br><br>Thanks to Matt for
|
||||
pointing that out to me.<br>I would also like to thank Kevin for
|
||||
hosting my last batch and Radu for the previous "DUEL"/"DUAL"
|
||||
hosting my last batch and Radu for the previous "DUEL"/"DUAL"
|
||||
error.<br>And 1 more person, THANK YOU TIM for letting me borrow
|
||||
your server space ;-)<br><br>If you need a weird resolution, feel
|
||||
free to <a href="mailto:Holodeck2@home.com">e-mail</a> me requesting
|
||||
@ -208,7 +208,7 @@ eval("page" + id + " = window.open(URL, '" + id + "', 'toolbars=0, scrollbars=0,
|
||||
BP6er but also a [H]ardOCPer<br></font><br><br><a name="newsitem964644047,60218,"></a><b><u><font color="#003366" face="Verdana, Arial" size="2">WiLd CaSe!!</font></u></b><br><font color="#0066cc" face="Arial" size="1"><small>Posted by <a class="nav" href="mailto:Holodeck@bp6.com">Holodeck2</a> @ 1:40PM
|
||||
PDT</small> <a href="http://bp6.gamesquad.net/news/964644047,60218,.html"><img border="0" src="doc3_files/comments.gif">8 comments</a>
|
||||
| <a href="http://bp6.gamesquad.net/#news_top">top</a></font> <br><font color="black" face="Arial" size="2">Now this person really knows how to
|
||||
keep his case cool!!<br>Addin an 18" Fan!! WOW!!<br><br><a href="http://www.envador.com/Photos/PVCII/" target="_blank"><img src="doc3_files/TN_OpenedUp1.jpg"></a><br>Click to go to his
|
||||
keep his case cool!!<br>Addin an 18" Fan!! WOW!!<br><br><a href="http://www.envador.com/Photos/PVCII/" target="_blank"><img src="doc3_files/TN_OpenedUp1.jpg"></a><br>Click to go to his
|
||||
site.<br></font><br><br><a name="newsitem964631110,84122,"></a><b><u><font color="#003366" face="Verdana, Arial" size="2">What the heck is a
|
||||
Peltier?!?!</font></u></b><br><font color="#0066cc" face="Arial" size="1"><small>Posted by <a class="nav" href="mailto:Holodeck@bp6.com">Holodeck2</a> @ 10:05AM
|
||||
PDT</small> <a href="http://bp6.gamesquad.net/news/964631110,84122,.html"><img border="0" src="doc3_files/comments.gif">6 comments</a>
|
||||
@ -239,7 +239,7 @@ eval("page" + id + " = window.open(URL, '" + id + "', 'toolbars=0, scrollbars=0,
|
||||
contact me or post it on the messageboard.<br><br>Ways to contact
|
||||
me.<br>E-mail: <a href="mailto:Holodeck2@home.com">Holodeck2@home.com</a> (All E-mails
|
||||
will be answered in 24 hours or less, I guarantee it.)<br>When you
|
||||
write me an e-mail please put in the subject line "BP6" then the
|
||||
write me an e-mail please put in the subject line "BP6" then the
|
||||
rest of your subject so my e-mail program can sort it, thanks<br><a href="http://www.aol.com/aim">AIM: </a>Holodeck2 (instant response
|
||||
if I’m in front of my comp and not trying to frag someone)<br><a href="http://www.icq.com/download">ICQ: </a>82640218 (rarely
|
||||
on)<br><br>P.S. If someone named “Digital Vortex” on either Quake 3
|
||||
@ -257,14 +257,14 @@ eval("page" + id + " = window.open(URL, '" + id + "', 'toolbars=0, scrollbars=0,
|
||||
rescue....</font></u></b><br><font color="#0066cc" face="Arial" size="1"><small>Posted by <a class="nav" href="mailto:tim@bp6.com">tim</a> @ 12:53AM PDT</small> <a href="http://bp6.gamesquad.net/news/964425184,95812,.html"><img border="0" src="doc3_files/comments.gif">2 comments</a>
|
||||
| <a href="http://bp6.gamesquad.net/#news_top">top</a></font> <br><font color="black" face="Arial" size="2">Do you sweat during the BIOS flashing
|
||||
procedure on your BP6 mobo? If so then this little gadget maybe
|
||||
worth a first look. It's called the "<b>RD1 BIOS Savior</b>" and it
|
||||
worth a first look. It's called the "<b>RD1 BIOS Savior</b>" and it
|
||||
plugs in between your BIOS ROM and the BIOS ROM socket on your mobo.
|
||||
This device will backup your BIOS and and allow you to recover your
|
||||
BIOS in the event that your flashing session goes wrong. In the
|
||||
event of a bad flash, just flip a switch on the RDI and boot up your
|
||||
system, and flash again. This is also good as a failsafe in case you
|
||||
don't believe in Virus Protecting your computer. (Thanks to Fred for
|
||||
link)<br><a href="http://www.ioss.com.tw/eg/rd1/RD1info0004.PDF" target="_NEW">Manufacturers Brochure</a> (PDF Format)<br><a href="http://192.216.185.10/mwave/doc/A06950.html" target="_BLANK"">Another info page</a><br><a href="http://192.216.185.10/mwave/ProdMB-AC-MW.hmx?UID=&CID=&updepts=MB&DNAME=%3Cb%3EMotherboards%3C%2Fb%3E&Back=ProdMB-AC-MW.hmx?" target="_BLANK">Available for about $20</a><br><br><img src="doc3_files/rd1.jpg"></font><br><br><a name="newsitem963875853,12731,"></a>
|
||||
link)<br><a href="http://www.ioss.com.tw/eg/rd1/RD1info0004.PDF" target="_NEW">Manufacturers Brochure</a> (PDF Format)<br><a href="http://192.216.185.10/mwave/doc/A06950.html" target='_BLANK"'>Another info page</a><br><a href="http://192.216.185.10/mwave/ProdMB-AC-MW.hmx?UID=&CID=&updepts=MB&DNAME=%3Cb%3EMotherboards%3C%2Fb%3E&Back=ProdMB-AC-MW.hmx?" target="_BLANK">Available for about $20</a><br><br><img src="doc3_files/rd1.jpg"></font><br><br><a name="newsitem963875853,12731,"></a>
|
||||
<table bgcolor="#003399" width="100%"><tbody><tr><td><font color="#ffffff" face="Verdana,arial" size="2"><b>Monday,
|
||||
July 17, 2000</b></font></td></tr></tbody></table>
|
||||
<br><!--<hr noshade width=100%>--><b><u><font color="#003366" face="Verdana, Arial" size="2">How To
|
||||
|
File diff suppressed because one or more lines are too long
@ -3,4 +3,4 @@
|
||||
<!ENTITY very_big_entity_name01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789_end_of_very_big_ent_name '"Yes"'>
|
||||
<!ENTITY WhatHeSaid "He said &very_big_entity_name01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789_end_of_very_big_ent_name;">
|
||||
]>
|
||||
<doc>He said "Yes"</doc>
|
||||
<doc>He said "Yes"</doc>
|
||||
|
@ -3,4 +3,4 @@
|
||||
<!ENTITY YN '"Yes"'>
|
||||
<!ENTITY WhatHeSaid "He said &YN;">
|
||||
]>
|
||||
<doc>He said "Yes"</doc>
|
||||
<doc>He said "Yes"</doc>
|
||||
|
@ -29,7 +29,7 @@
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<link>http://slashdot.org/askslashdot/99/06/05/1815225.shtml</link>
|
||||
</item>
|
||||
|
||||
|
@ -34,7 +34,7 @@
|
||||
<image>topictech2.jpg</image>
|
||||
</story>
|
||||
<story>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<url>http://slashdot.org/askslashdot/99/06/05/1815225.shtml</url>
|
||||
<time>1999-06-05 20:00:00</time>
|
||||
<author>Cliff</author>
|
||||
|
@ -29,7 +29,7 @@
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<link>http://slashdot.org/askslashdot/99/06/05/1815225.shtml</link>
|
||||
</item>
|
||||
|
||||
|
@ -34,7 +34,7 @@
|
||||
<image>topictech2.jpg</image>
|
||||
</story>
|
||||
<story>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<title>Ask Slashdot: Another Word for "Hacker"?</title>
|
||||
<url>http://slashdot.org/askslashdot/99/06/05/1815225.shtml</url>
|
||||
<time>1999-06-05 20:00:00</time>
|
||||
<author>Cliff</author>
|
||||
|
@ -145,8 +145,8 @@ Draft status, or it may be dropped as a W3C work item.</p>
|
||||
<p>Publication as a Proposed Recommendation does not imply endorsement
|
||||
by the W3C membership. This is still a draft document and may be
|
||||
updated, replaced or obsoleted by other documents at any time. It is
|
||||
inappropriate to cite W3C Proposed Recommendation as other than "work
|
||||
in progress."</p>
|
||||
inappropriate to cite W3C Proposed Recommendation as other than "work
|
||||
in progress."</p>
|
||||
|
||||
<p>This document has been produced as part of the <a href="http://www.w3.org/MarkUp/">W3C HTML Activity</a>. The goals of
|
||||
the <a href="http://www.w3.org/MarkUp/Group/">HTML Working
|
||||
@ -372,18 +372,18 @@ requirements for correct document construction.</dd>
|
||||
|
||||
<dt>May</dt>
|
||||
|
||||
<dd>With respect to implementations, the word "may" is to be
|
||||
<dd>With respect to implementations, the word "may" is to be
|
||||
interpreted as an optional feature that is not required in this
|
||||
specification but can be provided. With respect to <a href="#docconf">Document Conformance</a>, the word "may" means that
|
||||
the optional feature must not be used. The term "optional" has
|
||||
the same definition as "may".</dd>
|
||||
specification but can be provided. With respect to <a href="#docconf">Document Conformance</a>, the word "may" means that
|
||||
the optional feature must not be used. The term "optional" has
|
||||
the same definition as "may".</dd>
|
||||
|
||||
<dt>Must</dt>
|
||||
|
||||
<dd>In this specification, the word "must" is to be interpreted
|
||||
<dd>In this specification, the word "must" is to be interpreted
|
||||
as a mandatory requirement on the implementation or on Strictly
|
||||
Conforming XHTML Documents, depending upon the context. The term
|
||||
"shall" has the same definition as "must".</dd>
|
||||
"shall" has the same definition as "must".</dd>
|
||||
|
||||
<dt>Reserved</dt>
|
||||
|
||||
@ -393,9 +393,9 @@ Conforming User Agents.</dd>
|
||||
|
||||
<dt>Should</dt>
|
||||
|
||||
<dd>With respect to implementations, the word "should" is to be
|
||||
<dd>With respect to implementations, the word "should" is to be
|
||||
interpreted as an implementation recommendation, but not a
|
||||
requirement. With respect to documents, the word "should" is to
|
||||
requirement. With respect to documents, the word "should" is to
|
||||
be interpreted as recommended programming practice for documents
|
||||
and a requirement for Strictly Conforming XHTML Documents.</dd>
|
||||
|
||||
@ -549,16 +549,16 @@ local system conventions.</p>
|
||||
|
||||
<pre>
|
||||
<!DOCTYPE html
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-strict.dtd>
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-strict.dtd>
|
||||
|
||||
<!DOCTYPE html
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-transitional.dtd>
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-transitional.dtd>
|
||||
|
||||
<!DOCTYPE html
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-frameset.dtd>
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-frameset.dtd>
|
||||
</pre>
|
||||
</li>
|
||||
</ol>
|
||||
@ -567,16 +567,16 @@ local system conventions.</p>
|
||||
|
||||
<div class="good">
|
||||
<pre>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!DOCTYPE html
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
||||
"http://www.w3.org/TR/1999/PR-xhtml1-19991210/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<title>Virtual Library</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>Moved to <a href="http://vlib.org/">vlib.org</a>.</p>
|
||||
<p>Moved to <a href="http://vlib.org/">vlib.org</a>.</p>
|
||||
</body>
|
||||
</html></pre>
|
||||
</div>
|
||||
@ -601,13 +601,13 @@ be used in conjunction with the MathML Recommendation:</p>
|
||||
|
||||
<div class="good">
|
||||
<pre>
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
|
||||
<head>
|
||||
<title>A Math Example</title>
|
||||
</head>
|
||||
<body>
|
||||
<p>The following is MathML markup:</p>
|
||||
<math xmlns="http://www.w3.org/1998/Math/MathML">
|
||||
<math xmlns="http://www.w3.org/1998/Math/MathML">
|
||||
<apply> <log/>
|
||||
<logbase>
|
||||
<cn> 3 </cn>
|
||||
@ -625,16 +625,16 @@ could be incorporated into another XML namespace:</p>
|
||||
|
||||
<div class="good">
|
||||
<pre>
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!-- initially, the default namespace is "books" -->
|
||||
<?xml version="1.0" encoding="UTF-8"?>
|
||||
<!-- initially, the default namespace is "books" -->
|
||||
<book xmlns='urn:loc.gov:books'
|
||||
xmlns:isbn='urn:ISBN:0-395-36341-6' xml:lang="en" lang="en">
|
||||
xmlns:isbn='urn:ISBN:0-395-36341-6' xml:lang="en" lang="en">
|
||||
<title>Cheaper by the Dozen</title>
|
||||
<isbn:number>1568491379</isbn:number>
|
||||
<notes>
|
||||
<!-- make HTML the default namespace for a hypertext commentary -->
|
||||
<p xmlns='http://www.w3.org/1999/xhtml'>
|
||||
This is also available <a href="http://www.w3.org/">online</a>.
|
||||
This is also available <a href="http://www.w3.org/">online</a>.
|
||||
</p>
|
||||
</notes>
|
||||
</book>
|
||||
@ -829,7 +829,7 @@ to be numeric.</p>
|
||||
<div class="good">
|
||||
<p><strong><em>CORRECT: quoted attribute values</em></strong></p>
|
||||
|
||||
<p><table rows="3"></p>
|
||||
<p><table rows="3"></p>
|
||||
</div>
|
||||
|
||||
<div class="bad">
|
||||
@ -849,7 +849,7 @@ without their value being specified.</p>
|
||||
<div class="good">
|
||||
<p><strong><em>CORRECT: unminimized attributes</em></strong></p>
|
||||
|
||||
<p><dl compact="compact"></p>
|
||||
<p><dl compact="compact"></p>
|
||||
</div>
|
||||
|
||||
<div class="bad">
|
||||
@ -921,7 +921,7 @@ documents.</p>
|
||||
|
||||
<p>SGML gives the writer of a DTD the ability to exclude specific
|
||||
elements from being contained within an element. Such
|
||||
prohibitions (called "exclusions") are not possible in XML.</p>
|
||||
prohibitions (called "exclusions") are not possible in XML.</p>
|
||||
|
||||
<p>For example, the HTML 4.0 Strict DTD forbids the nesting of an
|
||||
'<code>a</code>' element within another '<code>a</code>' element
|
||||
@ -972,8 +972,8 @@ recommended MIME labeling for XML-based applications
|
||||
has yet to be resolved.</p>
|
||||
|
||||
<p>However, XHTML Documents which follow the guidelines set forth
|
||||
in <a href="#guidelines">Appendix C</a>, "HTML Compatibility Guidelines" may be
|
||||
labeled with the Internet Media Type "text/html", as they
|
||||
in <a href="#guidelines">Appendix C</a>, "HTML Compatibility Guidelines" may be
|
||||
labeled with the Internet Media Type "text/html", as they
|
||||
are compatible with most HTML browsers. This document
|
||||
makes no recommendation about MIME labeling of other
|
||||
XHTML documents.</p>
|
||||
@ -1153,7 +1153,7 @@ or UTF-16.</p>
|
||||
></code> of empty elements, e.g. <code class="greenmono">
|
||||
<br /></code>, <code class="greenmono">
|
||||
<hr /></code> and <code class="greenmono"><img
|
||||
src="karen.jpg" alt="Karen" /></code>. Also, use the
|
||||
src="karen.jpg" alt="Karen" /></code>. Also, use the
|
||||
minimized tag syntax for empty elements, e.g. <code class="greenmono"><br /></code>, as the alternative syntax <code class="greenmono"><br></br></code> allowed by XML
|
||||
gives uncertain results in many existing user agents.</p>
|
||||
|
||||
@ -1170,7 +1170,7 @@ do not use the minimized form (e.g. use <code class="greenmono">
|
||||
external scripts if your script uses <code><</code> or <code>
|
||||
&</code> or <code>]]></code> or <code>--</code>. Note that XML parsers
|
||||
are permitted to silently remove the contents of comments. Therefore, the historical
|
||||
practice of "hiding" scripts and style sheets within comments to make the
|
||||
practice of "hiding" scripts and style sheets within comments to make the
|
||||
documents backward compatible is likely to not work as expected in XML-based
|
||||
implementations.</p>
|
||||
|
||||
@ -1191,13 +1191,13 @@ of the <code>xml:lang</code> attribute takes precedence.</p>
|
||||
|
||||
<h2>C.8 Fragment Identifiers</h2>
|
||||
<p>In XML, <abbr title="Uniform Resource Identifiers">URIs</abbr> [<a href="#ref-rfc2396">RFC2396</a>] that end with fragment identifiers of the form
|
||||
<code>"#foo"</code> do not refer to elements with an attribute
|
||||
<code>name="foo"</code>; rather, they refer to elements with an
|
||||
<code>"#foo"</code> do not refer to elements with an attribute
|
||||
<code>name="foo"</code>; rather, they refer to elements with an
|
||||
attribute defined to be of type <code>ID</code>, e.g., the <code>
|
||||
id</code> attribute in HTML 4.0. Many existing HTML clients don't
|
||||
support the use of <code>ID</code>-type attributes in this way,
|
||||
so identical values may be supplied for both of these attributes to ensure
|
||||
maximum forward and backward compatibility (e.g., <code class="greenmono"><a id="foo" name="foo">...</a></code>).</p>
|
||||
maximum forward and backward compatibility (e.g., <code class="greenmono"><a id="foo" name="foo">...</a></code>).</p>
|
||||
|
||||
<p>Further, since the set of
|
||||
legal values for attributes of type <code>ID</code> is much smaller than
|
||||
@ -1220,10 +1220,10 @@ removed from XHTML in subsequent versions.</p>
|
||||
<h2>C.9 Character Encoding</h2>
|
||||
<p>To specify a character encoding in the document, use both the
|
||||
encoding attribute specification on the xml declaration (e.g.
|
||||
<code class="greenmono"><?xml version="1.0"
|
||||
encoding="EUC-JP"?></code>) and a meta http-equiv statement
|
||||
(e.g. <code class="greenmono"><meta http-equiv="Content-type"
|
||||
content='text/html; charset="EUC-JP"' /></code>). The
|
||||
<code class="greenmono"><?xml version="1.0"
|
||||
encoding="EUC-JP"?></code>) and a meta http-equiv statement
|
||||
(e.g. <code class="greenmono"><meta http-equiv="Content-type"
|
||||
content='text/html; charset="EUC-JP"' /></code>). The
|
||||
value of the encoding attribute of the xml processing instruction
|
||||
takes precedence.</p>
|
||||
|
||||
@ -1274,7 +1274,7 @@ accordingly.</li>
|
||||
<p>
|
||||
When an attribute value contains an ampersand, it must be expressed as a character
|
||||
entity reference
|
||||
(e.g. "<code>&amp;</code>"). For example, when the
|
||||
(e.g. "<code>&amp;</code>"). For example, when the
|
||||
<code>href</code> attribute
|
||||
of the <code>a</code> element refers to a
|
||||
CGI script that takes parameters, it must be expressed as
|
||||
@ -1304,14 +1304,14 @@ you should always explicitely add a tbody element if it is referred to
|
||||
in a CSS selector.</li>
|
||||
|
||||
<li>Within the XHTML name space, user agents are expected to
|
||||
recognize the "id" attribute as an attribute of type ID.
|
||||
recognize the "id" attribute as an attribute of type ID.
|
||||
Therefore, style sheets should be able to continue using the
|
||||
shorthand "#" selector syntax even if the user agent does not read
|
||||
shorthand "#" selector syntax even if the user agent does not read
|
||||
the DTD.</li>
|
||||
|
||||
<li>Within the XHTML name space, user agents are expected to
|
||||
recognize the "class" attribute. Therefore, style sheets should be
|
||||
able to continue using the shorthand "." selector syntax.</li>
|
||||
recognize the "class" attribute. Therefore, style sheets should be
|
||||
able to continue using the shorthand "." selector syntax.</li>
|
||||
|
||||
<li>
|
||||
CSS defines different conformance rules for HTML and XML documents;
|
||||
@ -1363,37 +1363,37 @@ Dan Zigmond, WebTV Networks</dd>
|
||||
|
||||
<dt><a name="ref-css2" id="ref-css2"><b>[CSS2]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.w3.org/TR/REC-CSS2">"Cascading Style Sheets, level 2 (CSS2) Specification"</a>, B.
|
||||
<dd><a href="http://www.w3.org/TR/REC-CSS2">"Cascading Style Sheets, level 2 (CSS2) Specification"</a>, B.
|
||||
Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.<br />
|
||||
Available at: <a href="http://www.w3.org/TR/REC-CSS2">
|
||||
http://www.w3.org/TR/REC-CSS2</a></dd>
|
||||
|
||||
<dt><a name="ref-dom" id="ref-dom"><b>[DOM]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.w3.org/TR/REC-DOM-Level-1">"Document Object Model (DOM) Level 1 Specification"</a>, Lauren
|
||||
<dd><a href="http://www.w3.org/TR/REC-DOM-Level-1">"Document Object Model (DOM) Level 1 Specification"</a>, Lauren
|
||||
Wood <i>et al.</i>, 1 October 1998.<br />
|
||||
Available at: <a href="http://www.w3.org/TR/REC-DOM-Level-1">
|
||||
http://www.w3.org/TR/REC-DOM-Level-1</a></dd>
|
||||
|
||||
<dt><a name="ref-html4" id="ref-html4"><b>[HTML]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.w3.org/TR/1999/PR-html40-19990824">"HTML 4.01 Specification"</a>, D. Raggett, A. Le Hors, I.
|
||||
<dd><a href="http://www.w3.org/TR/1999/PR-html40-19990824">"HTML 4.01 Specification"</a>, D. Raggett, A. Le Hors, I.
|
||||
Jacobs, 24 August 1999.<br />
|
||||
Available at: <a href="http://www.w3.org/TR/1999/PR-html40-19990824">
|
||||
http://www.w3.org/TR/1999/PR-html40-19990824</a></dd>
|
||||
|
||||
<dt><a name="ref-posix" id="ref-posix"><b>[POSIX.1]</b></a></dt>
|
||||
|
||||
<dd>"ISO/IEC 9945-1:1990 Information Technology - Portable
|
||||
<dd>"ISO/IEC 9945-1:1990 Information Technology - Portable
|
||||
Operating System Interface (POSIX) - Part 1: System Application
|
||||
Program Interface (API) [C Language]", Institute of Electrical
|
||||
Program Interface (API) [C Language]", Institute of Electrical
|
||||
and Electronics Engineers, Inc, 1990.</dd>
|
||||
|
||||
<dt><a name="ref-rfc2046" id="ref-rfc2046"><b>
|
||||
[RFC2046]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2046.txt">"RFC2046: Multipurpose Internet Mail Extensions (MIME) Part
|
||||
Two: Media Types"</a>, N. Freed and N. Borenstein, November
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2046.txt">"RFC2046: Multipurpose Internet Mail Extensions (MIME) Part
|
||||
Two: Media Types"</a>, N. Freed and N. Borenstein, November
|
||||
1996.<br />
|
||||
Available at <a href="http://www.ietf.org/rfc/rfc2046.txt">
|
||||
http://www.ietf.org/rfc/rfc2046.txt</a>. Note that this RFC
|
||||
@ -1402,15 +1402,15 @@ obsoletes RFC1521, RFC1522, and RFC1590.</dd>
|
||||
<dt><a name="ref-rfc2119" id="ref-rfc2119"><b>
|
||||
[RFC2119]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2119.txt">"RFC2119: Key words for use in RFCs to Indicate Requirement
|
||||
Levels"</a>, S. Bradner, March 1997.<br />
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2119.txt">"RFC2119: Key words for use in RFCs to Indicate Requirement
|
||||
Levels"</a>, S. Bradner, March 1997.<br />
|
||||
Available at: <a href="http://www.ietf.org/rfc/rfc2119.txt">
|
||||
http://www.ietf.org/rfc/rfc2119.txt</a></dd>
|
||||
|
||||
<dt><a name="ref-rfc2376" id="ref-rfc2376"><b>
|
||||
[RFC2376]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2376.txt">"RFC2376: XML Media Types"</a>, E. Whitehead, M. Murata, July
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2376.txt">"RFC2376: XML Media Types"</a>, E. Whitehead, M. Murata, July
|
||||
1998.<br />
|
||||
Available at: <a href="http://www.ietf.org/rfc/rfc2376.txt">
|
||||
http://www.ietf.org/rfc/rfc2376.txt</a></dd>
|
||||
@ -1418,8 +1418,8 @@ http://www.ietf.org/rfc/rfc2376.txt</a></dd>
|
||||
<dt><a name="ref-rfc2396" id="ref-rfc2396"><b>
|
||||
[RFC2396]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2396.txt">"RFC2396: Uniform Resource Identifiers (URI): Generic
|
||||
Syntax"</a>, T. Berners-Lee, R. Fielding, L. Masinter, August
|
||||
<dd><a href="http://www.ietf.org/rfc/rfc2396.txt">"RFC2396: Uniform Resource Identifiers (URI): Generic
|
||||
Syntax"</a>, T. Berners-Lee, R. Fielding, L. Masinter, August
|
||||
1998.<br />
|
||||
This document updates RFC1738 and RFC1808.<br />
|
||||
Available at: <a href="http://www.ietf.org/rfc/rfc2396.txt">
|
||||
@ -1427,14 +1427,14 @@ http://www.ietf.org/rfc/rfc2396.txt</a></dd>
|
||||
|
||||
<dt><a name="ref-xml" id="ref-xml"><b>[XML]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.w3.org/TR/REC-xml">"Extensible Markup Language (XML) 1.0 Specification"</a>, T.
|
||||
<dd><a href="http://www.w3.org/TR/REC-xml">"Extensible Markup Language (XML) 1.0 Specification"</a>, T.
|
||||
Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998.<br />
|
||||
Available at: <a href="http://www.w3.org/TR/REC-xml">
|
||||
http://www.w3.org/TR/REC-xml</a></dd>
|
||||
|
||||
<dt><a name="ref-xmlns" id="ref-xmlns"><b>[XMLNAMES]</b></a></dt>
|
||||
|
||||
<dd><a href="http://www.w3.org/TR/REC-xml-names">"Namespaces in XML"</a>, T. Bray, D. Hollander, A. Layman, 14
|
||||
<dd><a href="http://www.w3.org/TR/REC-xml-names">"Namespaces in XML"</a>, T. Bray, D. Hollander, A. Layman, 14
|
||||
January 1999.<br />
|
||||
XML namespaces provide a simple method for qualifying names used
|
||||
in XML documents by associating them with namespaces identified
|
||||
|
Loading…
x
Reference in New Issue
Block a user