Index: branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_DIA.tex
===================================================================
--- branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_DIA.tex	(revision 3854)
+++ branches/2013/dev_r3853_CNRS9_ConfSetting/DOC/TexFiles/Chapters/Chap_DIA.tex	(revision 3989)
@@ -1,4 +1,4 @@
 % ================================================================
-% Chapter Ñ I/O & Diagnostics
+% Chapter � I/O & Diagnostics
 % ================================================================
 \chapter{Ouput and Diagnostics (IOM, DIA, TRD, FLO)}
@@ -609,5 +609,5 @@
 set via an equivalent and identically named namelist to \textit{namnc4} 
 in \np{xmlio\_server.def}. Typically this namelist serves the mean files
-whilst the \np{ namnc4} in the main namelist file continues to serve the
+whilst the \ngn{ namnc4} in the main namelist file continues to serve the
 restart files. This duplication is unfortunate but appropriate since, if
 using io\_servers, the domain sizes of the individual files produced by the
@@ -631,5 +631,6 @@
 trend of the dynamics and/or temperature and salinity time evolution equations 
 is stored in three-dimensional arrays just after their computation ($i.e.$ at the end 
-of each $dyn\cdots.F90$ and/or $tra\cdots.F90$ routines). These trends are then 
+of each $dyn\cdots.F90$ and/or $tra\cdots.F90$ routines). Options are defined by
+\ngn{namtrd} namelist variables. These trends are then 
 used in \mdl{trdmod} (see TRD directory) every \textit{nn\_trd } time-steps.
 
@@ -675,5 +676,6 @@
 The on-line computation of floats advected either by the three dimensional velocity 
 field or constraint to remain at a given depth ($w = 0$ in the computation) have been 
-introduced in the system during the CLIPPER project. The algorithm used is based 
+introduced in the system during the CLIPPER project. Options are defined by \ngn{namflo}
+namelis variables. The algorithm used is based 
 either on the work of \cite{Blanke_Raynaud_JPO97} (default option), or on a $4^th$
 Runge-Hutta algorithm (\np{ln\_flork4}=true). Note that the \cite{Blanke_Raynaud_JPO97} 
@@ -687,5 +689,5 @@
 
 
-In case of Ariane convention, input filename is \np{"init\_float\_ariane"}. Its format is:
+In case of Ariane convention, input filename is \np{init\_float\_ariane}. Its format is:
 
 \texttt{ I J K nisobfl itrash itrash }
@@ -709,5 +711,5 @@
 
 
-In the other case ( longitude and latitude ), input filename is \np{"init\_float"}. Its format is:
+In the other case ( longitude and latitude ), input filename is init\_float. Its format is:
 
 \texttt{ Long Lat depth nisobfl ngrpfl itrash}
@@ -732,5 +734,5 @@
 
 \np{jpnfl} is the total number of floats during the run.
-When initial positions are read in a restart file ( \np{ln\_rstflo= .TRUE.} ),  \np{jpnflnewflo}
+When initial positions are read in a restart file ( \np{ln\_rstflo}= .TRUE. ),  \np{jpnflnewflo}
 can be added in the initialization file. 
 
@@ -740,10 +742,10 @@
 is the frequency of creation of the float restart file.
 
-Output data can be written in ascii files (\np{ln\_flo\_ascii = .TRUE.} ). In that case, 
-output filename is \np{is trajec\_float}.
-
-Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii = .FALSE.} ). There are 2 possibilities:
-
- - if (\key{iomput}) is used, outputs are selected in  \np{iodef.xml}. Here it is an example of specification 
+Output data can be written in ascii files (\np{ln\_flo\_ascii} = .TRUE. ). In that case, 
+output filename is trajec\_float.
+
+Another possiblity of writing format is Netcdf (\np{ln\_flo\_ascii} = .FALSE. ). There are 2 possibilities:
+
+ - if (\key{iomput}) is used, outputs are selected in  iodef.xml. Here it is an example of specification 
    to put in files description section:
 
@@ -768,5 +770,5 @@
 
 
- -  if (\key{iomput}) is not used, a file called \np{trajec\_float.nc} will be created by IOIPSL library.
+ -  if (\key{iomput}) is not used, a file called trajec\_float.nc will be created by IOIPSL library.
 
 
@@ -789,5 +791,6 @@
 %----------------------------------------------------------------------------------------------------------
 
-Concerning the on-line Harmonic analysis, some parameters are available in namelist:
+Concerning the on-line Harmonic analysis, some parameters are available in namelist
+\ngn{namdia\_harm} :
 
 - \texttt{nit000\_han} is the first time step used for harmonic analysis
@@ -841,6 +844,6 @@
 
 
-Namelist parameters control how frequently the flows are summed and the time scales over which
- they are averaged, as well as the level of output for debugging:
+Namelist variables in \ngn{namdct} control how frequently the flows are summed 
+and the time scales over which they are averaged, as well as the level of output for debugging:
 
 %------------------------------------------namdct----------------------------------------------------
@@ -992,6 +995,6 @@
 
 The poleward heat and salt transports, their advective and diffusive component, and 
-the meriodional stream function can be computed on-line in \mdl{diaptr} by setting 
-\np{ln\_diaptr} to true (see the \textit{namptr} namelist below).  
+the meriodional stream function can be computed on-line in \mdl{diaptr} 
+\np{ln\_diaptr} to true (see the \textit{\ngn{namptr} } namelist below).  
 When \np{ln\_subbas}~=~true, transports and stream function are computed 
 for the Atlantic, Indian, Pacific and Indo-Pacific Oceans (defined north of 30\deg S) 
