diff --git a/docs/manual.qbk b/docs/manual.qbk
index b234fee..17f6de1 100644
--- a/docs/manual.qbk
+++ b/docs/manual.qbk
@@ -12,6 +12,7 @@
[template file[name]''''''[name]'''''']
[template sref[name]'''''']
[template anchor[name]''''''[^[name]]]
+[template ftnt[id text]''''''[text]'''''']
[section:overview Overview]
@@ -138,7 +139,7 @@ The complete pugixml source consists of four files - two source files, [file pug
[section:embed Building pugixml as a part of another static library/executable]
-The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[footnote All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects.
+The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[ftnt trademarks All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects.
If you're using Microsoft Visual Studio and the project has precompiled headers turned on, you'll see the following error messages:
diff --git a/docs/manual.xsl b/docs/manual.xsl
index 1875f6e..58d2d99 100644
--- a/docs/manual.xsl
+++ b/docs/manual.xsl
@@ -86,14 +86,32 @@
-
-
-
-
-
-
+
+
+
+
+
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ ERROR: Autogenerated id detected for element
+
+
+
+
+
diff --git a/docs/quickstart.qbk b/docs/quickstart.qbk
index bedaa15..512db4a 100644
--- a/docs/quickstart.qbk
+++ b/docs/quickstart.qbk
@@ -7,11 +7,9 @@
[license Distributed under the MIT License]
]
-[template file[name] ''''''[name]'''''']
-[template sbr[] '''''']
-[template lbr[] ''''''] [/ for empty lines in lists]
-[template sref[name] '''''']
-[template anchor[name] ''''''[^[name]]]
+[template file[name]''''''[name]'''''']
+[template sref[name]'''''']
+[template ftnt[id text]''''''[text]'''''']
[section:main pugixml 0.9 quick start guide]
@@ -40,7 +38,7 @@ The distribution contains library source, documentation (the guide you're readin
The complete pugixml source consists of four files - two source files, [file pugixml.cpp] and [file pugixpath.cpp], and two header files, [file pugixml.hpp] and [file pugiconfig.hpp]. [file pugixml.hpp] is the primary header which you need to include in order to use pugixml classes/functions. The rest of this guide assumes that [file pugixml.hpp] is either in the current directory or in one of include directories of your projects, so that `#include "pugixml.hpp"` can find the header; however you can also use relative path (i.e. `#include "../libs/pugixml/src/pugixml.hpp"`) or include directory-relative path (i.e. `#include `).
-The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[footnote All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects. There are other building methods available, including building pugixml as a standalone static/shared library; read the manual for further information.
+The easiest way to build pugixml is to compile two source files, [file pugixml.cpp] and [file pugixpath.cpp], along with the existing library/executable. This process depends on the method of building your application; for example, if you're using Microsoft Visual Studio[ftnt trademarks All trademarks used are properties of their respective owners.], Apple Xcode, Code::Blocks or any other IDE, just add [file pugixml.cpp] and [file pugixpath.cpp] to one of your projects. There are other building methods available, including building pugixml as a standalone static/shared library; read the manual for further information.
[endsect] [/install]