docs: Update API documentation

Fixes to layout, dead links, typography, and more.

Thanks to Benjamin Berg <bberg@redhat.com> for the thorough review

doc/advanced-topics.xml

@@ -60,7 +60,7 @@
     <para>
     In summary, libfprint represents fingerprints in several internal structures
     and each representation will offer you a way of determining the
-    \ref driver_id "driver ID" and \ref devtype "devtype" of the print in
+    <ulink url="#driver_id">driver ID</ulink> and <ulink url="#device-types">devtype</ulink> of the print in
     question. Prints are only compatible if the driver ID <emphasis role="strong">and</emphasis> devtypes
     match. libfprint does offer you some "is this print compatible?" helper
     functions, so you don't have to worry about these details too much.
@@ -73,7 +73,7 @@
     <para>
     Each driver is assigned a unique ID by the project maintainer. These
     assignments are
-    <ulink href="http://www.reactivated.net/fprint/Driver_ID_assignments">
+    <ulink url="http://www.reactivated.net/fprint/Driver_ID_assignments">
     documented on the wiki</ulink> and will never change.
     </para>
 
@@ -93,7 +93,7 @@
     <title>Device types</title>
 
     <para>
-    Internally, the \ref drv "driver" behind a device assigns a 32-bit
+    Internally, the <ulink url="libfprint-Driver-operations.html#libfprint-Driver-operations.description">driver</ulink> behind a device assigns a 32-bit
     <emphasis>devtype</emphasis> identifier to the device. This cannot be used as a unique
     ID for a specific device as many devices under the same range may share
     the same devtype. The devtype may even be 0 in all cases.

doc/getting-started.xml

@@ -6,19 +6,19 @@
   <title>Getting Started</title>
 
   <para>
-  libfprint includes several simple functional examples under the examples/
+  libfprint includes several simple functional examples under the <computeroutput>examples/</computeroutput>
   directory in the libfprint source distribution. Those are good starting
   points.
   </para>
 
   <para>
   Usually the first thing you want to do is determine which fingerprint
-  devices are present. This is done through \ref dscv_dev "device discovery".
+  devices are present. This is done through <ulink url="libfprint-Device-discovery.html">device discovery</ulink>.
   </para>
 
   <para>
   Once you have found a device you would like to operate, you should open it.
-  Refer to \ref dev "device operations". This section also details enrollment,
+  Refer to <ulink url="libfprint-Devices-operations.html">device operations</ulink>. This section also details enrollment,
   image capture, and verification.
   </para>
 

doc/intro.xml

@@ -14,7 +14,7 @@
   <para>
   This documentation is aimed at application developers who wish to integrate
   fingerprint-related functionality into their software. libfprint has been
-  designed so that you only have to do this once - by integrating your
+  designed so that you only have to do this once – by integrating your
   software with libfprint, you'll be supporting all the fingerprint readers
   that we have got our hands on. As such, the API is rather general (and
   therefore hopefully easy to comprehend!), and does its best to hide the

doc/libfprint-docs.xml

@@ -31,8 +31,8 @@
     <xi:include href="xml/drv.xml"/>
     <xi:include href="xml/dev.xml"/>
     <xi:include href="xml/print_data.xml"/>
-    <!-- https://bugs.freedesktop.org/show_bug.cgi?id=106550
-    <xi:include href="xml/dscv_print.xml"/> -->
+    <!-- FIXME https://bugs.freedesktop.org/show_bug.cgi?id=106550 -->
+    <xi:include href="xml/dscv_print.xml"/>
     <xi:include href="xml/img.xml"/>
   </part>