source: trunk/SRC/Documentation/xmldoc/faqsaxo.xml @ 294

Last change on this file since 294 was 294, checked in by pinsard, 17 years ago

complete FAQ for spell checking

  • Property svn:keywords set to Id
File size: 8.6 KB
Line 
1<?xml version='1.0' encoding='iso-8859-1'?>
2<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
4[
5<!ENTITY promptidl "idl&gt;">
6]>
7<article>
8<!--
9en s'inspirant de
10http://www.csc.fi/math_topics/Mail/FAQ/msg00069.html
11pour les questions
12on pourra aussi s'inspirer de http://idlastro.gsfc.nasa.gov/idlfaq.html
13
14!! on notera l'utilisation hypersioux de xinclude xpointer pour ne pas répéter
15(avec des erreurs, forcément) ce qui est déjà écrit dans un autre document
16!!
17cf http://www.zvon.org/xxl/XIncludeTutorial/Output/example9.html
18cf http://www.zvon.org/xxl/XIncludeTutorial/Output/example12.html
19bon finalement c'est pas si hyper rusé parce qu'on hérite du plan (sect1 par
20exemple de l'entité incluse)
21-->
22<title>Frequently Asked questions about SAXO</title>
23  <articleinfo>
24    <authorgroup>
25      <author><firstname>Sébastien</firstname> <surname>Masson</surname> <email>Sebastien.Masson_at_locean-ipsl.upmc.fr</email></author>
26      <author><firstname>Françoise</firstname> <surname>Pinsard</surname> <email>Francoise.Pinsard_at_locean-ipsl.upmc.fr</email></author>
27    </authorgroup>
28    <keywordset>
29      <keyword>IDL</keyword>
30      <keyword>SAXO</keyword>
31      <keyword>FAQ</keyword>
32    </keywordset>
33    <revhistory>
34      <revision>
35        <revnumber>0.0</revnumber>
36        <date>August 2006</date>
37        <revremark>First draft</revremark>
38      </revision>
39      <revision>
40        <revnumber>0.1</revnumber>
41        <date>September 2006</date>
42        <revremark>+ onlinehelp</revremark>
43      </revision>
44    </revhistory>
45    <pubdate>$Id$</pubdate>
46  </articleinfo>
47
48<qandaset>
49<qandadiv id="intro">
50<title>Introduction</title>
51<para>
52This is a list of Frequently Asked Questions about SAXO.
53</para>
54<para>
55This list is roughly divided into categories: general questions,
56technical questions, contributors questions.
57</para>
58<para>
59Suggestions for corrections or additional sections are welcome -- please email them to <email>saxo-dev@forge.ipsl.jussieu.fr</email>.
60</para>
61</qandadiv>
62<qandadiv id="general">
63<title>General</title>
64<qandaentry>
65<question>
66<para>
67What is SAXO ?
68</para>
69</question>
70<answer>
71<para>
72see document <ulink url="./whatissaxo.html">What is SAXO</ulink>.
73</para>
74</answer>
75</qandaentry>
76<qandaentry>
77<question>
78<para>
79How can I get help ?
80</para>
81</question>
82<answer>
83<para>
84see Support in document <ulink url="./websaxo.html">Main page of SAXO</ulink>.
85</para>
86</answer>
87</qandaentry>
88<qandaentry>
89<question>
90<para>
91How do I get SAXO ?
92</para>
93</question>
94<answer>
95<para>
96see document <ulink url="./getsaxo.html">Get SAXO</ulink>.
97</para>
98</answer>
99</qandaentry>
100<qandaentry>
101<question>
102<para>
103What is the current version of SAXO ?
104</para>
105</question>
106<answer>
107<para>
108</para>
109</answer>
110</qandaentry>
111<qandaentry>
112<question>
113<para>
114On what systems does SAXO run ?
115</para>
116</question>
117<answer>
118<para>
119</para>
120</answer>
121</qandaentry>
122<qandaentry>
123<question>
124<para>
125Does SAXO works with GDL instead of IDL ?
126</para>
127</question>
128<answer>
129<para>
130Not yet. <!-- et de toute façon GDL est pour l'instant équivalent à la version
1316.0 de IDL donc peut-etre que tout SAXO ne fonctionnerait pas -->
132</para>
133</answer>
134</qandaentry>
135<qandaentry>
136<question>
137<para>
138When is the next version of SAXO due out ?
139</para>
140</question>
141<answer>
142<para>
143</para>
144</answer>
145</qandaentry>
146<qandaentry>
147<question>
148<para>
149How can I find if a routine to do what I want already exists ?
150</para>
151</question>
152<answer>
153<para>
154</para>
155</answer>
156</qandaentry>
157<qandaentry>
158<question>
159<para>
160How should SAXO be cited or acknowledged in publication ?
161</para>
162</question>
163<answer>
164<para>
165</para>
166</answer>
167</qandaentry>
168</qandadiv>
169<qandadiv id="technical">
170<title>Technical questions</title>
171<qandaentry>
172<question>
173<para>
174Is there on-line help for SAXO ?
175</para>
176</question>
177<answer>
178<para>
179Yes, if you use at least IDL 6.2. It is produced by <application><ulink url="http://www.ittvis.com/codebank/search.asp?FID=100">IDLdoc</ulink></application>. SAXO and IDL online_help have been merged, you can simply get the help by typing:
180     <screen>
181       <prompt>&promptidl;</prompt> <userinput><command>?</command></userinput>
182     </screen>
183</para>
184</answer>
185</qandaentry>
186</qandadiv>
187<qandadiv id="Contributors">
188<title>Contributors</title>
189<qandaentry>
190<question>
191<para>
192Is there an SAXO Style Guide available ?
193</para>
194</question>
195<answer>
196<para>
197There is a template for header <ulink url="../new_header.txt">new_header.txt</ulink>
198which can be parsed by <application>IDLdoc</application>.
199</para>
200<para>
201This file can be added in <application>Emacs</application> configuration
202<menuchoice>
203  <shortcut>
204    <keycombo><keysym>C-c</keysym><keysym>C-h</keysym></keycombo>
205  </shortcut>
206  <guimenu>IDLWAVE</guimenu>
207  <guimenuitem>Templates</guimenuitem>
208  <guimenuitem>Doc Header</guimenuitem>
209</menuchoice>.
210in your <filename>${HOME}/.emacs</filename> like this :
211<programlisting>
212(add-hook 'idlwave-mode-hook
213  (function
214    (lambda ()
215     (setq idlwave-file-header '("<replaceable>SAXO_basedirectory</replaceable>/SAXO_DIR/SRC/Documentation/new_header.txt")
216    ))))
217</programlisting>
218</para>
219</answer>
220</qandaentry>
221<qandaentry>
222<question>
223<para>
224Is there any trouble with <application>IDLdoc</application> ?
225</para>
226</question>
227<answer>
228<para>
229Yes, there are some :
230<itemizedlist>
231<listitem>
232<para>
233<literal>\</literal> in <filename>*.pro</filename> are not written
234in <filename>*.html</filename>.
235They must be escaped by an other <literal>\</literal> or you can choose an other character.
236</para>
237</listitem>
238<listitem>
239<para>
240<guimenu>Search</guimenu> doesn't handle characters like <literal>-</literal>
241and <literal>|</literal>.
242</para>
243</listitem>
244<listitem>
245<para>
246Paragraphs of <filename>*.pro</filename> headers are shown with a proportional
247font in the <literal>HTML</literal> release.
248</para>
249<para>
250If you need to draw some small figure like grid cell, you can encapsulate
251the block to be shown in constant font <!-- see savesaxo.sh -->
252between
253<literal>; &lt;fixe&gt;</literal> and
254<literal>; &lt;/fixe&gt;</literal>
255</para>
256</listitem>
257</itemizedlist>
258</para>
259<para>
260Unfortunately, these troubles may not be fixed because the author does not
261have anymore the opportunity to work on his own work.
262</para>
263<para>
264Bugs can be submitted to IDL but we do not expect answers !
265<!-- ++ rappel du bug soumis -->
266</para>
267</answer>
268</qandaentry>
269<qandaentry>
270<question>
271<para>
272How can I check spelling of XML files ?
273</para>
274</question>
275<answer>
276<para>
277There is one way with command line :
278     <screen>
279       <prompt>$</prompt> <userinput><command>aspell</command> <option>--mode=sgml</option> <option>-c</option> <parameter><filename><replaceable>xmlfile</replaceable></filename></parameter></userinput>
280     </screen>
281</para>
282</answer>
283</qandaentry>
284<qandaentry>
285<question>
286<para>
287How can I check spelling of IDL files ?
288</para>
289</question>
290<answer>
291<para>
292Not so easy but you can start with something like this :
293     <screen>
294       <prompt>$</prompt> <userinput><command>cd</command> <parameter><envar>${HOME}</envar>/SAXO_DIR/SRC</parameter></userinput>
295       <prompt>$</prompt> <userinput>list=$(find . -name "*.pro")</userinput>
296       <prompt>$</prompt> <userinput>for file in ${list}; do aspell list &lt; ${file}; done > /tmp/list_word </userinput>
297       <prompt>$</prompt> <userinput>sort -u /tmp/list_word > /tmp/list_sort</userinput>
298     </screen>
299</para>
300<para>
301This will give <filename>/tmp/list_sort</filename> a list of sorted word
302used in IDL files that are not in the default dictionnary.
303Some of these words are correct in IDL and SAXO vocabulary, so they do not have to be replaced but some typo can be found.
304</para>
305<para>
306To find occurences of one of these misspelled words, you have to do this :
307     <screen>
308       <prompt>$</prompt> <userinput>find . -name "*.pro" -exec grep -h "<replaceable>misspelled_word</replaceable>" {} \;</userinput>
309     </screen>
310</para>
311<para>
312We should improve this by providing some IDL and SAXO dictionnary. <!-- ++ -->
313</para>
314</answer>
315</qandaentry>
316<qandaentry>
317<question>
318<para>
319How can I see online help update ?
320</para>
321</question>
322<answer>
323<para>
324You won't see  online help update if you are working with the official distribution because of <varname>!HELP_PATH</varname>. To override this problem, when you are in <filename class="directory"><replaceable>SAXO_basedirectory</replaceable>/SAXO_DIR/SRC/Documentation/xmldoc/</filename>,  you can call online help like this :
325     <screen>
326       <prompt>&promptidl;</prompt> <userinput><command>ONLINE_HELP</command>,<option>book="../idldoc_assistant_output/idldoc-lib.adp"</option></userinput>
327     </screen>
328</para>
329</answer>
330</qandaentry>
331</qandadiv>
332</qandaset>
333</article>
Note: See TracBrowser for help on using the repository browser.