doc: do not use href for http references, otherwise http addresses are not directly readable

doc/doxygen/chapters/01building.doxy

@@ -32,8 +32,8 @@ can be used to install StarPU.
 
 \subsection OptionalDependencies Optional Dependencies
 
-The <a href="http://www.open-mpi.org/software/hwloc"><c>hwloc</c> topology
-discovery library</a> is not mandatory to use StarPU but strongly
+The <c>hwloc</c> (http://www.open-mpi.org/software/hwloc) topology
+discovery library is not mandatory to use StarPU but strongly
 recommended.  It allows for topology aware scheduling, which improves
 performance.  <c>hwloc</c> is available in major free operating system
 distributions, and for most operating systems.
@@ -46,17 +46,17 @@ no option is required, it will be detected automatically, otherwise
 
 \subsection GettingSources Getting Sources
 
-StarPU's sources can be obtained from the <a href="http://runtime.bordeaux.inria.fr/StarPU/files/">download page of
-the StarPU website</a>.
+StarPU's sources can be obtained from the download page of
+the StarPU website (http://runtime.bordeaux.inria.fr/StarPU/files/).
 
 All releases and the development tree of StarPU are freely available
 on INRIA's gforge under the LGPL license. Some releases are available
 under the BSD license.
 
-The latest release can be downloaded from the <a href="http://gforge.inria.fr/frs/?group_id=1570">INRIA's gforge</a> or
-directly from the <a href="http://runtime.bordeaux.inria.fr/StarPU/files/">StarPU download page</a>.
+The latest release can be downloaded from the INRIA's gforge (http://gforge.inria.fr/frs/?group_id=1570) or
+directly from the StarPU download page (http://runtime.bordeaux.inria.fr/StarPU/files/).
 
-The latest nightly snapshot can be downloaded from the <a href="http://starpu.gforge.inria.fr/testing/">StarPU gforge website</a>.
+The latest nightly snapshot can be downloaded from the StarPU gforge website (http://starpu.gforge.inria.fr/testing/).
 
 \verbatim
 $ wget http://starpu.gforge.inria.fr/testing/starpu-nightly-latest.tar.gz
@@ -66,7 +66,7 @@ And finally, current development version is also accessible via svn.
 It should be used only if you need the very latest changes (i.e. less
 than a day!). Note that the client side of the software Subversion can
 be obtained from http://subversion.tigris.org. If you
-are running on Windows, you will probably prefer to use <a href="http://tortoisesvn.tigris.org/">TortoiseSVN</a>.
+are running on Windows, you will probably prefer to use TortoiseSVN (http://tortoisesvn.tigris.org/).
 
 \verbatim
 $ svn checkout svn://scm.gforge.inria.fr/svn/starpu/trunk StarPU
@@ -126,7 +126,7 @@ $ make
 Once everything is built, you may want to test the result. An
 extensive set of regression tests is provided with StarPU. Running the
 tests is done by calling <c>make check</c>. These tests are run every night
-and the result from the main profile is publicly <a href="http://starpu.gforge.inria.fr/testing/">available</a>.
+and the result from the main profile is publicly available (http://starpu.gforge.inria.fr/testing/).
 
 \verbatim
 $ make check

doc/doxygen/chapters/12online_performance_tools.doxy

@@ -366,7 +366,7 @@ For ::STARPU_HISTORY_BASED, ::STARPU_REGRESSION_BASED, and
 ::STARPU_NL_REGRESSION_BASED, the dimensions of task data (both input
 and output) are used as an index by default. ::STARPU_HISTORY_BASED uses a CRC
 hash of the dimensions as an index to distinguish histories, and
-::REGRESSION_REGRESSION_BASED and ::STARPU_NL_REGRESSION_BASED use the total
+::STARPU_REGRESSION_BASED and ::STARPU_NL_REGRESSION_BASED use the total
 size as an index for the regression.
 
 The starpu_perfmodel::size_base and starpu_perfmodel::footprint fields however

doc/doxygen/chapters/13offline_performance_tools.doxy

@@ -108,8 +108,8 @@ to <c>1</c> before application execution will make StarPU do it automatically at
 application shutdown.
 
 This will create a file <c>paje.trace</c> in the current directory that
-can be inspected with the <a href="http://vite.gforge.inria.fr/">ViTE trace
-visualizing open-source tool</a>.  It is possible to open the
+can be inspected with the ViTE (http://vite.gforge.inria.fr/) trace
+visualizing open-source tool.  It is possible to open the
 file <c>paje.trace</c> with ViTE by using the following command:
 
 \verbatim
@@ -133,8 +133,8 @@ $ starpu_fxt_tool -i filename1 -i filename2
 By default, all tasks are displayed using a green color. To display tasks with
 varying colors, pass option <c>-c</c> to <c>starpu_fxt_tool</c>.
 
-To identify tasks precisely, the application can set the ::tag_id field of the
-tasks (or use STARPU_TAG_ONLY when using starpu_task_insert()), and with a recent
+To identify tasks precisely, the application can set the starpu_task::tag_id field of the
+task (or use STARPU_TAG_ONLY when using starpu_task_insert()), and with a recent
 enough version of vite (>= r1430) and the
 \ref enable-paje-codelet-details "--enable-paje-codelet-details"
 StarPU configure option, the value of the tag will show up in the trace.

doc/doxygen/chapters/19c_extensions.doxy

@@ -1,7 +1,7 @@
 /*
  * This file is part of the StarPU Handbook.
  * Copyright (C) 2009--2011  Universit@'e de Bordeaux
- * Copyright (C) 2010, 2011, 2012, 2013  Centre National de la Recherche Scientifique
+ * Copyright (C) 2010, 2011, 2012, 2013, 2014  Centre National de la Recherche Scientifique
  * Copyright (C) 2011, 2012 Institut National de Recherche en Informatique et Automatique
  * See the file version.doxy for copying conditions.
  */
@@ -15,8 +15,8 @@ code. This feature is only available for GCC 4.5 and later; it
 is known to work with GCC 4.5, 4.6, and 4.7.  You
 may need to install a specific <c>-dev</c> package of your distro, such
 as <c>gcc-4.6-plugin-dev</c> on Debian and derivatives.  In addition,
-the plug-in's test suite is only run when <a href="http://www.gnu.org/software/guile/">GNU Guile</a> is found at
-<c>configure</c>-time.  Building the GCC plug-in
+the plug-in's test suite is only run when GNU Guile (http://www.gnu.org/software/guile/)
+is found at <c>configure</c>-time.  Building the GCC plug-in
 can be disabled by configuring with \ref disable-gcc-extensions "--disable-gcc-extensions".
 
 Those extensions include syntactic sugar for defining

doc/doxygen/chapters/22openmp_runtime_support.doxy

@@ -6,8 +6,8 @@
 
 /*! \page OpenMPRuntimeSupport The StarPU OpenMP Runtime Support (SORS)
 
-StarPU provides the necessary routines and support to implement an <a
-href="http://www.openmp.org/">OpenMP</a> runtime compliant with the
+StarPU provides the necessary routines and support to implement an OpenMP
+(http://www.openmp.org/) runtime compliant with the
 revision 3.1 of the language specification, and compliant with the
 task-related data dependency functionalities introduced in the revision
 4.0 of the language. This StarPU OpenMP Runtime Support (SORS) has been