From b357bf21e757d00540242f4aa915289c15f0b524 Mon Sep 17 00:00:00 2001 From: Sebastian Pipping Date: Thu, 11 May 2017 09:02:03 +0200 Subject: [PATCH] Remove in favor of https://libexpat.github.io/ (issue #1) As htdocs/index.html included a change log: A (more recent) plain text version of the change log can be found at expat/Changes. --- htdocs/Makefile | 5 - htdocs/dev/cvs.html | 120 --------- htdocs/dev/expat3.html | 82 ------- htdocs/dev/index.html | 56 ----- htdocs/dev/relreqs-1-95-4.html | 86 ------- htdocs/dev/relreqs-1-95-5.html | 64 ----- htdocs/dev/roadmap.html | 235 ------------------ htdocs/dev/trackers.html | 266 -------------------- htdocs/expat.png | Bin 1719 -> 0 bytes htdocs/index.html | 433 --------------------------------- htdocs/oldnews.html | 246 ------------------- htdocs/style.css | 64 ----- 12 files changed, 1657 deletions(-) delete mode 100644 htdocs/Makefile delete mode 100644 htdocs/dev/cvs.html delete mode 100644 htdocs/dev/expat3.html delete mode 100644 htdocs/dev/index.html delete mode 100644 htdocs/dev/relreqs-1-95-4.html delete mode 100644 htdocs/dev/relreqs-1-95-5.html delete mode 100644 htdocs/dev/roadmap.html delete mode 100644 htdocs/dev/trackers.html delete mode 100644 htdocs/expat.png delete mode 100644 htdocs/index.html delete mode 100644 htdocs/oldnews.html delete mode 100644 htdocs/style.css diff --git a/htdocs/Makefile b/htdocs/Makefile deleted file mode 100644 index 3aeb0fcb..00000000 --- a/htdocs/Makefile +++ /dev/null @@ -1,5 +0,0 @@ -DIR=/home/groups/e/ex/expat/htdocs -HOST=expat.sourceforge.net - -install: - ssh $(HOST) cd $(DIR) '&&' cvs up -P -d diff --git a/htdocs/dev/cvs.html b/htdocs/dev/cvs.html deleted file mode 100644 index 5ba91ec0..00000000 --- a/htdocs/dev/cvs.html +++ /dev/null @@ -1,120 +0,0 @@ - - - CVS Access to Expat - - - - - - - - - - - - - - - -
- - -

View CVS Online

- - - -

Anonymous CVS Access

- -

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 modulename. When prompted -for a password for anonymous, simply press the Enter key.

- -
-cvs -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat login
-
-cvs -z3 -d:pserver:anonymous@expat.cvs.sourceforge.net:/cvsroot/expat co modulename
-
- -

Updates from within the module's directory do not need the -d -parameter.

- -

Developer CVS Access via SSH

- -

Only project developers can access the CVS tree via this method. -SSH1 must be installed on your client machine. Substitute -modulename with the name of the source module you want to check -out, and developername with your SourceForge user name. Enter -your site password when prompted.

- -
-export CVS_RSH=ssh
-
-cvs -z3 -d:ext:developername@expat.cvs.sourceforge.net:/cvsroot/expat co modulename
-
- -

Source Modules

- -

There are only two source modules for Expat at this time. They -are:

- -
-
expat
-
This contains the C source code for the library, xmlwf, example - applications, and test suite. This is what most people will be - interested in.
- -
htdocs
-
The content for www.libexpat.org is located - in this module.
-
- -

Receiving Notification of Changes

- -

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:

- - - -

CVS Documentation

- -

There is a variety of documentation on CVS available online. These -sources are perhaps the most useful:

- - - -
- - SourceForge.net Logo - -
- - diff --git a/htdocs/dev/expat3.html b/htdocs/dev/expat3.html deleted file mode 100644 index d37c7d21..00000000 --- a/htdocs/dev/expat3.html +++ /dev/null @@ -1,82 +0,0 @@ - - - Changes in Expat 3 - - - - - - - - - - - - - - - -
- - -

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 -not a projected feature list for Expat 3; to learn about the -target features, please read the Expat -Development Roadmap. 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.

- -

This list is not complete; we'll add to this as we think of things -and have time to write about them.

- -
    -
  • Support for XML 1.1 and the corresponding namespaces updates.
    • - -
  • The signature of the XML_ParserReset() method will - grow an additional argument allowing specification of what should be - reset. See bug report 1109116: Optimize implementation of - XML_ParserReset for more information.
    • - -
  • All structural event callback functions will return an - XML_Status value that the parser will check. This will - allow an application to stop or suspend processing without having to - call XML_StopParser, which will therefore become obsolete.
    • - -
  • 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.
    • - -
  • 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 QName structs with members for local name, - namespace URI and prefix. This will apply to element names and attribute - names passed to XML_StartElementHandler and - XML_EndElementHandler.
    • - -
  • We will try to add a way of setting additional encodings - by name, using the existing framework built around - XML_UnknownEncodingHandler.
    • - -
  • 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.
    • - -
- -
- - SourceForge.net Logo - -
- -@ diff --git a/htdocs/dev/index.html b/htdocs/dev/index.html deleted file mode 100644 index 39d55546..00000000 --- a/htdocs/dev/index.html +++ /dev/null @@ -1,56 +0,0 @@ - - - Development of Expat - - - - - - - - - - - - - - - -
- - -

This area contains information for the developers and maintainers -of Expat.

- - - -
- - SourceForge.net Logo - -
- - diff --git a/htdocs/dev/relreqs-1-95-4.html b/htdocs/dev/relreqs-1-95-4.html deleted file mode 100644 index 81917e08..00000000 --- a/htdocs/dev/relreqs-1-95-4.html +++ /dev/null @@ -1,86 +0,0 @@ - - - Expat 1.95.4 Requirements - - - - - - - - - - - - - - - -
- - -

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.

- - -

Expat 1.95.4 Requirements

- -
    -
  • The SkippedEntityHandler patch should be checked in and - thoroughly debugged.
    - See SF patch #559910.
    - Status: Done. -
    • -
  • SF bug #441449 should be resolved.
    - Status: Done. -
    • -
  • Hard tab characters will be removed from all source files. - They will be replaced with spaces.
    - See SF bug #570903.
    - Status: Done. -
    • -
- -

Delayed Requirements

- -
    -
  • The InternalEntityRefHandler feature needs to be implemented - and tested.
    - See the comments for SF patch #429501.
    - Status: Delayed: - 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. -
    • -
  • The build process on Unix should create both libexpat.{a,so} - and libexpatw.{a,so} by default. - Status: Delayed: - 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. -
    • -
- -

Dropped Requirements

- -

There are no dropped requirements at this time.

- -
- - SourceForge - Logo - -
- - diff --git a/htdocs/dev/relreqs-1-95-5.html b/htdocs/dev/relreqs-1-95-5.html deleted file mode 100644 index 0179b783..00000000 --- a/htdocs/dev/relreqs-1-95-5.html +++ /dev/null @@ -1,64 +0,0 @@ - - - Expat 1.95.5 Requirements - - - - - - - - - - - - - - - -
- - -

This document is partially obsolete! Please see -the roadmap document until this document is -updated.

- -

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.

- - -

Expat 1.95.5 Requirements

- -
    -
  • The InternalEntityRefHandler feature needs to be implemented - and tested.
    - See the comments for SF patch #429501. -
    • -
  • The build process on Unix should create both libexpat.{a,so} - and libexpatw.{a,so} by default. -
    • -
- -

Delayed Requirements

- -

There are no delayed requirements at this time.

- - -

Dropped Requirements

- -

There are no dropped requirements at this time.

- -
- - SourceForge - Logo - -
- - diff --git a/htdocs/dev/roadmap.html b/htdocs/dev/roadmap.html deleted file mode 100644 index f6e4f381..00000000 --- a/htdocs/dev/roadmap.html +++ /dev/null @@ -1,235 +0,0 @@ - - - Expat Development Roadmap - - - - - - - - - - - - - - - -
- - -

PROPOSAL

- -

Updated 5 September 2002.

- -

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.

- -

Discussion of this document should be directed to the expat-discuss -mailing list.

- - -

Goals

- -

We do not plan to alter the goals of the Expat -project. We intend to continue to develop Expat to have the following -qualities:

- -
    -
  • Fast
    • - -
  • Conformant to XML 1.0 and Namespaces
    • - -
  • Easy to use from C
    • - -
  • Easy to wrap / bind for non-C languages
    • - -
  • Sufficient to build DOM and SAX on top of - (any final specification for XML)
    • - -
  • Modest memory footprint
    • - -
  • Portable
    • -
- - -

Non-Goals

- -
    -
  • Parsing anything that isn't XML
    • - -
  • DOM (any level)
    • - -
  • SAX (any version)
    • - -
  • Data bindings
    • - -
  • Watching the kids
    • -
- - -

Historical Background

- -

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.

- -

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.

- -

Since that time, incremental releases of Expat have been made on a -sporadic schedule, improving functionality and portability with each -release.

- - -

Expat Development Roadmap

- -

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.

- -

Near Future Activity

- -

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:

- -
    -
  • Stabilize the current API with some minor revisions to make error - reporting more explicit to allow better reporting and diagnosis.
    • - -
  • 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.
    • - -
  • API revisions will be made to improve the runtime discoverability of - Expat capabilities.
    • - -
  • Improve portability and performance.
    • - -
  • Substantially improve regression tests.
    • - -
  • Improve documentation.
    • - -
  • Full support for 64-bit platforms. (There are some known decoding - problems currently.)
    • -
- -

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").

- - -

Far Future Activity

- -

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:

- -
-
More powerful event API
-
-

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).

- -

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.

-
- -
Support for either pull or suspendable parsing
-
-

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.

- -

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.

- -

The specific model and API will be discussed on the expat-discuss - mailing list.

- - -
New encoding support
-
-

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.)

- -

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.

-
- -
XML 1.1 (including Namespaces in XML - 1.1), if it ever happens
-
-

Well, we're hoping, but it's not time to code for this yet.

-
-
- -

Additional goals may be added during the development of Expat 3.0; -it's just too early to tell.

- - -
- - SourceForge - Logo - -
- - diff --git a/htdocs/dev/trackers.html b/htdocs/dev/trackers.html deleted file mode 100644 index c52afb49..00000000 --- a/htdocs/dev/trackers.html +++ /dev/null @@ -1,266 +0,0 @@ - - - SourceForge Tracker Usage - - - - - - - - - - - - - - - -
- - -

This document describes the use of the SourceForge bug & patch -trackers by the Expat maintainers. These guidelines are substantially -based on the guidelines used for Python.

- -

Tracker Item Priority

- -

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.

- -

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.

- -
    -
  1. Needs to be solved immediately. 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.
    2. - -
  2. Needs to be dealt with sooner rather than later, and - is before priority "7" reports.
    3. - -
  3. 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.
    4. - -
  4. More important than most reports, but won't cause a - release to be held up.
    5. - -
  5. Most reports. This is how reports are created by - default.
    6. - -
  6. 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.
    7. -
- -

The Status and Resolution Fields

- -

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.

- -

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.

- -

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.

- -

The actual patch status is given by the pair of fields called -"Status" and "Resolution":

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
StatusResolutionMeaning
OpenNoneThe initial state of all patches. - -

The patch is under consideration, but has not been - reviewed yet, or is under review but not yet Accepted or - Rejected.

- -

The Resolution will normally change to Accepted or - Rejected next.

- -

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.

- -

Discussion of major patches is carried out on the expat-discuss mailing list. For simple patches, the - SourceForge comment mechanism should be sufficient.

- -

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 expat-discuss.

OpenAcceptedThe patch has been accepted, but it hasn't been applied - yet. -

The Status will normally change to Closed next.

-

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).

ClosedAcceptedThe patch has been accepted and applied. -

The previous Resolution was Accepted or None (if the - reviewer checked it in).

ClosedRejectedThe patch has been reviewed and rejected. -

There are generally no transitions out of this state: the - patch is dead.

OpenOut of datePrevious Resolution was Accepted or Postponed, but the patch - no longer works. -

Please enter a comment when changing the Resolution to "Out - of date", to record the nature of the problem and the previous - state.

-

Also assign it back to the submitter, as they need to upload - a new version.

OpenPostponedThe 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. -

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.

-

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.

DeletedAnyBit bucket. -

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.

- -

SourceForge Tracker Quirks

- -

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.

- -
-
Who is "Nobody"?
-
That depends on who initially submitted the report. - -

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.

- -

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.

- -

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.

- -
- - 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. - -
- -

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 expat-bugs list.) Users who are monitoring a report are - often knowledgable enough to answer questions about whatever the - problem is.

- -

So, the "Nobody" listed as the submitter doesn't tell us - much, except that we might not get to know who the submitter - is.

- -
-
- -
- - SourceForge - Logo - -
- - diff --git a/htdocs/expat.png b/htdocs/expat.png deleted file mode 100644 index 97e45cde4e63dbeea5c7e34a48dce084195502b0..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 1719 zcmb7_{XY{39LJZiv$4>bXhfD0Cl4#PahN>JV_WBGX33HAaAL&hHicR`H>4eg$g>Ms zBIKdnj&-gkc2XK*GNX)Jnl%rn|KRTReSN;)*ZcE&eSZCXbFh9M8X$cT007YN#JHZ` zxqUlw|4M0RZ;p3;0p;^(Uo-%~$^&nNtL(7q58fWGfbB0+*;`+@`4uR7DK{w$TuW9p4Gsc)Ftf$z>nPml#V&)VYP<5!^8b!jJ5aTJ?06 z!ibW~2Z}k0tB+v@aOJ0Y@W-DiOyQNZg*?qY)0fLc^2#G0Hr5tFM=EZ5d1zIQ;<6i( zzcxN<;CAD`WBKrW%435(u5gvy6`EohQY(EekjPeO?J1(F0MvnJ!qt^2T7Ljar7GjP zAl}Y#T>cZpY*-|f$_4em*;}cfT(4g0=8GSuu1Y<$fcQ+AV^OU{QTz<~==_hR`>x+z z>aMe35jj?I{^l(oH-8Srz+&?IB!B+FN9gc-%EI^MS~r`#Mh4lEI)u_1+u@}53spjK zx8+7m?(6^*2G%Ost>#Xr=k)apnNO*4V6U;|kBA#z1Zng)bte80yA-xMaTHdsh=3Hya zw4}0Lqjq<-(;#)~vZzeuTTx7iA8Ik*8sZhziZX68v@+qGENK_B|>9zC(2Uc>Oq;fbf zinFI0LOPhhD+srLR*HZJfwD(nPK23w0meDjYbR)jt3)P(3zxwiY^KoT8+<5iXd?#p z=9q(6F@+SBaUKkwz-)ZKa;DQOCmrf_7>b5q1TOcSGg%sNYgBbCG}Z91No`K>Q4)v}nidl%8XI>upFG7PTPijza3x{L70 zrmVsoT{Hm$Y*7yx7Lt^-xg#2*C3Vq^2Z^8H=vtg{4PibuzziEVsb5-venk>HBcV(A z_ln8gnDzZKGQ{R%+e<2iGS;8nBh{4sy*rOvy>-o)!dpd@J0Xr|H$K~>4!fNN|7sB*c0;g@*05(K}|)1EIxd5XBZ1%|>&x zvF75Y2cw*b#GK?=2b~@xr0-na%DYkaF5iRnQ1|(FJ`v+61~_%-7D~Jrl%0G0F!sA7<=~#7tZB_BAkOC-1hs)m4bebzLlHf$ zW8#9XRVz;~ke{dwNiAMu$_(waRrP{X81(viqf8uL3jiM9=nuEz0$QdiEeD66!C-0pr))WwDRC z4;5!e&8ZXH4lz4n3*B<6#e|_ZE%y!Sc!_Q5^D1^!Oc$+4tIO|-{=ub+EVEeRiT+a9 z`vUOttv6+wq`>QgZznH~tmd0rjGnWR>B#RP*MlD5B6Dz!zHMU;!?X|ge^sSREw>v- zr1H7`IErIMLPnm0A1J!1eJ1}NdG0ps7nQ2h5}86Kv)eEe9P|6^TA3qNkJo=R zX!adR?U+QdB@)%w+1OKDd)iM-L)r3;E$8X3ER*P26Q>!)wk8qB+uN_n;1Q&sPdP{% zlBbHsx1>ln{g!kydtqHnv% dw*mK`|Dwug{SMxFC;(44Ki3wQvzgAIe*p-RH)j9< diff --git a/htdocs/index.html b/htdocs/index.html deleted file mode 100644 index 897f0486..00000000 --- a/htdocs/index.html +++ /dev/null @@ -1,433 +0,0 @@ - - - - - The Expat XML Parser - - - - - - - - - - - - - - - - -
(Expat logo)
- -

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 introductory article on using Expat is available on -xml.com.

- - - -

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.

- -

News

- -
-
21 June 2016, - Expat 2.2.0 released. -
-

Release 2.2.0 includes security & other bug fixes.

-

Security fixes

-
-
CVE-2016-0718 - (issue 537)
-
Fix crash on malformed input
-
CVE-2016-4472
-
Improve insufficient fix to - CVE-2015-1283 / - CVE-2015-2716 - introduced with Expat 2.1.1
-
CVE-2016-5300 - (issue 499)
-
Use more entropy for hash initialization than the original fix to - CVE-2012-0876
-
CVE-2012-6702 - (issue 519)
-
Resolve troublesome internal call to srand that was introduced - with Expat 2.1.0 when addressing CVE-2012-0876 - (issue 496)
-
-

Bug fixes

-
    -
  • Fix uninitialized reads of size 1 (e.g. in little2_updatePosition)
    • -
  • Fix detection of UTF-8 character boundaries
    • -
-

Other changes

-
    -
  • Fix compilation for Visual Studio 2010 - (bug 532)
    • -
  • Autotools: Resolve use of "$<" to better support bmake
    • -
  • Autotools: Add QA script "qa.sh" (and make target "qa")
    • -
  • Autotools: Respect CXXFLAGS if given
    • -
  • Autotools: Fix "make run-xmltest"
    • -
  • Autotools: Have "make run-xmltest" check for expected output
    • -
  • CMake: Fix static build (BUILD_shared=OFF) on Windows - (patch 90)
    • -
  • CMake: Add soversion, support -DNO_SONAME=yes to bypass - (bug 536)
    • -
  • CMake: Add suffix "d" to differentiate debug from release - (bug 323)
    • -
  • CMake: Define WIN32 with CMake on Windows
    • -
  • Annotate memory allocators for GCC
    • -
  • Address all currently known compile warnings
    • -
  • Make sure that API symbols remain visible despite -fvisibility=hidden
    • -
  • Remove executable flag from source files
    • -
  • Resolve COMPILED_FROM_DSP in favor of WIN32
    • -
-

Special thanks to

-
    -
  • Björn Lindahl
    • -
  • Christian Heimes
    • -
  • Cristian Rodríguez
    • -
  • Daniel Krügler
    • -
  • Gustavo Grieco
    • -
  • Karl Waclawek
    • -
  • László Böszörményi
    • -
  • Marco Grassi
    • -
  • Pascal Cuoq
    • -
  • Sergei Nikulov
    • -
  • Thomas Beutlich
    • -
  • Warren Young
    • -
  • Yann Droneaud
    • -
-
-
12 March 2016, - Expat 2.1.1 released. -
-

Release 2.1.1 includes security & other bug fixes.

-

Security fixes

- -

Bug fixes

-
    -
  • Fix potential null pointer dereference - (bug 502)
    • -
  • Symbol XML_SetHashSalt was not exported - (bug 520)
    • -
  • Output of xmlwf -h was incomplete
    • -
-

Other changes

-
    -
  • Document behavior of calling XML_SetHashSalt with salt 0 - (bug 503)
    • -
  • Minor improvements to man page xmlwf(1)
    • -
  • Improvements to the experimental CMake build system
    • -
  • libtool now invoked with --verbose
    • -
-
-
24 March 2012, - Expat 2.1.0 released. -
-

Release 2.1.0 includes security & other bug fixes, new - features, and updated build support.

-

Security fixes

- -

New features

-
    -
  • Added function XML_SetHashSalt that allows setting an initial - value (salt) for hash calculations (part of the fix for bug 3496608). -
  • 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 3446384).
    • -
  • Added CMake build system (bug 2990652, patch 3312568).
    • -
  • Added run-benchmark target to Makefile.in - relies on testdata - module present in the same relative location as in the repository. -
    • -
-

Bug fixes

-
    -
  • Harmful XML_ParserCreateNS suggestion (1742315)
    • -
  • CVE-2012-1147 - Resource leak in readfilemap.c (2895533)
    • -
  • Expat build fails on linux-amd64 with gcc version>=4.1 -O3 (1785430)
    • -
  • Build modifications using autoreconf instead of buildconf.sh (1983953, 2517952, 2517962, 2649838)
    • -
  • OBJEXT and EXEEXT support while building (2815947, 2884086)
    • -
  • CVE-2009-3720 - Parser crash with special UTF-8 sequences (1990430)
    • -
  • xmlwf should return non-zero exit status if not well-formed (2517938)
    • -
  • Wrong statement about XMLDecl in xmlwf.1 and xmlwf.sgml (2517946)
    • -
  • Dangling positionPtr after error (2855609)
    • -
  • CVE-2009-3560 - Buffer over-read and crash in big2_toUtf8() (2894085)
    • -
  • CVE-2012-1148 - Memory leak in poolGrow (2958794)
    • -
  • UNEXPECTED_STATE with a trailing "%" in entity value (3010819)
    • -
  • Unitialized memory returned from XML_Parse (3206497)
    • -
  • make check fails on mingw-w64 (87849)
    • -
-
-
-
-
5 June 2007, - Expat 2.0.1 released. -
-

Release 2.0.1 of the Expat XML parser is a bugfix release - resolving both code and build related issues. Changes include: -

    -
  • 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.
    • -
  • Fixed: Expat failed on EBCDIC systems as it assumed some character - constants to be ASCII encoded.
    • -
  • Minor cleanups of the test harness.
    • -
  • Minor fixes for xmlwf and example programs.
    • -
  • Fixes and improvements for the Windows platform. - New Windows directory structure.
    • -
  • Build fixes for various platforms: HP-UX, Tru64, Solaris 9.
    • -
  • Build fixes for Unix:
    - - Refreshed config.sub/config.guess.
    - - Support both, DESTDIR and INSTALL_ROOT, without relying on GNU-Make specific features.
    - - Patched configure.in to work better with Intel compiler.
    - - Fixes to Makefile.in to have make check work correctly.
    • -
  • Added Open Watcom support.
    • -
-
-
-
-
11 January 2006, - Expat 2.0.0 released. -
-

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: -

  • Fixed headers for use from C++.
    • -
  • XML_GetCurrentLineNumber() and XML_GetCurrentColumnNumber() - now return unsigned integers.
    • -
  • Added XML_LARGE_SIZE switch to enable 64-bit integers for - byte indexes and line/column numbers.
    • -
  • Added support for AmigaOS.
    • -
  • Some mostly minor bug fixes. SF issues include: 1006708, - 1021776, 1023646, 1114960, 1156398, 1221160, 1271642.
    • -
-
-
- -

Old news archive

- -

References & 3rd-party Wrappers

- -

If you know of any additional articles or resources which should be -linked to from this page, please send email to Fred Drake (fdrake@acm.org). -We're especially interested in links to tutorial information and open -source interfaces to Expat from languages other than C.

- - - -
- - SourceForge.net Logo - -
- - diff --git a/htdocs/oldnews.html b/htdocs/oldnews.html deleted file mode 100644 index aa5848d2..00000000 --- a/htdocs/oldnews.html +++ /dev/null @@ -1,246 +0,0 @@ - - - Old Expat News - - - - - - - - - - - - - - - -
- - -

Current news

- -
-
27 December 2005, - Final Expat 2.0 pre-release snapshot made available. -
-
-

This - pre-release distribution 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.

-

We plan to release after the New Year.

-
-
23 December 2005, - Expat 2.0 pre-release snapshot (another one) made available. -
-
-

As nothing happened here for a long time, we've posted another - pre-release - distribution snapshot 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.

-

A late addition was the new (optional) XML_LARGE_SIZE - feature to enable 64-bit integers on some API members. Please check - how it builds and works for you.

-
-
28 January 2005, - Expat pre-release snapshot made available. -
-
-

We've posted a pre-release - distribution snapshot 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.

-

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.

-
-
23 July 2004, - Expat 1.95.8 released. -
-
-

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.

-

    -
  • 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.
    • -
  • 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.
    • -

-
-
20 October 2003, - Expat 1.95.7 released. -
-
-

    -
  • Fixed enum XML_Status issue (reported on - SourceForge many times), so compilers that are properly - picky will be happy.
    • -
  • Introduced an XMLCALL 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.
    • -
  • Improved ability to build without the - configure-generated expat_config.h header. This is - useful for applications which embed Expat rather than - linking in the library.
    • -
  • Fixed a variety of bugs: see SF issues 458907, 609603, - 676844, 679754, 692878, 692964, 695401, 699323, 699487, - 820946.
    • -
  • Improved hash table lookups.
    • -
  • Added more regression tests and improved documentation.
    • -

-

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.

-
-
15 October 2003, - Upcoming release. -
-
-

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 expat-discuss mailing list. Our goals for this release are - portability and stability. -

-
-
28 January 2003, - Expat 1.95.6 released. -
-
-
    -
  • Added XML_FreeContentModel().
    • -
  • Added XML_MemMalloc(), - XML_MemRealloc(), - XML_MemFree().
    • -
  • Fixed a variety of bugs: see SF issues 615606, 616863, - 618199, 653180, 673791.
    • -
  • Enhanced the regression test suite.
    • -
  • Man page improvements: includes SF issue 632146.
    • -
-

-

-
6 September 2002, - Expat 1.95.5 released. -
-
-
    -
  • Added XML_UseForeignDTD() for improved SAX2 - support.
    • -
  • Added XML_GetFeatureList().
    • -
  • Defined XML_Bool type and the values - XML_TRUE and XML_FALSE.
    • -
  • Use an incomplete struct instead of a void* - for the parser.
    • -
  • Fixed UTF-8 decoding bug that caused legal UTF-8 to be - rejected.
    • -
  • Finally fixed bug where default handler would report DTD - events that were already handled by another handler. - Initial patch contributed by Darryl Miles.
    • -
  • Removed unnecessary DllMain() function that - caused static linking into a DLL to be difficult.
    • -
  • Added VC++ projects for building static libraries.
    • -
  • Reduced line-length for all source code and headers to be - no longer than 80 characters, to help with AS/400 - support.
    • -
  • Reduced memory copying during parsing (SF patch #600964).
    • -
  • Fixed a variety of bugs: see SF issues 580793, 434664, - 483514, 580503, 581069, 584041, 584183, 584832, 585537, - 596555, 596678, 598352, 598944, 599715, 600479, 600971.
    • -
-

-

-
4 September 2002, - Development roadmap published. -
-
-
    -
  • The initial version of the development roadmap was released - for comment.
    • -
-

-

-
12 July 2002, - Expat 1.95.4 released. -
-
-
    -
  • Added support for VMS, contributed by Craig Berry. See - vms/README.vms in the distrubution for more information.
    • -
  • Added Mac OS (classic) support, with a makefile for MPW, - contributed by Thomas Wegner and Daryle Walker.
    • -
  • Added Borland C++ Builder 5 / BCC 5.5 support, contributed - by Patrick McConnell (SF patch #538032).
    • -
  • Fixed a variety of bugs: see SF issues 441449, 563184, - 564342, 566334, 566901, 569461, 570263, 575168, 579196.
    • -
  • Made skippedEntityHandler conform to SAX2 (see source - comment).
    • -
  • 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.
    • -
  • Re-implemented section 5.1 from XML 1.0 spec: - see SF bug report 570263 and SF patch 578161.
    • -
- Expat 1.95.3 is being withdrawn due to bug #566334. If you are currently using Expat 1.95.3, please - update to 1.95.4. -

-

-
3 June 2002, - Expat 1.95.3 released. -
-
-
    -
  • 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.
    • -
  • 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.) -
    • -
  • 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.
    • -
  • Fixed XML_SetReturnNSTriplet() to work for element names. - This is now a usable feature.
    • -
  • Made the XML_UNICODE builds usable (thanks, Karl!).
    • -
  • Allow xmlwf to read from standard input.
    • -
  • Install a man page for xmlwf on Unix systems.
    • -
  • 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.
    • -
-
-
- -
- - SourceForge.net Logo - -
- - diff --git a/htdocs/style.css b/htdocs/style.css deleted file mode 100644 index a6ce4e1c..00000000 --- a/htdocs/style.css +++ /dev/null @@ -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; }