diff options
Diffstat (limited to 'docs/manual.html')
-rw-r--r-- | docs/manual.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/manual.html b/docs/manual.html index 0eb13b9..6a40fc2 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -1,16 +1,16 @@ <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII"> -<title>pugixml 1.5</title> +<title>pugixml 1.6</title> <link rel="stylesheet" href="pugixml.css" type="text/css"> <meta name="generator" content="DocBook XSL Stylesheets V1.78.1"> -<link rel="home" href="manual.html" title="pugixml 1.5"> +<link rel="home" href="manual.html" title="pugixml 1.6"> <link rel="next" href="manual/install.html" title="Installation"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <table width="100%"><tr> <td> -<a href="http://pugixml.org/">pugixml 1.5</a> manual | +<a href="http://pugixml.org/">pugixml 1.6</a> manual | <b>Overview</b> | <a href="manual/install.html">Installation</a> | Document: @@ -85,7 +85,7 @@ <p> If you believe you've found a bug in pugixml (bugs include compilation problems (errors/warnings), crashes, performance degradation and incorrect behavior), - please file an issue via <a href="http://code.google.com/p/pugixml/issues/entry" target="_top">issue + please file an issue via <a href="https://github.com/zeux/pugixml/issues/new" target="_top">issue submission form</a>. Be sure to include the relevant information so that the bug can be reproduced: the version of pugixml, compiler version and target architecture, the code that uses pugixml and exhibits the bug, etc. @@ -93,7 +93,7 @@ <p> Feature requests can be reported the same way as bugs, so if you're missing some functionality in pugixml or if the API is rough in some places and you - can suggest an improvement, <a href="http://code.google.com/p/pugixml/issues/entry?template=Feature%20request" target="_top">file + can suggest an improvement, <a href="https://github.com/zeux/pugixml/issues/new" target="_top">file an issue</a>. However please note that there are many factors when considering API changes (compatibility with previous versions, API redundancy, etc.), so generally features that can be implemented via a small function without @@ -102,7 +102,7 @@ <p> If you have a contribution to pugixml, such as build script for some build system/IDE, or a well-designed set of helper functions, or a binding to some - language other than C++, please <a href="http://code.google.com/p/pugixml/issues/entry?template=Feature%20request" target="_top">file + language other than C++, please <a href="https://github.com/zeux/pugixml/issues/new" target="_top">file an issue</a>. You can include the relevant patches as issue attachments. Your contribution has to be distributed under the terms of a license that's compatible with pugixml license; i.e. GPL/LGPL licensed code is not accepted. @@ -184,13 +184,13 @@ pugixml </div> </div></div> <table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr> -<td align="left"><p><small>Last revised: November 26, 2014 at 02:23:21 GMT</small></p></td> +<td align="left"><p><small>Last revised: March 20, 2015 at 07:16:25 GMT</small></p></td> <td align="right"><div class="copyright-footer"></div></td> </tr></table> <hr> <table width="100%"><tr> <td> -<a href="http://pugixml.org/">pugixml 1.5</a> manual | +<a href="http://pugixml.org/">pugixml 1.6</a> manual | <b>Overview</b> | <a href="manual/install.html">Installation</a> | Document: |