Changeset 294


Ignore:
Timestamp:
09/24/07 16:18:40 (17 years ago)
Author:
pinsard
Message:

complete FAQ for spell checking

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/SRC/Documentation/xmldoc/faqsaxo.xml

    r230 r294  
    55<!ENTITY promptidl "idl&gt;"> 
    66]> 
     7<article> 
    78<!-- 
    89en s'inspirant de 
     
    1213 
    1314!! on notera l'utilisation hypersioux de xinclude xpointer pour ne pas répéter 
    14 (avec des erreurs, forcément)à ce qui est déjà écrit dans un autre document 
     15(avec des erreurs, forcément) ce qui est déjà écrit dans un autre document 
    1516!! 
    1617cf http://www.zvon.org/xxl/XIncludeTutorial/Output/example9.html 
     
    1920exemple de l'entité incluse) 
    2021--> 
    21 <article> 
    2222<title>Frequently Asked questions about SAXO</title> 
    2323  <articleinfo> 
     
    178178<para> 
    179179Yes, 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 format="linespecific"> 
     180     <screen> 
    181181       <prompt>&promptidl;</prompt> <userinput><command>?</command></userinput> 
    182182     </screen> 
     
    209209</menuchoice>. 
    210210in your <filename>${HOME}/.emacs</filename> like this : 
    211 <programlisting format="linespecific"> 
     211<programlisting> 
    212212(add-hook 'idlwave-mode-hook 
    213213  (function 
     
    249249<para> 
    250250If you need to draw some small figure like grid cell, you can encapsulate 
    251 between the block to be shown in constant font <!-- see savesaxo.sh --> 
     251the block to be shown in constant font <!-- see savesaxo.sh --> 
    252252between 
    253253<literal>; &lt;fixe&gt;</literal> and 
     
    270270<question> 
    271271<para> 
    272 How can I check spelling of xml files ? 
     272How can I check spelling of XML files ? 
    273273</para> 
    274274</question> 
     
    276276<para> 
    277277There is one way with command line : 
    278      <screen format="linespecific"> 
     278     <screen> 
    279279       <prompt>$</prompt> <userinput><command>aspell</command> <option>--mode=sgml</option> <option>-c</option> <parameter><filename><replaceable>xmlfile</replaceable></filename></parameter></userinput> 
    280280     </screen> 
     
    285285<question> 
    286286<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> 
    287319How can I see online help update ? 
    288320</para> 
     
    291323<para> 
    292324You 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 : 
    293      <screen format="linespecific"> 
     325     <screen> 
    294326       <prompt>&promptidl;</prompt> <userinput><command>ONLINE_HELP</command>,<option>book="../idldoc_assistant_output/idldoc-lib.adp"</option></userinput> 
    295327     </screen> 
Note: See TracChangeset for help on using the changeset viewer.