Index: trunk/tutorial/model_tutorial.tex
===================================================================
--- trunk/tutorial/model_tutorial.tex	(revision 13)
+++ trunk/tutorial/model_tutorial.tex	(revision 14)
@@ -21,6 +21,6 @@
 This tutorial explains how to create a ToolMap project manually. This approach has the following advantages:
 \begin{enumerate*}
-  \item It ensures the IDs used
-  \item It generates a multilingual model
+  \item It ensures that the ID remain consistent
+  \item It could generate a multilingual model
   \item It allows better monitoring of model changes
 \end{enumerate*}
@@ -45,5 +45,5 @@
 
 \section{Data needed}
-In order to produce a ToolMap project, TmDmCreator needs the following files:
+In order work, TmDmCreator needs the following files:
 %\begin{itemize}
     \begin{description*}
@@ -55,5 +55,5 @@
 The recommended way to work with user\_structure.sql and user\_content.txt is described below
 
-
+\clearpage
 \section{Preparing user data}
 
@@ -70,4 +70,6 @@
   \item [LAYER\_NAME] the layer name. This name will be given to the SHP file when exporting
 \end{description*}
+
+Make sure you choose an Unicode format (Unicode Text (*.txt) or UTF-16 Unicode Text (*.txt)) when saving from the spreadsheet.
 
 \begin{figure} [hbp]
@@ -86,5 +88,5 @@
   \item [OBJECT\_CD] object code, should not necessarily be unique
   \item [OBJECT\_TYPE\_CD] object spatial type, uses same values as those described above for TYPE\_CD in thematic\_layers
-  \item [THEMATIC\_LAYERS\_LAYER\_INDEX] the index of the layer that the object refers to. The value 1 shown in the example (Figure 2) therefore relates to the theme Boreholes\_PT.
+  \item [THEMATIC\_LAYERS\_LAYER\_INDEX] the index of the layer that the object refers to. The value 1 shown in the example (Figure~\ref{fig:objects}) therefore relates to the theme Boreholes\_PT.
   \item [OBJECT\_DESC\_0,1,2,3,4,5] object description in up to 5 languages.
   \item [OBJECT\_ISFREQ] Set to 1 for frequent objects and 0 otherwise. This parameter is only taken into account for line type objects. Set to 0 for all point or polygon objects.
@@ -103,5 +105,5 @@
 
 \subsection{Attributes structure}
-Edit the file user\_structure.sql with Notepad (or even better with Notepad + +). For each topic containing attributes, there must be a SQL code of the type:
+Edit the file user\_structure.sql with Notepad (or even better with Notepad + +). For each layer containing attributes, there must be a SQL code of the type:
 
 \crealplisting{SQL}
@@ -117,5 +119,6 @@
 This code is the basic template for creating an attribute table. The number after layer\_at (see line 2) indicates the layer index and refers to the LAYER\_INDEX column in user\_content.txt. In our example layer\_at1 describe the attributes for the layer Boreholes\_PT. User attributes can then be added on line 4 of this template.
 Below are described the five attributes that can be used in a ToolMap data model as well as the corresponding SQL code
-\subsubsection {Enumeration} 
+\subsubsection {Enumeration}
+\label{sec:enumeration}
     \crealplisting{SQL}
     \begin{lstlisting}
@@ -149,9 +152,9 @@
 \subsection{Attributes values}
 \label{sec:attribute-values}
-For each enumeration field previously added in the user\_structure.sql file, it is necessary to define the allowed values. Therefore it is necessary to edit the attributes section of user\_content.txt. The structure of the Attributes section is shown in Figure~\ref{fig:attributs}. This table is divided into two parts, the first three columns describe the attribute fields, the remaining columns describe the values supported by these fields. Below is a description of each column.
+For each enumeration field  previously added in the user\_structure.sql file, it is necessary to define the allowed values. Therefore it is necessary to edit the attributes section of user\_content.txt. The structure of the attributes section is shown in Figure~\ref{fig:attributs}. This table is divided into two parts, the first three columns describe the attribute fields, the remaining columns describe the values supported by these fields. Below is a description of each column.
 
 \begin{description*}
   \item [ATTRIBUT\_ID] attribute unique ID.
-  \item [LAYER\_INDEX] the index of the layer that the attribute refers to. The value 1 shown in the example (Figure 4, row 42 and 43) therefore relates to the theme Boreholes\_PT.
+  \item [LAYER\_INDEX] the index of the layer that the attribute refers to. The value 1 shown in the example (Figure~\ref{fig:attributs}, row 42 and 43) therefore relates to the theme Boreholes\_PT.
   \item [ATTRIBUT\_NAME] attribute name. This name will be used as the column name in the exported SHP. Some limitations apply to SHP format for column names, for more information you can refer to \url{http://en.wikipedia.org/wiki/Shapefile#Shapefile\_attribute\_format\_.28.dbf.29} or \url{http://www.gdal.org/ogr/drv\_shapefile.html} 
   \item [CATALOG\_ID] attribute value unique ID
