kc3-lang/libxml2/result/HTML/fp40.htm
-
Show log
Commit
-
Hash : f933c898
Author :
Date : 2012-09-07T19:32:12
Keep non-significant blanks node in HTML parser For https://bugzilla.gnome.org/show_bug.cgi?id=681822 Regardless if the option HTML_PARSE_NOBLANKS is set or not, blank nodes are removed from a HTML document, for example: <html> <head> <title>This is a test.</title> </head> <body> <p>This is a test.</p> </body> </html> is read as: <html><head><title>This is a test.</title></head><body> <p>This is a test.</p> </body></html> This changes the default behaviour but the old behaviour is available as expected when using the parser flag HTML_PARSE_NOBLANKS Based on original patch from Igor Ignatyuk <igor_ignatiouk@hotmail.com> * HTMLparser.c: change various places in the parser where ignorable_space SAX callback was called without checking for the parser flag preference * xmllint.c: make sure we use the new flag even for HTML parsing * result/HTML/*: this modifies the output of a number of tests
-
result/HTML/fp40.htm
-
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN"> <html> <head> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <title>README - Microsoft FrontPage 2000 Server Extensions</title> <meta name="Microsoft Theme" content="none"> </head> <body> <font face="Verdana"> <h1><a name="top">Microsoft FrontPage 2000 Server Extensions, UNIX</a></h1> <font size="2"><i>© Copyright Microsoft Corporation, 1999 </i></font> <p>The FrontPage Server Extensions are a set of programs on the Web server that support: </p> <ul> <li>Authoring FrontPage webs</li> <li>Administering FrontPage webs</li> <li>Browse-time FrontPage web functionality</li> </ul> <h2>Contents </h2> <a href="#relnotes">Release Notes</a><br> <a href="#moreinfo">Resources for More Information</a> <p> </p> <hr> <h2><a name="relnotes">Release Notes</a></h2> <p>This section provides complementary or late-breaking information to supplement the Microsoft FrontPage Server Extensions documentation.</p> <p><a href="#apache">Apache 1.3.4 Support</a><br> <a href="#upgrading">Upgrading from previous version of FrontPage Server Extensions</a><br> <a href="#executables">Uploading files into executable folders</a></p> <p align="right"><font size="1"><a href="#top">Top of Page</a></font></p> <h3><a name="apache">Apache 1.3.4 Support</a></h3> <p>You need to take some special steps to run the FrontPage Server Extensions with Apache 1.3.4. FrontPage Server Extensions expect to find all resource directives in the main server configuration file, usually http.conf. To prevent the server extensions from using any secondary configuration files (access.conf, srm.conf), add the following lines to http.conf:</p> </font> <blockquote> <font face="Courier New"> ResourceConfig /dev/null <br> AccessConfig /dev/null</font> </blockquote> <font face="Verdana"> <p>If you have some settings stored in secondary configuration files, move them to http.conf.</p> <p>You must stop and restart the web server for your changes to http.conf to take effect.</p> <p align="right"><font size="1"><a href="#relnotes">Top of Section</a></font></p> <h3><a name="upgrading">Upgrading from previous version of FrontPage Server Extensions</a></h3> <p>Custom entries in frontpage.cnf are not migrated to FrontPage 2000.</p> <p>When you install FrontPage 2000 Server Extensions, a new frontpage.cnf file is created in the /usr/local/frontpage/version4.0 directory. Any custom settings stored in a previous-version frontpage.cnf are not used. However, you can copy your custom settings from the previous-version frontpage.cnf file after you install the FrontPage 2000 Server Extensions.</p> <p>Do not overwrite the FrontPage 2000 frontpage.cnf file with a frontpage.cnf file from an earlier version of the FrontPage Server Extensions.</p> <p align="right"><font size="1"><a href="#relnotes">Top of Section</a></font></p> <h3><a name="executables">Uploading files into executable folders</a></h3> <p>After upgrading to FrontPage 2000, FrontPage authors will not be able to upload files into executable folders. For security reasons, the default setting on FrontPage 2000 webs does not allow authors to upload executable files into executable folders in a FrontPage web. This setting protects servers so that authors do not inadvertently upload a program containing a bug or a virus.</p> <p>To allow FrontPage authors to upload executables, set the NoExecutableCgiUpload configuration variable to zero (0). For information about FrontPage Server Extension configuration variables, see the FrontPage 2000 Server Extensions Resource Kit at <a href="http://officeupdate.microsoft.com/frontpage/wpp/serk/">http://officeupdate.microsoft.com/frontpage/wpp/serk/</a>.</p> <p align="right"><font size="1"><a href="#relnotes">Top of Section</a></font></p> <hr> <h2><a name="moreinfo">Resources for More Information</a></h2> <p>This section lists sources of more information about the FrontPage Server Extensions.</p> <p><a href="#serk">Server Extensions Resource Kit</a><br> <a href="#serkupdate">Server Extensions Resource Kit Update</a><br> <a href="#kb">Knowledge Base</a></p> <p align="right"><font size="1"><a href="#top">Top of Page</a></font></p> <h3><a name="serk">Server Extensions Resource Kit</a></h3> <p>The FrontPage 2000 Server Extensions include a full set of documentation: the Server Extensions Resource Kit. This is an HTML document installed on the server machine (by default) in /usr/local/frontpage/version4.0/serk. To view the Server Extensions Resource Kit, open /usr/local/frontpage/version4.0/serk/default.htm in your Web browser.</p> <p>The Server Extensions Resource Kit contains detailed information about installing and administering the FrontPage Server Extensions along with an overview of the Server Extensions, a detailed discussion of Server Extensions security on UNIX and Windows, troubleshooting information, and a full set of appendixes.</p> <p align="right"><font size="1"><a href="#moreinfo">Top of Section</a></font></p> <h3><a name="serkupdate">Server Extensions Resource Kit Update</a></h3> <p>For updated information about installing, setting up, and administrating the FrontPage Server Extensions, see the Server Extensions Resource Kit Update at: <a href="http://officeupdate.microsoft.com/frontpage/wpp/serk/">http://officeupdate.microsoft.com/frontpage/wpp/serk/</a>.</p> <p align="right"><font size="1"><a href="#moreinfo">Top of Section</a></font></p> <h3><a name="kb">Microsoft Knowledge Base</a></h3> <p>For further technical information on FrontPage, please consult Support Online. Use Support Online to easily search Microsoft Product Support Services' collection of resources including technical articles from Microsoft's extensive Knowledge Base, FAQs, & troubleshooters to find fast, accurate answers. You can also customize the site to control your search using either keywords or the site's natural language search engine, which uses normal everyday language for answering inquiries, so you can write your question in your own words. To begin, go to <a href="http://support.microsoft.com/support/">http://support.microsoft.com/support/</a>.</p> <p align="right"><font size="1"><a href="#moreinfo">Top of Section</a></font></p> <p> </p> </font> </body> </html>