cheng/libexpat
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove in favor of https://libexpat.github.io/ (issue #1)

Browse Source 
As htdocs/index.html included a change log: A (more recent)
plain text version of the change log can be found at expat/Changes.
This commit is contained in:
Sebastian Pipping 2017-05-11 09:02:03 +02:00
parent 14f175334d
commit b357bf21e7
12 changed files with 0 additions and 1657 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
htdocs/Makefile
View File

@ -1,5 +0,0 @@
DIR=/home/groups/e/ex/expat/htdocs
HOST=expat.sourceforge.net
install:
ssh $(HOST) cd $(DIR) '&&' cvs up -P -d

120
htdocs/dev/cvs.html
View File

@ -1,120 +0,0 @@
<html>
<head>
<title>CVS Access to Expat</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>CVS Access to Expat</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<h3>View CVS Online</h3>
<ul>
<li><a href="http://expat.cvs.sourceforge.net"
>Browse online.</a></li>
</ul>
<h3>Anonymous CVS Access</h3>
<p>The Expat CVS repository can be checked out through anonymous
(pserver) CVS with the following instructions. The module you wish to
check out must be specified as the <i>modulename</i>. When prompted
for a password for <i>anonymous</i>, simply press the Enter key.</p>
<pre>
cvs -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat login
cvs -z3 -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat co <i>modulename</i>
</pre>
<p>Updates from within the module's directory do not need the -d
parameter.</p>
<h3>Developer CVS Access via SSH</h3>
<p>Only project developers can access the CVS tree via this method.
SSH1 must be installed on your client machine. Substitute
<i>modulename</i> with the name of the source module you want to check
out, and <i>developername</i> with your SourceForge user name. Enter
your site password when prompted.</p>
<pre>
export CVS_RSH=ssh
cvs -z3 -d:ext:<i>developername</i>@expat.cvs.sourceforge.net:/cvsroot/expat co <i>modulename</i>
</pre>
<h3>Source Modules</h3>
<p>There are only two source modules for Expat at this time. They
are:</p>
<dl>
<dt> expat </dt>
<dd> This contains the C source code for the library, xmlwf, example
applications, and test suite. This is what most people will be
interested in. </dd>
<dt> htdocs </dt>
<dd> The content for <a href="../">www.libexpat.org</a> is located
in this module. </dd>
</dl>
<h3>Receiving Notification of Changes</h3>
<p>If you are interested in the low-level details of Expat's
development, it is possible to have an email sent to you for every
change made to the CVS repository via this mailing list:</p>
<ul>
<li> <a href="http://mail.libexpat.org/mailman/listinfo/expat-checkins/"
>expat-checkins</a> mailing list information, including how to
subscribe. </li>
<li> <a href="http://mail.libexpat.org/pipermail/expat-checkins/"
>expat-checkins archives</a> are also available. </li>
</ul>
<h3>CVS Documentation</h3>
<p>There is a variety of documentation on CVS available online. These
sources are perhaps the most useful:</p>
<ul>
<li> <em><a href="http://www.cvshome.org/docs/manual/">Version
Management with CVS</a></em>
<br />
The official manual for CVS, by Per Cederqvist and others.</li>
<li> <em><a href="http://cvsbook.red-bean.com/">Open Source
Development with CVS</a></em>
<br />
Online version of portions of Karl Fogel's book on using CVS
for open source projects.</li>
<li> <em><a href="http://www.cvshome.org/docs/">CVS Documentation</a></em>
<br />
A list of available documentation on CVS.</li>
</ul>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net">
<img src="http://sflogo.sourceforge.net/sflogo.php?group_id=10127&amp;type=2"
width="125" height="37" border="0" alt="SourceForge.net Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

82
htdocs/dev/expat3.html
View File

@ -1,82 +0,0 @@
<html>
<head>
<title>Changes in Expat 3</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>Changes in Expat 3</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p> This page describes some of the changes which should be expected
in Expat 3. These are intended as notes made by the developers as
things get thought through; these can change at any time. This is
<em>not</em> a projected feature list for Expat 3; to learn about the
target features, please read the <cite><a href="roadmap.html">Expat
Development Roadmap</a></cite>. The changes described here are much
more focused on the details of Expat 3, and no attempt has been made
to balance the description of small changes with major new feature
development. </p>
<p> This list is not complete; we'll add to this as we think of things
and have time to write about them. </p>
<ul>
<li> Support for XML 1.1 and the corresponding namespaces updates. </li>
<li> The signature of the <code>XML_ParserReset()</code> method will
grow an additional argument allowing specification of what should be
reset. See <a href=
"http://sourceforge.net/tracker/index.php?func=detail&aid=1109116&group_id=10127&atid=110127"
>bug report 1109116: <em>Optimize implementation of
XML_ParserReset</em></a> for more information. </li>
<li> All structural event callback functions will return an
<code>XML_Status</code> value that the parser will check. This will
allow an application to stop or suspend processing without having to
call <code>XML_StopParser</code>, which will therefore become obsolete. </li>
<li> The memory management function signatures will gain an additional
userData-like parameter, so that memory usage can be associated
with a context, allowing usage of memory pools and tracking of memory
usage per parser. The latter could be used to prevent the so-called
"million laughs" DoS attack. </li>
<li> Change how qualified names are reported. Instead of passing one
string where the name parts are separated by a special character, we
are going to use <code>QName</code> structs with members for local name,
namespace URI and prefix. This will apply to element names and attribute
names passed to <code>XML_StartElementHandler</code> and
<code>XML_EndElementHandler</code>. </li>
<li> We will try to add a way of setting additional encodings
by name, using the existing framework built around
<code>XML_UnknownEncodingHandler</code>. </li>
<li> Create different link symbols for different XML_Char sizes.
This would make it possible for different shared libraries making up an
application on linux, to link against expat shared libraries that have
been compiled with different definitions for XML_Char.</li>
</ul>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net">
<img src="http://sflogo.sourceforge.net/sflogo.php?group_id=10127&amp;type=2"
width="125" height="37" border="0" alt="SourceForge.net Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>@

56
htdocs/dev/index.html
View File

@ -1,56 +0,0 @@
<html>
<head>
<title>Development of Expat</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>Development of Expat</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p>This area contains information for the developers and maintainers
of Expat.</p>
<ul>
<!-- the requirements documents have not been maintained
<li> <a href="relreqs-1-95-5.html">Requirements</a> for the next
release (1.95.5).
<br />
Other releases:
<a href="relreqs-1-95-4.html">1.95.4</a>
</li>
-->
<li> <a href="roadmap.html">Development roadmap</a> sketching the
directions for future development. </li>
<li> <a href="expat3.html">Changes in Expat 3</a>, some notes about
what's likely to change in Expat 3. </li>
<li> <a href="cvs.html">CVS instructions</a> for developers and
occasional contributors. </li>
<li> <a href="trackers.html">Guidelines</a> for using the
SourceForge bug and patch trackers. </li>
</ul>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net">
<img src="http://sflogo.sourceforge.net/sflogo.php?group_id=10127&amp;type=2"
width="125" height="37" border="0" alt="SourceForge.net Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

86
htdocs/dev/relreqs-1-95-4.html
View File

@ -1,86 +0,0 @@
<html>
<head>
<title>Expat 1.95.4 Requirements</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>Expat 1.95.4 Requirements</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p>The following are the currently-planned release requirements for
Expat 1.95.4. Items will not be removed from this page; if a
requirement is dropped or delayed, it will be moved to the appropriate
section at the end and the reason for the change will be noted.</p>
<h3>Expat 1.95.4 Requirements</h3>
<ul>
<li> The SkippedEntityHandler patch should be checked in and
thoroughly debugged.<br />
See <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=559910&amp;group_id=10127&amp;atid=310127" >SF patch #559910</a>.<br />
<strong>Status: <em>Done.</em></strong>
</li>
<li> <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=441449&amp;group_id=10127&amp;atid=110127"
>SF bug #441449</a> should be resolved.<br />
<strong>Status: <em>Done.</em></strong>
</li>
<li> Hard tab characters will be removed from all source files.
They will be replaced with spaces.<br />
See <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=570903&amp;group_id=10127&amp;atid=110127"
>SF bug #570903</a>.<br />
<strong>Status: <em>Done.</em></strong>
</li>
</ul>
<h3>Delayed Requirements</h3>
<ul>
<li> The InternalEntityRefHandler feature needs to be implemented
and tested.<br />
See the comments for <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=429501&amp;group_id=10127&amp;atid=310127"
>SF patch #429501</a>.<br />
<strong>Status: <em>Delayed</em>:</strong>
This was delayed to a future release to allow urgent bugfixes to be
released sooner rather than being delayed by this feature. The
interface for this feature is proving difficult to design, so this
deserves more consideration.
</li>
<li> The build process on Unix should create both libexpat.{a,so}
and libexpatw.{a,so} by default.
<strong>Status: <em>Delayed</em>:</strong>
Delayed since we don't want the build process changes to hold up
the release of real bug fixes. We can have another release later.
</li>
</ul>
<h3>Dropped Requirements</h3>
<p>There are no dropped requirements at this time.</p>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net/">
<img src="http://cvs.sourceforge.net/sourceforge_whitebg.gif"
width="136" height="79" border="0" alt="SourceForge
Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

64
htdocs/dev/relreqs-1-95-5.html
View File

@ -1,64 +0,0 @@
<html>
<head>
<title>Expat 1.95.5 Requirements</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>Expat 1.95.5 Requirements</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p><strong>This document is partially obsolete!</strong> Please see
the <a href="roadmap.html">roadmap document</a> until this document is
updated.</p>
<p>The following are the currently-planned release requirements for
Expat 1.95.5. Items will not be removed from this page; if a
requirement is dropped or delayed, it will be moved to the appropriate
section at the end and the reason for the change will be noted.</p>
<h3>Expat 1.95.5 Requirements</h3>
<ul>
<li> The InternalEntityRefHandler feature needs to be implemented
and tested.<br />
See the comments for <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=429501&amp;group_id=10127&amp;atid=310127"
>SF patch #429501</a>.
</li>
<li> The build process on Unix should create both libexpat.{a,so}
and libexpatw.{a,so} by default.
</li>
</ul>
<h3>Delayed Requirements</h3>
<p>There are no delayed requirements at this time.</p>
<h3>Dropped Requirements</h3>
<p>There are no dropped requirements at this time.</p>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net/">
<img src="http://cvs.sourceforge.net/sourceforge_whitebg.gif"
width="136" height="79" border="0" alt="SourceForge
Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

235
htdocs/dev/roadmap.html
View File

@ -1,235 +0,0 @@
<html>
<head>
<title>Expat Development Roadmap</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>Expat Development Roadmap</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<h2>PROPOSAL</h2>
<p><em>Updated 5 September 2002.</em></p>
<p>This is a proposed roadmap for the further development of Expat. The
primary purpose for making this proposal is to determine whether our
ideas for continued development are aligned with the needs of the
community. We welcome comment both from Expat users, would-be users,
and members of the XML community who have decided against using Expat
for technical reasons directly related to Expat.</p>
<p>Discussion of this document should be directed to the <a href=
"http://mail.libexpat.org/mailman-21/listinfo/" >expat-discuss</a>
mailing list.</p>
<h3>Goals</h3>
<p>We do <strong>not</strong> plan to alter the goals of the Expat
project. We intend to continue to develop Expat to have the following
qualities:</p>
<ul>
<li> Fast </li>
<li> Conformant to XML 1.0 and Namespaces </li>
<li> Easy to use from C </li>
<li> Easy to wrap / bind for non-C languages </li>
<li> Sufficient to build DOM and SAX on top of
(any final specification for XML) </li>
<li> Modest memory footprint </li>
<li> Portable </li>
</ul>
<h3>Non-Goals</h3>
<ul>
<li> Parsing anything that isn't XML </li>
<li> DOM (any level) </li>
<li> SAX (any version) </li>
<li> Data bindings </li>
<li> Watching the kids </li>
</ul>
<h3>Historical Background</h3>
<p>James Clark initially developed Expat, releasing three stable
versions, identified as versions 1.0, 1.1, and 1.2. Clark Cooper
created a forked version of Expat based on Expat 1.1, for use in the
XML::Parser extension module for Perl.</p>
<p>As James Clark's interests shifted, and his development moved to
the Java environment, the authors of 3rd party language bindings found
it increasingly difficult to integrate Expat with their languages, and
other developers found it difficult to get fixes accepted into Expat
and released. A small group of extension authors were gathered by
Paul Prescod in the hope that Expat could be formed into a more
readily usable library for both direct use in C-language applications
and indirect use from other languages. This group was led by Clark
Cooper and Fred Drake, and received sanction to take over maintenance
of Expat from James Clark. The project is hosted on SourceForge.
This group made their first release as Expat 1.95.0 in September
2000.</p>
<p>Since that time, incremental releases of Expat have been made on a
sporadic schedule, improving functionality and portability with each
release.</p>
<h3>Expat Development Roadmap</h3>
<p>Now that our goals and non-goals have been spelled out, let's take
a look at how we should get there from where we are now. This will be
broken down into two stages: near future activities and far future
activities. In spite of the somewhat temporal labeling of these
categories, please realize that no actual scheduling has been done,
nor is that considered relevant at this time. Actual time to meet
these goals is dependent on the availability of resources to work on
Expat. Parallel development may also happen, depending on the
specific interests of contributers.</p>
<h4>Near Future Activity</h4>
<p>The target of the current line of development will be to release Expat
2.0. The intent is that once Expat 2.0 is released, most of the
development activity for this line will be maintenance, and will be
driven by user-provided problem reports. These are the goals for
goals we have specific to the release of Expat 2.0:</p>
<ul>
<li> Stabilize the current API with some minor revisions to make error
reporting more explicit to allow better reporting and diagnosis. </li>
<li> Introduce a new feature-test macro, XML_MINIMAL, parallel to
XML_DTD, XML_UNICODE, and XML_UNICODE_WCHAR_T. Defining the new
feature when compiling Expat will cause functions that are not
relevant to the rest of the feature macros. (For example, if
XML_DTD is not set but XML_MINIMAL is, the functions that set
handlers for DTD-related events won't be included at all.) This
is intended to make it easier to use Expat in small-memory
devices. </li>
<li> API revisions will be made to improve the runtime discoverability of
Expat capabilities. </li>
<li> Improve portability and performance. </li>
<li> Substantially improve regression tests. </li>
<li> Improve documentation. </li>
<li> Full support for 64-bit platforms. (There are some known decoding
problems currently.) </li>
</ul>
<p>When we're confident that the minor API changes are "right", we'll
finallize the API and release Expat 2.0. Should additional functions
be required as evolutionary improvements, the minor version number
will be incremented, but all existing functions will be maintained for
backward compatibility. Releases that are strictly bug fixes will
have the same minor version number and will gain a "micro" version
number (sometimes called a "patch level").</p>
<h4>Far Future Activity</h4>
<p>Once Expat 2.0 has been released, it will be maintained on a CVS
branch. The head of CVS will be used to develop Expat 3.0. The
changes in Expat 3.0 will be more substantial and will include
important API changes. At this time, we're looking at the following
changes:</p>
<dl>
<dt> More powerful event API </dt>
<dd>
<p>The new API will be sufficiently detailed that a complete and
detailed DOM structure can be built, including both internal and
external entity boundaries in parsed character data content,
attribute value content, and entity values (such as found in
internal entity declarations).</p>
<p>This API will of necessity be somewhat more complex than the
current API, but we expect the current API can be implemented on top
of the new API. For users for whom the Expat 2.0 API is
sufficiently powerful, this API will remain available.</p>
</dd>
<dt> Support for either pull or suspendable parsing </dt>
<dd>
<p>The new API will need to support some way to interrupt processing
without having to parse all XML text passed to the parser so far.
This can be done by either using a pull-based model or a push-based
model (similar to the current API) with the added ability to suspend
parsing on request.</p>
<p>The specific API will depend on the model selected; either a
pull-based model or an suspension model can support each other with
little additional work, and the current push model can be built on
top of either.</p>
<p>The specific model and API will be discussed on the <a href=
"http://mail.libexpat.org/mailman-21/listinfo/" >expat-discuss</a>
mailing list.</p>
</dt>
<dt> New encoding support </dt>
<dd>
<p>A new library may be added to the Expat package that provides a
flexible architecture for defining new encodings, and provides a
large range of common encodings. (It should be possible to develop
this so that it supports both Expat 2.0 and Expat 3.0.)</p>
<p>Another approach which will be considered will be to support
Expat's requirements for decoders using one of the existing open
source encoding support libraries that meets Expat's requirements
for portability. Possible technical approaches would include
implementing an adapter, and developing such an external library to
include direct support for the kind of interface support Expat
needs.</p>
</dd>
<dt> <a href= "http://www.w3.org/TR/xml11/" >XML 1.1</a> (including <a
href="http://www.w3.org/TR/xml-names11/" >Namespaces in XML
1.1</a>), if it ever happens </dt>
<dd>
<p>Well, we're hoping, but it's not time to code for this yet.</p>
</dd>
</dl>
<p>Additional goals may be added during the development of Expat 3.0;
it's just too early to tell.</p>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net/">
<img src="http://cvs.sourceforge.net/sourceforge_whitebg.gif"
width="136" height="79" border="0" alt="SourceForge
Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

266
htdocs/dev/trackers.html
View File

@ -1,266 +0,0 @@
<html>
<head>
<title>SourceForge Tracker Usage</title>
<link rel="STYLESHEET" href="../style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><a href="../"><img src="../expat.png"
border="0"/></a></td>
<td class="banner"><h2>SourceForge Tracker Usage</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p>This document describes the use of the SourceForge bug &amp; patch
trackers by the Expat maintainers. These guidelines are substantially
based on the <a href="http://www.python.org/dev/devfaq.html#a1"
>guidelines used for Python</a>.</p>
<h3>Tracker Item Priority</h3>
<p>The priority field is simple enough; the higher the priority a
report is, the more important it is that the report needs to be
handled. Note that it is the priority of the report relative to other
reports; it does not mean action needs to be taken on the software;
it may be that a report takes a high priority because the bug it
describes is very damaging for someone. Review may, however,
determine that the bug is in someone else's code.</p>
<p>So, how should priority be assigned? SourceForge assigns all new
reports a priority of "5", which is considered "normal". The follow
list shows the meanings of each priority level as used by the Expat
project.</p>
<ol>
<li value="9"> Needs to be solved <em>immediately</em>. We
shouldn't need this since we're volunteers, but it's Ok to use this
if it's assigned to yourself and you have some external reason to
deal with it immediately. </li>
<li value="8"> Needs to be dealt with sooner rather than later, and
is before priority "7" reports. </li>
<li value="7"> Needs to be handled before release. No release can
be made so long as any report with priority "7" or higher is in any
of the trackers we use. </li>
<li value="6"> More important than most reports, but won't cause a
release to be held up. </li>
<li value="5"> Most reports. This is how reports are created by
default. </li>
<li value="4"> Reports with priority "4" and lower typically wait a
long time to be closed, or they're closed fairly quickly because
they're really easy to close. </li>
</ol>
<h3>The Status and Resolution Fields</h3>
<p>In general, the Resolution and Status fields should be close to
self-explanatory, and the "Assigned to:" field should be the person
responsible for taking the next step in the patch process. Both
fields are expected to change value over the life of a patch; the
normal workflow is detailed below.</p>
<p>When you've got the time and the ability, feel free to move any
patch that catches your eye along, whether or not it's been assigned
to you. And if you're assigned to a patch but aren't going to take
reasonably quick action (for whatever reason), please assign it to
someone else or unassign it ASAP: at those times you can't actively
help, actively get out of the way.</p>
<p>If you're an expert in some area and know that a patch in that area
is both needed and non-controversial, just commit your changes
directly -- no need then to get the patch mechanism involved in
it.</p>
<p>The actual patch status is given by the pair of fields called
"Status" and "Resolution":</p>
<table>
<thead>
<tr><th>Status</th>
<th>Resolution</th>
<th>Meaning</th></tr>
</thead>
<tbody>
<tr><td>Open</td>
<td>None</td>
<td>The initial state of all patches.
<p>The patch is under consideration, but has not been
reviewed yet, or is under review but not yet Accepted or
Rejected.</p>
<p>The Resolution will normally change to Accepted or
Rejected next.</p>
<p>The person submitting the report should (if they have
permission) assign it to the person they most want to review
it, else the patch will be assigned based on the judgement
of the reviewer.</p>
<p>Discussion of major patches is carried out on the <a
href="http://mail.libexpat.org/mailman-21/listinfo/expat-discuss/"
>expat-discuss</a> mailing list. For simple patches, the
SourceForge comment mechanism should be sufficient.</p>
<p>For the reviewer: If you're certain the patch should be
applied, change the Resolution to Accepted and assign it
back to the submitter for checkin if they are a developer on
the project (if they aren't, the reviewer should commit it
and change Resolution to Accepted and Status to Closed). If
you're certain the patch should never be
accepted, change the Resolution to Rejected, Status to
Closed, and write an explanation in the comment box. If you
have specific complaints that would cause you to change your
mind if addressed, explain them clearly in a comment, leave
the status Open, and reassign back to the submitter (again,
if they're a developer on the project). If you're
uncertain, leave the status Open, explain your uncertainies
in a comment, and reassign the patch to someone you believe
can address your remaining questions; or leave the status
Open and bring it up on <a
href="http://mail.libexpat.org/mailman-21/listinfo/expat-discuss/"
>expat-discuss</a>.</p></td></tr>
<tr><td>Open</td>
<td>Accepted</td>
<td>The patch has been accepted, but it hasn't been applied
yet.
<p>The Status will normally change to Closed next.</p>
<p>The person changing the Resolution to Accepted should, at the
same time, assign the patch to whoever they believe is most
likely to be able and willing to apply it (the submitter if
possible).</p></td></tr>
<tr><td>Closed</td>
<td>Accepted</td>
<td>The patch has been accepted and applied.
<p>The previous Resolution was Accepted or None (if the
reviewer checked it in).</p></td></tr>
<tr><td>Closed</td>
<td>Rejected</td>
<td>The patch has been reviewed and rejected.
<p>There are generally no transitions out of this state: the
patch is dead.</p></td></tr>
<tr><td>Open</td>
<td>Out of date</td>
<td>Previous Resolution was Accepted or Postponed, but the patch
no longer works.
<p>Please enter a comment when changing the Resolution to "Out
of date", to record the nature of the problem and the previous
state.</p>
<p>Also assign it back to the submitter, as they need to upload
a new version.</p></td></tr>
<tr><td>Open</td>
<td>Postponed</td>
<td>The previous Resolution was None or Accepted, but for some
reason (e.g., pending release) the patch should not be reviewed
or applied until further notice.
<p>The Resolution will normally change to None or Accepted next,
which should be done as soon after the relevant event (release,
etc.) as possible. Checking for Postponed reports should be
part of the release process.</p>
<p>Please enter a comment when changing the Resolution to
Postponed, to record the reason, the previous Resolution, and
the conditions under which the patch should revert to Resolution
None or Accepted.</p></td></tr>
<tr><td>Deleted</td>
<td>Any</td>
<td>Bit bucket.
<p>Use only if it's OK for the patch and its SourceForge history
to disappear. As of 13-June-2002, SourceForge does not actually
throw away Deleted patches, but that may change.</p></td></tr>
</tbody>
</table>
<h3>SourceForge Tracker Quirks</h3>
<p>The SourceForge trackers, though quite nice to work with for
moderate sized projects, do have some quirks and limitations. Most of
the funcional limitations are unlikely to affect small projects like
Expat, but the quirky behavior... well, we should be aware of it.</p>
<dl>
<dt> Who is "Nobody"? </dt>
<dd> That depends on who initially submitted the report.
<p>The most important thing to know is that SourceForge asks
reporters who are not logged in to provide an email address,
but does not require it. There is no way to determine whether
"Nobody" provided one.</p>
<p>There are at least two common instances of "Nobody". The
simple interpretation of "Nobody" (and probably the most common
case) is that the reporter did not log into SourceForge and did
not provide an email address. Sometimes a name or email
address will be included in the initial report or a followup;
it is not always the reporters intention to remain anonymous.
If an email address is available this way, it is a good idea to
send an email to the provided address when following up to a
report, allowing the reporter to learn of the response and
provide additional feedback or information.</p>
<p>The second common case is that the report was filed by
someone without a SourceForge login or who wanted to remain
anonymous for some reason, but provided an email address to
SourceForge so that they would be automatically notified of any
followup activity. In this case, requests for additional
information in followup comments can actually get results,
sometimes including an email address if the anonymous filing
was not designed to protect anonymity but simply to avoid going
through the SourceForge login screen.</p>
<blockquote>
<em>
It's good to know that when filing a report while not logged
in, clicking on the "Please log in!" link beneath the large
text box will take you to a login page that will return you
to your submission form. Contents of the submission form
will be lost, unfortunately, but that link can save a bit of
navigating if you remember it soon enough.
</em>
</blockquote>
<p>SourceForge also provides a feature allowing authenticated
users to "monitor" a tracker report. Clicking on the "Monitor"
button will cause SourceForge to send the user an email on each
change to the report in much the way it sends an email to the
current assignee or the address configured in the tracker admin
for new or modified items. (For Expat, this would be the <a
href="http://mail.libexpat.org/mailman-21/listinfo/expat-bugs/"
>expat-bugs</a> list.) Users who are monitoring a report are
often knowledgable enough to answer questions about whatever the
problem is.</p>
<p>So, the "Nobody" listed as the submitter doesn't tell us
much, except that we might not get to know who the submitter
is.</p>
</dd>
</dl>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net/">
<img src="http://cvs.sourceforge.net/sourceforge_whitebg.gif"
width="136" height="79" border="0" alt="SourceForge
Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

BIN
htdocs/expat.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 1.7 KiB

433
htdocs/index.html
View File

@ -1,433 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>The Expat XML Parser</title>
<link rel="STYLESHEET" href="style.css" type="text/css" />
<style type="text/css">
body { margin: 0px; }
</style>
</head>
<body>
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><img src="expat.png" alt="(Expat logo)" /></td>
<td class="banner"><h2>The Expat XML Parser</h2></td>
</tr>
<tr>
<td class="navbar"></td>
<td class="content">
<p>Expat is an XML parser library written in C. It is a
stream-oriented parser in which an application registers handlers for
things the parser might find in the XML document (like start tags).
An <a href="http://www.xml.com/pub/1999/09/expat/index.html"
>introductory article</a> on using Expat is available on
<a href="http://www.xml.com/">xml.com</a>.</p>
<ul>
<li>
<a href="http://sourceforge.net/projects/expat/"
>Expat project page (includes downloads)</a></li>
<li>
<a href="https://sourceforge.net/p/expat/mailman/"
>Mailing lists</a></li>
<li>
<a href="#wrappers"
>3rd-party wrappers (SAX, DOM, other language bindings)</a></li>
<li>
<a href="https://github.com/libexpat/libexpat"
>Git repository</a>
</li>
<li>
(<a href="dev/cvs.html"
>CVS repository</a>
(<a href="http://expat.cvs.sourceforge.net"
>browse online</a>))</li>
<li>
<a href="https://github.com/libexpat/libexpat/issues"
>Bug reports</a></li>
<li>
<a href="dev/">Notes for Expat maintainers</a></li>
</ul>
<p>This project aims to maintain Expat for both current and future
users while improving the API to allow more reliable and robust access
from "scripting" languages such as Python and Perl. We invite the
community to participate on the mailing lists to help shape the future
of Expat.</p>
<h3 id="news">News</h3>
<dl>
<dt><em>21 June 2016</em>,
Expat 2.2.0 released.
</dt>
<dd><p>Release 2.2.0 includes security &amp; other bug fixes.</p>
<h4>Security fixes</h4>
<dl>
<dt><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0718">CVE-2016-0718</a>
(<a href="https://sourceforge.net/p/expat/bugs/537/">issue 537</a>)</dt>
<dd>Fix crash on malformed input</dd>
<dt><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4472">CVE-2016-4472</a></dt>
<dd>Improve insufficient fix to
<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1283">CVE-2015-1283</a> /
<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2716">CVE-2015-2716</a>
introduced with Expat 2.1.1</dd>
<dt><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5300">CVE-2016-5300</a>
(<a href="https://sourceforge.net/p/expat/bugs/499/">issue 499</a>)</dt>
<dd>Use more entropy for hash initialization than the original fix to
<a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876">CVE-2012-0876</a></dd>
<dt><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-6702">CVE-2012-6702</a>
(<a href="https://sourceforge.net/p/expat/bugs/519/">issue 519</a>)</dt>
<dd>Resolve troublesome internal call to srand that was introduced
with Expat 2.1.0 when addressing <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876">CVE-2012-0876</a>
(<a href="https://sourceforge.net/p/expat/bugs/496/">issue 496</a>)</dd>
</dl>
<h4>Bug fixes</h4>
<ul>
<li>Fix uninitialized reads of size 1 (e.g. in <code>little2_updatePosition</code>)</li>
<li>Fix detection of UTF-8 character boundaries</li>
</ul>
<h4>Other changes</h4>
<ul>
<li>Fix compilation for Visual Studio 2010
(<a href="https://sourceforge.net/p/expat/bugs/532/">bug 532</a>)</li>
<li>Autotools: Resolve use of &quot;$&lt;&quot; to better support bmake</li>
<li>Autotools: Add QA script &quot;qa.sh&quot; (and make target &quot;qa&quot;)</li>
<li>Autotools: Respect <code>CXXFLAGS</code> if given</li>
<li>Autotools: Fix &quot;make run-xmltest&quot;</li>
<li>Autotools: Have &quot;make run-xmltest&quot; check for expected output</li>
<li>CMake: Fix static build (<code>BUILD_shared=OFF</code>) on Windows
(<a href="https://sourceforge.net/p/expat/patches/90/">patch 90</a>)</li>
<li>CMake: Add soversion, support <code>-DNO_SONAME=yes</code> to bypass
(<a href="https://sourceforge.net/p/expat/bugs/536/">bug 536</a>)</li>
<li>CMake: Add suffix &quot;d&quot; to differentiate debug from release
(<a href="https://sourceforge.net/p/expat/bugs/323/">bug 323</a>)</li>
<li>CMake: Define <code>WIN32</code> with CMake on Windows</li>
<li>Annotate memory allocators for GCC</li>
<li>Address all currently known compile warnings</li>
<li>Make sure that API symbols remain visible despite <code>-fvisibility=hidden</code></li>
<li>Remove executable flag from source files</li>
<li>Resolve <code>COMPILED_FROM_DSP</code> in favor of <code>WIN32</code></li>
</ul>
<h4>Special thanks to</h4>
<ul>
<li>Björn Lindahl</li>
<li>Christian Heimes</li>
<li>Cristian Rodríguez</li>
<li>Daniel Krügler</li>
<li>Gustavo Grieco</li>
<li>Karl Waclawek</li>
<li>László Böszörményi</li>
<li>Marco Grassi</li>
<li>Pascal Cuoq</li>
<li>Sergei Nikulov</li>
<li>Thomas Beutlich</li>
<li>Warren Young</li>
<li>Yann Droneaud</li>
</ul>
</dd>
<dt><em>12 March 2016</em>,
Expat 2.1.1 released.
</dt>
<dd><p>Release 2.1.1 includes security &amp; other bug fixes.</p>
<h4>Security fixes</h4>
<ul>
<li><a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1283">CVE-2015-1283</a>
&mdash;
Multiple integer overflows in the <code>XML_GetBuffer</code> function
(<a href="https://sourceforge.net/p/expat/bugs/528/">bug 528</a>)</li>
</ul>
<h4>Bug fixes</h4>
<ul>
<li>Fix potential null pointer dereference
(<a href="https://sourceforge.net/p/expat/bugs/520/">bug 502</a>)</li>
<li>Symbol <code>XML_SetHashSalt</code> was not exported
(<a href="https://sourceforge.net/p/expat/bugs/520/">bug 520</a>)</li>
<li>Output of <code>xmlwf -h</code> was incomplete</li>
</ul>
<h4>Other changes</h4>
<ul>
<li>Document behavior of calling <code>XML_SetHashSalt</code> with salt <code>0</code>
(<a href="https://sourceforge.net/p/expat/bugs/503/">bug 503</a>)</li>
<li>Minor improvements to man page <code>xmlwf(1)</code></li>
<li>Improvements to the <em>experimental</em> CMake build system</li>
<li>libtool now invoked with <code>--verbose</code></li>
</ul>
</dd>
<dt><em>24 March 2012</em>,
Expat 2.1.0 released.
</dt>
<dd><p>Release 2.1.0 includes security &amp; other bug fixes, new
features, and updated build support.</p>
<h4>Security fixes</h4>
<ul>
<li>Memory leak in poolGrow (<a
href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-1148"
>CVE-2012-1148</a>)</li>
<li>Resource leak in readfilemap.c (<a
href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-1147"
>CVE-2012-1147</a>)</li>
<li>Hash DOS attack (<a
href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0876"
>CVE-2012-0876</a>)</li>
<li>Buffer over-read and crash in big2_toUtf8 (<a
href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-3560"
>CVE-2009-3560</a>)</li>
<li>Parser crash with special UTF-8 sequences (<a
href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2009-3720"
>CVE-2009-3270</a>)</li>
</ul>
<h4>New features</h4>
<ul>
<li>Added function XML_SetHashSalt that allows setting an initial
value (salt) for hash calculations (part of the fix for bug <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=3496608&amp;group_id=10127&amp;atid=110127"
>3496608</a>).
<li>When compiled with XML_ATTR_INFO defined, adds new API member
XML_GetAttributeInfo() that allows retrieving the byte offsets
for attribute names and values (patch <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=3446384&amp;group_id=10127&amp;atid=310127"
>3446384</a>).</li>
<li>Added CMake build system (bug <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2990652&amp;group_id=10127&amp;atid=110127"
>2990652</a>, patch <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=3312568&amp;group_id=10127&amp;atid=310127"
>3312568</a>).</li>
<li>Added run-benchmark target to Makefile.in - relies on testdata
module present in the same relative location as in the repository.
</li>
</ul>
<h4>Bug fixes</h4>
<ul>
<li>Harmful XML_ParserCreateNS suggestion (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=1742315&amp;group_id=10127&amp;atid=110127"
>1742315</a>)</li>
<li>CVE-2012-1147 - Resource leak in readfilemap.c (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2895533&amp;group_id=10127&amp;atid=110127"
>2895533</a>)</li>
<li>Expat build fails on linux-amd64 with gcc version&gt;=4.1 -O3 (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=1785430&amp;group_id=10127&amp;atid=110127"
>1785430</a>)</li>
<li>Build modifications using autoreconf instead of buildconf.sh (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=1983953&amp;group_id=10127&amp;atid=110127"
>1983953</a>, <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2517952&amp;group_id=10127&amp;atid=110127"
>2517952</a>, <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2517962&amp;group_id=10127&amp;atid=110127"
>2517962</a>, <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2649838&amp;group_id=10127&amp;atid=110127"
>2649838</a>)</li>
<li>OBJEXT and EXEEXT support while building (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2815947&amp;group_id=10127&amp;atid=110127"
>2815947</a>, <a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2884086&amp;group_id=10127&amp;atid=110127"
>2884086</a>)</li>
<li>CVE-2009-3720 - Parser crash with special UTF-8 sequences (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=1990430&amp;group_id=10127&amp;atid=110127"
>1990430</a>)</li>
<li>xmlwf should return non-zero exit status if not well-formed (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2517938&amp;group_id=10127&amp;atid=110127"
>2517938</a>)</li>
<li>Wrong statement about XMLDecl in xmlwf.1 and xmlwf.sgml (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2517946&amp;group_id=10127&amp;atid=110127"
>2517946</a>)</li>
<li>Dangling positionPtr after error (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2855609&amp;group_id=10127&amp;atid=110127"
>2855609</a>)</li>
<li>CVE-2009-3560 - Buffer over-read and crash in big2_toUtf8() (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2894085&amp;group_id=10127&amp;atid=110127"
>2894085</a>)</li>
<li>CVE-2012-1148 - Memory leak in poolGrow (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=2958794&amp;group_id=10127&amp;atid=110127"
>2958794</a>)</li>
<li>UNEXPECTED_STATE with a trailing "%" in entity value (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=3010819&amp;group_id=10127&amp;atid=110127"
>3010819</a>)</li>
<li>Unitialized memory returned from XML_Parse (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=3206497&amp;group_id=10127&amp;atid=110127"
>3206497</a>)</li>
<li>make check fails on mingw-w64 (<a
href="https://sourceforge.net/tracker/?func=detail&amp;aid=87849&amp;group_id=10127&amp;atid=110127"
>87849</a>)</li>
</ul>
</dd>
</dl>
<dl>
<dt><em>5 June 2007</em>,
Expat 2.0.1 released.
</dt>
<dd><p>Release 2.0.1 of the Expat XML parser is a bugfix release
resolving both code and build related issues. Changes include:
<ul>
<li>Fixed: The character data handler's calling of XML_StopParser()
was not handled properly; if the parser was stopped and the handler
set to NULL, the parser would segfault.</li>
<li>Fixed: Expat failed on EBCDIC systems as it assumed some character
constants to be ASCII encoded.</li>
<li>Minor cleanups of the test harness.</li>
<li>Minor fixes for xmlwf and example programs.</li>
<li>Fixes and improvements for the Windows platform.
New Windows directory structure.</li>
<li>Build fixes for various platforms: HP-UX, Tru64, Solaris 9.</li>
<li>Build fixes for Unix:<br/>
- Refreshed config.sub/config.guess.<br/>
- Support both, DESTDIR and INSTALL_ROOT, without relying on GNU-Make specific features.<br/>
- Patched configure.in to work better with Intel compiler.<br/>
- Fixes to Makefile.in to have make check work correctly.</li>
<li>Added Open Watcom support.</li>
</ul>
</dd>
</dl>
<dl>
<dt><em>11 January 2006</em>,
Expat 2.0.0 released.
</dt>
<dd><p>Release 2.0.0 of the Expat XML parser is the end point of the
1.95.X series of releases. The goal was to solidify and stabilize
the implementation of the given API, to add desirable features as
long as they fit with the API, and to keep the API backwards compatible
if extensions were required. Changes include:
<ul><li>Fixed headers for use from C++.</li>
<li>XML_GetCurrentLineNumber() and XML_GetCurrentColumnNumber()
now return unsigned integers.</li>
<li>Added XML_LARGE_SIZE switch to enable 64-bit integers for
byte indexes and line/column numbers.</li>
<li>Added support for AmigaOS.</li>
<li>Some mostly minor bug fixes. SF issues include: 1006708,
1021776, 1023646, 1114960, 1156398, 1221160, 1271642.</li>
</ul>
</dd>
</dl>
<p><a href="oldnews.html">Old news archive</a></p>
<h3 id="wrappers">References &amp; 3rd-party Wrappers</h3>
<p>If you know of any additional articles or resources which should be
linked to from this page, please send email to <a
href="mailto:fdrake@acm.org">Fred Drake (fdrake&#64;acm.org)</a>.
We're especially interested in links to tutorial information and open
source interfaces to Expat from languages other than C.</p>
<ul>
<li>
<a href="http://www.jclark.com/xml/expat.html"
>James Clark's original Expat page</a>, for Expat 1.2 and
earlier</li>
<li>
<a href="http://www.xml.com/pub/1999/09/expat/index.html"
>Introductory article</a> on using Expat on
<a href="http://www.xml.com/">xml.com</a></li>
<li>
<a href="http://www.keplerproject.org/luaexpat/">LuaExpat</a> is a
wrapper around Expat for the <a href="http://www.lua.org/">Lua</a>
programming language. The <a href=
"http://www.keplerproject.org/luasoap/">LuaSOAP</a> library is a <a
href="http://xml.coverpages.org/soap.html">SOAP</a> implementation
built on top of <a href= "http://www.keplerproject.org/luaexpat/"
>LuaExpat</a>.</li>
<li>
Perl's <code>XML::Parser</code> module is a wrapper built around a
binding to Expat in the <code>XML::Parser::Expat</code> module.</li>
<li>
<a href="http://www.python.org/doc/current/lib/module-xml.parsers.expat.html"
>Documentation for the Python interface to Expat</a>, part of the
standard documentation for Python.</li>
<li>
<a href="http://saxdotnet.sourceforge.net/saxexpat.html"
>SAXExpat.NET</a>, a <a href="http://www.microsoft.com/net/">.NET</a>
wrapper for Expat, conforming to the
<a href="http://saxdotnet.sourceforge.net">SAX for .NET</a> specifications.</li>
<li>
The <a href="http://www.nongnu.org/scew/">Simple C Expat Wrapper</a>
is a wrapper around Expat that provides a light-weight object model
somewhat like a DOM.</li>
<!-- Alex Conchillo Flaque: aconchillo at acm.org -->
<li>
<em><a href="http://www.codeproject.com/soap/expatimpl.asp"
title="C++ Wrappers for the Expat XML Parser">C++ Wrappers
for the Expat XML Parser</a></em>, an article by Tim Smith
providing object-oriented wrappers for Expat. The wrappers use
some MFC-biased naming, but look interesting.</li>
<li>
<a href="http://www.jezuk.co.uk/cgi-bin/view/arabica" title="Arabica"
>Arabica</a> -- an XML Parser toolkit for C++ programmers, with
SAX2 implementations based on several parsers, including Expat.</li>
<li>
<a href="http://devzone.intellitree.com/projects/expatmm/"
>ExpatMM -- C++ interface to Expat</a></li>
<li>
<a href="http://sourceforge.net/projects/kdsxml"
>SAX2 Wrapper for using Expat in Delphi,</a>
based on
<a href="http://saxforpascal.sourceforge.net"
>"SAX for Pascal"</a>
interface specs</li>
<li>
The <a href="http://tclxml.sourceforge.net/"
>TclXML project</a> includes a <a href="http://tcl.activestate.com/"
>Tcl</a> binding for Expat</li>
<li>
<a href="http://www.tdom.org/"
>tDOM</a> is an alternate package providing XML support for <a
href="http://tcl.activestate.com/" >Tcl</a>, based in part on
Expat.</li>
<li>
<a href="http://www.phpbuilder.com/columns/justin20000428.php3"
>Article on using Expat from PHP</a> on
<a href="http://www.phpbuilder.com/">&lt;?PHPBuilder?&gt;</a>
<br />(broken into lots of tiny pieces)</li>
<li>
<a href="http://expatobjc.sourceforge.net/"
>Objective-C interface to Expat</a></li>
<li>
<a href="http://www.xs4all.nl/~mmzeeman/ocaml/">OCaml Expat</a> is a
wrapper around Expat for the <a href="http://www.ocaml.org"
>Objective Caml</a> language.</li>
<li>
<a href="http://www.yoshidam.net/Ruby.html#xmlparser"
>Ruby interface to Expat</a></li>
<li>
<a href="http://www.latenightsw.com/freeware/XMLTools2/">XML Tools
2</a> is an AppleScript scripting addition that allows AppleScript
applications to work with XML data; it is based on Expat.</li>
<li>
<a href="http://www.simkin.co.uk/">Simkin</a> is an open source
scripting language available under the GNU LGPL. It can be embedded
in XML and supports a DOM-like API backed by Expat.</li>
<li>
<a href="http://easysoap.sourceforge.net/">EasySoap</a> is a C++
SOAP implementation which uses Expat.</li>
<li>
<a href=
"http://www.codepedia.com/wiki/display.aspx?WikiID=1&amp;pagename=thunks"
>A discussion</a> of another way to manage stateful callbacks, using
Expat as a sample library.</li>
<li>
The <a href="http://sourceforge.net/projects/gobo-eiffel/">GOBO
project</a> is working on an Eiffel binding for Expat. Development
is active and the package is fully supported in GOBO 3.0 and 3.1,
though there isn't much status information about the Expat bindings
on the website. (Most activity is reportedly on the relevant
mailing lists.)</li>
<li>
<a href="http://www.mitchenall.com/expat4d">Expat4D</a> is a plug-in
for the <a href="http://www.4duk.com/">4th Dimension</a> application
framework.</li>
</ul>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net">
<img src="http://sflogo.sourceforge.net/sflogo.php?group_id=10127&amp;type=2"
width="125" height="37" border="0" alt="SourceForge.net Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

246
htdocs/oldnews.html
View File

@ -1,246 +0,0 @@
<html>
<head>
<title>Old Expat News</title>
<link rel="STYLESHEET" href="style.css" type="text/css" />
</head>
<body marginwidth="0" marginheight="0">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="corner"><img src="expat.png" /></td>
<td class="banner"><h2>Old Expat News</h2></td>
</tr>
<tr>
<td class="navbar">
</td>
<td class="content">
<p><a href="./index.html#news">Current news</a></p>
<dl>
<dt><em>27 December 2005</em>,
Final Expat 2.0 pre-release snapshot made available.
</dt>
<dd>
<p>This <a href="http://www.libexpat.org/expat-2005-12-27.tar.gz" >
pre-release distribution</a> is based on the feedback we got from the
Dec. 23 snapshot and represents the final opportunity for
feedback before the actual release goes out.</p>
<p>We plan to release after the New Year.</p>
</dd>
<dt><em>23 December 2005</em>,
Expat 2.0 pre-release snapshot (another one) made available.
</dt>
<dd>
<p>As nothing happened here for a long time, we've posted another
<a href="http://www.libexpat.org/expat-2005-12-23.tar.gz" >pre-release
distribution snapshot</a> of the code currently in CVS on
libexpat.org. Please try this out and report any problems you
have. We'd like to get Expat 2.0 out soon.</p>
<p>A late addition was the new (optional) <code>XML_LARGE_SIZE</code>
feature to enable 64-bit integers on some API members. Please check
how it builds and works for you.</p>
</dd>
<dt><em>28 January 2005</em>,
Expat pre-release snapshot made available.
</dt>
<dd>
<p>We've posted a <a href=
"http://www.libexpat.org/expat-2005-01-28.tar.gz" >pre-release
distribution snapshot</a> of the code currently in CVS on
libexpat.org. Please try this out and report any problems you
have. We'd like to get a release out soon.</p>
<p>The coming release will either be 1.95.9 or 2.0, depending
primarily on the response to this snapshot. If we do decide to
make this 1.95.9, then we'll try to follow up with 2.0 in about a
month.</p>
</dd>
<dt><em>23 July 2004</em>,
Expat 1.95.8 released.
</dt>
<dd>
<p>The release schedule described in the previous news item didn't
work out. As a compensation, we've fixed a number of the
nuissance warnings generated on many platforms, and added a nice
new suspend/resume feature to the parser.</p>
<p><ul>
<li> Major new feature: suspend/resume. Handlers can now request
that a parse be suspended for later resumption or aborted
altogether. See "Temporarily Stopping Parsing" in the
documentation for more details. </li>
<li> Some mostly minor bug fixes, but compilation should no
longer generate warnings on most platforms. SF issues
include: 827319, 840173, 846309, 888329, 896188, 923913,
928113, 961698, 985192.</li>
</ul></p>
</dd>
<dt><em>20 October 2003</em>,
Expat 1.95.7 released.
</dt>
<dd>
<p><ul>
<li> Fixed <code>enum XML_Status</code> issue (reported on
SourceForge many times), so compilers that are properly
picky will be happy. </li>
<li> Introduced an <code>XMLCALL</code> macro to control the
calling convention used by the Expat API; this macro should
be used to annotate prototypes and definitions of callback
implementations in code compiled with a calling convention
other than the default convention for the host
platform. </li>
<li> Improved ability to build without the
<b>configure</b>-generated <span
class="filename">expat_config.h</span> header. This is
useful for applications which embed Expat rather than
linking in the library. </li>
<li> Fixed a variety of bugs: see SF issues 458907, 609603,
676844, 679754, 692878, 692964, 695401, 699323, 699487,
820946. </li>
<li> Improved hash table lookups. </li>
<li> Added more regression tests and improved documentation. </li>
</ul></p>
<p>Our plan is to wait for a short while and re-release this
version as the long-awaited Expat 2.0 if no major problems are
identified. If significant problems are found, additional
iterative releases will be made as fixes are made.</p>
</dd>
<dt><em>15 October 2003</em>,
Upcoming release.
</dt>
<dd>
<p>We're working on getting the long-delayed Expat 1.95.7 out the
door. A snapshot of the current source code is available as
expat-2003-10-15.tar.gz (no longer available);
please give this a try on your platform and report how it works
for you to the <a href=
"http://mail.libexpat.org/mailman/listinfo/expat-discuss"
>expat-discuss</a> mailing list. Our goals for this release are
portability and stability.
</p>
</dd>
<dt><em>28 January 2003</em>,
Expat 1.95.6 released.
</dt>
<dd>
<ul>
<li> Added <code>XML_FreeContentModel()</code>. </li>
<li> Added <code>XML_MemMalloc()</code>,
<code>XML_MemRealloc()</code>,
<code>XML_MemFree()</code>. </li>
<li> Fixed a variety of bugs: see SF issues 615606, 616863,
618199, 653180, 673791. </li>
<li> Enhanced the regression test suite. </li>
<li> Man page improvements: includes SF issue 632146. </li>
</ul>
<p />
</dd>
<dt><em>6 September 2002</em>,
Expat 1.95.5 released.
</dt>
<dd>
<ul>
<li> Added <code>XML_UseForeignDTD()</code> for improved SAX2
support. </li>
<li> Added <code>XML_GetFeatureList()</code>. </li>
<li> Defined <code>XML_Bool</code> type and the values
<code>XML_TRUE</code> and <code>XML_FALSE</code>. </li>
<li> Use an incomplete struct instead of a <code>void*</code>
for the parser. </li>
<li> Fixed UTF-8 decoding bug that caused legal UTF-8 to be
rejected. </li>
<li> Finally fixed bug where default handler would report DTD
events that were already handled by another handler.
Initial patch contributed by Darryl Miles. </li>
<li> Removed unnecessary <code>DllMain()</code> function that
caused static linking into a DLL to be difficult. </li>
<li> Added VC++ projects for building static libraries. </li>
<li> Reduced line-length for all source code and headers to be
no longer than 80 characters, to help with AS/400
support. </li>
<li> Reduced memory copying during parsing (SF patch #600964). </li>
<li> Fixed a variety of bugs: see SF issues 580793, 434664,
483514, 580503, 581069, 584041, 584183, 584832, 585537,
596555, 596678, 598352, 598944, 599715, 600479, 600971. </li>
</ul>
<p />
</dd>
<dt><em>4 September 2002</em>,
<a href="dev/roadmap.html">Development roadmap</a> published.
</dt>
<dd>
<ul>
<li> The initial version of the development roadmap was released
for comment. </li>
</ul>
<p />
</dd>
<dt><em>12 July 2002</em>,
Expat 1.95.4 released.
</dt>
<dd>
<ul>
<li> Added support for VMS, contributed by Craig Berry. See
vms/README.vms in the distrubution for more information. </li>
<li> Added Mac OS (classic) support, with a makefile for MPW,
contributed by Thomas Wegner and Daryle Walker. </li>
<li> Added Borland C++ Builder 5 / BCC 5.5 support, contributed
by Patrick McConnell (SF patch #538032). </li>
<li> Fixed a variety of bugs: see SF issues 441449, 563184,
564342, 566334, 566901, 569461, 570263, 575168, 579196. </li>
<li> Made skippedEntityHandler conform to SAX2 (see source
comment). </li>
<li> Re-implemented WFC: Entity Declared from XML 1.0 spec and
added a new error "entity declared in parameter entity":
see SF bug report 569461 and SF patch 578161. </li>
<li> Re-implemented section 5.1 from XML 1.0 spec:
see SF bug report 570263 and SF patch 578161. </li>
</ul>
Expat 1.95.3 is being withdrawn due to <a href=
"http://sourceforge.net/tracker/index.php?func=detail&amp;aid=566334&amp;group_id=10127&amp;atid=110127"
>bug #566334</a>. If you are currently using Expat 1.95.3, please
update to 1.95.4.
<p />
</dd>
<dt><em>3 June 2002</em>,
Expat 1.95.3 released.
</dt>
<dd>
<ul>
<li> Changed the name of the Windows DLLs from expat.dll to
libexpat.dll; this fixes SF bug #432456. This is a problem
only known to affect the Perl XML::Parser::Expat extension,
but is very important for that extension.</li>
<li> Added a project to the MSVC workspace to create a wchar_t
version of the library; the DLLs are named libexpatw.dll.
(Note the addition of the "w" character in the file name.)
</li>
<li> Added the XML_ParserReset() API function. This allows a
parser to be re-used, reducing the number of memory
allocations needed to set up a parser. This can be a
substantial benefit when parsing a large number of small
documents. </li>
<li> Fixed XML_SetReturnNSTriplet() to work for element names.
This is now a usable feature. </li>
<li> Made the XML_UNICODE builds usable (thanks, Karl!). </li>
<li> Allow xmlwf to read from standard input. </li>
<li> Install a man page for xmlwf on Unix systems. </li>
<li> Fixed many bugs; see SF bug reports 231864, 461380, 464837,
466885, 469226, 477667, 484419, 487840, 494749, 496505,
547350. Other bugs which we can't test as easily may also
have been fixed, especially in the area of build support. </li>
</ul>
</dd>
</dl>
</td>
</tr>
<tr>
<td class="corner">
<a href="http://sourceforge.net">
<img src="http://sflogo.sourceforge.net/sflogo.php?group_id=10127&amp;type=2"
width="125" height="37" border="0" alt="SourceForge.net Logo" />
</a>
</td>
</tr>
</table>
</body>
</html>

64
htdocs/style.css
View File

@ -1,64 +0,0 @@
html { border: 0px;
margin: 0px;
padding: 0px;
}
.corner { width: 200px;
height: 80px;
text-align: center;
}
.navbar { background-color: rgb(110,139,61);
padding-top: 2em;
}
.banner { background-color: rgb(110,139,61);
color: rgb(255,236,176);
padding-left: 2em;
}
.banner h2 { font-size: 200%; }
.content { padding: 2em; }
dl dt { font-weight: bold; }
.content thead { background-color: rgb(110,139,61);
color: rgb(255,236,176);
}
.content td,
.content th { padding: .2em;
margin: 0em;
border-width: 0px;
vertical-align: baseline;
border-bottom: 2px solid rgb(110,139,61);
}
.content li { margin: 0em;
padding-bottom: 0.75em;
}
.filename { font-family: sans-serif; }
/* These margin and padding settings are tedious at best. The idea is
to make sure we can put news items on the site that aren't just a
ordered or unordered list, and have it not look too ugly.
*/
dl dd ul,
dl dd ul li { padding-left: 0em;
margin-left: 0em; }
dl dd { margin-left: 2em; }
dl, ol, ul,
dl dt { margin-top: 0em;
margin-bottom: 0em;
padding-top: 0em;
padding-bottom: 0em; }
p { margin-top: 0em;
margin-bottom: 1em;
padding-top: 0em;
padding-bottom: 0em; }
li,
dl dd { margin-top: 0em;
margin-bottom: 0.5em; }