on master help sign in
Update the readme to give some more information
commit6a74d3d9c5ae66d33716a45a1435a08dc53d3f9d authorNeil Mitchell <ndmitchell@gmail.com> dateWed 30 Nov 2016, 19:08 (10 years ago) parent3eb8ee0
1 file changed+8−1
README.md+8−1
README.md+8−1
@@ -1,4 +1,11 @@
11# Hexml [![Hackage version](https://img.shields.io/hackage/v/hexml.svg?label=Hackage)](https://hackage.haskell.org/package/hexml) [![Stackage version](https://www.stackage.org/package/hexml/badge/lts?label=Stackage)](https://www.stackage.org/package/hexml) [![Linux Build Status](https://img.shields.io/travis/ndmitchell/hexml.svg?label=Linux%20build)](https://travis-ci.org/ndmitchell/hexml) [![Windows Build Status](https://img.shields.io/appveyor/ci/ndmitchell/hexml.svg?label=Windows%20build)](https://ci.appveyor.com/project/ndmitchell/hexml)
22
3−A bad XML parser, that you probably shouldn't use.
3+A bad XML DOM-style parser, that only parses a subset of XML, but is designed to be fast. In particular:
44
5+* Entities, e.g. `&amp;`, are not expanded.
6+* Not all the validity conditions are checked.
7+* No support for `<!DOCTYPE` related features.
8+
9+The name "hexml" is a combination of "Hex" (a curse) and "XML". The "X" should not be capitalised because the parser is more curse and less XML.
10+
11+Hexml may be suitable if you want to quickly parse XML, from known sources, and a full XML parser has been shown to be a bottleneck. As an alternative to hexml, which supports things like entities but is still pretty fast, see Pugixml.