Changeset 356

Timestamp:

04/23/08 11:07:27 (16 years ago)

Author:

pinsard

Message:

some improvements in wiki production

Location:

trunk/SRC/Documentation/xmldoc

Files:

• makefile (modified) (1 diff)
• mini_notice.html (modified) (25 diffs)
• mini_notice.xml (modified) (26 diffs)
• saxo_tracwiki.xsl (modified) (5 diffs)
• wiki/FaqSaxo (modified) (1 diff)
• wiki/FirstSteps (modified) (11 diffs)
• wiki/MiniNotice (modified) (35 diffs)
• wiki/WhatisSaxo (modified) (1 diff)
• wiki/WhatsNew (modified) (1 diff)

trunk/SRC/Documentation/xmldoc/makefile

@@ -325 +325 @@
         awk 'sub(/ @star@ $$/,""){printf(" * %s", $$0);next};1' | \
         sed -e "s+@star@+*+" \
+        -e "s+=== idl\>+=== idl\>+" \
+        -e "s+---\>+---\>+" \
         > $@
 

trunk/SRC/Documentation/xmldoc/mini_notice.html

@@ -52 +52 @@
 </p><div class="figure"><a name="fig_xxx_0101" id="fig_xxx_0101"></a><p class="title"><b>Figure 1. Window xxx 1</b></p><div class="figure-contents">
 
-<div class="mediaobject"><img border="0" usemap="id2572796" src="figpng/xxx_0101.png" alt="Window xxx 1" /><map name="id2572796" id="id2572796"><area shape="rect" coords="27,298,504,249" /><area shape="rect" coords="81,242,450,183" /><area shape="rect" coords="3,175,538,36" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">
+<div class="mediaobject"><img border="0" usemap="id2572841" src="figpng/xxx_0101.png" alt="Window xxx 1" /><map name="id2572841" id="id2572841"><area shape="rect" coords="27,298,504,249" /><area shape="rect" coords="81,242,450,183" /><area shape="rect" coords="3,175,538,36" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">
 <p>Data file name</p>
 </td></tr><tr><td width="5%" valign="top" align="left"><img src="images/callouts/2.png" alt="2" border="0" /></td><td valign="top" align="left">
@@ -69 +69 @@
 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="initmethodtxt" id="initmethodtxt"></a>1.1.2. Grid initialization method</h4></div></div></div>
   <p>
-    For visualising grilled data, you need to <a href="./firststeps.html#load_grid" target="_top">define the grid</a> on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <span><strong class="command">initncdf</strong></span>) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default <span><strong class="command">initncdf</strong></span> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
+    For visualising grilled data, you need to <a href="./firststeps.html#load_grid" target="_top">define the grid</a> on which are located the data. By default, <span class="guibutton">automatic grid construction with initncdf.pro</span> is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <span><strong class="command">initncdf</strong></span>) without needing any other auxiliary file. If you checked <span class="guibutton">grid construction with other IDL batch or procedure</span>, this means that you don't want to use the default <span><strong class="command">initncdf</strong></span> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
   </p>
 </div>
@@ -75 +75 @@
   <p>
     This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid.
-By default the name of the procedure is <span><strong class="command">initncdf</strong></span>, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
+By default the name of the procedure is <span><strong class="command">initncdf</strong></span>, its argument will be automatically defined so you cannot change them. If you checked <span class="guibutton">grid construction with other IDL batch or procedure</span>, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
     </p><div class="figure"><a name="fig_xxx_0102" id="fig_xxx_0102"></a><p class="title"><b>Figure 2. Window xxx 1</b></p><div class="figure-contents">
       
@@ -84 +84 @@
     Once these two lines have been completed, click on <span class="guibutton">let's go</span>.
   </p>
-  <p>For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro" checked. Cf <a href="#fig_xxx_0404" title="Figure 18. temperature of the ocean at depth 125 meters without proper land/sea mask">Figure 18, “temperature of the ocean at depth 125 meters without proper land/sea mask”</a>
+  <p>For example, we choose the IDL batch file <code class="filename">tst_initlev</code>. Compare the result with <span class="guibutton">automatic grid construction with initncdf.pro</span> checked. Cf <a href="#fig_xxx_0404" title="Figure 18. temperature of the ocean at depth 125 meters without proper land/sea mask">Figure 18, “temperature of the ocean at depth 125 meters without proper land/sea mask”</a>
   </p>
 <p>
@@ -97 +97 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_2" id="launch_xxx_2"></a>1.2. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>/separate</code></em></code></strong></h3></div></div></div>
 <p>
-This is the same as the simple <a href="#launch_xxx_1" title="1.1. idl&gt; xxx"><code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong></a> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
+This is the same as the simple <a href="#launch_xxx_1" title="1.1. idl&gt; xxx">Section 1.1, “<code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong>”</a> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
 </p>
 </div>
@@ -103 +103 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_3" id="launch_xxx_3"></a>1.3. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong></h3></div></div></div>
 <p>
-In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see <a href="#restore">+++++++</a>
+In that case xxx window will open directly in the same state as it was when the file <code class="filename">file.dat</code> was created. see <a href="#restore">???</a>.
 </p>
 </div>
@@ -109 +109 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_4" id="launch_xxx_4"></a>1.4. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em></code></strong></h3></div></div></div>
 <p>
-In this case, the xxx window directly open the data file 'file.nc' and build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span>. For example:
+In this case, the xxx window directly open the data file <code class="filename">file.nc</code> and build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span>. For example:
   </p><pre class="screen">
     <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</code></em></code></strong>
@@ -118 +118 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_5" id="launch_xxx_5"></a>1.5. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong></h3></div></div></div>
 <p>
-In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong> in the call of <span><strong class="command">initncdf</strong></span>. For example:
+In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid automatically with the IDL procedure <span><strong class="command">initncdf</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong> in the call of <span><strong class="command">initncdf</strong></span>. For example:
   </p><pre class="screen">
     <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</code></em>, <em class="parameter"><code>useasmask = 'votemper'</code></em>, <em class="parameter"><code>missing_value = 31.0720</code></em></code></strong>
@@ -127 +127 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_6" id="launch_xxx_6"></a>1.6. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em></code></strong></h3></div></div></div>
 <p>
-In this case, the xxx window directly open the data file 'file.nc' and build the grid directly with the IDL procedure or batch file <span><strong class="command">initgrid</strong></span>
+In this case, the xxx window directly open the data file <code class="filename">file.nc</code> and build the grid directly with the IDL procedure or batch file <span><strong class="command">initgrid</strong></span>
   </p><pre class="screen">
     <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_ORCA2.nc'</code></em>, <em class="parameter"><code>'tst_initorca2'</code></em></code></strong>
@@ -136 +136 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_7" id="launch_xxx_7"></a>1.7. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em>, <em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong></h3></div></div></div>
 <p>
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong> in the call of <span><strong class="command">initgrid</strong></span>.
+In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the keywords <strong class="userinput"><code><em class="parameter"><code>keywd1 = 
</code></em>, <em class="parameter"><code>keywd2 = 
</code></em></code></strong> in the call of <span><strong class="command">initgrid</strong></span>.
 </p>
 </div>
@@ -142 +142 @@
 <div class="sect2" lang="en" xml:lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="launch_xxx_8" id="launch_xxx_8"></a>1.8. <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'file.nc'</code></em>, <em class="parameter"><code>'initgrid'</code></em>, <em class="parameter"><code>'arg1, arg2, 
'</code></em></code></strong></h3></div></div></div>
 <p>
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the string <strong class="userinput"><code><em class="parameter"><code>'arg1, arg2, 
'</code></em></code></strong> to specify the input arguments in the call of <span><strong class="command">initgrid</strong></span>.
+In this case, the xxx window directly open the data file <code class="filename">file.nc</code>, build the grid directly with the IDL procedure <span><strong class="command">initgrid</strong></span> and use the string <strong class="userinput"><code><em class="parameter"><code>'arg1, arg2, 
'</code></em></code></strong> to specify the input arguments in the call of <span><strong class="command">initgrid</strong></span>.
 </p>
 </div>
@@ -154 +154 @@
 </p><div class="figure"><a name="fig_xxx_0201" id="fig_xxx_0201"></a><p class="title"><b>Figure 4. Window xxx 2</b></p><div class="figure-contents">
 
-<div class="mediaobject"><img border="0" usemap="id2573385" src="figpng/xxx_0201.png" alt="Window xxx 2" /><map name="id2573385" id="id2573385"><area shape="rect" coords="4,346,122,331" /><area shape="rect" coords="136,346,409,330" /><area shape="rect" coords="6,326,55,311" /><area shape="rect" coords="88,326,243,311" /><area shape="rect" coords="263,326,407,311" /><area shape="rect" coords="2,306,433,293" /><area shape="rect" coords="2,288,436,269" /><area shape="rect" coords="2,263,267,237" /><area shape="rect" coords="20,230,388,105" /><area shape="rect" coords="1,98,434,29" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">
+<div class="mediaobject"><img border="0" usemap="id2573460" src="figpng/xxx_0201.png" alt="Window xxx 2" /><map name="id2573460" id="id2573460"><area shape="rect" coords="4,346,122,331" /><area shape="rect" coords="136,346,409,330" /><area shape="rect" coords="6,326,55,311" /><area shape="rect" coords="88,326,243,311" /><area shape="rect" coords="263,326,407,311" /><area shape="rect" coords="2,306,433,293" /><area shape="rect" coords="2,288,436,269" /><area shape="rect" coords="2,263,267,237" /><area shape="rect" coords="20,230,388,105" /><area shape="rect" coords="1,98,434,29" /></map><div class="calloutlist"><table border="0" summary="Callout list"><tr><td width="5%" valign="top" align="left"><img src="images/callouts/1.png" alt="1" border="0" /></td><td valign="top" align="left">
 <p>Plot type</p>
 </td></tr><tr><td width="5%" valign="top" align="left"><img src="images/callouts/2.png" alt="2" border="0" /></td><td valign="top" align="left">
@@ -202 +202 @@
 </p>
 <p>
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Open:</span> to open a new file. Same procedure as during the <a href="#launch_xxx_1" title="1.1. idl&gt; xxx">launch of XXX</a>.
+</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Open:</span> to open a new file. Same procedure as during the <a href="#launch_xxx_1" title="1.1. idl&gt; xxx">Section 1.1, “<code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span></code></strong>”</a>.
 The new file can be on a different grid, with different variables, with a different time base 

 </p></li><li><p><span class="guisubmenu">New XXX:</span> to open a second XXX window identical to the first one.</p></li><li><p><span class="guisubmenu">Quit:</span> to close the XXX window.</p></li></ul></div><p>
@@ -232 +232 @@
 </pre><p>
 will then create a Postscript file of the figure.
-</p></li><li><p><a name="restore" id="restore"></a><span class="guisubmenu">RESTORE kwd of xxx:</span> to save the xxx widget (all buttons and parameters stored in memory 
) in a binary file in order to quit xxx and relaunch it later with <a href="#launch_xxx_3" title="1.3. idl&gt; xxx, restore = 'file.dat'"><code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong></a> and get exactly the same configuration.</p></li><li><p><span class="guisubmenu">Print to prompt:</span> lists in the IDL window the command history that created the last plot. Useful primarily for debugging
</p></li></ul></div><p>
+</p></li><li>
+<p><a name="restore" id="restore"></a><span class="guisubmenu">RESTORE kwd of xxx:</span> to save the xxx widget (all buttons and parameters stored in memory 
) in a binary file in order to quit xxx and relaunch it later like in <a href="#launch_xxx_3" title="1.3. idl&gt; xxx, restore = 'file.dat'">Section 1.3, “<code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>restore = 'file.dat'</code></em></code></strong>”</a> and get exactly the same configuration.
+</p>
+</li><li>
+<p>
+<span class="guisubmenu">Print to prompt:</span> lists in the IDL window the command history that created the last plot. Useful primarily for debugging

+</p>
+</li></ul></div><p>
 </p>
 </div>
 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="flagsubmenu" id="flagsubmenu"></a>2.2.3. <span class="guisubmenu">Flag options</span> sub-menu</h4></div></div></div>
 <p>
-    </p><div class="figure"><a name="fig_xxx_0205" id="fig_xxx_0205"></a><p class="title"><b>Figure 8. The Flag Option menu</b></p><div class="figure-contents">
-      
-<div class="mediaobject"><img src="figpng/xxx_0205.png" alt="The Flag Option menu" /></div>
-    </div></div><p><br class="figure-break" />
-</p>
-<p>
-</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Portrait/Landscape:</span> changes the configuration of the plot.</p></li><li><p><span class="guisubmenu">Overlay:</span> to plot contours of a different field on top the
-one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</p></li><li><p><span class="guisubmenu">Vecteur:</span> to plot a vector field on top of contours. Only
-works on horizontal plots (<code class="filename">plt.pro</code>).
+    </p><div class="figure"><a name="fig_xxx_0205" id="fig_xxx_0205"></a><p class="title"><b>Figure 8. The <span class="guisubmenu">Flag option</span> menu</b></p><div class="figure-contents">
+      
+<div class="mediaobject"><img src="figpng/xxx_0205.png" alt="The Flag option menu" /></div>
+    </div></div><p><br class="figure-break" />
+</p>
+<p>
+</p><div class="itemizedlist"><ul type="disc"><li><p><span class="guisubmenu">Portrait/Landscape:</span> changes the configuration of the plot.</p></li><li><p><span class="guisubmenu">Overlay:</span> to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</p></li><li><p><span class="guisubmenu">Vecteur:</span> to plot a vector field on top of contours. Only works on horizontal plots (<code class="filename">plt.pro</code>).
 As for Overlay, a relaunch of the entire plot is necessary.</p></li><li><p><span class="guisubmenu">Longitude / x index:</span> switches longitude labeling of the plot sub-domain from degrees to indexes following i.</p></li><li><p><span class="guisubmenu">Latitude / y index:</span> switches latitude labeling of the plot sub-domain from degrees to indexes following j.</p></li></ul></div><p>
 </p>
@@ -275 +280 @@
 <p>You can choose the variable to work on.</p>
 <p>
-    </p><div class="figure"><a name="fig_xxx_0207" id="fig_xxx_0207"></a><p class="title"><b>Figure 11. Example of different Variables available</b></p><div class="figure-contents">
-      
-<div class="mediaobject"><img src="figpng/xxx_0207.png" alt="Example of different Variables available" /></div>
+    </p><div class="figure"><a name="fig_xxx_0207" id="fig_xxx_0207"></a><p class="title"><b>Figure 11. Example of different variables available</b></p><div class="figure-contents">
+      
+<div class="mediaobject"><img src="figpng/xxx_0207.png" alt="Example of different variables available" /></div>
     </div></div><p><br class="figure-break" />
 </p>
@@ -299 +304 @@
 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="commandtext_linear" id="commandtext_linear"></a>2.7.1. Linear calculation</h4></div></div></div>
 <p>
-If you want to make basic linear computation (like difference between fields, add/multiply by a constant 
). you can simply put the following commands: </p><pre class="screen">a - b</pre><pre class="screen">numb1*a</pre><pre class="screen">a + numb</pre><p> or any command with the following format </p><pre class="screen">numb1*a + numb2*b  + numb3*c 
 + numb</pre><p> where numb1, numb2, 
 correspond to numbers and a, b, c 
 will be the data to read.
+If you want to make basic linear computation (like difference between fields, add/multiply by a constant 
), you can simply put the following commands: <code class="literal">a - b</code><code class="literal">numb1*a</code><code class="literal">a + numb</code> or any command with the following format <code class="literal">numb1*a + numb2*b  + numb3*c 
 + numb</code> where numb1, numb2, 
 correspond to numbers and a, b, c 
 will be the data to read.
 </p>
 </div>
 <div class="sect3" lang="en" xml:lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="commandtext_anykind" id="commandtext_anykind"></a>2.7.2. Any kind of computation</h4></div></div></div>
 <p>
-If you want to make a computation more complicated than a basic linear you must put designate the data you want to read between <span><strong class="keycap">"</strong></span><span><strong class="keycap">"</strong></span> (with anything in between the "). For example: </p><pre class="screen">"a"^2</pre><pre class="screen">"a" - abs("b")</pre><pre class="screen">grad("a", 'x')</pre><p> 

+If you want to make a computation more complicated than a basic linear you must designate the data you want to read between <span><strong class="keycap">"</strong></span><span><strong class="keycap">"</strong></span> (with anything in between the "). For example: </p><pre class="screen">"a"^2</pre><pre class="screen">"a" - abs("b")</pre><pre class="screen">grad("a", 'x')</pre><p> 

 </p>
 </div>
@@ -497 +502 @@
 </p>
 <p>
-    </p><div class="figure"><a name="fig_xxx_0801" id="fig_xxx_0801"></a><p class="title"><b>Figure 33. The reference frame is selected</b></p><div class="figure-contents">
+    </p><div class="figure"><a name="fig_xxx_0801" id="fig_xxx_0801"></a><p class="title"><b>Figure 33. The “<span class="quote">reference</span>” frame is selected</b></p><div class="figure-contents">
       
       <div class="mediaobject"><img src="figpng/xxx_0801.png" alt="The reference frame is selected" /></div>
@@ -511 +516 @@
 </p>
 <p>
-    </p><div class="figure"><a name="fig_xxx_0802" id="fig_xxx_0802"></a><p class="title"><b>Figure 35. The target frame is selected</b></p><div class="figure-contents">
+    </p><div class="figure"><a name="fig_xxx_0802" id="fig_xxx_0802"></a><p class="title"><b>Figure 35. The “<span class="quote">target</span>” frame is selected</b></p><div class="figure-contents">
       
       <div class="mediaobject"><img src="figpng/xxx_0802.png" alt="The target frame is selected" /></div>
@@ -528 +533 @@
 <div class="procedure"><ol type="1"><li>
 <p>
-load xxx with the command:
+Load xxx with the command:
   </p><pre class="screen">
     <code class="prompt">idl&gt;</code> <strong class="userinput"><code><span><strong class="command">xxx</strong></span>, <em class="parameter"><code>'Levitus98_1m_01_12_Temperature_Pot_ORCA05.nc'</code></em>, <em class="parameter"><code>'tst_initorca05'</code></em></code></strong>
@@ -543 +548 @@
 </li><li>
 <p>
-<abbr class="abbrev">DCM</abbr> in frame 2, <abbr class="abbrev">LCL</abbr> on the plot in frame 1, to create a horizontal
-zoom in frame 2.</p>
-<p>
-<abbr class="abbrev">DCM</abbr> in frame 3, <abbr class="abbrev">LCM</abbr> on the plot in frame 1, to create a vertical cut
-in frame 3.</p>
-<p>
-<abbr class="abbrev">DCM</abbr> in frame 4, <abbr class="abbrev">LCR</abbr> on the plot in frame 1, to create a hovmoeller in frame 4.
+<abbr class="abbrev">DCM</abbr> in frame 2, <abbr class="abbrev">LCL</abbr> on the plot in frame 1 to create a horizontal zoom in frame 2.</p>
+<p>
+<abbr class="abbrev">DCM</abbr> in frame 3, <abbr class="abbrev">LCM</abbr> on the plot in frame 1 to create a vertical cut in frame 3.</p>
+<p>
+<abbr class="abbrev">DCM</abbr> in frame 4, <abbr class="abbrev">LCR</abbr> on the plot in frame 1 to create a hovmoeller in frame 4.
 </p>
 <p>
@@ -577 +580 @@
 </li><li>
 <p>
-click <span class="guibutton">OK</span>, and the plot is redone.
+Click <span class="guibutton">OK</span>, and the plot is redone.
 </p>
 <p>
@@ -587 +590 @@
 </li></ol></div>
 <div class="procedure"><p>
-in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
+In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
 </p><ol type="1"><li>
 <p>
@@ -598 +601 @@
 </li><li>
 <p>
-change plt for pltv
+Change plt for pltv
 </p>
 </li><li>
@@ -624 +627 @@
 </p></li><li>
 <p>
-in the IDL window, type
-  </p><pre class="screen">
-<code class="prompt">idl&gt;</code> <strong class="userinput"><code>domdef</code></strong>
+In the IDL window, type
+</p><pre class="screen">
+ <code class="prompt">idl&gt;</code> <strong class="userinput"><code>domdef</code></strong>
 </pre><p>
 </p></li><li>
 <p><abbr class="abbrev">DCR</abbr> to erase the problem frame.
 </p>
-</li><li><p>change the orientation of the plot by pressing Flag options -&gt; Portrait/Landscape. Cf <a href="#flagsubmenu" title="2.2.3. Flag options sub-menu">Section 2.2.3, “<span class="guisubmenu">Flag options</span> sub-menu”</a>
-</p></li><li><p>quit XXX cleanly using <span class="guisubmenu">quit</span> from the <span class="guibutton">File</span> menu. Cf <a href="#filesubmenu" title="2.2.1. File sub-menu">Section 2.2.1, “<span class="guibutton">File</span> sub-menu”</a>
-</p></li></ol></div><p>
+</li><li>
+<p>change the orientation of the plot by pressing <span class="guisubmenu">Flag options</span> → <span class="guimenuitem">Portrait/Landscape</span>. Cf <a href="#flagsubmenu" title="2.2.3. Flag options sub-menu">Section 2.2.3, “<span class="guisubmenu">Flag options</span> sub-menu”</a>
+</p>
+</li><li>
+<p>quit XXX cleanly using <span class="guisubmenu">quit</span> from the <span class="guibutton">File</span> menu. Cf <a href="#filesubmenu" title="2.2.1. File sub-menu">Section 2.2.1, “<span class="guibutton">File</span> sub-menu”</a>
+</p>
+</li></ol></div><p>
 </p>
 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
@@ -643 +650 @@
 overflow.
 To clean up this memory:
-  </p><pre class="screen">
-<code class="prompt">idl&gt;</code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>
+</p><pre class="screen">
+ <code class="prompt">idl&gt;</code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>
 </pre><p>
 </p>

trunk/SRC/Documentation/xmldoc/mini_notice.xml

@@ -141 +141 @@
 <sect3 xml:id="initmethodtxt"><title>Grid initialization method</title>
   <para>
-    For visualising grilled data, you need to <link xl:href="./firststeps.html#load_grid">define the grid</link> on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <command>initncdf</command>) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default <command>initncdf</command> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
+    For visualising grilled data, you need to <link xl:href="./firststeps.html#load_grid">define the grid</link> on which are located the data. By default, <guibutton>automatic grid construction with initncdf.pro</guibutton> is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure <command>initncdf</command>) without needing any other auxiliary file. If you checked <guibutton>grid construction with other IDL batch or procedure</guibutton>, this means that you don't want to use the default <command>initncdf</command> procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
   </para>
 </sect3>
@@ -147 +147 @@
   <para>
     This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid.
-By default the name of the procedure is <command>initncdf</command>, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
+By default the name of the procedure is <command>initncdf</command>, its argument will be automatically defined so you cannot change them. If you checked <guibutton>grid construction with other IDL batch or procedure</guibutton>, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
     <figure xml:id="fig_xxx_0102">
       <title>Window xxx 1</title>
@@ -160 +160 @@
     Once these two lines have been completed, click on <guibutton>let's go</guibutton>.
   </para>
-  <para>For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro" checked. Cf <xref linkend="fig_xxx_0404"/>
+  <para>For example, we choose the IDL batch file <filename>tst_initlev</filename>. Compare the result with <guibutton>automatic grid construction with initncdf.pro</guibutton> checked. Cf <xref linkend="fig_xxx_0404"/>
   </para>
 <para>
@@ -177 +177 @@
 <sect2 xml:id="launch_xxx_2"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>/separate</parameter></userinput></title>
 <para>
-This is the same as the simple <link linkend="launch_xxx_1"><prompt>&promptidl;</prompt> <userinput><command>xxx</command></userinput></link> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
+This is the same as the simple <xref linkend="launch_xxx_1"/> except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
 </para>
 </sect2>
@@ -183 +183 @@
 <sect2 xml:id="launch_xxx_3"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></title>
 <para>
-In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see <link linkend="restore">+++++++</link>
+In that case xxx window will open directly in the same state as it was when the file <filename>file.dat</filename> was created. see <xref linkend="restore"/>.
 </para>
 </sect2>
@@ -189 +189 @@
 <sect2 xml:id="launch_xxx_4"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter></userinput></title>
 <para>
-In this case, the xxx window directly open the data file 'file.nc' and build the grid automatically with the IDL procedure <command>initncdf</command>. For example:
+In this case, the xxx window directly open the data file <filename>file.nc</filename> and build the grid automatically with the IDL procedure <command>initncdf</command>. For example:
   <screen>
     <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter></userinput>
@@ -198 +198 @@
 <sect2 xml:id="launch_xxx_5"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput></title>
 <para>
-In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure <command>initncdf</command> and use the keywords <userinput><parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput> in the call of <command>initncdf</command>. For example:
+In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid automatically with the IDL procedure <command>initncdf</command> and use the keywords <userinput><parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput> in the call of <command>initncdf</command>. For example:
   <screen>
     <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_1x1.nc'</parameter>, <parameter>useasmask = 'votemper'</parameter>, <parameter>missing_value = 31.0720</parameter></userinput>
@@ -207 +207 @@
 <sect2 xml:id="launch_xxx_6"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter></userinput></title>
 <para>
-In this case, the xxx window directly open the data file 'file.nc' and build the grid directly with the IDL procedure or batch file <command>initgrid</command>
+In this case, the xxx window directly open the data file <filename>file.nc</filename> and build the grid directly with the IDL procedure or batch file <command>initgrid</command>
   <screen>
     <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA2.nc'</parameter>, <parameter>'tst_initorca2'</parameter></userinput>
@@ -216 +216 @@
 <sect2 xml:id="launch_xxx_7"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput></title>
 <para>
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the keywords <userinput><parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput> in the call of <command>initgrid</command>.
+In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid directly with the IDL procedure <command>initgrid</command> and use the keywords <userinput><parameter>keywd1 = &hellip;</parameter>, <parameter>keywd2 = &hellip;</parameter></userinput> in the call of <command>initgrid</command>.
 </para>
 </sect2>
@@ -222 +222 @@
 <sect2 xml:id="launch_xxx_8"><title><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'file.nc'</parameter>, <parameter>'initgrid'</parameter>, <parameter>'arg1, arg2, &hellip;'</parameter></userinput></title>
 <para>
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure <command>initgrid</command> and use the string <userinput><parameter>'arg1, arg2, &hellip;'</parameter></userinput> to specify the input arguments in the call of <command>initgrid</command>.
+In this case, the xxx window directly open the data file <filename>file.nc</filename>, build the grid directly with the IDL procedure <command>initgrid</command> and use the string <userinput><parameter>'arg1, arg2, &hellip;'</parameter></userinput> to specify the input arguments in the call of <command>initgrid</command>.
 </para>
 </sect2>
@@ -330 +330 @@
 <para>
 <itemizedlist>
-<listitem><para><menuchoice><guisubmenu>Open:</guisubmenu></menuchoice> to open a new file. Same procedure as during the <link linkend="launch_xxx_1">launch of XXX</link>.
+<listitem><para><menuchoice><guisubmenu>Open:</guisubmenu></menuchoice> to open a new file. Same procedure as during the <xref linkend="launch_xxx_1"/>.
 The new file can be on a different grid, with different variables, with a different time base &hellip;
 </para></listitem>
@@ -372 +372 @@
 will then create a Postscript file of the figure.
 </para></listitem>
-<listitem><para xml:id='restore'><menuchoice><guisubmenu>RESTORE kwd of xxx:</guisubmenu></menuchoice> to save the xxx widget (all buttons and parameters stored in memory &hellip;) in a binary file in order to quit xxx and relaunch it later with <link linkend="launch_xxx_3"><prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>restore = 'file.dat'</parameter></userinput></link> and get exactly the same configuration.</para></listitem>
-<listitem><para><menuchoice><guisubmenu>Print to prompt:</guisubmenu></menuchoice> lists in the IDL window the command history that created the last plot. Useful primarily for debugging&hellip;</para></listitem>
+<listitem>
+<para xml:id="restore"><menuchoice><guisubmenu>RESTORE kwd of xxx:</guisubmenu></menuchoice> to save the xxx widget (all buttons and parameters stored in memory &hellip;) in a binary file in order to quit xxx and relaunch it later like in <xref linkend="launch_xxx_3"/> and get exactly the same configuration.
+</para>
+</listitem>
+<listitem>
+<para>
+<menuchoice><guisubmenu>Print to prompt:</guisubmenu></menuchoice> lists in the IDL window the command history that created the last plot. Useful primarily for debugging&hellip;
+</para>
+</listitem>
 </itemizedlist>
 </para>
@@ -380 +387 @@
 <para>
     <figure xml:id="fig_xxx_0205">
-      <title>The Flag Option menu</title>
+      <title>The <guisubmenu>Flag option</guisubmenu> menu</title>
 <mediaobject>
   <imageobject>
@@ -391 +398 @@
 <itemizedlist>
 <listitem><para><guisubmenu>Portrait/Landscape:</guisubmenu> changes the configuration of the plot.</para></listitem>
-<listitem><para><guisubmenu>Overlay:</guisubmenu> to plot contours of a different field on top the
-one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</para></listitem>
-<listitem><para><guisubmenu>Vecteur:</guisubmenu> to plot a vector field on top of contours. Only
-works on horizontal plots (<filename>plt.pro</filename>).
+<listitem><para><guisubmenu>Overlay:</guisubmenu> to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!</para></listitem>
+<listitem><para><guisubmenu>Vecteur:</guisubmenu> to plot a vector field on top of contours. Only works on horizontal plots (<filename>plt.pro</filename>).
 As for Overlay, a relaunch of the entire plot is necessary.</para></listitem>
 <listitem><para><guisubmenu>Longitude / x index:</guisubmenu> switches longitude labeling of the plot sub-domain from degrees to indexes following i.</para></listitem>
@@ -436 +441 @@
 <para>
     <figure xml:id="fig_xxx_0207">
-      <title>Example of different Variables available</title>
+      <title>Example of different variables available</title>
 <mediaobject>
   <imageobject>
@@ -467 +472 @@
 <sect3 xml:id="commandtext_linear"><title>Linear calculation</title>
 <para>
-If you want to make basic linear computation (like difference between fields, add/multiply by a constant &hellip;). you can simply put the following commands: <screen>a - b</screen><screen>numb1*a</screen><screen>a + numb</screen> or any command with the following format <screen>numb1*a + numb2*b  + numb3*c &hellip; + numb</screen> where numb1, numb2, &hellip; correspond to numbers and a, b, c &hellip; will be the data to read.
+If you want to make basic linear computation (like difference between fields, add/multiply by a constant &hellip;), you can simply put the following commands: <literal>a - b</literal><literal>numb1*a</literal><literal>a + numb</literal> or any command with the following format <literal>numb1*a + numb2*b  + numb3*c &hellip; + numb</literal> where numb1, numb2, &hellip; correspond to numbers and a, b, c &hellip; will be the data to read.
 </para>
 </sect3>
 <sect3 xml:id="commandtext_anykind"><title>Any kind of computation</title>
 <para>
-If you want to make a computation more complicated than a basic linear you must put designate the data you want to read between <keycap>"</keycap><keycap>"</keycap> (with anything in between the "). For example: <screen>"a"^2</screen><screen>"a" - abs("b")</screen><screen>grad("a", 'x')</screen> &hellip;
+If you want to make a computation more complicated than a basic linear you must designate the data you want to read between <keycap>"</keycap><keycap>"</keycap> (with anything in between the "). For example: <screen>"a"^2</screen><screen>"a" - abs("b")</screen><screen>grad("a", 'x')</screen> &hellip;
 </para>
 </sect3>
@@ -755 +760 @@
 <para>
     <figure xml:id="fig_xxx_0801">
-      <title>The reference frame is selected</title>
+      <title>The <quote>reference</quote> frame is selected</title>
       <mediaobject>
   <imageobject>
@@ -778 +783 @@
 <para>
     <figure xml:id="fig_xxx_0802">
-      <title>The target frame is selected</title>
+      <title>The <quote>target</quote> frame is selected</title>
       <mediaobject>
   <imageobject>
@@ -805 +810 @@
 <step>
 <para>
-load xxx with the command:
+Load xxx with the command:
   <screen>
     <prompt>&promptidl;</prompt> <userinput><command>xxx</command>, <parameter>'Levitus98_1m_01_12_Temperature_Pot_ORCA05.nc'</parameter>, <parameter>'tst_initorca05'</parameter></userinput>
@@ -824 +829 @@
 <step>
 <para>
-<abbrev>DCM</abbrev> in frame 2, <abbrev>LCL</abbrev> on the plot in frame 1, to create a horizontal
-zoom in frame 2.</para>
-<para>
-<abbrev>DCM</abbrev> in frame 3, <abbrev>LCM</abbrev> on the plot in frame 1, to create a vertical cut
-in frame 3.</para>
-<para>
-<abbrev>DCM</abbrev> in frame 4, <abbrev>LCR</abbrev> on the plot in frame 1, to create a hovmoeller in frame 4.
+<abbrev>DCM</abbrev> in frame 2, <abbrev>LCL</abbrev> on the plot in frame 1 to create a horizontal zoom in frame 2.</para>
+<para>
+<abbrev>DCM</abbrev> in frame 3, <abbrev>LCM</abbrev> on the plot in frame 1 to create a vertical cut in frame 3.</para>
+<para>
+<abbrev>DCM</abbrev> in frame 4, <abbrev>LCR</abbrev> on the plot in frame 1 to create a hovmoeller in frame 4.
 </para>
 <para>
@@ -871 +874 @@
 <step>
 <para>
-click <guibutton>OK</guibutton>, and the plot is redone.
+Click <guibutton>OK</guibutton>, and the plot is redone.
 </para>
 <para>
@@ -887 +890 @@
 <procedure>
 <para>
-in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
+In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
 </para>
 <step>
@@ -901 +904 @@
 <step>
 <para>
-change plt for pltv
+Change plt for pltv
 </para>
 </step>
@@ -935 +938 @@
 <listitem>
 <para>
-in the IDL window, type
-  <screen>
-<prompt>&promptidl;</prompt> <userinput>domdef</userinput>
+In the IDL window, type
+<screen>
+ <prompt>&promptidl;</prompt> <userinput>domdef</userinput>
 </screen>
 </para></listitem>
@@ -944 +947 @@
 </para>
 </listitem>
-<listitem><para>change the orientation of the plot by pressing Flag options -> Portrait/Landscape. Cf <xref linkend="flagsubmenu"/>
-</para></listitem>
-<listitem><para>quit XXX cleanly using <guisubmenu>quit</guisubmenu> from the <guibutton>File</guibutton> menu. Cf <xref linkend="filesubmenu"/>
-</para></listitem>
+<listitem>
+<para>change the orientation of the plot by pressing <menuchoice><guisubmenu>Flag options</guisubmenu> <guimenuitem>Portrait/Landscape</guimenuitem></menuchoice>. Cf <xref linkend="flagsubmenu"/>
+</para>
+</listitem>
+<listitem>
+<para>quit XXX cleanly using <guisubmenu>quit</guisubmenu> from the <guibutton>File</guibutton> menu. Cf <xref linkend="filesubmenu"/>
+</para>
+</listitem>
 </orderedlist>
 </para>
@@ -958 +965 @@
 overflow.
 To clean up this memory:
-  <screen>
-<prompt>&promptidl;</prompt> <userinput>ptr_free, ptr_valid()</userinput>
+<screen>
+ <prompt>&promptidl;</prompt> <userinput>ptr_free, ptr_valid()</userinput>
 </screen>
 </para>

trunk/SRC/Documentation/xmldoc/saxo_tracwiki.xsl

@@ -64 +64 @@
 <xsl:template match="d:sect2/d:title">
  <xsl:text>&#xA;</xsl:text>
- <xsl:text>=== </xsl:text><xsl:value-of select="normalize-space(.)"/><xsl:text> ===</xsl:text>
+ <xsl:variable name="newtitle">
+  <xsl:call-template name="replace-string">
+   <xsl:with-param name="text" select="normalize-space(.)"/>
+   <xsl:with-param name="replace" select="'&gt;'"/>
+<!-- do not how to write > instead of &gt; ++. need sed features --> 
+   <xsl:with-param name="with" select="'&gt;'"/>
+  </xsl:call-template>
+ </xsl:variable>
+ <xsl:text>=== </xsl:text><xsl:value-of select="$newtitle"/><xsl:text> ===</xsl:text>
  <xsl:text>&#xA;</xsl:text>
 </xsl:template>
@@ -118 +126 @@
  <xsl:text>{{{</xsl:text><xsl:apply-templates/><xsl:text>}}}</xsl:text>
 </xsl:template>
+<xsl:template match="d:literal">
+ <xsl:text>{{{</xsl:text><xsl:apply-templates/><xsl:text>}}}</xsl:text>
+</xsl:template>
 
 <xsl:template match="d:screen">
  <!-- 
-we open an HTML block because it is not possible to have font effect (bold, italic)
-using TracWiki
+we open an HTML block because it is not possible to have font effect (bold, italic) using TracWiki
  -->
  <xsl:text>&#xA;</xsl:text>
@@ -238 +248 @@
    <xsl:text>wiki:WikiStart</xsl:text>
   </xsl:when>
-  <xsl:when test="contains(@xl:href,'../../Tests/')">
-   <xsl:text>source:/trunk/SRC/Tests/</xsl:text><xsl:value-of select="substring-after(@xl:href,'../../Tests/')"/>
+  <xsl:when test="contains(@xl:href,'../../')">
+   <xsl:text>source:/trunk/SRC/</xsl:text><xsl:value-of select="substring-after(@xl:href,'../../')"/>
   </xsl:when>
   <xsl:when test="contains(@xl:href,'idldoc_html_output')">
@@ -278 +288 @@
 </xsl:template>
 
+<xsl:template match="d:caution">
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>'''Caution'''</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template match="d:note">
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>'''Note'''</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:text>&#xA;</xsl:text>
+ <xsl:apply-templates/>
+</xsl:template>
 
 <xsl:template match="d:replaceable">
@@ -327 +354 @@
 </xsl:template>
 
+<xsl:template match="d:link[@linkend]"> 
+ <xsl:variable name="target" select="key('id',@linkend)[1]"/>
+ <xsl:text>[#</xsl:text><xsl:value-of select="translate(normalize-space(//*[normalize-space(@xml:id='$target')]/d:title),' ','')"/><xsl:text>]</xsl:text>
+</xsl:template>
+
 <xsl:template match="d:xref"> 
   <xsl:variable name="target" select="key('id',@linkend)[1]"/>
   <xsl:text>[#</xsl:text><xsl:value-of select="translate(normalize-space(//d:sect1[normalize-space(@xml:id='$target')]/d:title),' ','')"/><xsl:text> </xsl:text> <xsl:value-of select="normalize-space(//d:sect1[normalize-space(@xml:id='$target')]/d:title)"/><xsl:text>]</xsl:text>
 </xsl:template>
+
+<xsl:template match="d:callout"> 
+ <xsl:text>[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/</xsl:text><xsl:value-of select="position() div 2"/><xsl:text>.png)]]</xsl:text><xsl:apply-templates/>
+</xsl:template>
+
+<xsl:template name="replace-string">
+<!-- from http://www.dpawson.co.uk/xsl/sect2/replace.html -->
+    <xsl:param name="text"/>
+    <xsl:param name="replace"/>
+    <xsl:param name="with"/>
+    <xsl:choose>
+      <xsl:when test="contains($text,$replace)">
+        <xsl:value-of select="substring-before($text,$replace)"/>
+        <xsl:value-of select="$with"/>
+        <xsl:call-template name="replace-string">
+          <xsl:with-param name="text"
+select="substring-after($text,$replace)"/>
+          <xsl:with-param name="replace" select="$replace"/>
+          <xsl:with-param name="with" select="$with"/>
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:value-of select="$text"/>
+      </xsl:otherwise>
+    </xsl:choose>
+  </xsl:template>
 
 <!-- do not reproduce the followings elements -->

trunk/SRC/Documentation/xmldoc/wiki/FaqSaxo

@@ -182 +182 @@
 Yes, there are some :
 
- * \ in {{{*.pro}}} are not written
+ * {{{\}}} in {{{*.pro}}} are not written
 in {{{*.html}}}.
-They must be escaped by an other \ or you can choose an other character.
-
- * Search doesn't handle characters like -
-and |.
+They must be escaped by an other {{{\}}} or you can choose an other character.
+
+ * Search doesn't handle characters like {{{-}}}
+and {{{|}}}.
 
  * Paragraphs of {{{*.pro}}} headers are shown with a proportional
-font in the HTML release.
+font in the {{{HTML}}} release.
 
 If you need to draw some small figure like grid cell, you can encapsulate
 the block to be shown in constant font 
 between
-; <fixe> and
-; </fixe>
+{{{; <fixe>}}} and
+{{{; </fixe>}}}
 
 Unfortunately, these troubles may not be fixed because the author does not

trunk/SRC/Documentation/xmldoc/wiki/FirstSteps

@@ -95 +95 @@
 
    
-    
+    [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
       {{{findgen}}} stands for '''f'''loat '''ind'''ex '''gen'''erator.
 
@@ -151 +151 @@
 
   
-    
+    [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
       
 If needed, the name of the postscript will automatically be completed with .ps. Just hit return, if you want to use the default postscript name: {{{idl.ps}}}.
@@ -231 +231 @@
 
   
-    
+    [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
       
 the small keyword is a 3 elements vector which defines how we divide the page and in which case we should make the plot: [number of columns, number of rows, case number]. The case numbering is starting at 1, from top to bottom and left to right.
       
     
-    
+    [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]]
       
 you must put /noerase otherwise the second plot will be done in a new window.
@@ -257 +257 @@
 </pre>
 }}}
-{{{scontour}}} accepts the same keywords as {{{contour}}} (C_ANNOTATION=vector_of_strings, C_CHARSIZE=value, C_CHARTHICK=integer, C_COLORS=vector, C_LABELS=vector{each element 0 or 1}, C_LINESTYLE=vector, { /FILL | /CELL_FILL | C_ORIENTATION=degrees}, C_SPACING=value, C_THICK=vector, /CLOSED, /DOWNHILL, /FOLLOW, /IRREGULAR, /ISOTROPIC, LEVELS=vector, NLEVELS=integer{1 to 60}, MAX_VALUE=value, MIN_VALUE=value, /OVERPLOT, {/PATH_DATA_COORDS, PATH_FILENAME=string, PATH_INFO=variable, PATH_XY=variable}, TRIANGULATION=variable, /PATH_DOUBLE, /XLOG, /YLOG, ZAXIS={0 | 1 | 2 | 3 | 4}), including the graphics keywords (except LINESTYLE, PSYM, SYMSIZE).
+{{{scontour}}} accepts the same keywords as {{{contour}}} (C_ANNOTATION=vector_of_strings, C_CHARSIZE=value, C_CHARTHICK=integer, C_COLORS=vector, C_LABELS=vector{each element 0 or 1}, C_LINESTYLE=vector, { /FILL | /CELL_FILL | C_ORIENTATION=degrees}, C_SPACING=value, C_THICK=vector, /CLOSED, /DOWNHILL, /FOLLOW, /IRREGULAR, /ISOTROPIC, LEVELS=vector, NLEVELS=integer{1 to 60}, MAX_VALUE=value, MIN_VALUE=value, /OVERPLOT, {/PATH_DATA_COORDS, PATH_FILENAME=string, PATH_INFO=variable, PATH_XY=variable}, TRIANGULATION=variable, /PATH_DOUBLE, /XLOG, /YLOG, ZAXIS={0 | 1 | 2 | 3 | 4}), including the [#FirststepswithSAXO] (except LINESTYLE, PSYM, SYMSIZE).
       It can therefore be customized ''as much as you want''. See these short examples:
 {{{
@@ -284 +284 @@
 
 
-  
+  [[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
     {{{rebin}}} is used to build an array containing an alternation of 1 and 0 in order to label one contour every two contours.
 
@@ -340 +340 @@
 </pre>
 }}}
+
+
+'''Note'''
+
 New Feature
 
@@ -353 +357 @@
 
 ==== Formal quick look at 2D arrays: pltv ====
-{{{pltv}}} is a mix between tvplus and plt and allow you to have formal quick look of 2D arrays.
+{{{pltv}}} is a mix between [#FirststepswithSAXO] and [#FirststepswithSAXO] and allow you to have formal quick look of 2D arrays.
   
 {{{
@@ -451 +455 @@
 ==== Load the grid from OPA meshmask file ====
 
-  When the grid is really irregular (its abscissa and ordinate cannot be descried by a vector), loading the grid directly from the data forces us to make an approximation when computing the grid corners position and the cells size. In that case, it can be preferable to load the grid from the meshmask file created by OPA. As OPA use a Arakawa-C discretization, loading the grid from the meshmask will also define all parameters related to the U, V and F grids (glam[uv],gphi[uv], e[12][uvf]). Note that, when using a simple grid definition from the data itself (with {{{initncdf}}} or {{{computegrid}}}), adding the keyword /FULLCGRID leads also to the definition of all U, V and F grids parameters. There is the examples to load ORCA grids from OPA meshmask.
+  When the grid is really irregular (its abscissa and ordinate cannot be descried by a vector), loading the grid directly from the data forces us to make an approximation when computing the grid corners position and the cells size. In that case, it can be preferable to load the grid from the meshmask file created by OPA. As OPA use a Arakawa-C discretization, loading the grid from the meshmask will also define all parameters related to the U, V and F grids (glam[uv],gphi[uv], e[12][uvf]). Note that, when using a simple [#FirststepswithSAXO] (with {{{initncdf}}} or {{{computegrid}}}), adding the keyword /FULLCGRID leads also to the definition of all U, V and F grids parameters. There is the examples to load ORCA grids from OPA meshmask.
   
  * [source:/trunk/SRC/Tests/tst_initorca2.pro @tst_initorca2] : ORCA2
@@ -463 +467 @@
 === Horizontal plots and maps ===
 
-  A quick presentation of horizontal plots and maps is shown in [source:/trunk/SRC/Tests/tst_plt.pro tst_plt]. After loading any of the grid (for example with one of the above examples). Just try:
+  A quick presentation of horizontal plots and maps is shown in [source:/trunk/SRC/Tests/tst_plt.pro tst_plt]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try:
   
 {{{
@@ -482 +486 @@
 === Vertical sections ===
 
-  A quick presentation of vertical sections is shown in [source:/trunk/SRC/Tests/tst_pltz.pro tst_pltz]. After loading any of the grid (for example with one of the above examples). Just try:
+  A quick presentation of vertical sections is shown in [source:/trunk/SRC/Tests/tst_pltz.pro tst_pltz]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try:
   
 {{{
@@ -501 +505 @@
 === Hovmoellers and time series ===
 
-  A quick presentation of hovmoellers and time series is shown in [source:/trunk/SRC/Tests/tst_pltt.pro tst_pltt]. After loading any of the grid (for example with one of the above examples). Just try:
+  A quick presentation of hovmoellers and time series is shown in [source:/trunk/SRC/Tests/tst_pltt.pro tst_pltt]. After loading any of the grid (for example with one of the [#FirststepswithSAXO]). Just try:
   
 {{{

trunk/SRC/Documentation/xmldoc/wiki/MiniNotice

@@ -25 +25 @@
 }}}
 
-=== idl> xxx ===
+=== idl> xxx ===
 
     A window will open with 3 parts to consider.
@@ -41 +41 @@
 
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
 Data file name
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]]
 Grid initialization method
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/3.png)]]
 Grid initialization parameters
 
@@ -61 +61 @@
 ==== Grid initialization method ====
 
-    For visualising grilled data, you need to [wiki:FirstSteps define the grid] on which are located the data. By default, "automatic grid construction with initncdf.pro" is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure {{{initncdf}}}) without needing any other auxiliary file. If you checked "grid construction with other IDL batch or procedure", this means that you don't want to use the default {{{initncdf}}} procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
+    For visualising grilled data, you need to [wiki:FirstSteps define the grid] on which are located the data. By default, automatic grid construction with initncdf.pro is checked. This means that the grid will be defined by using the informations contained in the data file (through the IDL prodecure {{{initncdf}}}) without needing any other auxiliary file. If you checked grid construction with other IDL batch or procedure, this means that you don't want to use the default {{{initncdf}}} procedure to define the grid and you will provide your own IDL procedure or the so-called IDL batch file (a file which is called by using @, see IDL documentation).
   
 ==== Grid initialization parameters ====
 
     This third part allows you to specify the name, the argument and the keywords of the routine you want to use to initialize the grid.
-By default the name of the procedure is {{{initncdf}}}, its argument will be automatically defined so you cannot change them. If you If you checked "grid construction with other IDL batch or procedure", you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
+By default the name of the procedure is {{{initncdf}}}, its argument will be automatically defined so you cannot change them. If you checked grid construction with other IDL batch or procedure, you have to select the name of the IDL procedure or batch file and its suitable arguments and keywords. Note that if you select an IDL batch file you cannot give any parameter or keyword.
     
       Window xxx 1
@@ -76 +76 @@
     
     Once these two lines have been completed, click on let's go.
-  For example, we choose the IDL batch file "tst_initlev". Compare the result with "automatic grid construction with initncdf.pro" checked. Cf [#LaunchingXXX Launching XXX]
+  For example, we choose the IDL batch file {{{tst_initlev}}}. Compare the result with automatic grid construction with initncdf.pro checked. Cf [#LaunchingXXX Launching XXX]
       Oceania at 125 meters of depth with proper grid initialization
 
@@ -84 +84 @@
       
   
-=== idl> xxx, /separate ===
-
-This is the same as the simple idl> xxx except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
-
-=== idl> xxx, restore = 'file.dat' ===
-
-In that case xxx window will open directly in the same state as it was when the file "file.dat" was created. see +++++++
-=== idl> xxx, 'file.nc' ===
-
-In this case, the xxx window directly open the data file 'file.nc' and build the grid automatically with the IDL procedure {{{initncdf}}}. For example:
+=== idl> xxx, /separate ===
+
+This is the same as the simple [#LaunchingXXX Launching XXX] except that once the xxx window open, you will have 2 separate windows (command and plotting window) instead of one.
+
+=== idl> xxx, restore = 'file.dat' ===
+
+In that case xxx window will open directly in the same state as it was when the file {{{file.dat}}} was created. see [#LaunchingXXX Launching XXX].
+
+=== idl> xxx, 'file.nc' ===
+
+In this case, the xxx window directly open the data file {{{file.nc}}} and build the grid automatically with the IDL procedure {{{initncdf}}}. For example:
   
 {{{
@@ -102 +103 @@
 }}}
 
-=== idl> xxx, 'file.nc', keywd1 = 
, keywd2 = 
 ===
-
-In this case, the xxx window directly open the data file 'file.nc', build the grid automatically with the IDL procedure {{{initncdf}}} and use the keywords keywd1 = 
, keywd2 = 
 in the call of {{{initncdf}}}. For example:
+=== idl> xxx, 'file.nc', keywd1 = 
, keywd2 = 
 ===
+
+In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid automatically with the IDL procedure {{{initncdf}}} and use the keywords keywd1 = 
, keywd2 = 
 in the call of {{{initncdf}}}. For example:
   
 {{{
@@ -113 +114 @@
 }}}
 
-=== idl> xxx, 'file.nc', 'initgrid' ===
-
-In this case, the xxx window directly open the data file 'file.nc' and build the grid directly with the IDL procedure or batch file {{{initgrid}}}
+=== idl> xxx, 'file.nc', 'initgrid' ===
+
+In this case, the xxx window directly open the data file {{{file.nc}}} and build the grid directly with the IDL procedure or batch file {{{initgrid}}}
 {{{
 #!html
@@ -123 +124 @@
 }}}
 
-=== idl> xxx, 'file.nc', 'initgrid', keywd1 = 
, keywd2 = 
 ===
-
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure {{{initgrid}}} and use the keywords keywd1 = 
, keywd2 = 
 in the call of {{{initgrid}}}.
-
-=== idl> xxx, 'file.nc', 'initgrid', 'arg1, arg2, 
' ===
-
-In this case, the xxx window directly open the data file 'file.nc', build the grid directly with the IDL procedure {{{initgrid}}} and use the string 'arg1, arg2, 
' to specify the input arguments in the call of {{{initgrid}}}.
+=== idl> xxx, 'file.nc', 'initgrid', keywd1 = 
, keywd2 = 
 ===
+
+In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid directly with the IDL procedure {{{initgrid}}} and use the keywords keywd1 = 
, keywd2 = 
 in the call of {{{initgrid}}}.
+
+=== idl> xxx, 'file.nc', 'initgrid', 'arg1, arg2, 
' ===
+
+In this case, the xxx window directly open the data file {{{file.nc}}}, build the grid directly with the IDL procedure {{{initgrid}}} and use the string 'arg1, arg2, 
' to specify the input arguments in the call of {{{initgrid}}}.
 
 == Description of XXX window ==
@@ -152 +153 @@
 
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/1.png)]]
 Plot type
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/2.png)]]
 Menu
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/3.png)]]
 OK
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/4.png)]]
 Page layout
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/5.png)]]
 Variables list
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/6.png)]]
 Files list
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/7.png)]]
 Command text
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/8.png)]]
 Calendar
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/9.png)]]
 Domdef
 
-
+[[Image(source:/trunk/SRC/Documentation/xmldoc/images/callouts/10.png)]]
 Spefications
 
@@ -197 +198 @@
     
 
+'''Note'''
+
+
+
 If the type plt is selected, the selection of plot type
 is made by mouse. Cf [#LaunchingXXX Launching XXX]
@@ -211 +216 @@
       
     
- * Open: to open a new file. Same procedure as during the launch of XXX.
+ * Open: to open a new file. Same procedure as during the [#LaunchingXXX Launching XXX].
 The new file can be on a different grid, with different variables, with a different time base 

 
@@ -227 +232 @@
  * Postscript: to save the plotting window in Postscript format
  * Animated gif: to create an animation of the plotting window.
-The creation of an animation is only possible if none of the plots have a time axis, and if the plots are all on the same time base (calendar). On the other hand, animations of horizontal and vertical plots, with different color palettes (for those not on an X-terminal), are possible.The creation of animations has a tendency to saturate the video memory of X-terminals, crashing the entire program 

+
+
+'''Note'''
+
+The creation of an animation is only possible if none of the plots have a time axis, and if the plots are all on the same time base (calendar). On the other hand, animations of horizontal and vertical plots, with different color palettes (for those not on an X-terminal), are possible.
+
+'''Note'''
+
+The creation of animations has a tendency to saturate the video memory of X-terminals, crashing the entire program 

  * Gif: to save a gif of the plotting window.
  * IDL procedure: to save the command history that has created the plot in an IDL procedure that can be re-executed later. For example if I save the commands in {{{xxx_figure.pro}}} file, when ever I want, I can then launch a new IDL session and type:
@@ -259 +272 @@
 will then create a Postscript file of the figure.
 
- * RESTORE kwd of xxx: to save the xxx widget (all buttons and parameters stored in memory 
) in a binary file in order to quit xxx and relaunch it later with idl> xxx, restore = 'file.dat' and get exactly the same configuration.
+ * RESTORE kwd of xxx: to save the xxx widget (all buttons and parameters stored in memory 
) in a binary file in order to quit xxx and relaunch it later like in [#LaunchingXXX Launching XXX] and get exactly the same configuration.
+
  * Print to prompt: lists in the IDL window the command history that created the last plot. Useful primarily for debugging

+
 ==== Flag options sub-menu ====
 
-      The Flag Option menu
+      The Flag option menu
 
   
@@ -271 +286 @@
     
  * Portrait/Landscape: changes the configuration of the plot.
- * Overlay: to plot contours of a different field on top the
-one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!
- * Vecteur: to plot a vector field on top of contours. Only
-works on horizontal plots ({{{plt.pro}}}).
+ * Overlay: to plot contours of a different field on top the one represented as color-filled contours. It is necessary to relaunch the entire plot to make this work!
+ * Vecteur: to plot a vector field on top of contours. Only works on horizontal plots ({{{plt.pro}}}).
 As for Overlay, a relaunch of the entire plot is necessary.
  * Longitude / x index: switches longitude labeling of the plot sub-domain from degrees to indexes following i.
- * Latitude / y index: switches latitude labeling of the plot sub-domain from degrees to indexes following j.Careful, a selected option remains selected until it is re-clicked.
+ * Latitude / y index: switches latitude labeling of the plot sub-domain from degrees to indexes following j.
+
+'''Caution'''
+
+Careful, a selected option remains selected until it is re-clicked.
 === OK button ===
 Click on this OK button is required to make a new plot appear
@@ -298 +315 @@
 === List of variables ===
 You can choose the variable to work on.
-      Example of different Variables available
+      Example of different variables available
 
   
@@ -317 +334 @@
 
 To specify in the widget part number 7 the computation you want to do on the data
+
+
+'''Note'''
+
 In all cases bellow, the name given to a field (a, b, c, 
) is of no importance.
 ==== Linear calculation ====
 
-If you want to make basic linear computation (like difference between fields, add/multiply by a constant 
). you can simply put the following commands: 
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">a - b</pre>
-}}}
-
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">numb1*a</pre>
-}}}
-
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">a + numb</pre>
-}}}
- or any command with the following format 
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">numb1*a + numb2*b  + numb3*c 
 + numb</pre>
-}}}
- where numb1, numb2, 
 correspond to numbers and a, b, c 
 will be the data to read.
+If you want to make basic linear computation (like difference between fields, add/multiply by a constant 
), you can simply put the following commands: {{{a - b}}}{{{numb1*a}}}{{{a + numb}}} or any command with the following format {{{numb1*a + numb2*b  + numb3*c 
 + numb}}} where numb1, numb2, 
 correspond to numbers and a, b, c 
 will be the data to read.
 
 ==== Any kind of computation ====
 
-If you want to make a computation more complicated than a basic linear you must put designate the data you want to read between "" (with anything in between the "). For example: 
+If you want to make a computation more complicated than a basic linear you must designate the data you want to read between "" (with anything in between the "). For example: 
 {{{
 #!html
@@ -423 +424 @@
   
   You can restore configuration by default by pressing the Default button.
-  The path of the file [../../ToBeReviewed/WIDGET/AUTOUR_de_XXX/definedefaultextra.pro definedefaultextra.pro] that defines the default values for each variable names is displayed when the cursor hovers over the button Default. This file contains a case statement based on the name of the variable and defining the min, max, contour interval and other keywords that should be used as default for the specified variable. You can copy this file in your own {{{${HOME}/My_IDL/}}} directory and easily modify it to suit your favorite default values.
+  
+
+'''Note'''
+
+The path of the file [source:/trunk/SRC/ToBeReviewed/WIDGET/AUTOUR_de_XXX/definedefaultextra.pro definedefaultextra.pro] that defines the default values for each variable names is displayed when the cursor hovers over the button Default. This file contains a case statement based on the name of the variable and defining the min, max, contour interval and other keywords that should be used as default for the specified variable. You can copy this file in your own {{{${HOME}/My_IDL/}}} directory and easily modify it to suit your favorite default values.
 ==== Specify the palette to be used ====
 For the color palette, you can either specify the name or go search for one among the palettes available.
@@ -465 +470 @@
       
   
-    Graphic with /realcont, map=[90,0,0], /ortho, cell_fill=2 keywords
+    Graphic with {{{/realcont, map=[90,0,0], /ortho, cell_fill=2}}} keywords
 
     
@@ -491 +496 @@
  * the middle mouse button to create vertical plots (pltz)
  * the right mouse button to create common hovmoellers for xt and yt cuts (pltt)In summary:
- *       LCL---&gt;plt
+ *       LCL--->plt
       
   
@@ -505 +510 @@
       
     
- *       LCM---&gt;pltz
+ *       LCM--->pltz
       
   
@@ -519 +524 @@
       
     
- *       LCR---&gt;pltt
+ *       LCR--->pltt
       
   
@@ -532 +537 @@
   
       
-    If the plot selector is on something other than plt the indicated plot type is made.
+    
+
+'''Note'''
+
+If the plot selector is on something other than plt the indicated plot type is made.
 === Create multiple plots on the same sheet and make them interact ===
 
@@ -549 +558 @@
 A double-click with the right button in the second frame will erase the
 plot.In summary: 
- *       DCL---&gt;"reference" frame
+ *       DCL--->"reference" frame
       
   
@@ -556 +565 @@
       
     
-      The reference frame is selected
+      The "reference" frame is selected
       
   
@@ -563 +572 @@
       
     
- *       DCM---&gt;"target" frame
+ *       DCM--->"target" frame
       
   
@@ -570 +579 @@
       
     
-      The target frame is selected
+      The "target" frame is selected
       
   
@@ -577 +586 @@
       
     
- *       DCR---&gt;erase the frame
+ *       DCR--->erase the frame
       
   
@@ -586 +595 @@
 
 
-load xxx with the command:
+Load xxx with the command:
   
 {{{
@@ -608 +617 @@
 
 
-DCM in frame 2, LCL on the plot in frame 1, to create a horizontal
-zoom in frame 2.
-DCM in frame 3, LCM on the plot in frame 1, to create a vertical cut
-in frame 3.
-DCM in frame 4, LCR on the plot in frame 1, to create a hovmoeller in frame 4.
+DCM in frame 2, LCL on the plot in frame 1 to create a horizontal zoom in frame 2.
+DCM in frame 3, LCM on the plot in frame 1 to create a vertical cut in frame 3.
+DCM in frame 4, LCR on the plot in frame 1 to create a hovmoeller in frame 4.
 
 
@@ -645 +652 @@
 
 
-click OK, and the plot is redone.
+Click OK, and the plot is redone.
 
 
@@ -658 +665 @@
 
 
-in frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
+In frame 5, let's create the same plot as in frame 2 except we use pltv instead of plt
 
 
@@ -670 +677 @@
 
 
-change plt for pltv
+Change plt for pltv
 
 
@@ -699 +706 @@
 
 
-in the IDL window, type
-  
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">
-<code class="prompt">idl&gt;</code> <strong class="userinput"><code>domdef</code></strong>
+In the IDL window, type
+
+{{{
+#!html
+<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">
+ <code class="prompt">idl&gt;</code> <strong class="userinput"><code>domdef</code></strong>
 </pre>
 }}}
@@ -710 +717 @@
 DCR to erase the problem frame.
 
-change the orientation of the plot by pressing Flag options -&gt; Portrait/Landscape. Cf [#LaunchingXXX Launching XXX]
+change the orientation of the plot by pressing Flag options Portrait/Landscape. Cf [#LaunchingXXX Launching XXX]
 quit XXX cleanly using quit from the File menu. Cf [#LaunchingXXX Launching XXX]
+
+
+'''Note'''
+
 
 
@@ -720 +731 @@
 overflow.
 To clean up this memory:
-  
-{{{
-#!html
-<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">
-<code class="prompt">idl&gt;</code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>
+
+{{{
+#!html
+<pre xmlns:xl="http://www.w3.org/1999/xlink" class="screen">
+ <code class="prompt">idl&gt;</code> <strong class="userinput"><code>ptr_free, ptr_valid()</code></strong>
 </pre>
 }}}

trunk/SRC/Documentation/xmldoc/wiki/WhatisSaxo

@@ -18 +18 @@
 SAXO needs at least [http://www.ittvis.com/idl/ IDL] 6.0.
   
+
+'''Note'''
+
+
     SAXO can be used with the 7 minutes demo-mode (within the limitations of this mode: impossible to save data and create a file).
   

trunk/SRC/Documentation/xmldoc/wiki/WhatsNew

@@ -33 +33 @@
 == Changeset 152 (2006-08-10) ==
 
-This revision includes new [../../ToBeReviewed/PLOTS/DESSINE/pltv.pro pltv] (a mix between {{{plt}}} and {{{tvplus}}}) plotting procedure.
+This revision includes new [source:/trunk/SRC/ToBeReviewed/PLOTS/DESSINE/pltv.pro pltv] (a mix between {{{plt}}} and {{{tvplus}}}) plotting procedure.
 
 Details can be seen in [http://forge.ipsl.jussieu.fr/saxo/changeset/152 Changeset 152].