--- a/doc/config-manual/generating_maps.tex	Mon May 10 21:47:24 2010 +0000
+++ b/doc/config-manual/generating_maps.tex	Wed May 12 11:35:25 2010 +0000
@@ -25,7 +25,6 @@
     \item Rendering requested map
 \end{enumerate}
 
-%% FIXME: box it
 In order to understand the configuration facilities for generating maps
 in more detail, the internal
 interaction of the artifact-server and the mapserver is described below
@@ -40,39 +39,40 @@
     
     \item By requesting a map in the GNV-WebClient, the artifact-server writes a ESRI
     shapefile with (clipped) geometries, attribute data, projection
-    information and a special file storing meta information ({\tt
+    information and a special file storing meta information (\texttt{
     meta.xml}) for this artifact in the a corresponding directory in the
-    {\tt shapefile-directory}.
+    \texttt{shapefile-directory}.
     
-    \item After that the so called {\tt map-generator}
-    is triggered. The map-generator searches the {\tt shape-directory}
-    and its subfolders with all existing {\tt meta.xml} files and
-    generates a central configuration file for the mapserver at {\tt
+    \item After that the so called \texttt{map-generator}
+    is triggered. The map-generator searches the \texttt{shape-directory}
+    and its subfolders with all existing \texttt{meta.xml} files and
+    generates a central configuration file for the mapserver at \texttt{
     map-generator/mapfile@path}. Each shapefile will be published as a WMS
     layer. \\
-    The generated mapfile is constructed out of a base template from {\tt
+    The generated mapfile is constructed out of a base template from
+    \texttt{
     map-generator/templates/maptemplate} and a parameter-/layer-specific
-    part generated from {\tt map-generator/templates/path}. The
+    part generated from \texttt{map-generator/templates/path}. The
     selection of the correct file-based templates is extracted out of
-    the {\tt meta.xml}-file.
+    the \texttt{meta.xml}-file.
     
     \item The matching between the generated geograpic data and the corresponding
     style files is been done by the artifact-server, constructing
     filenames of maptemplates out of parameter-information. For
-    horizontal-cross-sections the schema looks like this {\tt
+    horizontal-cross-sections the schema looks like this \texttt{
     horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated
-    FIS like e.g. NAUTHIS and CONTIS like this {\tt
+    FIS like e.g. NAUTHIS and CONTIS like this \texttt{
     layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER}  e.g.
-    {\tt layer\_BSH\_IMS\_CONTIS\_Resources\_2}.
+    \texttt{layer\_BSH\_IMS\_CONTIS\_Resources\_2}.
     %% FIXME@TE: Marine Feature? Name of WMS?
     In order to set at least title, geometry-type and path to the
     corresponding shapefile dynamically a templating language, called
-    {\tt velocity} is used.
+    \texttt{velocity} is used.
 
-    \item The corresponding subfolder of an artifact in {\tt
+    \item The corresponding subfolder of an artifact in \texttt{
     shape-directory} with their shapefiles
-    and {\tt meta.xml}-document will be deleted after the time of
-    expiry. By triggering the {\tt map-generator} the next time, the
+    and \texttt{meta.xml}-document will be deleted after the time of
+    expiry. By triggering the \texttt{map-generator} the next time, the
     geographic data and the central configuration of the mapserver will
     be updated.
 
@@ -102,13 +102,13 @@
 \end{itemize}
 
 \paragraph*{velocity}
-{\em Function}: Templating language used in the maptemplates at {\tt
+{\em Function}: Templating language used in the maptemplates at \texttt{
 map-generator/templates/path} for accessing the parameters from
-dynamically generated {\tt meta.xml}-configuration of artifacts
+dynamically generated \texttt{meta.xml}-configuration of artifacts.
 
 \begin{itemize}
     \item {\tt logfile}: Setting the path to write log files.
-    Preconfigured to {\tt /var/log/artifacts/velocity.log}. {\bf Just
+    Preconfigured to \texttt{/var/log/artifacts/velocity.log}. {\bf Just
     absolute pathes are allowed here!}
 \end{itemize}
 
@@ -147,5 +147,4 @@
     \item {\tt ground}: {\tt interpolation} method for calculating the
     interpolation from the last measured value in meshes against the seafloor.
     Available methods are {\tt nearest-neighbor | bilinear | bicubic}.
-%%    FIXME: Could not find nn and bicubic in the code ...
 \end{itemize}