Skip to content

pugixml moves to GitHub

October 26, 2014

pugixml project used to be hosted on Google Code since time immemorial. About a year ago the active development switched to Git but the Subversion repository on Google Code was still maintained via svn-git and the primary way to report issues was via Issue Tracker on Google Code.

Since Google disabled the downloads feature on Google Code, pugixml releases are hosted on github anyway; also git-svn makes some git workflows more complicated. As of this day, pugixml moves to GitHub and Google Code project is no longer maintained.

You can use GitHub’s issue tracker, submit pull requests, use pugixml as Git submodules, etc.

Note that you can still use Subversion to access pugixml repository on github as follows:

svn checkout https://github.com/zeux/pugixml/tags/latest

Please let me know if you find any issues with GitHub’s Subversion access.

pugixml 1.4 release

February 28, 2014

pugixml-1.4 is finally out. This is a major release with several new features and compatibility improvements (read the changelog for details).

Highlights for this release include:

  • Improved validation of documents without element nodes;
  • More parsing options (parse_fragment flag to parse XML document fragments, parse_trim_pcdata flag to remove leading/trailing whitespace);
  • Better integer support for attribute and text nodes (long long types and hexadecimal conversion);
  • More stack-efficient XPath compilation and evaluation;

You can download the source package or get the new version from Subversion using the latest tag (http://pugixml.googlecode.com/svn/tags/latest).

pugixml 1.2 release

May 1, 2012

pugixml-1.2 is finally out. This is a major release with lots of new features and compatibility improvements (read the changelog for details).

Highlights for this release include:

  • New optional header-only compilation mode that does not require compiling pugixml sources and can improve performance for certain applications due to inlining;
  • Enhanced interface for PCDATA manipulation using an xml_text object;
  • C++11 range-based for-loop support for node/attribute iteration;
  • Compatibility improvements for many mobile platforms (including Android, Windows Mobile and other SDKs/devices).

You can download the source package or get the new version from Subversion using the latest tag (http://pugixml.googlecode.com/svn/tags/latest).

pugixml 1.0 release

October 31, 2010

pugixml-1.0 is out. This is a major release with lots of fixes/improvements (read the changelog for the details). The most important changes are:

  • XPath implementation was considerably improved – variable support was added, exceptions and STL are no longer required for XPath to function, query evaluation performance was improved and several bugs were fixed.
  • All deprecated functions and types were removed
  • File loading/saving functions can now work with wide character paths

You can download the source package or get the new version from Subversion using the latest tag (http://pugixml.googlecode.com/svn/tags/latest).

New project site

October 14, 2010

pugixml now has a new home, pugixml.org. This site acts as a frontend for all pugixml-related stuff (downloads, documentation, support and other information). Additionally, there is a news feed, which you can subscribe to via RSS.

All downloads, documentation, Subversion repository and issue tracker are still hosted at Google Code; the existing links still work, and this is not going to change.

pugixml 0.9 release

July 11, 2010

pugixml-0.9 is out. This is a major release with lots of fixes/improvements (read the changelog for the details). The most important changes are:

  • Unicode support is completely reworked: now pugixml can be configured to use wchar_t instead of char for all string-based interfaces; also encoding conversion is performed during parsing/saving (with automatic encoding detection). All popular Unicode encodings are supported.
  • New version features a new documentation, with detailed description of library interface and behavior, more samples, quick-start guide and so on.
  • There are new functions for loading document from memory; they do not require the input buffer to be null-terminated. Old functions still work, but are deprecated and will be removed in the future version.

Also there are a lot of other changes, including performance and memory consumption improvements.

Follow

Get every new post delivered to your Inbox.