Xcos help: improve the en_US and fr_FR pages 26/13026/2
Clément DAVID [Thu, 24 Oct 2013 16:04:33 +0000 (18:04 +0200)]
 * Remove old latex-generated images, inline the latex source
 * Recreate images without a source (memory representation, bitshift algo)
   using the pic language [http://en.wikipedia.org/wiki/Pic_language].
   Inline the PIC code as <textobject>

Change-Id: I8e3a54bf2f253b79d178cbb3d17cb5bbbef7e335

262 files changed:
scilab/modules/helptools/etc/images_md5.txt
scilab/modules/helptools/images/C_struct_img12_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/C_struct_img1_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/C_struct_img2_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/C_struct_img3_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/C_struct_img4_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/C_struct_img9_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/DIFF_f_gui.gif
scilab/modules/helptools/images/ENDBLK_gui.gif
scilab/modules/helptools/images/END_c_gui.gif
scilab/modules/helptools/images/ScilabCaution.png
scilab/modules/helptools/images/ScilabEdit.png
scilab/modules/helptools/images/ScilabExecute.png
scilab/modules/helptools/images/ScilabImportant.png
scilab/modules/helptools/images/ScilabNote.png
scilab/modules/helptools/images/ScilabTip.png
scilab/modules/helptools/images/ScilabWarning.png
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_10.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_11.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_4.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_5.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_6.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_7.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_8.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_9.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_COSBLK_f.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_4.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_5.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_C_struct.xml_6.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_Capacitor.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_DERIV.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_DLSS.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_DLSS.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_DLSS.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_DLSS.xml_4.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_Diode.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_END_c.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_4.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_5.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_6.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_INTRP2BLK_f.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_Inductor.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_PerteDP.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_READC_f.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_READC_f.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_READC_f.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_Resistor.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_SINBLK_f.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_TANBLK_f.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_2.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_3.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_4.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_5.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VariableResistor.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_1.png [new file with mode: 0644]
scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_fr_FR_1.png [new file with mode: 0644]
scilab/modules/helptools/images/dae_1.png
scilab/modules/helptools/images/rfile_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/rfile_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_arithmetic_left.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_arithmetic_left_en_US.png [deleted file]
scilab/modules/helptools/images/shift_arithmetic_right.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_arithmetic_right_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_arithmetic_right_en_US.png [deleted file]
scilab/modules/helptools/images/shift_rotate_left.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_rotate_left_en_US.png [deleted file]
scilab/modules/helptools/images/shift_rotate_right.gif [new file with mode: 0644]
scilab/modules/helptools/images/shift_rotate_right_en_US.png [deleted file]
scilab/modules/helptools/images/wfile_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/wfile_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/helptools/images/writec_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/helptools/images/writec_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/helptools/src/java/org/scilab/modules/helptools/HTMLDocbookTagConverter.java
scilab/modules/xcos/help/en_US/palettes/Continuous_pal/DERIV.xml
scilab/modules/xcos/help/en_US/palettes/Continuous_pal/TCLSS.xml
scilab/modules/xcos/help/en_US/palettes/Demonstrationsblocks_pal/AUTOMAT.xml
scilab/modules/xcos/help/en_US/palettes/Discrete_pal/DLSS.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/Capacitor.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/Diode.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/Inductor.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/Resistor.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/VariableResistor.xml
scilab/modules/xcos/help/en_US/palettes/Electrical_pal/VoltageSensor.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/ANDBLK.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/CEVENTSCOPE.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/EDGE_TRIGGER.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/Extract_Activation.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/MCLOCK_f.xml
scilab/modules/xcos/help/en_US/palettes/Events_pal/freq_div.xml
scilab/modules/xcos/help/en_US/palettes/Implicit_pal/DIFF_f.xml
scilab/modules/xcos/help/en_US/palettes/Integer_pal/SHIFT.xml
scilab/modules/xcos/help/en_US/palettes/Lookuptables_pal/INTRP2BLK_f.xml
scilab/modules/xcos/help/en_US/palettes/Mathoperations_pal/COSBLK_f.xml
scilab/modules/xcos/help/en_US/palettes/Mathoperations_pal/SINBLK_f.xml
scilab/modules/xcos/help/en_US/palettes/Mathoperations_pal/TANBLK_f.xml
scilab/modules/xcos/help/en_US/palettes/Signalrouting_pal/DEMUX.xml
scilab/modules/xcos/help/en_US/palettes/Signalrouting_pal/SWITCH2_m.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CANIMXY.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CANIMXY3D.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CFSCOPE.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CMAT3D.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CMATVIEW.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CMSCOPE.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CSCOPE.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CSCOPXY.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/CSCOPXY3D.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/ENDBLK.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/END_c.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/WFILE_f.xml
scilab/modules/xcos/help/en_US/palettes/Sinks_pal/WRITEC_f.xml
scilab/modules/xcos/help/en_US/palettes/Sources_pal/FROMWSB.xml
scilab/modules/xcos/help/en_US/palettes/Sources_pal/READC_f.xml
scilab/modules/xcos/help/en_US/palettes/Sources_pal/RFILE_f.xml
scilab/modules/xcos/help/en_US/palettes/Sources_pal/Sigbuilder.xml
scilab/modules/xcos/help/en_US/palettes/Thermohydraulics_pal/PerteDP.xml
scilab/modules/xcos/help/en_US/palettes/Thermohydraulics_pal/VanneReglante.xml
scilab/modules/xcos/help/en_US/palettes/Userdefinedfunctions_pal/CBLOCK.xml
scilab/modules/xcos/help/en_US/programming_scicos_blocks/c_computational_functions/C_struct.xml
scilab/modules/xcos/help/en_US/programming_scicos_blocks/utilities_functions/getscicosvars.xml
scilab/modules/xcos/help/fr_FR/palettes/Continuous_pal/DERIV.xml
scilab/modules/xcos/help/fr_FR/palettes/Continuous_pal/TCLSS.xml
scilab/modules/xcos/help/fr_FR/palettes/Discrete_pal/DLSS.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/Capacitor.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/Diode.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/Inductor.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/Resistor.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/VariableResistor.xml
scilab/modules/xcos/help/fr_FR/palettes/Electrical_pal/VoltageSensor.xml
scilab/modules/xcos/help/fr_FR/palettes/Integer_pal/SHIFT.xml
scilab/modules/xcos/help/fr_FR/palettes/Mathoperations_pal/COSBLK_f.xml
scilab/modules/xcos/help/fr_FR/palettes/Mathoperations_pal/SINBLK_f.xml
scilab/modules/xcos/help/fr_FR/palettes/Mathoperations_pal/TANBLK_f.xml
scilab/modules/xcos/help/fr_FR/palettes/Sinks_pal/WFILE_f.xml
scilab/modules/xcos/help/fr_FR/palettes/Sinks_pal/WRITEC_f.xml
scilab/modules/xcos/help/fr_FR/palettes/Sources_pal/RFILE_f.xml
scilab/modules/xcos/help/images/ANDBLK_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img17_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img18_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img19_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img20_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img21_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img23_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img24_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img25_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img7_eng.gif [deleted file]
scilab/modules/xcos/help/images/AUTOMAT_img9_eng.gif [deleted file]
scilab/modules/xcos/help/images/CANIMXY3D_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CANIMXY3D_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CANIMXY_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CANIMXY_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CBLOCK_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CEVENTSCOPE_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CEVENTSCOPE_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CEVENTSCOPE_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/CFSCOPE_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CFSCOPE_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CMAT3D_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CMATVIEW_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CMSCOPE_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CMSCOPE_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/COSBLK_f_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPE_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPE_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPXY3D_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPXY3D_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPXY_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/CSCOPXY_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/C_struct_img6_eng.gif [deleted file]
scilab/modules/xcos/help/images/C_struct_img7_eng.gif [deleted file]
scilab/modules/xcos/help/images/C_struct_img8_eng.gif [deleted file]
scilab/modules/xcos/help/images/Capacitor_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/DEMUX_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/DERIV_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/DIFF_f_gui.gif [deleted file]
scilab/modules/xcos/help/images/DLSS_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/DLSS_img6_eng.gif [deleted file]
scilab/modules/xcos/help/images/DLSS_img7_eng.gif [deleted file]
scilab/modules/xcos/help/images/DLSS_img8_eng.gif [deleted file]
scilab/modules/xcos/help/images/Diode_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/EDGE_TRIGGER_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/ENDBLK_gui.gif [deleted file]
scilab/modules/xcos/help/images/ENDBLK_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/END_c_gui.gif [deleted file]
scilab/modules/xcos/help/images/END_c_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/Extract_Activation_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img13_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img14_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img15_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img6_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img7_eng.gif [deleted file]
scilab/modules/xcos/help/images/FROMWSB_img8_eng.gif [deleted file]
scilab/modules/xcos/help/images/INTRP2BLK_f_img9_eng.gif [deleted file]
scilab/modules/xcos/help/images/Inductor_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/MCLOCK_f_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/PerteDP_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/READC_f_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/READC_f_img4_eng.gif [deleted file]
scilab/modules/xcos/help/images/READC_f_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/Resistor_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/SINBLK_f_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/SWITCH2_m_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/Sigbuilder_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/TANBLK_f_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/TCLSS_img5_eng.gif [deleted file]
scilab/modules/xcos/help/images/TCLSS_img6_eng.gif [deleted file]
scilab/modules/xcos/help/images/TCLSS_img7_eng.gif [deleted file]
scilab/modules/xcos/help/images/TCLSS_img8_eng.gif [deleted file]
scilab/modules/xcos/help/images/VanneReglante_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/VariableResistor_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/VoltageSensor_img2_eng.gif [deleted file]
scilab/modules/xcos/help/images/freq_div_img3_eng.gif [deleted file]
scilab/modules/xcos/help/images/getscicosvars_img1_eng.gif [deleted file]
scilab/modules/xcos/help/images/integer_pal/en_US/shift_arithmetic_left_en_US.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/en_US/shift_arithmetic_right_en_US.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/en_US/shift_rotate_left_en_US.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/en_US/shift_rotate_right_en_US.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/fr_FR/shift_arithmetic_left_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/fr_FR/shift_arithmetic_right_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/fr_FR/shift_rotate_left_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/integer_pal/fr_FR/shift_rotate_right_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/palettes/integer_pal/shift_arithmetic_left.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/integer_pal/shift_arithmetic_right.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/integer_pal/shift_rotate_left.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/integer_pal/shift_rotate_right.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sinks_pal/en_US/wfile_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sinks_pal/en_US/writec_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sinks_pal/fr_FR/wfile_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sinks_pal/fr_FR/writec_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sources_pal/en_US/rfile_f_record_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/palettes/sources_pal/fr_FR/rfile_f_record_fr_FR.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img12_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img1_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img2_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img3_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img4_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img9_en_US.gif [new file with mode: 0644]
scilab/modules/xcos/help/images/sinks_pal/en_US/wfile_f_record_en_US.png [deleted file]
scilab/modules/xcos/help/images/sinks_pal/en_US/writec_f_record_en_US.png [deleted file]
scilab/modules/xcos/help/images/sinks_pal/fr_FR/wfile_f_record_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/sinks_pal/fr_FR/writec_f_record_fr_FR.png [deleted file]
scilab/modules/xcos/help/images/sources_pal/en_US/rfile_f_record_en_US.png [deleted file]
scilab/modules/xcos/help/images/sources_pal/fr_FR/rfile_f_record_fr_FR.png [deleted file]
scilab/modules/xcos/images/gui/DIFF_f_gui.gif [new file with mode: 0644]
scilab/modules/xcos/images/gui/ENDBLK_gui.gif [new file with mode: 0644]
scilab/modules/xcos/images/gui/END_c_gui.gif [new file with mode: 0644]

index 27d4593..41f0509 100644 (file)
@@ -209,10 +209,23 @@ _LaTeX_7-IDA.xml_2.png=1aa0a943d7130da822dd44a06bd29841
 _LaTeX_7-IDA.xml_3.png=dc4144bc7f206b73cb21d076e514318
 _LaTeX_7-IDA.xml_4.png=fd4d98e3f51e0df40b7279037376fcfa
 _LaTeX_7-IDA.xml_5.png=45cccc2e93d5e06aac213e08e7ce740f
+_LaTeX_AUTOMAT.xml_1.png=b00dadb00ee90db8e89a48a304c39b21
+_LaTeX_AUTOMAT.xml_10.png=be926979cd0fddca24f69853a3671cf5
+_LaTeX_AUTOMAT.xml_11.png=e6a4cc642eb347c2d00876299bf47cbd
+_LaTeX_AUTOMAT.xml_2.png=ed35373880183d013fc1bba898b2e3ae
+_LaTeX_AUTOMAT.xml_3.png=69cf58ca5b45e67bed0857e236236440
+_LaTeX_AUTOMAT.xml_4.png=ed35373880183d013fc1bba898b2e3ae
+_LaTeX_AUTOMAT.xml_5.png=5a5dac85bf6322e43c574824bbbaa38c
+_LaTeX_AUTOMAT.xml_6.png=fe9d99984ffd4d3101639b23ee999df5
+_LaTeX_AUTOMAT.xml_7.png=61063ba399317a3b1dd61c29e43aa141
+_LaTeX_AUTOMAT.xml_8.png=a5291981a6797b501c614f64f669a46b
+_LaTeX_AUTOMAT.xml_9.png=ed35373880183d013fc1bba898b2e3ae
 _LaTeX_BITCLEAR.xml_1.png=b97ed20387467efe4809952c888e36a8
 _LaTeX_BITCLEAR.xml_fr_FR_1.png=ff1bb557dff0583158de44fc29c54874
 _LaTeX_BITSET.xml_1.png=2ad868695d0f0e2a7f7033f8c47190
 _LaTeX_BITSET.xml_fr_FR_1.png=621e13adf345efdb45c083751a051f93
+_LaTeX_CBLOCK.xml_1.png=3def24cf259215eefdd43e76525fb473
+_LaTeX_CBLOCK.xml_2.png=3def24cf259215eefdd43e76525fb473
 _LaTeX_CLSS.xml_1.png=8392c4dff7f5f80b1f7d1d2c89a0aa82
 _LaTeX_CLSS.xml_2.png=944e22433464f50dd883ec1b8fadea37
 _LaTeX_CLSS.xml_3.png=7903ebcafc1cfe1683893d926193ce4b
@@ -220,10 +233,19 @@ _LaTeX_CLSS.xml_4.png=ddfaf0bfb39cf7978750a26a0eb22cb6
 _LaTeX_CLSS.xml_5.png=1aba733342de1f90dc856add5ca377ac
 _LaTeX_CLSS.xml_6.png=4dee794e36bb3162f5d87469d93692c2
 _LaTeX_CLSS.xml_7.png=28d86ad35e7440ebe638ed73e5bdbaae
+_LaTeX_COSBLK_f.xml_1.png=77816ca8d4dcd485e422fae43cd365c6
+_LaTeX_C_struct.xml_1.png=52c86a4ad6c4965b8ab1c7eaf209ac79
+_LaTeX_C_struct.xml_2.png=13a9a96a786dee13df2173663f5dc314
+_LaTeX_C_struct.xml_3.png=f38be9f2ade4b4e859ad132872d8db
+_LaTeX_C_struct.xml_4.png=c734c26c78ca1e6b8d6d82ef3326a5a0
+_LaTeX_C_struct.xml_5.png=9049e58ebe910ce762c2d8cb913c31b0
+_LaTeX_C_struct.xml_6.png=7da7b61069dbeeab5098c7db2ecdb241
+_LaTeX_Capacitor.xml_1.png=7e362ac68b7a1be4b076d42012db22dd
 _LaTeX_DEADBAND.xml_1.png=ab52676340ed2c7e0b0a114f45f11ae3
 _LaTeX_DEADBAND.xml_2.png=4325de0b0c0231bdb1c86f6b9fe08d8e
 _LaTeX_DEADBAND.xml_3.png=6b4be892f0c70b1412654dba7ed3a7c0
 _LaTeX_DELAY_f.xml_1.png=24f6fce55bbf2d7fdd9e525327b07847
+_LaTeX_DERIV.xml_1.png=af8e5c958fcd978c52c5650e4d817e0
 _LaTeX_DFLIPFLOP.xml_1.png=4c963e0829007142fc75fab4213a3cbf
 _LaTeX_DFLIPFLOP.xml_10.png=574c44a7bfd9f5229484328e422c48d7
 _LaTeX_DFLIPFLOP.xml_11.png=65532efbf8fbd662e6ab99f1bfb0bbf7
@@ -264,6 +286,12 @@ _LaTeX_DLATCH.xml_6.png=2129bb861061d1a052c592e2dc6b383
 _LaTeX_DLATCH.xml_7.png=ec9e5c721c4fcc0e2d249a1973ff64d4
 _LaTeX_DLATCH.xml_8.png=574c44a7bfd9f5229484328e422c48d7
 _LaTeX_DLATCH.xml_9.png=c4ca4238a0b923820dcc509a6f75849b
+_LaTeX_DLSS.xml_1.png=53d147e7f3fe6e47ee05b88b166bd3f6
+_LaTeX_DLSS.xml_2.png=61e84f854bc6258d4108d08d4c4a0852
+_LaTeX_DLSS.xml_3.png=9b325b9e31e85137d1de765f43c0f8bc
+_LaTeX_DLSS.xml_4.png=78ec2b7008296ce0561cf83393cb746d
+_LaTeX_Diode.xml_1.png=35ef86d813c2415f365050f60e55df90
+_LaTeX_END_c.xml_1.png=13097602ca0eb5da626754319bb02464
 _LaTeX_EVTDLY_c.xml_1.png=8f611346748fcfa435fd909ec853aca
 _LaTeX_EVTDLY_c.xml_2.png=4dbaad557f05602327668c829f0b3ef3
 _LaTeX_EVTDLY_c.xml_3.png=aa817d3182426d8666a9d48dd0f4ae21
@@ -271,12 +299,20 @@ _LaTeX_EVTDLY_c.xml_4.png=865c0c0b4ab0e063e5caa3387c1a8741
 _LaTeX_EXPRESSION.xml_1.png=a6e41d7103d886552b5f6125d09ee0f1
 _LaTeX_EXTRACTBITS.xml_1.png=b97ed20387467efe4809952c888e36a8
 _LaTeX_EXTRACTBITS.xml_fr_FR_1.png=ff1bb557dff0583158de44fc29c54874
+_LaTeX_FROMWSB.xml_1.png=feeff6ccf7aa5e2628deb23b59c1c759
+_LaTeX_FROMWSB.xml_2.png=89ac95276e337f7f5deb93198d6833b5
+_LaTeX_FROMWSB.xml_3.png=feeff6ccf7aa5e2628deb23b59c1c759
+_LaTeX_FROMWSB.xml_4.png=34e58a0bbafa0ba54a7640470bb2cb56
+_LaTeX_FROMWSB.xml_5.png=477562945adc8016ca3ea2a72d59c4f3
+_LaTeX_FROMWSB.xml_6.png=55eec060dcb110392536c63814ff45d4
 _LaTeX_GENSIN_f.xml_1.png=df7110d93d01f93f0b54d9aa298e9635
 _LaTeX_GENSQR_f.xml_1.png=746f663ac5f83b108763d9273b5f0e21
 _LaTeX_GENSQR_f.xml_2.png=aa318bdb2a27d84eca5689f9e78acaaf
 _LaTeX_GENSQR_f.xml_3.png=b6e19724204b26861523de89ac4da149
 _LaTeX_GENSQR_f.xml_4.png=aa318bdb2a27d84eca5689f9e78acaaf
+_LaTeX_INTRP2BLK_f.xml_1.png=205995f88b807b2f5268f7ef4053f049
 _LaTeX_INTRPLBLK_f.xml_1.png=82f1018ad624f54faa176b27fa4f92fd
+_LaTeX_Inductor.xml_1.png=4e69417e6e0001a48e9abb40adf4be71
 _LaTeX_JKFLIPFLOP.xml_1.png=268c8a111a4f0706e82e926c47212724
 _LaTeX_JKFLIPFLOP.xml_10.png=c4ca4238a0b923820dcc509a6f75849b
 _LaTeX_JKFLIPFLOP.xml_11.png=cfcd208495d565ef66e7dff9f98764da
@@ -319,8 +355,14 @@ _LaTeX_JKFLIPFLOP_content.dbk_8.png=574c44a7bfd9f5229484328e422c48d7
 _LaTeX_JKFLIPFLOP_content.dbk_9.png=cfcd208495d565ef66e7dff9f98764da
 _LaTeX_LOGIC.xml_1.png=e19cac88e786393f792adb75013e7d0a
 _LaTeX_LOGIC.xml_fr_FR_1.png=bf10ac30d0fee3333d2dae9f5f8c1b33
+_LaTeX_PerteDP.xml_1.png=aaa66cecfcbc25a73e52eb804020799
 _LaTeX_RAMP.xml_1.png=c851aba90cb36bc4a4d869245c01a167
+_LaTeX_READC_f.xml_1.png=13c8b97affd37ff01af15dfd18fef48b
+_LaTeX_READC_f.xml_2.png=ec71f47b6aee7b3cd545386b93601915
+_LaTeX_READC_f.xml_3.png=3def24cf259215eefdd43e76525fb473
+_LaTeX_Resistor.xml_1.png=690f0f4260cdc2f68b498676f4c1d44c
 _LaTeX_SAWTOOTH_f.xml_1.png=d2352f773be10a7110da96a1bf7f316d
+_LaTeX_SINBLK_f.xml_1.png=bbef421f84139065997738e07d5c88d1
 _LaTeX_SRFLIPFLOP.xml_1.png=abbb4819d673c4ef29f8e480d4cbfac6
 _LaTeX_SRFLIPFLOP.xml_10.png=c4ca4238a0b923820dcc509a6f75849b
 _LaTeX_SRFLIPFLOP.xml_11.png=cfcd208495d565ef66e7dff9f98764da
@@ -362,7 +404,16 @@ _LaTeX_STEP_FUNCTION.xml_6.png=d19b0bac1346857335abaa691e249433
 _LaTeX_STEP_FUNCTION.xml_7.png=88d1c2d945a448f132494fd3f1f8762b
 _LaTeX_STEP_FUNCTION.xml_8.png=d19b0bac1346857335abaa691e249433
 _LaTeX_STEP_FUNCTION.xml_9.png=ae9633ee9e89f17bf6b6f461d70412b2
+_LaTeX_TANBLK_f.xml_1.png=65228506d7be0db07b24b865f0df3e45
 _LaTeX_VARIABLE_DELAY.xml_1.png=1382fab19264d949b01a95cd2d7a6159
+_LaTeX_VanneReglante.xml_1.png=23b744e7272c7ae86c4e526ad5ebbde7
+_LaTeX_VanneReglante.xml_2.png=2ad9d098b937e46f9f58968551adac57
+_LaTeX_VanneReglante.xml_3.png=cf915fa47dd8857fde5c36b09c7db763
+_LaTeX_VanneReglante.xml_4.png=1afcdb0f704394b16fe85fb40c45ca7a
+_LaTeX_VanneReglante.xml_5.png=63bb9849783d01d91403bc9a5fea12a2
+_LaTeX_VariableResistor.xml_1.png=687d0cce878d1b8ec6bfc029064a6e5b
+_LaTeX_VoltageSensor.xml_1.png=8ffb1ef2419edc9b239447d79b7210de
+_LaTeX_VoltageSensor.xml_fr_FR_1.png=429b7d2eaa7c5fce1357c725d0ceba0a
 _LaTeX_acosh.xml_1.png=fedb433f0728f6668a0245ba07f4e13f
 _LaTeX_assert_computedigits.xml_1.png=82a70de2c216b6eb1951a75720fdcfc
 _LaTeX_assert_computedigits.xml_2.png=27dba5ee1401d31d2106736651e99140
diff --git a/scilab/modules/helptools/images/C_struct_img12_en_US.gif b/scilab/modules/helptools/images/C_struct_img12_en_US.gif
new file mode 100644 (file)
index 0000000..80676ab
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img12_en_US.gif differ
diff --git a/scilab/modules/helptools/images/C_struct_img1_en_US.gif b/scilab/modules/helptools/images/C_struct_img1_en_US.gif
new file mode 100644 (file)
index 0000000..afd5230
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img1_en_US.gif differ
diff --git a/scilab/modules/helptools/images/C_struct_img2_en_US.gif b/scilab/modules/helptools/images/C_struct_img2_en_US.gif
new file mode 100644 (file)
index 0000000..994a607
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img2_en_US.gif differ
diff --git a/scilab/modules/helptools/images/C_struct_img3_en_US.gif b/scilab/modules/helptools/images/C_struct_img3_en_US.gif
new file mode 100644 (file)
index 0000000..c3f2060
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img3_en_US.gif differ
diff --git a/scilab/modules/helptools/images/C_struct_img4_en_US.gif b/scilab/modules/helptools/images/C_struct_img4_en_US.gif
new file mode 100644 (file)
index 0000000..df4d2ff
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img4_en_US.gif differ
diff --git a/scilab/modules/helptools/images/C_struct_img9_en_US.gif b/scilab/modules/helptools/images/C_struct_img9_en_US.gif
new file mode 100644 (file)
index 0000000..e4dbc7d
Binary files /dev/null and b/scilab/modules/helptools/images/C_struct_img9_en_US.gif differ
index 846715e..11ed16f 100644 (file)
Binary files a/scilab/modules/helptools/images/DIFF_f_gui.gif and b/scilab/modules/helptools/images/DIFF_f_gui.gif differ
index 073e8f9..c79eb58 100644 (file)
Binary files a/scilab/modules/helptools/images/ENDBLK_gui.gif and b/scilab/modules/helptools/images/ENDBLK_gui.gif differ
index 073e8f9..e36a9f8 100644 (file)
Binary files a/scilab/modules/helptools/images/END_c_gui.gif and b/scilab/modules/helptools/images/END_c_gui.gif differ
index 8edb56e..a9e4ff3 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabCaution.png and b/scilab/modules/helptools/images/ScilabCaution.png differ
index e139988..188e1c1 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabEdit.png and b/scilab/modules/helptools/images/ScilabEdit.png differ
index b083271..a7de0fe 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabExecute.png and b/scilab/modules/helptools/images/ScilabExecute.png differ
index 3a80744..81e9ed2 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabImportant.png and b/scilab/modules/helptools/images/ScilabImportant.png differ
index ed46c3e..8851b99 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabNote.png and b/scilab/modules/helptools/images/ScilabNote.png differ
index ed46c3e..8851b99 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabTip.png and b/scilab/modules/helptools/images/ScilabTip.png differ
index 8edb56e..a9e4ff3 100644 (file)
Binary files a/scilab/modules/helptools/images/ScilabWarning.png and b/scilab/modules/helptools/images/ScilabWarning.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_1.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_1.png
new file mode 100644 (file)
index 0000000..bd06a07
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_10.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_10.png
new file mode 100644 (file)
index 0000000..8e476a8
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_10.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_11.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_11.png
new file mode 100644 (file)
index 0000000..4bd81cc
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_11.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_2.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_2.png
new file mode 100644 (file)
index 0000000..047012a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_3.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_3.png
new file mode 100644 (file)
index 0000000..479304c
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_4.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_4.png
new file mode 100644 (file)
index 0000000..047012a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_4.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_5.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_5.png
new file mode 100644 (file)
index 0000000..0d9c9c6
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_5.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_6.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_6.png
new file mode 100644 (file)
index 0000000..6f1cc88
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_6.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_7.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_7.png
new file mode 100644 (file)
index 0000000..fe08ce0
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_7.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_8.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_8.png
new file mode 100644 (file)
index 0000000..bd77975
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_8.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_9.png b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_9.png
new file mode 100644 (file)
index 0000000..047012a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_AUTOMAT.xml_9.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_1.png b/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_1.png
new file mode 100644 (file)
index 0000000..c55eab9
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_2.png b/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_2.png
new file mode 100644 (file)
index 0000000..c55eab9
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_CBLOCK.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_COSBLK_f.xml_1.png b/scilab/modules/helptools/images/_LaTeX_COSBLK_f.xml_1.png
new file mode 100644 (file)
index 0000000..d22d45a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_COSBLK_f.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_1.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_1.png
new file mode 100644 (file)
index 0000000..b243f14
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_2.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_2.png
new file mode 100644 (file)
index 0000000..8b9177d
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_3.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_3.png
new file mode 100644 (file)
index 0000000..decf71d
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_4.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_4.png
new file mode 100644 (file)
index 0000000..7373064
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_4.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_5.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_5.png
new file mode 100644 (file)
index 0000000..b41fa1c
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_5.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_C_struct.xml_6.png b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_6.png
new file mode 100644 (file)
index 0000000..6af498f
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_C_struct.xml_6.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_Capacitor.xml_1.png b/scilab/modules/helptools/images/_LaTeX_Capacitor.xml_1.png
new file mode 100644 (file)
index 0000000..fee620b
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_Capacitor.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_DERIV.xml_1.png b/scilab/modules/helptools/images/_LaTeX_DERIV.xml_1.png
new file mode 100644 (file)
index 0000000..1af29eb
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_DERIV.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_DLSS.xml_1.png b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_1.png
new file mode 100644 (file)
index 0000000..df29093
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_DLSS.xml_2.png b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_2.png
new file mode 100644 (file)
index 0000000..83a189a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_DLSS.xml_3.png b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_3.png
new file mode 100644 (file)
index 0000000..f61ce2a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_DLSS.xml_4.png b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_4.png
new file mode 100644 (file)
index 0000000..df7b267
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_DLSS.xml_4.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_Diode.xml_1.png b/scilab/modules/helptools/images/_LaTeX_Diode.xml_1.png
new file mode 100644 (file)
index 0000000..29b0a8a
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_Diode.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_END_c.xml_1.png b/scilab/modules/helptools/images/_LaTeX_END_c.xml_1.png
new file mode 100644 (file)
index 0000000..c7fc064
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_END_c.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_1.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_1.png
new file mode 100644 (file)
index 0000000..57a43de
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_2.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_2.png
new file mode 100644 (file)
index 0000000..e9f06ec
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_3.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_3.png
new file mode 100644 (file)
index 0000000..57a43de
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_4.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_4.png
new file mode 100644 (file)
index 0000000..853e2b8
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_4.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_5.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_5.png
new file mode 100644 (file)
index 0000000..7aae77f
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_5.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_6.png b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_6.png
new file mode 100644 (file)
index 0000000..bbc74f4
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_FROMWSB.xml_6.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_INTRP2BLK_f.xml_1.png b/scilab/modules/helptools/images/_LaTeX_INTRP2BLK_f.xml_1.png
new file mode 100644 (file)
index 0000000..6734c82
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_INTRP2BLK_f.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_Inductor.xml_1.png b/scilab/modules/helptools/images/_LaTeX_Inductor.xml_1.png
new file mode 100644 (file)
index 0000000..1cc62a7
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_Inductor.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_PerteDP.xml_1.png b/scilab/modules/helptools/images/_LaTeX_PerteDP.xml_1.png
new file mode 100644 (file)
index 0000000..a975b3d
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_PerteDP.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_READC_f.xml_1.png b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_1.png
new file mode 100644 (file)
index 0000000..56994de
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_READC_f.xml_2.png b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_2.png
new file mode 100644 (file)
index 0000000..3fcd58d
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_READC_f.xml_3.png b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_3.png
new file mode 100644 (file)
index 0000000..5943158
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_READC_f.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_Resistor.xml_1.png b/scilab/modules/helptools/images/_LaTeX_Resistor.xml_1.png
new file mode 100644 (file)
index 0000000..154b4fb
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_Resistor.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_SINBLK_f.xml_1.png b/scilab/modules/helptools/images/_LaTeX_SINBLK_f.xml_1.png
new file mode 100644 (file)
index 0000000..80d423b
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_SINBLK_f.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_TANBLK_f.xml_1.png b/scilab/modules/helptools/images/_LaTeX_TANBLK_f.xml_1.png
new file mode 100644 (file)
index 0000000..e39a5bb
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_TANBLK_f.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_1.png b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_1.png
new file mode 100644 (file)
index 0000000..5646ace
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_2.png b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_2.png
new file mode 100644 (file)
index 0000000..8acfe6d
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_2.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_3.png b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_3.png
new file mode 100644 (file)
index 0000000..41c9804
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_3.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_4.png b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_4.png
new file mode 100644 (file)
index 0000000..ef05f74
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_4.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_5.png b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_5.png
new file mode 100644 (file)
index 0000000..5c970d7
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VanneReglante.xml_5.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VariableResistor.xml_1.png b/scilab/modules/helptools/images/_LaTeX_VariableResistor.xml_1.png
new file mode 100644 (file)
index 0000000..f97f7d2
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VariableResistor.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_1.png b/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_1.png
new file mode 100644 (file)
index 0000000..295a723
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_1.png differ
diff --git a/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_fr_FR_1.png b/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_fr_FR_1.png
new file mode 100644 (file)
index 0000000..f4bedc0
Binary files /dev/null and b/scilab/modules/helptools/images/_LaTeX_VoltageSensor.xml_fr_FR_1.png differ
index a3da40f..4aa16e0 100644 (file)
Binary files a/scilab/modules/helptools/images/dae_1.png and b/scilab/modules/helptools/images/dae_1.png differ
diff --git a/scilab/modules/helptools/images/rfile_f_record_en_US.gif b/scilab/modules/helptools/images/rfile_f_record_en_US.gif
new file mode 100644 (file)
index 0000000..6af8d57
Binary files /dev/null and b/scilab/modules/helptools/images/rfile_f_record_en_US.gif differ
diff --git a/scilab/modules/helptools/images/rfile_f_record_fr_FR.gif b/scilab/modules/helptools/images/rfile_f_record_fr_FR.gif
new file mode 100644 (file)
index 0000000..0c6f3ec
Binary files /dev/null and b/scilab/modules/helptools/images/rfile_f_record_fr_FR.gif differ
diff --git a/scilab/modules/helptools/images/shift_arithmetic_left.gif b/scilab/modules/helptools/images/shift_arithmetic_left.gif
new file mode 100644 (file)
index 0000000..9241bca
Binary files /dev/null and b/scilab/modules/helptools/images/shift_arithmetic_left.gif differ
diff --git a/scilab/modules/helptools/images/shift_arithmetic_left_en_US.png b/scilab/modules/helptools/images/shift_arithmetic_left_en_US.png
deleted file mode 100644 (file)
index 493030b..0000000
Binary files a/scilab/modules/helptools/images/shift_arithmetic_left_en_US.png and /dev/null differ
diff --git a/scilab/modules/helptools/images/shift_arithmetic_right.gif b/scilab/modules/helptools/images/shift_arithmetic_right.gif
new file mode 100644 (file)
index 0000000..f7a9db1
Binary files /dev/null and b/scilab/modules/helptools/images/shift_arithmetic_right.gif differ
diff --git a/scilab/modules/helptools/images/shift_arithmetic_right_en_US.gif b/scilab/modules/helptools/images/shift_arithmetic_right_en_US.gif
new file mode 100644 (file)
index 0000000..71702f8
Binary files /dev/null and b/scilab/modules/helptools/images/shift_arithmetic_right_en_US.gif differ
diff --git a/scilab/modules/helptools/images/shift_arithmetic_right_en_US.png b/scilab/modules/helptools/images/shift_arithmetic_right_en_US.png
deleted file mode 100644 (file)
index 4b4cbcf..0000000
Binary files a/scilab/modules/helptools/images/shift_arithmetic_right_en_US.png and /dev/null differ
diff --git a/scilab/modules/helptools/images/shift_rotate_left.gif b/scilab/modules/helptools/images/shift_rotate_left.gif
new file mode 100644 (file)
index 0000000..57031a5
Binary files /dev/null and b/scilab/modules/helptools/images/shift_rotate_left.gif differ
diff --git a/scilab/modules/helptools/images/shift_rotate_left_en_US.png b/scilab/modules/helptools/images/shift_rotate_left_en_US.png
deleted file mode 100644 (file)
index 1604228..0000000
Binary files a/scilab/modules/helptools/images/shift_rotate_left_en_US.png and /dev/null differ
diff --git a/scilab/modules/helptools/images/shift_rotate_right.gif b/scilab/modules/helptools/images/shift_rotate_right.gif
new file mode 100644 (file)
index 0000000..681cb9d
Binary files /dev/null and b/scilab/modules/helptools/images/shift_rotate_right.gif differ
diff --git a/scilab/modules/helptools/images/shift_rotate_right_en_US.png b/scilab/modules/helptools/images/shift_rotate_right_en_US.png
deleted file mode 100644 (file)
index 5e06e30..0000000
Binary files a/scilab/modules/helptools/images/shift_rotate_right_en_US.png and /dev/null differ
diff --git a/scilab/modules/helptools/images/wfile_f_record_en_US.gif b/scilab/modules/helptools/images/wfile_f_record_en_US.gif
new file mode 100644 (file)
index 0000000..ef593f7
Binary files /dev/null and b/scilab/modules/helptools/images/wfile_f_record_en_US.gif differ
diff --git a/scilab/modules/helptools/images/wfile_f_record_fr_FR.gif b/scilab/modules/helptools/images/wfile_f_record_fr_FR.gif
new file mode 100644 (file)
index 0000000..b87b050
Binary files /dev/null and b/scilab/modules/helptools/images/wfile_f_record_fr_FR.gif differ
diff --git a/scilab/modules/helptools/images/writec_f_record_en_US.gif b/scilab/modules/helptools/images/writec_f_record_en_US.gif
new file mode 100644 (file)
index 0000000..6af8d57
Binary files /dev/null and b/scilab/modules/helptools/images/writec_f_record_en_US.gif differ
diff --git a/scilab/modules/helptools/images/writec_f_record_fr_FR.gif b/scilab/modules/helptools/images/writec_f_record_fr_FR.gif
new file mode 100644 (file)
index 0000000..0c6f3ec
Binary files /dev/null and b/scilab/modules/helptools/images/writec_f_record_fr_FR.gif differ
index e6a801a..e2dc2ce 100644 (file)
@@ -1456,6 +1456,7 @@ public class HTMLDocbookTagConverter extends DocbookTagConverter implements Temp
      */
     public String handleTr(final Map<String, String> attributes, final String contents) throws SAXException {
         String bgcolor = attributes.get("bgcolor");
+
         return encloseContents("tr", new String[] {"bgcolor", bgcolor}, contents);
     }
 
@@ -1469,7 +1470,10 @@ public class HTMLDocbookTagConverter extends DocbookTagConverter implements Temp
     public String handleTd(final Map<String, String> attributes, final String contents) throws SAXException {
         String align = attributes.get("align");
         String bgcolor = attributes.get("bgcolor");
-        return encloseContents("td", new String[] {"align", align, "bgcolor", bgcolor}, contents);
+        String colspan = attributes.get("colspan");
+        String rowspan = attributes.get("rowspan");
+
+        return encloseContents("td", new String[] {"align", align, "bgcolor", bgcolor, "colspan", colspan, "rowspan", rowspan}, contents);
     }
 
     /**
@@ -1535,6 +1539,17 @@ public class HTMLDocbookTagConverter extends DocbookTagConverter implements Temp
     }
 
     /**
+     * Handle an textobject (as an alternative to imageobject)
+     * @param attributes the tag attributes
+     * @param contents the tag contents
+     * @return the HTML code
+     * @throws SAXEception if an error is encountered
+     */
+    public String handleTextobject(final Map<String, String> attributes, final String contents) throws SAXException {
+        return "<!-- " + contents + " -->";
+    }
+
+    /**
      * Handle an inlinemediaobject
      * @param attributes the tag attributes
      * @param contents the tag contents
index 95b9862..75fc808 100644 (file)
         <para>The Derivative block approximates the instantaneous derivative of
             its input with respect to time t.
         </para>
-        <para>It is a measure of how an output changes as its input changes Δu. The
-            derivative is given by:
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../images/DERIV_img2_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
+        <latex>
+            $$
+            y(t) = {u(t) - u(t-h)} over h
+            $$
+        </latex>
         <para>The derivative block has no setting and the initial output for the
             block is zero.
         </para>
index 8d5ec68..8754915 100644 (file)
     <refsection id="Description_TCLSS">
         <title>Description</title>
         <para>
-            This block realizes a continuous-time linear state-space system with
-            the possibility of jumps in the state. The number of inputs to this
-            block is two. The first input is the regular input of the linear
-            system, the second carries the new value of the state which is copied
-            into the state when an event arrives at the unique event input port of
-            this block. That means the state of the system jumps to the value
-            present on the second input (of size equal to that of the state). The
-            system is defined by the  matrices and the initial state
-            . The dimensions must be compatible. The sizes of inputs and outputs
-            are adjusted automatically.
+            This block realizes a continuous-time linear state-space system with the possibility of jumps in the state. The number of inputs to this block is two. The first input is the regular input of the linear system, the second carries the new value of the state which is copied into the state when an event arrives at the unique event input port of this block. That means the state of the system jumps to the value present on the second input (of size equal to that of the state). The system is defined by the <literal>(A,B,C,D)</literal> matrices and the initial state <literal>x_0</literal>. The dimensions must be compatible. The sizes of inputs and outputs are adjusted automatically. 
         </para>
     </refsection>
     <refsection id="Dialogbox_TCLSS">
                     <emphasis role="bold">A matrix</emphasis>
                 </para>
                 <para>
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/TCLSS_img5_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    square matrix.
+                    <literal>A</literal> square matrix.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1]. </para>
             </listitem>
                     <emphasis role="bold">B matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/TCLSS_img6_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix, [] if system has no input.
+                    The <literal>B</literal> matrix, [] if system has no input.
                 </para>
                 <para> Properties : Type 'mat' of size ["size(%1,2)","-1"]. </para>
             </listitem>
                     <emphasis role="bold">C matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/TCLSS_img7_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix , [] if system has no output.
+                    The <literal>C</literal> matrix , [] if system has no output.
                 </para>
                 <para> Properties : Type 'mat' of size ["-1","size(%1,2)"]. </para>
             </listitem>
                     <emphasis role="bold">D matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/TCLSS_img8_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix, [] if system has no D term.
+                    The <literal>D</literal> matrix, [] if system has no D term.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1]. </para>
             </listitem>
index d5d6027..a4ac78e 100644 (file)
                             <xref linkend="Defaultproperties_AUTOMAT">Default properties</xref>
                         </para>
                     </listitem>
-                    <listitem>
-                        <para>
-                            <xref linkend="Interfacingfunction_AUTOMAT">Interfacing function</xref>
-                        </para>
-                    </listitem>
-                    <listitem>
-                        <para>
-                            <xref linkend="Computationalfunction_AUTOMAT">Computational function</xref>
-                        </para>
-                    </listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
@@ -95,8 +85,7 @@
         <para>
             This block gives the possibility to construct hybrid automata, i.e., a
             hybrid system whose discrete part is defined via modes and transitions
-            between modes, and the continuous part is defined via DAE
-            (differential algebraic equations). 
+            between modes, and the continuous part is defined via DAE (differential algebraic equations). 
         </para>
         <para>
             The automaton block provides a switching mechanism between subsystems
             subsystems are static functions.
         </para>
         <para>
-            Suppose that a hybrid automaton consists of 
-            <emphasis role="bold">
-                <inlinemediaobject>
-                    <imageobject>
-                        <imagedata fileref="../../../images/AUTOMAT_img2_eng.gif" align="center" valign="middle"/>
-                    </imageobject>
-                </inlinemediaobject>
-            </emphasis>
+            Suppose that a hybrid automaton consists of <literal>M</literal>
             control
             modes. The continuous-time dynamics in mode  is defined with DAE
-            (
-            ) where 
+            (<latex>$0 = F_i(\dot{x}, x, u)$</latex>
+            ) where <literal>i</literal> is in <literal>[1 .. M]</literal>
             and the dimension
-            of  is  () for any 
-            . Suppose that in
-            control mode , there are  jump conditions indicating jumps
-            toward other modes. The jump conditions are defined by
-            
-            functions where 
-            .
+            of <literal>x</literal> is <literal>N</literal> (<literal>N</literal> ≥ 0) for any <literal>i</literal> in <literal>[1 .. M]</literal>. Suppose that in
+            control mode <literal>i</literal>, there are <latex>$Z_i$</latex> jump conditions indicating jumps toward other modes. The jump conditions are defined by
+            functions <latex>$\mathrm{Jump}_{i,j}(\dot{x}, x, u)$</latex> where 
+            <literal>j</literal> is in <literal>[1 .. </literal><latex>$Z_i$</latex><literal>]</literal>.
         </para>
         <para>
             When a jump function changes sign and becomes positive, a mode
-            transition will happen. When  transition function becomes
-            positive, a transition to mode  happens and  state vector  is reset
-            to 
-            ,  
-            
-            for 
-            .
+            transition will happen. When <literal>k</literal>-th transition function becomes positive, a transition to mode <literal>k</literal> happens and state vector <literal>x</literal> is reset to : <latex>$\mathrm{Reset}_{k}(\dot{x}, x, u)$</latex> for i.e., <latex>$x_l = \mathrm{Reset}_{k,l}(\dot{x}, x, u) \mathrm{for} l \in \{1...N\} $</latex>.
         </para>
         <para>
             In order to develop an automaton containing a mode with multiple
         <para>
             The automaton block has the following input/output ports.
         </para>
-        <para>
-            
-        </para>
         <itemizedlist>
             <listitem>
                 <para>
-                    <emphasis role="bold">Output 1:</emphasis> The first output port is a vector of size two consisting of the current and the previous active control modes, i.e., 
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img17_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    . 
+                    <emphasis role="bold">Output 1:</emphasis> The first output port is a vector of size two consisting of the current and the previous active control modes, i.e., <latex>$\mathrm{out}_1 = [\mathrm{current mode}, \mathrm{previous mode}]^t$</latex>. 
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">Output 2:</emphasis> The second output port is a vector of size
-                    <emphasis role="bold">
-                        <inlinemediaobject>
-                            <imageobject>
-                                <imagedata fileref="../../../images/AUTOMAT_img18_eng.gif" align="center" valign="middle"/>
-                            </imageobject>
-                        </inlinemediaobject>
-                    </emphasis>
-                    providing the state vector and its first time derivative,  
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img19_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    . 
+                    <emphasis role="bold">Output 2:</emphasis> The second output port is a vector of size <literal>2N</literal> providing the state vector and its first time derivative, <latex>$[x,\dot{x}]^t$</latex>. 
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">Inputs:</emphasis> The automaton block has
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img2_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    vector input ports corresponding to
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img2_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    modes or subsystems of the automaton. Each input defines the dynamic behavior in the control each mode as well as the reset functions and the transition functions. The input port
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    which is the output of the
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img20_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    subsystem is a vector of size
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img21_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    . Each input is composed of the following vector.
-                    
-                    
-                    
-                    
+                    <emphasis role="bold">Inputs:</emphasis> The automaton block has <literal>M</literal> vector input ports corresponding to <literal>M</literal> modes or subsystems of the automaton. Each input defines the dynamic behavior in the control each mode as well as the reset functions and the transition functions. The input port <literal>i</literal> which is the output of the <literal>i</literal>-th subsystem is a vector of size <literal>2N+</literal><latex>$Z_i$</latex>. Each input is composed of the following vector.
                 </para>
+                <latex>$$
+                    \mathrm{Input}_i = [F_i(\dot{x}, x, u), \mathrm{Reset}_i(\dot{x}, x, u), \mathrm{Jump}_i(\dot{x}, x, u)] ^ t
+                    $$
+                </latex>
                 <itemizedlist>
                     <listitem>
                         <para>
-                            The first 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img7_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            elements of the 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img23_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            are the continuous-time
-                            dynamics.  The dynamics of the system in the control mode 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img3_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            is
-                            described by a smooth index-1 DAE ( 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img24_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            ).
+                            The first <literal>N</literal> elements of the <literal>Input_i</literal> are the continuous-time dynamics.  The dynamics of the system in the control mode <literal>i</literal> is described by a smooth index-1 DAE <latex>$0 = F_i(\dot{x}, x, u, t)$</latex>.
                             
                             
                         </para>
                     </listitem>
                     <listitem>
                         <para>
-                            The next 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img7_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            elements of 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img23_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            are the values used to
+                            The next <literal>N</literal> elements of <literal>Input_i</literal> are the values used to
                             reset the continuous-time state when a transition to 
-                            control mode 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img3_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
+                            control mode <literal>i</literal>
                             is activated.
-                            
-                            
                         </para>
                     </listitem>
                     <listitem>
                         <para>
-                            The next 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img9_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            elements of 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img23_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            are the jump or
-                            zero-crossing functions. If the 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img25_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
+                            The next <literal>Z_i</literal> elements of <literal>Input_i</literal> are the jump or
+                            zero-crossing functions. If the <literal>j</literal>-th
                             zero-crossing function of
-                            mode 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img3_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
+                            mode <literal>i</literal>
                             crosses zero with negative to positive direction, a
-                            transition to 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata fileref="../../../images/AUTOMAT_img25_eng.gif" align="center" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
+                            transition to <literal>j</literal>-th
                             destination mode happens.
                         </para>
                     </listitem>
             In the interface window, the number of control modes, the initial
             control mode and the initial value of continuous-time state at the
             beginning of the simulation should be given.
-            
-        </para>
-        <para>
-            Find more documentation and demos about the Automaton block oat
-            www.scicos.org. Interested users are referred to the paper "Modeling
-            Hybrid Automata in Scicos", Masoud Najafi, Ramine Nikoukhah, 2007 IEEE
-            Multi-conference on Systems and Control, Singapore. 
-            
         </para>
     </refsection>
     <refsection id="Dialogbox_AUTOMAT">
                     <emphasis role="bold">Xproperties of continuous-time states in each Mode</emphasis>
                 </para>
                 <para>
-                    In this field the state types in mode are given. A state in an index 1 DAE can be either differential state or algebraic state. vector is coded in an M*N matrix, where M is the number of modes and N is the number of states. This matrices indicates whether a continuous-time state is algebraic or differential in each control mode. If in the
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img20_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    mode,
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/AUTOMAT_img25_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    state is differential, the (i,j)-th element of the Xproperty matrix should set to "+1", otherwise it should set to "-1". Xproperty can be given as a 1*N vector if type of states remain the same in all modes.
+                    In this field the state types in mode are given. A state in an index 1 DAE can be either differential state or algebraic state. vector is coded in an M*N matrix, where M is the number of modes and N is the number of states. This matrices indicates whether a continuous-time state is algebraic or differential in each control mode. If in the <literal>i</literal>-th mode,<literal>j</literal>-th state is differential, the <literal>(i,j)</literal>-th element of the Xproperty matrix should set to "+1", otherwise it should set to "-1". Xproperty can be given as a 1*N vector if type of states remain the same in all modes.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1]. </para>
             </listitem>
             </listitem>
         </itemizedlist>
     </refsection>
+    
+    <refsection>
+        <title>References</title>
+        <simplelist type="vert">
+            <member>"Modeling Hybrid Automata in Scicos", Masoud Najafi, Ramine Nikoukhah, 2007 IEEE.
+                Multi-conference on Systems and Control, Singapore
+            </member>
+        </simplelist>
+    </refsection>
 </refentry>
index 23ebbb8..2af57e6 100644 (file)
@@ -97,7 +97,6 @@
             system is defined by the  matrices and the initial state
             . The dimensions must be compatible. At the arrival of an input
             event on the unique input event port, the state is updated.
-            
         </para>
     </refsection>
     <refsection id="Dialogbox_DLSS">
                     <emphasis role="bold">A matrix</emphasis>
                 </para>
                 <para>
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/DLSS_img5_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    square matrix.
+                    <latex>$A$</latex> square matrix.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1]. </para>
             </listitem>
                     <emphasis role="bold">B matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/DLSS_img6_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix, [] if system has no input.
+                    The <latex>$B$</latex> matrix, [] if system has no input.
                 </para>
                 <para> Properties : Type 'mat' of size ["size(%1,2)","-1"]. </para>
             </listitem>
                     <emphasis role="bold">C matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/DLSS_img7_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix , [] if system has no output.
+                    The <latex>$C$</latex> matrix, [] if system has no output.
                 </para>
                 <para> Properties : Type 'mat' of size ["-1","size(%1,2)"]. </para>
             </listitem>
                     <emphasis role="bold">D matrix</emphasis>
                 </para>
                 <para>
-                    The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/DLSS_img8_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix, [] if system has no D term.
+                    The <latex>$D$</latex> matrix, [] if system has no D term.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1]. </para>
             </listitem>
index a0de1b5..aad85f3 100644 (file)
             capacitor with capacitance  and the current  passing through it
             is given by the:
         </para>
-        <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/Capacitor_img5_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
+        <latex>$ I = C \mathrm{d}V \ over \mathrm{d}t $</latex>
         <para>
             Capacitors can also be used to differentiate between high-frequency
             and low-frequency signals and this makes them useful in electronic
index ff99808..e5f2e30 100644 (file)
         <title>Description</title>
         <para>
             This component consists of a simple diode parallel with an ohmic
-            resistance (
-            <emphasis role="bold">
-                <emphasis>R</emphasis>
-            </emphasis>
-            ).
-            The current (
-            <emphasis role="bold">
-                <emphasis>I</emphasis>
-            </emphasis>
-            )
-            passing through this component is defined as a function of the voltage across
-            the ports (
-            <emphasis role="bold">
-                <emphasis>V</emphasis>
-            </emphasis>
-            ):
-        </para>
-        <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/Diode_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            resistance (<literal>R</literal>).
+            The current (<literal>I</literal>)
+            passing through this component is defined as a function of the voltage across the ports (<literal>V</literal>):
         </para>
+        <latex><![CDATA[
+        $$
+        i = I_{ds} \times (\exp {v/V_t} - 1) + v \over R
+        $$
+        ]]></latex>
         <para>
             where 
-            <emphasis role="bold">
-                <emphasis>Ids</emphasis>
-            </emphasis>
+            <literal>Ids</literal>
             and
-            <emphasis role="bold">
-                <emphasis>Vt</emphasis>
-            </emphasis>
+            <literal>Vt</literal>
             are the saturation
-            current and the voltage equivalent of temperature, respectively. If the exponent
-            reaches a certain limit (<emphasis role="bold">Max exponent for linear continuation</emphasis>),
+            current and the voltage equivalent of temperature, respectively. If the exponent reaches a certain limit (<emphasis role="bold">Max exponent for linear continuation</emphasis>),
             the diode characteristic becomes linear to avoid overflow.
         </para>
     </refsection>
index 6042e8a..b4f7157 100644 (file)
             the ports of an inductor of inductance  and the current  passing
             through it is given by:
         </para>
-        <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/Inductor_img5_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
+        <latex><![CDATA[$$
+        v = L \times \frac{\mathrm d I}{\mathrm d t}
+        $$]]></latex>
         <para>
             Inductors can also be used to differentiate between high-frequency and
             low-frequency signals and this makes them useful in electronic
             filters. An inductor shows a high impedance for high frequency
             signals.
-            
         </para>
     </refsection>
     <refsection id="Dialogbox_Inductor">
index 79a62fb..909bf50 100644 (file)
         <title>Description</title>
         <para>
             A resistor is a two-port electrical component that resists an electric
-            current (
-            <emphasis role="bold">
-                <emphasis>I</emphasis>
-            </emphasis>
-            )
-            by producing a voltage drop (
-            <emphasis role="bold">
-                <emphasis>V
-                </emphasis>
-            </emphasis>
-            )between its terminals according to the Ohm's law.
+            current (<literal>I</literal>) by producing a voltage drop (<literal>V</literal>) between its terminals according to the Ohm's law.
         </para>
+        <latex>$$ R = I \over V $$</latex>
         <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/Resistor_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-        <para>
-            The electrical resistance (
-            <emphasis role="bold">
-                <emphasis>R
-                </emphasis>
-            </emphasis>
-            )is equal to the voltage drop across
-            (
-            <emphasis role="bold">
-                <emphasis>V</emphasis>
-            </emphasis>
-            )the resistor divided
-            by the current (
-            <emphasis role="bold">
-                <emphasis>I</emphasis>
-            </emphasis>
-            )
-            through the resistor.
+            The electrical resistance (<literal>R</literal>) is equal to the voltage drop across (<literal>V</literal>) the resistor divided by the current (<literal>I</literal>) through the resistor.
         </para>
     </refsection>
     <refsection id="Dialogbox_Resistor">
index 1e1668d..d5e88ab 100644 (file)
         <title>Description</title>
         <para>
             This component represents a variable ohmic resistor. The resistance
-            (
-            <emphasis role="bold">
-                <emphasis>Rx</emphasis>
-            </emphasis>
-            )is controlled
-            via an explicit input port.
-        </para>
-        <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/VariableResistor_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            (<literal>Rx</literal>) is controlled via an explicit input port.
         </para>
+        <latex>$$ R_x = V \over I $$</latex>
     </refsection>
     <refsection id="Defaultproperties_VariableResistor">
         <title>Default properties</title>
index 18ee85f..8964194 100644 (file)
         <para>
             This component is used to measure the voltage difference between two
             nodes in an electrical circuit. The output signal is the difference
-            between the voltages of the black port and the white port, ,
-        </para>
-        <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/VoltageSensor_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            between the voltages of the black port and the white port, ie. ,
         </para>
+        <latex>$$ V_{output} = V_{black} - V_{white} $$</latex>
         <para>
             The ohmic conductance of this block is zero.
-            
         </para>
     </refsection>
     <refsection id="Defaultproperties_VoltageSensor">
index a56e17d..d4777fc 100644 (file)
@@ -91,7 +91,7 @@
             The Bus Creator block combines a set of signals, i.e., a
             group of signals represented by a single line in a block diagram. It
             allows you to reduce the number of lines required to route signals
-            from one part of a diagram to another. This makes your easier to
+            from one part of a diagram to another. This makes your diagram easier to
             understand.  
             
         </para>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_ANDBLK">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/ANDBLK_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
 </refentry>
index de19ebd..2218cd8 100644 (file)
                     <emphasis role="bold">Number of event inputs</emphasis>
                 </para>
                 <para>
-                    an integer giving the number of event input ports colors : a vector of integers. The i-th element is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/CEVENTSCOPE_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/CEVENTSCOPE_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">xset</emphasis> for color (dash type) definitions.
+                    an integer giving the number of event input ports colors : a vector of integers. The i-th element is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">xset</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size 1 </para>
             </listitem>
                     <emphasis role="bold">Colors c </emphasis>
                 </para>
                 <para>
-                    an integer. It is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/CEVENTSCOPE_img5_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/CEVENTSCOPE_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
+                    an integer. It is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size -1 </para>
             </listitem>
index f131a96..523fb0a 100644 (file)
                             <xref linkend="Interfacingfunction_EDGE_TRIGGER">Interfacing function</xref>
                         </para>
                     </listitem>
-                    <listitem>
-                        <para>
-                            <link linkend="EDGE_TRIGGER">Compiled Super Block content</link>
-                        </para>
-                    </listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_EDGE_TRIGGER">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/EDGE_TRIGGER_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
 </refentry>
index ab6596c..4421fef 100644 (file)
                             <xref linkend="Interfacingfunction_Extract_Activation">Interfacing function</xref>
                         </para>
                     </listitem>
-                    <listitem>
-                        <para>
-                            <link linkend="Extract_Activation">Compiled Super Block content</link>
-                        </para>
-                    </listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_Extract_Activation">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/Extract_Activation_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
 </refentry>
index e08b542..4f01c8b 100644 (file)
                             <xref linkend="Interfacingfunction_MCLOCK_f">Interfacing function</xref>
                         </para>
                     </listitem>
-                    <listitem>
-                        <para>
-                            <link linkend="MCLOCK_f">Compiled Super Block content</link>
-                        </para>
-                    </listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_MCLOCK_f">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/MCLOCK_f_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
 </refentry>
index 19a4ef7..2ab180b 100644 (file)
                             <xref linkend="Interfacingfunction_freq_div">Interfacing function</xref>
                         </para>
                     </listitem>
-                    <listitem>
-                        <para>
-                            <link linkend="freq_div">Compiled Super Block content</link>
-                        </para>
-                    </listitem>
                 </itemizedlist>
             </listitem>
         </itemizedlist>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_freq_div">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/freq_div_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
     <refsection id="Examples_freq_div">
         <title>Examples</title>
         <para>
index 9e0b058..41f3b22 100644 (file)
         <para>
             <inlinemediaobject>
                 <imageobject>
-                    <imagedata align="center" fileref="../../../images/DIFF_f_gui.gif" valign="middle"/>
+                    <imagedata align="center" fileref="../../../../images/gui/DIFF_f_gui.gif" valign="middle"/>
                 </imageobject>
             </inlinemediaobject>
         </para>
index add1751..1a764f9 100644 (file)
         <title>Description</title>
         <para>
             This block shifts the bits of the input signal. In this operation the digits are moved to the
-            right or to the left.The user can choose the rule to shifts the bits that can be normal or cycle
-            by setting the <emphasis role="bold">Shift Type</emphasis> parameter to 0 or 1. The number and
+            right or to the left. The user can choose the rule to shifts the bits that can be normal or cycle
+            by setting the <emphasis role="bold">Shift Type</emphasis> parameter to <literal>0</literal> or <literal>1</literal>. The number and
             the direction of the shifts are set with the <emphasis role="bold">Number of Bits to Shift Left</emphasis>.
             If this number is positive the input is shifted to the left, otherwise it is shifted to the right.
         </para>
                     By example, the one bit shift right gives: 
                     <inlinemediaobject>
                         <imageobject>
-                            <imagedata fileref="../../../images/integer_pal/en_US/shift_arithmetic_right_en_US.png"/>
+                            <imagedata fileref="../../../images/palettes/integer_pal/shift_arithmetic_right.gif"/>
                         </imageobject>
+                        <textobject>
+                            <programlisting role="pic"><![CDATA[
+.PS
+First: box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+Last: box width 0.25 height 0.25 "1";
+
+move 0.5; arrow 0.5 dashed; move 0.5;
+
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+
+spline at First.w left 0.375 then up 0.5 then right 0.5 then down 0.375 ->;
+
+up;
+arrow at Last.n;
+.PE
+                ]]></programlisting>
+                        </textobject>
                     </inlinemediaobject>
-                    and the one bit shift left gives: 
+                    and the one bit shift left gives:
                     <inlinemediaobject>
                         <imageobject>
-                            <imagedata fileref="../../../images/integer_pal/en_US/shift_arithmetic_left_en_US.png"/>
+                            <imagedata fileref="../../../images/palettes/integer_pal/shift_arithmetic_left.gif"/>
                         </imageobject>
+                        <textobject>
+                            <programlisting role="pic"><![CDATA[
+.PS
+First: box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+Last: box width 0.25 height 0.25 "1";
+
+move 0.5; arrow 0.5 dashed; move 0.5;
+
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "0";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+
+up;
+arrow at First.n;
+move;
+down;
+arrow at Last.n+(0,0.5) "  0";
+.PE
+                ]]></programlisting>
+                        </textobject>
                     </inlinemediaobject>
                 </para>
-                <para/>
             </listitem>
             <listitem>
                 <para>
                     By example, the one bit rotation right gives: 
                     <inlinemediaobject>
                         <imageobject>
-                            <imagedata fileref="../../../images/integer_pal/en_US/shift_rotate_right_en_US.png" valign="middle"/>
+                            <imagedata fileref="../../../images/palettes/integer_pal/shift_rotate_right.gif"/>
                         </imageobject>
+                        <textobject>
+                            <programlisting role="pic"><![CDATA[
+.PS
+First: box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+Last: box width 0.25 height 0.25 "1";
+
+move 0.5; arrow 0.5 dashed; move 0.5;
+
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "1";
+
+spline at First.s down 0.25 then right then right 1.125 then right then up 0.375 then left 0.25 ->;
+
+.PE
+                ]]></programlisting>
+                        </textobject>
                     </inlinemediaobject>
                     and the one bit rotation left gives: 
                     <inlinemediaobject>
                         <imageobject>
-                            <imagedata fileref="../../../images/integer_pal/en_US/shift_rotate_left_en_US.png" valign="middle"/>
+                            <imagedata fileref="../../../images/palettes/integer_pal/shift_rotate_left.gif" valign="middle"/>
                         </imageobject>
+                        <textobject>
+                            <programlisting role="pic"><![CDATA[
+.PS
+First: box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+Last: box width 0.25 height 0.25 "1";
+
+move 0.5; arrow 0.5 dashed; move 0.5;
+
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+box height 0.25 "...";
+box width 0.25 height 0.25 "1";
+box width 0.25 height 0.25 "0";
+
+spline at Last.s down 0.25 then left then left 1.125 then left then up 0.375 then right 0.25 ->;
+
+.PE
+                ]]></programlisting>
+                        </textobject>
                     </inlinemediaobject>
                     .
                 </para>
index 96172e6..8428da6 100644 (file)
     <refsection id="Description_INTRP2BLK_f">
         <title>Description</title>
         <para>
-            The output of this block is a function of the inputs obtained by
-            bilinear interpolation. This block has two scalar inputs and a single
-            scalar output. The  and  give respectively the  coordinate
-            and the  coordinate of the -th data point to be interpolated and
-            
-            its value.   
-            
+            The output of this block is a function of the inputs obtained by bilinear interpolation. This block has two scalar inputs and a single scalar output. The <literal>X(i)</literal> and <literal>Y(i)</literal> give respectively the <literal>X</literal> coordinate and the <literal>Y</literal> coordinate of the <literal>i</literal>-th data point to be interpolated and <literal>Z(Y(i),X(i))</literal> its value.
         </para>
     </refsection>
     <refsection id="Dialogbox_INTRP2BLK_f">
                     <emphasis role="bold">Z values</emphasis>
                 </para>
                 <para>
-                    an 
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/INTRP2BLK_f_img9_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    matrix.
+                    an <latex>$m \times n$</latex> matrix.
                 </para>
                 <para> Properties : Type 'mat' of size [-1,-1] </para>
             </listitem>
index 779f237..bf35ba4 100644 (file)
         <title>Description</title>
         <para>That block computes the cosine of the elements of the input vector.</para>
         <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../images/COSBLK_f_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            <link linkend="cos">
+                <latex>$y = \cos(u)$</latex>
+            </link>
         </para>
     </refsection>
     <refsection id="Defaultproperties_COSBLK_f">
index 6a28ed9..79a04a8 100644 (file)
             That block computes the sine of the elements of the input vector.
         </para>
         <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/SINBLK_f_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            <link linkend="sin">
+                <latex>$y = \sin(u)$</latex>
+            </link>
         </para>
     </refsection>
     <refsection id="Defaultproperties_SINBLK_f">
index b7d1240..f19a2f1 100644 (file)
             That block computes the tangent of the elements of the input vector.
         </para>
         <para>
-        </para>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/TANBLK_f_img2_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
+            <link linkend="tan">
+                <latex>$y = \tan(u)$</latex>
+            </link>
         </para>
     </refsection>
     <refsection id="Defaultproperties_TANBLK_f">
index b93bbe4..75d42c8 100644 (file)
                     <emphasis role="bold">Number of output ports or vector of sizes</emphasis>
                 </para>
                 <para>
-                    positive integer less than or equal to
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/DEMUX_img5_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
+                    positive integer less than or equal to <literal>8</literal>
                     .
                 </para>
                 <para> Properties : Type 'vec' of size -1</para>
index dab661f..077662c 100644 (file)
             <listitem>
                 <para>
                     <emphasis role="bold">
-                        Pass first input if: u2
-                        <inlinemediaobject>
-                            <imageobject>
-                                <imagedata fileref="../../../../help/images/SWITCH2_m_img3_eng.gif" align="center" valign="middle"/>
-                            </imageobject>
-                        </inlinemediaobject>
-                        =a 
+                        Pass first input if: u2 ≥ a 
                     </emphasis>
                 </para>
                 <para> Select the conditions under which the first input is passed. You can make the block check whether the control input is greater than or equal to the threshold value, purely greater than the threshold value, or nonzero. If the control input meets the condition set in this parameter, then the first input is passed. Otherwise, the third input is passed.</para>
index f8b2c57..d616e2c 100644 (file)
                     <emphasis role="bold">color </emphasis>
                 </para>
                 <para>
-                    an integer. It is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CANIMXY_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or marker type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CANIMXY_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the input port signal. See<emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
+                    an integer. It is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the input port signal. See<emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size 1 </para>
             </listitem>
index da408aa..ce19e2e 100644 (file)
                     <emphasis role="bold">color </emphasis>
                 </para>
                 <para>
-                    an integer. It is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CANIMXY3D_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or marker type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CANIMXY3D_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the input port signal. See<emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
+                    an integer. It is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the input port signal. See<emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size -1 </para>
             </listitem>
index 93a93f1..0679839 100644 (file)
                     <emphasis role="bold">Color </emphasis>
                 </para>
                 <para>
-                    a vector of integers. The i-th element is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CFSCOPE_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CFSCOPE_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
+                    a vector of integers. The i-th element is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size 8 </para>
             </listitem>
index 72ca898..54b0384 100644 (file)
                 </para>
                 <para> The colormap is a range color linked to the window output of the scope. You can put a jetcolormap or hotcolormap or graycolormap or your own (see colormap help).</para>
                 <para>
-                    Properties : Must be a mx3 matrix and m
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CMAT3D_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    = 3 
+                    Properties : Must be a mx3 matrix and m ≥ 3 
                 </para>
             </listitem>
             <listitem>
index ecea168..7a76c5f 100644 (file)
                 </para>
                 <para> The colormap is a range color linked to the window output of the scope. You can put a jetcolormap or hotcolormap or graycolormap or your own (see colormap help).</para>
                 <para>
-                    Properties : Must be a mx3 matrix and m
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CMATVIEW_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    = 3 
+                    Properties : Must be a mx3 matrix and m ≥ 3 
                 </para>
             </listitem>
             <listitem>
index 06ff549..8f12308 100644 (file)
                     <emphasis role="bold">Drawing colors </emphasis>
                 </para>
                 <para>
-                    a vector of integers. The i-th element is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CMSCOPE_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CMSCOPE_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
+                    a vector of integers. The i-th element is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size -1 </para>
             </listitem>
index ec578d3..07d7164 100644 (file)
                     <emphasis role="bold">Color </emphasis>
                 </para>
                 <para>
-                    a vector of integers. The i-th element is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPE_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPE_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
+                    a vector of integers. The i-th element is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the i-th input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size 8 </para>
             </listitem>
index 9ca0d21..e8ff2de 100644 (file)
                     <emphasis role="bold">color </emphasis>
                 </para>
                 <para>
-                    an integer. It is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPXY_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or dash type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPXY_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
+                    an integer. It is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the input port signal. See<emphasis role="bold">plot2d</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size 1 </para>
             </listitem>
index 39b7b2b..ab05429 100644 (file)
                     <emphasis role="bold">color </emphasis>
                 </para>
                 <para>
-                    an integer. It is the color number (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPXY3D_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) or marker type (
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CSCOPXY3D_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ) used to draw the evolution of the input port signal. See<emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
+                    an integer. It is the color number (≥ 0) or marker type (&lt; 0) used to draw the evolution of the input port signal. See <emphasis role="bold">xset()</emphasis> for color (dash type) definitions.
                 </para>
                 <para> Properties : Type 'vec' of size -1 </para>
             </listitem>
index f43832b..9a57325 100644 (file)
                     </listitem>
                     <listitem>
                         <para>
-                            <link linkend="ENDBLK">Compiled Super Block
-                                content
-                            </link>
-                        </para>
-                    </listitem>
-                    <listitem>
-                        <para>
                             <xref linkend="Seealso_ENDBLK">See also</xref>
                         </para>
                     </listitem>
         <para>
             <inlinemediaobject>
                 <imageobject>
-                    <imagedata align="center" fileref="../../../images/ENDBLK_gui.gif" valign="middle"/>
+                    <imagedata align="center" fileref="../../../../images/gui/ENDBLK_gui.gif" valign="middle"/>
                 </imageobject>
             </inlinemediaobject>
         </para>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_ENDBLK">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../images/ENDBLK_img3_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
     <refsection id="Seealso_ENDBLK">
         <title>See also</title>
         <itemizedlist>
index 5b8b796..1dd2cdf 100644 (file)
         <para>That block increases the current time to the final integration time
             of the simulation when it is activated :
         </para>
-        <para/>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../images/END_c_img2_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-        <para/>
+        <latex>$$T_f = T_{cur}$$</latex>
         <para>
             with <emphasis role="bold">Tcur</emphasis> the activation date of
             the block and <emphasis role="bold">Tf</emphasis> the final integration
         <para>
             <inlinemediaobject>
                 <imageobject>
-                    <imagedata align="center" fileref="../../../images/END_c_gui.gif" valign="middle"/>
+                    <imagedata align="center" fileref="../../../../images/gui/END_c_gui.gif" valign="middle"/>
                 </imageobject>
             </inlinemediaobject>
         </para>
index ea6d1a4..87df31d 100644 (file)
     <refsection id="Description_WFILE_f">
         <title>Description</title>
         <para>
-            This block is <emphasis role="bold">obsolete</emphasis>. This block allows user to save data in a file with the name defined with the <emphasis role="bold">Output File Name</emphasis> parameter, in text formatted mode or in binary mode.
+            This block is <emphasis role="bold">obsolete</emphasis>, use <link linkend="WRITEC_f">WRITEC_f</link> instead.
+        </para>
+        <para>
+            This block allows user to save data in a file with the name defined with the <emphasis role="bold">Output File Name</emphasis> parameter, in text formatted mode or in binary mode.
         </para>
         <para>
             The file is a sequence of records. Each record has a length <emphasis role="bold">Output Size</emphasis> <literal> + 1 </literal> and the structure shown below:
         </para>
-        <para />
-        <mediaobject><imageobject>
-                <imagedata fileref="../../../images/sinks_pal/en_US/wfile_f_record_en_US.png" align="center" />
+        <mediaobject>
+            <imageobject>
+                <imagedata fileref="../../../images/palettes/sinks_pal/en_US/wfile_f_record_en_US.gif"/>
             </imageobject>
+            <textobject>
+                <programlisting role="pic"><![CDATA[
+.PS
+box "Date";
+box "Input 1";
+box "...";
+box "Input (N-1)";
+box "Input N";
+.PE
+                ]]></programlisting>
+            </textobject>
         </mediaobject>
         <para>
-            where the first field is the date of the event received on the activation input of the block during the simulation and other fields the regular input data. Each call to the
-            bloc writes a record in the file.
+            where the first field is the date of the event received on the activation input of the block during the simulation and other fields the regular input data. Each call to the bloc writes a record in the file.
         </para>
         <para>
             The <emphasis role="bold">Output Format</emphasis> parameter gives the record format.
index 33e03c7..ae6b0b7 100644 (file)
             The file is a sequence of records. Each record has the length fixed by the parameter <emphasis role="bold">Input Size</emphasis> and the structure shown
             below:
         </para>
-        <para />
-        <mediaobject><imageobject>
-                <imagedata fileref="../../../images/sinks_pal/en_US/writec_f_record_en_US.png" align="center" />
+        <mediaobject>
+            <imageobject>
+                <imagedata fileref="../../../images/palettes/sinks_pal/en_US/writec_f_record_en_US.gif"/>
             </imageobject>
+            <textobject>
+                <programlisting role="pic"><![CDATA[
+.PS
+box "Field #1";
+box "Field #2";
+box "...";
+box "Field #(N-1)";
+box "Field #N";
+.PE
+                ]]></programlisting>
+            </textobject>
         </mediaobject>
         <para>where the block inputs are numbered from top to bottom.</para>
         <para>
index cf54829..282711e 100644 (file)
                     <listitem>
                         <para>
                             <emphasis role="bold">0: "Zero order method"</emphasis>.
-                            This method generates a piecewise constant signal. i.e., for
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img3_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            ,
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img4_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            .This method is available for all data
-                            types.
+                            This method generates a piecewise constant signal. i.e., for <latex><![CDATA[$t_i \leq t < t_{i+1} $]]></latex>, <latex><![CDATA[$y(t) = y_i$]]></latex>. This method is available for all data types.
                         </para>
                     </listitem>
                     <listitem>
                         <para>
                             <emphasis role="bold">1: "Linear method"</emphasis>. This
-                            method generates a piecewise linear signal, i.e., for
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img5_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            ,
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img6_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            .For data types other than double and
-                            complex, the linear interpolation can be used, but the final
-                            output will be computed by casting interpolation result into the
-                            original data type.
+                            method generates a piecewise linear signal, i.e., for <latex><![CDATA[$t_i \leq t < t_{i+1} $]]></latex>, <latex><![CDATA[$y(t) = y_i + (t - t_i) \times {y_{i+1} - y_i} over {t_{i+1} - t_i}$]]></latex>. For data types other than double and complex, the linear interpolation can be used, but the final output will be computed by casting interpolation result into the original data type.
                         </para>
                     </listitem>
                     <listitem>
                         <para>
                             <emphasis role="bold">2:"NATURAL method"</emphasis>. This
                             cubic spline is computed by using the following conditions
-                            (considering 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img7_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            points 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img8_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            ): . This method is only available for Real
-                            and complex data types.
+                            (considering <literal>n</literal> points <literal>x_1, ..., x_n</literal>):
+                        </para>
+                        <latex>
+                            $$
+                            S^(2) (x_1) = 0
+                            \vdots
+                            S^(2) (x_n) = 0
+                            $$
+                        </latex>
+                        <para>This method is only available for Real and complex data types.
                         </para>
                     </listitem>
                     <listitem>
                         <para>
                             <emphasis role="bold">3:"NOT_A_KNOT method"</emphasis>. The
                             cubic spline is computed by using the following conditions
-                            (considering 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img7_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            points 
-                            <inlinemediaobject>
-                                <imageobject>
-                                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img8_eng.gif" valign="middle"/>
-                                </imageobject>
-                            </inlinemediaobject>
-                            ): . This method is only available for Real
-                            and complex data types.
+                            (considering <literal>n</literal> points <literal>x_1, ..., x_n</literal>) :
+                        </para>
+                        <latex>
+                            $$
+                            S^(3) (x_2^-) = S^(3) (x_2^+)
+                            \vdots
+                            S^(3) (x_{n-1}^-) = S^(3) (x_{n-1}^+)
+                            $$
+                        </latex>
+                        <para>This method is only available for Real and complex data types.
                         </para>
                     </listitem>
                 </itemizedlist>
                     output of the block affects data used by the numerical solver, at
                     discontinuous points, a discrete event is generated and the numerical
                     solver is cold restarted. The discrete event is also generated at
-                    the
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata align="center" fileref="../../../../help/images/FROMWSB_img13_eng.gif" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    and
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata align="center" fileref="../../../../help/images/FROMWSB_img14_eng.gif" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    for other interpolating methods.
+                    the <literal>t_1</literal> and <literal>t_n</literal> for other interpolating methods.
                 </para>
             </listitem>
             <listitem>
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_FROMWSB">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../../help/images/FROMWSB_img15_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
     <refsection id="Seealso_FROMWSB">
         <title>See also</title>
         <itemizedlist>
index 2d1727d..b5e64fd 100644 (file)
     <refsection id="Description_READC_f">
         <title>Description</title>
         <para>
-            This block allows user to read data in a C file. <emphasis role="bold">Output record
-                selection
-            </emphasis>
-            and <emphasis role="bold">Time record Selection</emphasis> allows the user to select data
-            among file records. Each call to the block advance one record in the
-            file.    
-            
+            This block allows user to read data in a C file. <emphasis role="bold">Output record selection</emphasis> and <emphasis role="bold">Time record Selection</emphasis> allows the user to select data among file records. Each call to the block advance one record in the file.        
         </para>
     </refsection>
     <refsection id="Dialogbox_READC_f">
                 <para>
                     <emphasis role="bold">Outputs record selection</emphasis>
                 </para>
-                <para> a vector of positive integer.</para>
+                <para>a vector of positive integer.</para>
                 <para>
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/READC_f_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    ,The
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/READC_f_img4_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    th element of the read record gives the value of
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/READC_f_img5_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    output.
+                    <latex>$\left k_1, \dot , k_n \right$</latex> : The <latex>$k_i$</latex>th element of the read record gives the value of <latex>$i^{th}$</latex> output.
                 </para>
                 <para> Properties : Type 'vec' of size -1 </para>
             </listitem>
index 25f214d..4816d49 100644 (file)
             </literal>
             and the structure shown below:
         </para>
-        <para/>
         <mediaobject>
             <imageobject>
-                <imagedata fileref="../../../images/sources_pal/en_US/rfile_f_record_en_US.png" align="center"/>
+                <imagedata fileref="../../../images/palettes/sources_pal/en_US/rfile_f_record_en_US.gif"/>
             </imageobject>
+            <textobject>
+                <programlisting role="pic"><![CDATA[
+.PS
+box "Field #1";
+box "Field #2";
+box "...";
+box "Field #(N-1)";
+box "Field #N";
+.PE
+                ]]></programlisting>
+            </textobject>
         </mediaobject>
         <para>
             The <emphasis role="bold">Time Record Selection</emphasis> parameter allows to user the selection of one field in the
index 3165ce5..35f6af8 100644 (file)
             </listitem>
         </itemizedlist>
     </refsection>
-    <refsection id="CompiledSuperBlockcontent_Sigbuilder">
-        <title>Compiled Super Block content</title>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata fileref="../../../../help/images/Sigbuilder_img3_eng.gif" align="center" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-    </refsection>
 </refentry>
index d0a14e4..32d2dd4 100644 (file)
             hydraulic resistance and pressure loss is directly proportional to the
             flow rate. Conventionally, the flow direction is the positive when fluid
             flows from the black port to the white port. The pressure loss is
-            obtained
+            obtained with :
         </para>
-        <para>with</para>
-        <para/>
-        <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../../help/images/PerteDP_img2_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-        <para>. The key parameters of this block are the pipes' length, the pipe's
+        <latex>
+            $$
+            P_{loss} = P_{black} - P_{white}
+            $$
+        </latex>
+        <para>The key parameters of this block are the pipes' length, the pipe's
             diameter, inlet and outlet altitudes, and some other thermal-hydraulic
             coefficients.
         </para>
index a2da5a9..8859143 100644 (file)
         <para>
             The <emphasis role="bold">VanneReglante</emphasis> block represents
             a variable orifice control valve. The flow rate through the valve is
-            proportional to the valve opening, ,
+            proportional to the valve opening.
         </para>
-        <para/>
+        <latex>
+            $$
+            \Delta P \times h \times |h| = k \times Q \times |Q|
+            $$
+        </latex>
         <para>
-            <inlinemediaobject>
-                <imageobject>
-                    <imagedata align="center" fileref="../../../../help/images/VanneReglante_img2_eng.gif" valign="middle"/>
-                </imageobject>
-            </inlinemediaobject>
-        </para>
-        <para>where is the valve opening, is the pressure difference, and is the
-            flow rate. This model is only used for the laminar flow regimes. is a
+            where <latex>$h$</latex> is the valve opening, <latex>$\Delta P$</latex> is the pressure difference, and <latex>$Q$</latex> is the
+            flow rate. This model is only used for the laminar flow regimes. <latex>$k$</latex> is a
             constant depending on the valve geometry and mass density of fluid.
         </para>
     </refsection>
index 251277a..3396ca4 100644 (file)
@@ -90,7 +90,6 @@
         <para>
             This block creates skeleton of the C-computing function. It also
             creates library file and object files.  
-            
         </para>
     </refsection>
     <refsection id="Dialogbox_CBLOCK">
                     <emphasis role="bold">initial firing vector </emphasis>
                 </para>
                 <para>
-                    A vector. Size of this vector corresponds to the number of event outputs. The value of the
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CBLOCK_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    entry specifies the time of the preprogrammed event firing on the
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../../help/images/CBLOCK_img3_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    output event port. If less than zero, no event is preprogrammed.
+                    A vector. Size of this vector corresponds to the number of event outputs. The value of the <latex>$i^{th}$</latex> entry specifies the time of the preprogrammed event firing on the <latex>$i^{th}$</latex> output event port. If less than zero, no event is preprogrammed.
                 </para>
                 <para> Properties : Type 'vec' of size 'sum(%6)' </para>
             </listitem>
index 636b866..4af4709 100644 (file)
     <refsection id="Description_C_struct">
         <title>Description</title>
         <para>
-            The C structure of a Scicos block defines all the fields to handle data provided by the simulator
-            such inputs/outputs, parameters, states, ...
+            The C structure of a Scicos block defines all the fields to handle data provided by the simulator such inputs/outputs, parameters, states, ...
         </para>
         <para>
-            That structure of type <literal>scicos_block</literal> is defined in the file scicos_block4.h, and user must include that header in each computational functions in the form :
+            That structure of type <literal>scicos_block</literal> is defined in the file <literal>scicos_block4.h</literal> included into the standard Scilab distribution, and users must include that header in each computational functions.
         </para>
         <para>
-            
-        </para>
-        <para>
-            The fields, that can be either C pointers or directly data, are then accessible via the <literal>*block</literal>
-            structure :
-        </para>
-        <para>
-            
-        </para>
-        <para>
-            This access is a  approach and most of users should prefer the  approach for facilities purpose.
-        </para>
-        <para>
-            In the current version of Scicos, the <literal>scicos-&gt;block</literal> structure is defined :
-        </para>
-        <para>
-            
-        </para>
-        <para>
-            
+            This access is a direct approach and most of users should prefer the <link linkend="C_macros">C macros</link> approach for facilities purpose. 
         </para>
     </refsection>
     <refsection id="Inputsoutputs_C_struct">
         <title>Inputs/outputs</title>
-        <para>
-            
-        </para>
         <itemizedlist>
             <listitem>
                 <para>
                     <emphasis role="bold">block-&gt;nin :</emphasis> Integer that gives the number of regular input ports of the block.
                 </para>
-                <para> One can't override the index when reading sizes of input ports in the array and the index when reading data in the array with a C computational function.</para>
-                <para> The number of regular input ports can also be got by the use of the C macros . </para>
+                <para>
+                    One can't override the index <literal>(3*block-&gt;nin)-1</literal> when reading sizes of input ports in the array <literal>insz</literal> and the index <literal>block-&gt;nin-1</literal> when reading data in the array <literal>inptr</literal> with a C computational function.
+                    The number of regular input ports can also be got by the use of the C macros <literal>GetNin(block)</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;insz :</emphasis> An array of integers of size that respectively gives the first dimensions, the second dimensions and the type of data driven by regular input ports.
+                    <emphasis role="bold">block-&gt;insz :</emphasis> An array of integers of size <literal>(3*block-&gt;nin)-1</literal> that respectively gives the first dimensions, the second dimensions and the type of data driven by regular input ports.
                 </para>
-                <para> Note that this array of size differs from the array and to provide full compatibility with blocks that only use a single dimension.</para>
-                <para> Suppose that you have a block with three inputs : the first is an int32 matrix of size 3,2, the second a single complex number (matrix of size 1,1) and the last a real matrix of size 4,1.</para>
                 <para>
-                    In the<link linkend="scicos_model">scicos_model</link> of such a block, the inputs will be defined :
+                     Note that this array of size differs from the array <literal>ozsz</literal> and <literal>oparsz</literal> to provide full compatibility with blocks that only use a single dimension.
                 </para>
-                <programlisting role="code"><![CDATA[                     model.in    = [3;1;4] 
-
-model.in2   = [2;1;1] 
-
-model.intyp = [2;1;3] 
-                    ]]></programlisting>
+                <para>Suppose that you have a block with three inputs : the first is an int32 matrix of size [3,2], the second a single complex number (matrix of size [1,1]) and the last a real matrix of size [4,1].</para>
                 <para>
-                    
-                    and the corresponding 
+                    In the<link linkend="scicos_model">scicos_model</link> of such a block, the inputs will be defined :
                 </para>
-                <programlisting role="code"><![CDATA[block->insz]]></programlisting>
-                <para> field at C computational function level will be
-                    coded as :
-                    
-                    
-                    
-                    
-                    Do the difference here in the type numbers defined at the <emphasis role="bold">Scilab level</emphasis> (2,1,3)
-                    and the type numbers defined at the <emphasis role="bold">C level</emphasis> (84,11,10). The following table gives
-                    the correspondance for all Scicos type:
-                    
+                <programlisting role="scilab">
+                    model = scicos_model();
+                    model.in = [3;1;4];
+                    model.in2 = [2;1;1];
+                    model.intyp = [2;1;3];
+                </programlisting>
+                <para>
+                    and the corresponding <literal>block-&gt;insz</literal> field at C computational function level will be coded as :
+                </para>
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img1_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+Dim1start: box "3"; Dim1center: box "1"; Dim1end: box "4";
+Dim2start: box "2"; Dim2center: box "1"; Dim2end: box "1";
+Typestart: box "84"; Typecenter: box "11"; Typeend: box "10";
+
+{"insz[0]" at Dim1start .n + (0, 0.2);}
+{"insz[nin]" at Dim2start .n + (0, 0.2);}
+{"insz[2*nin]" at Typestart .n + (0, 0.2);}
+
+boxwid=Dim1start.wid * 3;
+boxht=Dim1start.ht * 0.5;
+{box "First dimension" at Dim1center .s + (0, -0.5);}
+{box "Second dimension" at Dim2center .s + (0, -0.5);}
+{box "Type" at Typecenter .s + (0, -0.5);}
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                <para>
+                    Do the difference here in the type numbers defined at the <emphasis role="bold">Scilab level</emphasis> (2,1,3) and the type numbers defined at the <emphasis role="bold">C level</emphasis> (84,11,10). The following table gives the correspondance for all Scicos type:
                 </para>
                 <informaltable border="1" cellpadding="3">
                     <tr>
@@ -237,160 +232,133 @@ model.intyp = [2;1;3]
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;inptr :</emphasis> An array of pointers of size nin,1 that allow to directly acces to the data contained in the regular input matrices.
+                    <emphasis role="bold">block-&gt;inptr :</emphasis> An array of pointers of size nin,1 that allow to directly access to the data contained in the regular input matrices.
                 </para>
-                <para> Suppose the previous example (block with three inputs : an int32 matrix of size [3,2], a complex scalar and a real matrix of size [4,1]).</para>
-                <para>  contains three pointers, and should be viewed as arrays contained the data for the int32, the real and the complex matrices :
-                    
-                    
-                    
-                    For i.e., to directly access to the data, the user can use theses instructions :
-                    
+                <para>Suppose the previous example (block with three inputs : an int32 matrix of size [3,2], a complex scalar and a real matrix of size [4,1]).</para>
+                <para>
+                    <literal>block-&gt;inptr</literal> contains three pointers, and should be viewed as arrays contained the data for the int32, the real and the complex matrices :
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
-
-SCSINT32_COP *ptr_i;
-
-SCSCOMPLEX_COP *ptr_dc;
-
-SCSREAL_COP *ptr_d;
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img2_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+down;
+Inptr0ptr: box "long*";Inptr1ptr: box "double*";Inptr2ptr: box "double*";
 
-int n1,m1;
-
-SCSINT32_COP cumsum_i=0;
-
-int i;
-                     ...
+Inptr0: box at Inptr0ptr.e + (2.0, 3.0);box;box;box;box;box;
+move;
+Inptr1: box; box;
+move;
+Inptr2: box;box;box;box;
 
-void mycomputfunc(scicos_block *block,int flag) 
-                     {
-                     ...
-                     /*get the ptrs of the first int32 regular input port*/
+right;
+line at Inptr0ptr.e; arc; line; line; line; arc cw; arrow;
+line at Inptr1ptr.e; line; arrow;
+line at Inptr2ptr.e; arc cw; line; line; arc; arrow;
 
-ptr_i = (SCSINT32_COP *) block->inptr[0];
-                     /*get the ptrs of the second complex regular input port*/
+{"inptr" at Inptr0ptr.n + (0, 0.2);}
+{"inptr[0]" at Inptr0 .n + (0, 0.2);}
+{"inptr[1]" at Inptr1 .n + (0, 0.2);}
+{"inptr[2]" at Inptr2 .n + (0, 0.2);}
 
-ptr_dc = (SCSCOMPLEX_COP *) block->inptr[1];
-                     /*get the ptrs of the third real regular input port*/
+"inptr[0][0]" ljust at Inptr0.e + (0.1, 0);
+"inptr[0][1]" ljust at Inptr0.e + (0.1, -0.5);
+"inptr[0][2]" ljust at Inptr0.e + (0.1, -1.0);
+"inptr[0][3]" ljust at Inptr0.e + (0.1, -1.5);
+"inptr[0][4]" ljust at Inptr0.e + (0.1, -2.0);
+"inptr[0][5]" ljust at Inptr0.e + (0.1, -2.5);
 
-ptr_d = (SCSREAL_COP *) block->inptr[2];
-                     ...
-                     /*get the dimension of the first int32 regular input port*/
+"inptr[1][0] - Real part" ljust at Inptr1.e + (0.1, 0);
+"inptr[1][1] - Imaginary part" ljust at Inptr1.e + (0.1, -0.5);
 
-n1=block->insz[0];
+"inptr[2][0]" ljust at Inptr2.e + (0.1, 0);
+"inptr[2][1]" ljust at Inptr2.e + (0.1, -0.5);
+"inptr[2][2]" ljust at Inptr2.e + (0.1, -1.0);
+"inptr[2][3]" ljust at Inptr2.e + (0.1, -1.5);
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                <para>
+                    For i.e., to directly access to the data, the user can use theses instructions :   
+                </para>
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-m1=block->insz[3];
-                     ...
-                     /*compute the cumsum of the input int32 matrix*/
+...
 
-for(i=0;i<n1*m1;i++) {
+SCSINT32_COP *ptr_i;
+SCSCOMPLEX_COP *ptr_dc;
+SCSREAL_COP *ptr_d;
+int n1,m1;
+SCSINT32_COP cumsum_i=0;
+int i;
 
-cumsum_i += ptr_i[i];
-                     }
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    One can also use the set of C macros :
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetInPortPtrs(blk,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetRealInPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetImagInPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getint8InPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint16InPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getint32InPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint8InPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint16InPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint32InPortPtrs(block,x)]]></programlisting>
-                <para> 
-                </para>
-                <para>
-                    to have the appropriate pointer of the data to handle and 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetNin(block)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetInPortRows(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetInPortCols(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetInPortSize(block,x,y)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetInType(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetSizeOfIn(block,x)]]></programlisting>
-                <para> 
-                </para>
-                <para>
-                    to handle number, dimensions and type of regular input ports.
+void mycomputfunc(scicos_block *block,int flag)
+{
+    ...
+    
+    /*get the ptrs of the first int32 regular input port*/
+    ptr_i = (SCSINT32_COP *) block->inptr[0];
+    /*get the ptrs of the second complex regular input port*/
+    ptr_dc = (SCSCOMPLEX_COP *) block->inptr[1];
+    /*get the ptrs of the third real regular input port*/
+    ptr_d = (SCSREAL_COP *) block->inptr[2];
+    
+    ...
+    
+    /*get the dimension of the first int32 regular input port*/
+    n1=block->insz[0];
+    m1=block->insz[3];
+    
+    /*compute the cumsum of the input int32 matrix*/
+    for(i=0;i<n1*m1;i++) {
+        cumsum_i += ptr_i[i];
+    }
+    ...
+}]]></programlisting>
+                <para>
+                    One can also use the set of C macros : <literal>GetInPortPtrs(blk,x)</literal>, <literal>GetRealInPortPtrs(block,x)</literal>, <literal>GetImagInPortPtrs(block,x)</literal>, <literal>Getint8InPortPtrs(block,x)</literal>, <literal>Getint16InPortPtrs(block,x)</literal>, <literal>Getint32InPortPtrs(block,x)</literal>, <literal>Getuint8InPortPtrs(block,x)</literal>, <literal>Getuint16InPortPtrs(block,x)</literal>, <literal>Getuint32InPortPtrs(block,x)</literal> to have the appropriate pointer of the data to handle and <literal>GetNin(block)</literal>, <literal>GetInPortRows(block,x)</literal>, <literal>GetInPortCols(block,x)</literal>, <literal>GetInPortSize(block,x,y)</literal>, <literal>GetInType(block,x)</literal>, <literal>GetSizeOfIn(block,x)</literal> to handle number, dimensions and type of regular input ports.
                     (<emphasis role="bold">x is numbered from 1 to nin and y numbered  from 1 to 2</emphasis>).
                 </para>
                 <para> 
                     For the previous example that gives :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-SCSINT32_COP *ptr_i;
+...
 
+SCSINT32_COP *ptr_i;
 SCSCOMPLEX_COP *ptr_dc;
-
 SCSREAL_COP *ptr_d;
-
 int n1,m1;
-
 SCSINT32_COP cumsum_i=0;
-
 int i;
-                     ...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of the first int32 regular input port*/
-
-ptr_i = Getint32InPortPtrs(block,1);
-                     /*get the ptrs of the second complex regular input port*/
-
-ptr_dc = GetRealInPortPtrs(block,2);
-                     /*get the ptrs of the third real regular input port*/
-
-ptr_d = GetRealInPortPtrs(block,3);
-                     ...
-                     /*get the dimension of the first int32 regular input port*/
-
-n1=GetInPortRows(block,1);
-
-m1=GetInPortCols(block,1);
-                     ...
-                     }
-                    ]]></programlisting>
+{
+    ...
+    
+    /*get the ptrs of the first int32 regular input port*/
+    ptr_i = Getint32InPortPtrs(block,1);
+    /*get the ptrs of the second complex regular input port*/
+    ptr_dc = GetRealInPortPtrs(block,2);
+    /*get the ptrs of the third real regular input port*/
+    ptr_d = GetRealInPortPtrs(block,3);
+    
+    ...
+    
+    /*get the dimension of the first int32 regular input port*/
+    n1=GetInPortRows(block,1);
+    m1=GetInPortCols(block,1);
+    
+    ...
+}]]></programlisting>
                 <para>
-                    
                     Finally note that the regular input port registers are only accessible for reading.
                 </para>
             </listitem>
@@ -398,281 +366,253 @@ m1=GetInPortCols(block,1);
                 <para>
                     <emphasis role="bold">block-&gt;nout :</emphasis> Integer that gives the number of regular output ports of the block.
                 </para>
-                <para> One can't override the index when reading sizes of output ports in the array and the index when reading data in the array with a C computational function.</para>
-                <para> The number of regular output ports can also be got by the use of the C macros . </para>
+                <para>
+                    One can't override the index <literal>(3*block-&gt;nout)-1</literal> when reading sizes of output ports in the array <literal>outsz</literal> and the index <literal>block-&gt;nout-1</literal> when reading data in the array <literal>outptr</literal>with a C computational function.
+                </para>
+                <para>
+                     The number of regular output ports can also be got by the use of the C macros <literal>GetNout(block)</literal> . 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;outsz :</emphasis> An array of integers of size that respectively gives the first dimensions, the second dimensions and the type of data driven by regular output ports.
+                    <emphasis role="bold">block-&gt;outsz :</emphasis> An array of integers of size <literal>(3*block-&gt;nout)-1</literal> that respectively gives the first dimensions, the second dimensions and the type of data driven by regular output ports.
                 </para>
-                <para> Note that this array of size differs from the array and to provide full compatibility with blocks that only use a single dimension.</para>
-                <para> Suppose that you have a block with two outputs : the first is an int32 matrix of size 3,2, the second a single complex number (matrix of size 1,1) and the last a real matrix of size 4,1.</para>
+                <para>
+                    Note that this array of size differs from the array <literal>ozsz</literal> and <literal>oparsz</literal> to provide full compatibility with blocks that only use a single dimension.
+                </para>
+                <para>Suppose that you have a block with two outputs : the first is an int32 matrix of size [3,2], the second a single complex number (matrix of size 1,1) and the last a real matrix of size [4,1].</para>
                 <para>
                     In the<link linkend="scicos_model">scicos_model</link> of such a block, the outputs will be defined :
                 </para>
-                <programlisting role="code"><![CDATA[                      model.out   = [3;1;4] 
-
-model.out2   = [2;1;1] 
-
-model.outtyp = [2;1;3] 
+                <programlisting role="code"><![CDATA[
+model = scicos_model();
+model.out = [3;1;4];
+model.out2 = [2;1;1]; 
+model.outtyp = [2;1;3];
                      ]]></programlisting>
                 <para>
-                    
-                    and the corresponding 
-                </para>
-                <programlisting role="code"><![CDATA[block->outsz]]></programlisting>
-                <para> field at C computational function level will be
-                    coded as :
-                    
-                    
-                    
-                    
+                    and the corresponding <literal>block-&gt;outsz</literal> field at C computational function level will be coded as :
+                </para>
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img3_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+Dim1start: box "3"; Dim1center: box "1"; Dim1end: box "4";
+Dim2start: box "2"; Dim2center: box "1"; Dim2end: box "1";
+Typestart: box "84"; Typecenter: box "11"; Typeend: box "10";
+
+{"outsz[0]" at Dim1start .n + (0, 0.2);}
+{"outsz[nin]" at Dim2start .n + (0, 0.2);}
+{"outsz[2*nin]" at Typestart .n + (0, 0.2);}
+
+boxwid=Dim1start.wid * 3;
+boxht=Dim1start.ht * 0.5;
+{box "First dimension" at Dim1center .s + (0, -0.5);}
+{box "Second dimension" at Dim2center .s + (0, -0.5);}
+{box "Type" at Typecenter .s + (0, -0.5);}
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                <para>
                     Do the difference here in the type numbers defined at the <emphasis role="bold">Scilab level</emphasis> (2,1,3)
-                    and the type numbers defined at the <emphasis role="bold">C level</emphasis> (84,11,10) and please report to the 
-                    previous table to have the correspondence for all Scicos type.
+                    and the type numbers defined at the <emphasis role="bold">C level</emphasis> (84,11,10) and please report to the previous table to have the correspondence for all Scicos type.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;outptr :</emphasis> An array of pointers of size nout,1 that allow to directly acces to the data contained in the regular output matrices.
+                    <emphasis role="bold">block-&gt;outptr :</emphasis> An array of pointers of size [nout,1] that allow to directly acces to the data contained in the regular output matrices.
                 </para>
                 <para> Suppose the previous example (block with three outputs : an int32 matrix of size [3,2], a complex scalar and a real matrix of size [4,1]).</para>
-                <para>  contains three pointers, and should be viewed as arrays contained the data for the int32, the real and the complex matrices :
-                    
-                    
-                    
+                <para>
+                    <literal>block-&gt;outptr</literal> contains three pointers, and should be viewed as arrays contained the data for the int32, the real and the complex matrices :
+                </para>
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img4_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+down;
+Outptr0ptr: box "long*";Outptr1ptr: box "double*";Outptr2ptr: box "double*";
+
+Outptr0: box at Outptr0ptr.e + (2.0, 3.0);box;box;box;box;box;
+move;
+Outptr1: box; box;
+move;
+Outptr2: box;box;box;box;
+
+right;
+line at Outptr0ptr.e; arc; line; line; line; arc cw; arrow;
+line at Outptr1ptr.e; line; arrow;
+line at Outptr2ptr.e; arc cw; line; line; arc; arrow;
+
+{"outptr" at Outptr0ptr.n + (0, 0.2);}
+{"outptr[0]" at Outptr0 .n + (0, 0.2);}
+{"outptr[1]" at Outptr1 .n + (0, 0.2);}
+{"outptr[2]" at Outptr2 .n + (0, 0.2);}
+
+"outptr[0][0]" ljust at Outptr0.e + (0.1, 0);
+"outptr[0][1]" ljust at Outptr0.e + (0.1, -0.5);
+"outptr[0][2]" ljust at Outptr0.e + (0.1, -1.0);
+"outptr[0][3]" ljust at Outptr0.e + (0.1, -1.5);
+"outptr[0][4]" ljust at Outptr0.e + (0.1, -2.0);
+"outptr[0][5]" ljust at Outptr0.e + (0.1, -2.5);
+
+"outptr[1][0] - Real part" ljust at Outptr1.e + (0.1, 0);
+"outptr[1][1] - Imaginary part" ljust at Outptr1.e + (0.1, -0.5);
+
+"outptr[2][0]" ljust at Outptr2.e + (0.1, 0);
+"outptr[2][1]" ljust at Outptr2.e + (0.1, -0.5);
+"outptr[2][2]" ljust at Outptr2.e + (0.1, -1.0);
+"outptr[2][3]" ljust at Outptr2.e + (0.1, -1.5);
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                <para>
                     For i.e., to directly access to the data, the user can use theses instructions :
                     
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
 SCSINT32_COP *ptr_i;
-
 SCSCOMPLEX_COP *ptr_dc;
-
 SCSREAL_COP *ptr_d;
-
 int n1,m1;
-
 SCSINT32_COP cumsum_i=0;
-
 int i;
-                     ...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     /*get the ptrs of the first int32 regular output port*/
-
-ptr_i = (SCSINT32_COP *) block->outptr[0];
-                     /*get the ptrs of the second complex regular output port*/
-
-ptr_dc = (SCSCOMPLEX_COP *) block->outptr[1];
-                     /*get the ptrs of the third real regular output port*/
-
-ptr_d = (SCSREAL_COP *) block->outptr[2];
-                     ...
-                     /*get the dimension of the first int32 regular output port*/
-
-n1=block->outsz[0];
-
-m1=block->outsz[3];
-                     ...
-                     /*compute the cumsum of the output int32 matrix*/
-
-for(i=0;i<n1*m1;i++) {
-
-cumsum_i += ptr_i[i];
-                     }
-                     ...
-                     }
+{
+    /*get the ptrs of the first int32 regular output port*/
+    ptr_i = (SCSINT32_COP *) block->outptr[0];
+    /*get the ptrs of the second complex regular output port*/
+    ptr_dc = (SCSCOMPLEX_COP *) block->outptr[1];
+    /*get the ptrs of the third real regular output port*/
+    ptr_d = (SCSREAL_COP *) block->outptr[2];
+
+    /*get the dimension of the first int32 regular output port*/
+    n1=block->outsz[0];
+    m1=block->outsz[3];
+
+    /*compute the cumsum of the output int32 matrix*/
+    for(i=0;i<n1*m1;i++) {
+        cumsum_i += ptr_i[i];
+    }
+}
                     ]]></programlisting>
-                <para>
-                    
-                    One can also use the set of C macros :
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetOutPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetRealOutPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetImagOutPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getint8OutPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint16OutPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getint32OutPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint8OutPortPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint16OutPortPtrs(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint32OutPortPtrs(block,x)]]></programlisting>
-                <para> 
-                </para>
-                <para>
-                    to have the appropriate pointer of the data to handle and 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetNout(block)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetOutPortRows(block,x)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetOutPortCols(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetOutPortSize(block,x,y)]]></programlisting>
-                <para>, 
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetOutType(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[GetSizeOfOut(block,x)]]></programlisting>
-                <para> 
+                <para>One can also use the set of C macros : 
+                    <literal>GetOutPortPtrs(block,x)</literal>, <literal>GetRealOutPortPtrs(block,x)</literal>, <literal>GetImagOutPortPtrs(block,x)</literal>, <literal>Getint8OutPortPtrs(block,x)</literal>, <literal>Getint16OutPortPtrs(block,x)</literal>, <literal>Getint32OutPortPtrs(block,x)</literal>, <literal>Getuint8OutPortPtrs(block,x)</literal>, <literal>Getuint16OutPortPtrs(block,x)</literal>, <literal>Getuint32OutPortPtrs(block,x)</literal> to have the appropriate pointer of the data to handle and <literal>GetNout(block)</literal>, <literal>GetOutPortRows(block,x)</literal>, <literal>GetOutPortCols(block,x)</literal>, <literal>GetOutPortSize(block,x,y)</literal>, <literal>GetOutType(block,x)</literal>, <literal>GetSizeOfOut(block,x)</literal>to handle number, dimensions and type of regular output ports. (<emphasis role="bold">x is numbered from 1 to nout and y is numbered  from 1 to 2</emphasis>).
                 </para>
                 <para>
-                    to handle number, dimensions and type of regular output ports.
-                    (<emphasis role="bold">x is numbered from 1 to nout and y is numbered  from 1 to 2</emphasis>).
-                    
                     For the previous example that gives :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
 SCSINT32_COP *ptr_i;
-
 SCSCOMPLEX_COP *ptr_dc;
-
 SCSREAL_COP *ptr_d;
-
 int n1,m1;
-
 SCSINT32_COP cumsum_i=0;
-
 int i;
-                     ...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of the first int32 regular output port*/
-
-ptr_i = GetOutPortPtrs(block,1);
-                     /*get the ptrs of the second complex regular output port*/
-
-ptr_dc = GetRealOutPortPtrs(block,2);
-                     /*get the ptrs of the third real regular output port*/
-
-ptr_d = GetRealOutPortPtrs(block,3);
-                     ...
-                     /*get the dimension of the first int32 regular output port*/
-
-n1=GetOutPortRows(block,1);
-
-m1=GetOutPortCols(block,1);
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    Finally note that the regular output port registers must be only written for 
+{
+    ...
+    
+    /*get the ptrs of the first int32 regular output port*/
+    ptr_i = GetOutPortPtrs(block,1);
+    /*get the ptrs of the second complex regular output port*/
+    ptr_dc = GetRealOutPortPtrs(block,2);
+    /*get the ptrs of the third real regular output port*/
+    ptr_d = GetRealOutPortPtrs(block,3);
+    ...
+    
+    /*get the dimension of the first int32 regular output port*/
+    n1=GetOutPortRows(block,1);
+    m1=GetOutPortCols(block,1);
+    ...
+    
+}
+]]></programlisting>
+                <para>
+                    Finally note that the regular output port registers must be only written for <literal>flag=1</literal>.
                 </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=1. </para>
             </listitem>
         </itemizedlist>
-        <para>
-            
-        </para>
     </refsection>
     <refsection id="Events_C_struct">
         <title>Events</title>
-        <para>
-            
-        </para>
         <itemizedlist>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;nevprt :</emphasis> Integer that gives the event input port number by which the block has been activated. This number is a binary coding. For i.e, if block has two event inputs ports, can take the value 1 if the block has been called by its first event input port, the value 2 if it has been called by the second event input port and 3 if it is called by the same event on both input port 1 and 2.
+                    <emphasis role="bold">block-&gt;nevprt :</emphasis> Integer that gives the event input port number by which the block has been activated. This number is a binary coding. For i.e, if block has two event inputs ports, <literal> block-&gt;nevptr</literal>can take the value <literal>1</literal> if the block has been called by its first event input port, the value <literal>2</literal> if it has been called by the second event input port and <literal>3</literal> if it is called by the same event on both input port 1 and 2.
+                </para>
+                <para>
+                     Note that can be <literal>-1</literal> if the block is internally called.
+                </para>
+                <para>
+                     One can also retrieve this number by using the C macros <literal>GetNevIn(block)</literal>
                 </para>
-                <para> Note that can be -1 if the block is internally called.</para>
-                <para> One can also retrieve this number by using the C macros . </para>
             </listitem>
             <listitem>
                 <para>
                     <emphasis role="bold">block-&gt;nevout :</emphasis> Integer that gives the number of event output ports of the block (also called the length of the output event register).
                 </para>
-                <para> One can't override the index when setting value of events in the output event register .</para>
-                <para> The number of event output ports can also be got by the use of the C macro . </para>
+                <para>
+                     One can't override the index <literal>block-&gt;nevout-1</literal> when setting value of events in the output event register <literal>evout</literal>.
+                </para>
+                <para>
+                     The number of event output ports can also be got by the use of the C macro <literal>GetNevOut(block)</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;evout :</emphasis> Array of double of size nevout,1 corresponding to the output event register. That register is used to program date of events during the simulation.
+                    <emphasis role="bold">block-&gt;evout :</emphasis> Array of double of size [nevout,1] corresponding to the output event register. That register is used to program date of events during the simulation.
                 </para>
                 <para> When setting values in that array, you must understand that you give a delay relative to the current time of simulator :</para>
+                <latex>
+                    $$
+                    t_{event} = t_{current} + T_{delay}
+                    $$
+                </latex>
+                <para>
+                    where <latex>$t_{event}$</latex> is the date of the programmed event, <latex>$t_{cur}$</latex> is the current time in the simulator and <latex>$T_{delay}$</latex> the value that must be informed in the output event register.
+                </para>
                 <para>
-                    where 
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/C_struct_img6_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    is the date of the programmed event, 
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/C_struct_img7_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    is the current time in the simulator and 
-                    <inlinemediaobject>
-                        <imageobject>
-                            <imagedata fileref="../../../images/C_struct_img8_eng.gif" align="center" valign="middle"/>
-                        </imageobject>
-                    </inlinemediaobject>
-                    the value that must be informed in the output event register.
                     For i.e, suppose that you want generate an event with the first event output port, 1ms after
                     each calls of the block, then you'll use :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                      #include "scicos_block4.h"
-                      ...
-
-void mycomputfunc(scicos_block *block,int flag)
-                      {
-                      ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-if (flag==3) { 
+...
 
-block->evout[0]=0.001;
-                      }
-                      ...
-                     }
-                     ]]></programlisting>
-                <para>
-                </para>
+void mycomputfunc(scicos_block *block,int flag)
+{
+...
+    if (flag==3) {
+        block->evout[0]=0.001;
+    }
+...
+}
+
+]]></programlisting>
                 <para> 
-                    Note that every events generated from output event register will be asynchronous with event
-                    coming from event input port (even if you set 
-                </para>
-                <programlisting role="code"><![CDATA[block->evout[x]=0]]></programlisting>
-                <para>). 
+                    Note that every events generated from output event register will be asynchronous with event coming from event input port (even if you set 
+                    <literal>block-&gt;evout[x]=0</literal>). 
                 </para>
                 <para>
                     The event output register must be only written for 
+                    <literal>flag=3</literal>.
                 </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=3. </para>
             </listitem>
         </itemizedlist>
         <para>
@@ -689,100 +629,95 @@ block->evout[0]=0.001;
                 <para>
                     <emphasis role="bold">block-&gt;nrpar :</emphasis> Integer that gives the length of the real parameter register.
                 </para>
-                <para> One can't override the index when reading value of real parameters in the register .</para>
-                <para> The total number of real parameters can also be got by the use of the C macro . </para>
+                <para>
+                     One can't override the index <literal>(block-&gt;nrpar)-1</literal> when reading value of real parameters in the register <literal>rpar</literal>.
+                </para>
+                <para>
+                     The total number of real parameters can also be got by the use of the C macro <literal>rpar</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;rpar :</emphasis> Array of double of size nrpar,1 corresponding to the real parameter register. That register is used to pass real parameters coming from the scilab/scicos environment to your block model.
+                    <emphasis role="bold">block-&gt;rpar :</emphasis> Array of double of size [nrpar,1] corresponding to the real parameter register. That register is used to pass real parameters coming from the Scilab/Xcos environment to your block model.
                 </para>
                 <para> The C type of that array is (or C scicos type ).</para>
                 <para>
                     Suppose that you have defined the following real parameters in the<link linkend="scicos_model">scicos_model</link> of a block :
                 </para>
-                <programlisting role="code"><![CDATA[                     model.rpar   = [%pi;%pi/2;%pi/4]
+                <programlisting role="scilab"><![CDATA[
+model = scicos_model();
+model.rpar   = [%pi;%pi/2;%pi/4];
                     ]]></programlisting>
                 <para>
-                    
                     you can retrieve the previous data in the C computational function with :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-double PI;
+...
 
+double PI;
 double PI_2;
-
 double PI_4;
-                     ...
 
-void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the first value of the real param register*/
+...
 
-PI = block->rpar[0];
-                     /*get the second value of the real param register*/
-
-PI_2 = block->rpar[1];
-                     /*get the third value of the real param register*/
-
-PI_4 = block->rpar[2];
-                     ...
-                     }
+void mycomputfunc(scicos_block *block,int flag)
+{
+...
+    /*get the first value of the real param register*/
+    PI = block->rpar[0];
+    /*get the second value of the real param register*/
+    PI_2 = block->rpar[1];
+    /*get the third value of the real param register*/
+    PI_4 = block->rpar[2];
+...
+} 
                     ]]></programlisting>
                 <para>
                     
-                    You can also use the C macro 
-                </para>
-                <programlisting role="code"><![CDATA[GetRparPtrs(block)]]></programlisting>
-                <para> to get the pointer of the
+                    You can also use the C macro <literal>GetRparPtrs(block)</literal> to get the pointer of the
                     real parameter register. For i.e., if we define the following
                     <link linkend="scicos_model">scicos_model</link>
                     in an interfacing function of a
                     scicos block :
                     
                 </para>
-                <programlisting role="code"><![CDATA[                     A = [1.3 ; 4.5 ; 7.9 ; 9.8];
-
-B = [0.1 ; 0.98]; 
+                <programlisting role="code"><![CDATA[
+A = [1.3 ; 4.5 ; 7.9 ; 9.8];
+B = [0.1 ; 0.98];
+model = scicos_model();
 
 model.rpar   = [A;B] 
                     ]]></programlisting>
                 <para>
-                    
                     in the corresponding C computational function of that block, we'll use :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-double *rpar;
+...
 
-double *A; 
+double *rpar;
+double *A;
+double *B;
 
-double *B; 
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get ptrs of the real param register*/
-
-rpar = GetRparPtrs(block); 
-                     /*get the A ptrs array*/
-
-A = rpar;
-                     /*get the B ptrs array*/
-
-B = &rpar[4];
-                     /*or B = rpar + 4;*/
-                     ...
-                     }
-                    ]]></programlisting>
+{
+...
+    /*get ptrs of the real param register*/
+    rpar = GetRparPtrs(block);
+    /*get the A ptrs array*/
+    A = rpar;
+    /*get the B ptrs array*/
+    B = &rpar[4];
+    /*or B = rpar + 4;*/
+...
+}
+                ]]></programlisting>
                 <para>
-                    
                     Note that real parameters register is only accessible for reading.
                 </para>
             </listitem>
@@ -790,151 +725,123 @@ B = &rpar[4];
                 <para>
                     <emphasis role="bold">block-&gt;nipar :</emphasis> Integer that gives the length of the integer parameter register.
                 </para>
-                <para> One can't override the index when reading value of integer parameters in the register .</para>
-                <para> The total number of integer parameters can also be got by the use of the C macro . </para>
+                <para>
+                     One can't override the index <literal>(block-&gt;nipar)-1</literal> when reading value of integer parameters in the register <literal>ipar</literal>.
+                </para>
+                <para>
+                     The total number of integer parameters can also be got by the use of the C macro <literal>GetNipar(block)</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;ipar :</emphasis> Array of int of size nipar,1 corresponding to the integer parameter register. That register is used to pass integer parameters coming from the scilab/scicos environment to your block model.
+                    <emphasis role="bold">block-&gt;ipar :</emphasis> Array of int of size nipar,1 corresponding to the integer parameter register. That register is used to pass integer parameters coming from the Scilab/Xcos environment to your block model.
+                </para>
+                <para>
+                    The C type of that array is <literal>int*</literal> (or C scicos type <literal>SCSINT_COP *</literal>).
                 </para>
-                <para> The C type of that array is (or C scicos type ).</para>
                 <para>
                     Suppose that you have defined the following integer parameters in the<link linkend="scicos_model">scicos_model</link> of a block :
                 </para>
-                <programlisting role="code"><![CDATA[                     model.ipar   = [(1:3)';5] 
+                <programlisting role="scilab"><![CDATA[
+model = scicos_model();
+model.ipar = [(1:3)';5] 
                     ]]></programlisting>
                 <para>
-                    
                     you can retrieve the previous data in the C computational function with :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
-int one;
+...
 
+int one;
 int two;
-
 int three;
-
 int five;
-                     ...
-
-void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the first value of the integer param register*/
-
-one = block->ipar[0]; 
-                     /*get the second value of the integer param register*/
 
-two = block->ipar[1]; 
-                     /*get the third value of the integer param register*/
+...
 
-three = block->ipar[2]; 
-                     /*get the fourth value of the integer param register*/
-
-five = block->ipar[3]; 
-                     ...
-                     }
+void mycomputfunc(scicos_block *block,int flag)
+{
+...
+    /*get the first value of the integer param register*/
+    one = block->ipar[0];
+    /*get the second value of the integer param register*/
+    two = block->ipar[1];
+    /*get the third value of the integer param register*/
+    three = block->ipar[2];
+    /*get the fourth value of the integer param register*/
+    five = block->ipar[3];
+...
+}
                     ]]></programlisting>
                 <para>
-                    
-                    You can also use the C macro 
-                </para>
-                <programlisting role="code"><![CDATA[GetIparPtrs(block)]]></programlisting>
-                <para> to get the pointer of the
-                    real parameter register.
+                    You can also use the C macro <literal>GetIparPtrs(block)</literal> to get the pointer of the integer parameter register.
                 </para>
                 <para>
-                    Most of time in the scicos C block libraries, the integer register is used to
-                    parametrize the length of real parameters. For i.e. if you define the following
-                    <link linkend="scicos_model">scicos_model</link>
-                    in a block :
-                    
+                    Most of time in the scicos C block libraries, the integer register is used to parametrize the length of real parameters. For i.e. if you define the following <link linkend="scicos_model">scicos_model</link> in a block :
                 </para>
-                <programlisting role="code"><![CDATA[                     // set a random size for the first real parameters 
-
-A_sz = int(rand(10)*10); 
-                     // set a random size for the second real parameters 
-
-B_sz = int(rand(10)*10); 
-                     // set the first real parameters 
-
-A = rand(A_sz,1,``uniform''); 
-                     // set the second real parameters 
-
-B = rand(B_sz,1,``normal''); 
-                     // set ipar 
-
-model.ipar = [A_sz;B_sz] 
-                     // set rpar (length of A_sz+B_sz) 
+                <programlisting role="scilab"><![CDATA[
+// set a random size for the first real parameters
+A_sz = int(rand(10)*10);
+// set a random size for the second real parameters
+B_sz = int(rand(10)*10);
+// set the first real parameters
+A = rand(A_sz,1,``uniform'');
+// set the second real parameters
+B = rand(B_sz,1,``normal'');
 
-model.rpar = [A;B] 
-                    ]]></programlisting>
+model = scicos_model();
+// set ipar
+model.ipar = [A_sz;B_sz]
+// set rpar (length of A_sz+B_sz)
+model.rpar = [A;B]
+]]></programlisting>
                 <para>
-                    
-                    the array of real parameters (parametrized by ipar) can be retrieved in the
-                    correspondig C computational function with :
-                    
+                    the array of real parameters (parametrized by <literal>ipar</literal>) can be retrieved in the correspondig C computational function with :
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
-
-int A_sz; 
-
-int B_sz; 
-
-double *rpar; 
-
-double *A; 
-
-double *B; 
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
+int A_sz;
+int B_sz;
+double *rpar;
+double *A;
+double *B;
 double cumsum;
-
-int i; 
-                     ...
+int i; 
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get ptrs of the real param register*/
-
-rpar = GetRparPtrs(block); 
-                     /*get size of the first real param register*/
-
-A_sz = block->ipar[0]; 
-                     /*get size of the second real param register*/
-
-B_sz = block->ipar[1]; 
-                     /*get the A ptrs array*/
-
-A = rpar; 
-                     /*get the B ptrs array*/
-
-B = &rpar[A_sz]; 
-                     ...
-                     /*compute the cumsum of the first real parameter array*/
-
-cumsum = 0;
-
-for(i=0;i<A_sz;i++) {
-
-cumsum += A[i];
-                     }
-                     ...
-                     /*compute the cumsum of the second real parameter array*/
-
-cumsum = 0;
-
-for(i=0;i<B_sz;i++) {
-
-cumsum += B[i]; 
-                     }
-                    ]]></programlisting>
+{
+...
+    /*get ptrs of the real param register*/
+    rpar = GetRparPtrs(block);
+    /*get size of the first real param register*/
+    A_sz = block->ipar[0];
+    /*get size of the second real param register*/
+    B_sz = block->ipar[1];
+    /*get the A ptrs array*/
+    A = rpar;
+    /*get the B ptrs array*/
+    B = &rpar[A_sz];
+
+    /*compute the cumsum of the first real parameter array*/
+    cumsum = 0;
+    for(i=0;i<A_sz;i++) {
+        cumsum += A[i];
+    }
+
+    /*compute the cumsum of the second real parameter array*/
+    cumsum = 0;
+    for(i=0;i<B_sz;i++) {
+        cumsum += B[i];
+    }
+...
+}
+]]></programlisting>
                 <para>
-                    
                     Note that integer parameters register is only accessible for reading.
                 </para>
             </listitem>
@@ -942,228 +849,236 @@ cumsum += B[i];
                 <para>
                     <emphasis role="bold">block-&gt;nopar :</emphasis> Integer that gives the number of the object parameters.
                 </para>
-                <para> One can't override the index when accessing data in the arrays , and in a C computational function.</para>
-                <para> This value is also accessible via the C macro . </para>
+                <para>
+                     One can't override the index <literal>block-&gt;nopar-1</literal> when accessing data in the arrays <literal>oparsz</literal>, <literal>opartyp</literal>and <literal>oparptr</literal> in a C computational function.
+                </para>
+                <para>
+                     This value is also accessible via the C macro <literal>GetNopar(block)</literal>.
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;oparsz :</emphasis> An array of integer of size nopar,2 that contains the dimensions of matrices of object parameters.
+                    <emphasis role="bold">block-&gt;oparsz :</emphasis> An array of integer of size [nopar,2] that contains the dimensions of matrices of object parameters.
                 </para>
                 <para> The first column is for the first dimension and the second for the second dimension. For i.e. if we want the dimensions of the last object parameters, we'll use the instructions :
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
 int nopar;
-
 int n,m;
-                     ...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the number of object parameter*/
-
-nopar=block>nopar;
-                     ...
-                     /*get number of row of the last object parameter*/
-
-n=block>oparsz[nopar-1];
-                     /*get number of column of the last object parameter*/
-
-m=block>oparsz[2*nopar-1];
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    The dimensions of object parameters can be get with the following C macro :
-                    
-                </para>
-                <programlisting role="code"><![CDATA[                     GetOparSize(block,x,1); /*get first dimension of opar*/ 
-
-GetOparSize(block,x,2); /*get second dimension of opar*/ 
-                    ]]></programlisting>
-                <para>
-                    
-                    with 
-                </para>
-                <programlisting role="code"><![CDATA[x]]></programlisting>
-                <para>
-                    an integer that gives the index of the object parameter, <emphasis role="bold">numbered
-                        from 1 to nopar
-                    </emphasis>
-                    .
+{
+...
+    /*get the number of object parameter*/
+    nopar=block>nopar;
+    
+    ...
+    
+    /*get number of row of the last object parameter*/
+    n=block>oparsz[nopar-1];
+    /*get number of column of the last object parameter*/
+    m=block>oparsz[2*nopar-1];
+...
+} 
+]]></programlisting>
+                <para>
+                    The dimensions of object parameters can be get with the following C macros <literal>GetOparSize(block,x,1)</literal> to get the first dimension of <literal>opar</literal> and <literal>GetOparSize(block,x,2)</literal>to get the second dimension with <literal>x</literal> an integer that gives the index of the object parameter, <emphasis role="bold">numbered from 1 to nopar</emphasis>.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;opartyp :</emphasis> An array of integer of size nopar,1 that contains the type of matrices of object parameters.
+                    <emphasis role="bold">block-&gt;opartyp :</emphasis> An array of integer of size [nopar,1] that contains the type of matrices of object parameters.
                 </para>
-                <para> The following table gives the correspondence for scicos type expressed in Scilab number, in C number and also corresponding C pointers and C macros used for :
-                    
-                    The type of object parameter can also be got by the use of the C macro
+                <para>
+                     The following table gives the correspondence for Scicos/Xcos type expressed in Scilab number, in C number and also corresponding C pointers and C macros used for <literal>oparptr</literal>:
                 </para>
-                <programlisting role="code"><![CDATA[GetOparType(block,x)]]></programlisting>
-                <para>. For i.e, if we want the C number type of the first
-                    object parameter, we'll use the following C instructions:
-                    
+                <informaltable>
+                    <tr>
+                        <td colspan="2">Scilab</td><td colspan="3">C</td>
+                    </tr>
+                    <tr>
+                        <td>Type</td><td>Number</td><td>Number</td><td>Type</td><td>Macros</td>
+                    </tr>
+                    <tr>
+                        <td>Real</td><td>1</td><td>10</td><td>double</td><td>SCSREAL_OP</td>
+                    </tr>
+                    <tr>
+                        <td>complex</td><td>2</td><td>11</td><td>double</td><td>SCSCOMPLEX_COP</td>
+                    </tr>
+                    <tr>
+                        <td>int32</td><td>3</td><td>84</td><td>long</td><td>SCSINT32_OP</td>
+                    </tr>
+                    <tr>
+                        <td>int16</td><td>4</td><td>82</td><td>short</td><td>SCSINT16_OP</td>
+                    </tr>
+                    <tr>
+                        <td>int8</td><td>5</td><td>81</td><td>char</td><td>SCSINT8_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint32</td><td>6</td><td>814</td><td>unsigned long</td><td>SCSUINT32_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint16</td><td>7</td><td>812</td><td>unsigned short</td><td>SCSUINT16_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint8</td><td>8</td><td>811</td><td>unsigned char</td><td>SCSUINT8_OP</td>
+                    </tr>
+                    <tr>
+                        <td>all other data</td><td></td><td>-1</td><td>double</td><td>SCSUNKNOWN_COP</td>
+                    </tr>
+                </informaltable>
+                <para>
+                    The type of object parameter can also be got by the use of the C macro <literal>GetOparType(block,x)</literal>. For i.e, if we want the C number type of the first object parameter, we'll use the following C instructions:
                 </para>
-                <programlisting role="code"><![CDATA[                      #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
+
+...
 
 int opartyp_1;
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                      {
-                      ...
-                      /*get the number type of the first object parameter*/
-
-opartyp_1 = GetOparType(block,1);
-                      ...
-                     }
-                     ]]></programlisting>
+{
+...
+    /*get the number type of the first object parameter*/
+    opartyp_1 = GetOparType(block,1);
+...
+}
+]]></programlisting>
                 <para>
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;oparptr :</emphasis> An array of pointers of size nopar,1 that allow to directly acces to the data contained in the object parameter.
+                    <emphasis role="bold">block-&gt;oparptr :</emphasis> An array of pointers of size [nopar,1] that allow to a direct access to the data contained in the object parameter.
                 </para>
                 <para>
                     Suppose that you have defined in the editor a block with the following<emphasis role="bold">opar</emphasis> field in<link linkend="scicos_model">scicos_model</link> :
                 </para>
-                <programlisting role="code"><![CDATA[model.opar=list(int32([1,2;3,4]),[1+%i %i 0.5]);]]></programlisting>
-                <para>
-                    
-                    Then we have two object parameters, one is an 32-bit integer matrix with two rows and two
-                    columns and the second is a vector of complex numbers that can be understand as a matrix
-                    of size 1,3.
-                </para>
-                <para>
-                    At the C computational function level, the instructions 
-                </para>
-                <programlisting role="code"><![CDATA[block->oparsz[0]]]></programlisting>
-        <para>,
-                     </para>
-        <programlisting role="code"><![CDATA[block->oparsz[1]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->oparsz[2]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->oparsz[3]]]></programlisting>
-        <para> will respectively return the
-                     values 2,1,2,3 and the instructions </para>
-        <programlisting role="code"><![CDATA[block->opartyp[0]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->opartyp[1]]]></programlisting>
-        <para> the values 11 and
-                     84.
-</para>
-        <para>                     </para>
-        <programlisting role="code"><![CDATA[block->oparptr]]></programlisting>
-                <para> will contain then two pointers, and should be viewed as arrays contained data of
-                    object parameter as shown in the following figure :
-                    
-                    
-                    
-                    
-                    For i.e., to directly access to the data, the user can use theses instructions :
-                    
-                </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
-
+                <programlisting role="scilab"><![CDATA[
+model = scicos_model();
+model.opar=list( ..
+    int32([1,2;3,4]), ..
+    [1+%i %i 0.5], ..
+    int8([ascii("me") 0]) ..
+);]]></programlisting>
+                <para>
+                    Then we have three object parameters, one is an 32-bit integer matrix with two rows and two columns, the second is a vector of complex numbers that can be understand as a matrix of size [1,3] and the third is a string encoded as a standard C one (ASCII ended with a '\0').
+                </para>
+                <para>
+                    At the C computational function level, the instructions <literal>block-&gt;oparsz[0]</literal>, <literal>block-&gt;oparsz[1]</literal>, <literal>block-&gt;oparsz[2]</literal>, <literal>block-&gt;oparsz[3]</literal>, <literal>block-&gt;oparsz[4]</literal>, <literal>block-&gt;oparsz[5]</literal> will respectively return the values <literal>2, 1, 1, 2, 3, 3</literal> and the instructions <literal>block-&gt;opartyp[0]</literal>, <literal>block-&gt;opartyp[1]</literal>, <literal>block-&gt;opartyp[2]</literal> the values <literal>11, 84, 81</literal>.
+                </para>
+                <para>
+                    <literal>block-&gt;oparptr</literal> will contain then three pointers, and should be viewed as arrays contained data of object parameter as shown in the following figure :
+                </para>
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img9_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+down;
+Oparptr0ptr: box "long*";Oparptr1ptr: box "double*";Oparptr2ptr: box "char*";
+
+Oparptr0: box "1" at Oparptr0ptr.e + (2.0, 3.0);box "2";box "3";box "4";
+move;
+Oparptr1: box "1"; box "0"; box "0.5"; box "1";box "1"; box "0";
+move;
+Oparptr2: box "115 'm'"; box "116 'e'"; box "0 '\0'";
+
+right;
+line at Oparptr0ptr.e; arc; line; line; line; arc cw; arrow;
+line at Oparptr1ptr.e; line; arrow;
+line at Oparptr2ptr.e; arc cw; line; line; line; arc; arrow;
+
+{"oparptr" at Oparptr0ptr.n + (0, 0.2);}
+{"oparptr[0]" at Oparptr0 .n + (0, 0.2);}
+{"oparptr[1]" at Oparptr1 .n + (0, 0.2);}
+{"oparptr[2]" at Oparptr2 .n + (0, 0.2);}
+
+"oparptr[0][0]" ljust at Oparptr0.e + (0.1, 0);
+"oparptr[0][1]" ljust at Oparptr0.e + (0.1, -0.5);
+"oparptr[0][2]" ljust at Oparptr0.e + (0.1, -1.0);
+"oparptr[0][3]" ljust at Oparptr0.e + (0.1, -1.5);
+
+"oparptr[1][0] - Real part" ljust at Oparptr1.e + (0.1, 0);
+"oparptr[1][1] - Real part" ljust at Oparptr1.e + (0.1, -0.5);
+"oparptr[1][2] - Real part" ljust at Oparptr1.e + (0.1, -1.0);
+"oparptr[1][3] - Imaginary part" ljust at Oparptr1.e + (0.1, -1.5);
+"oparptr[1][4] - Imaginary part" ljust at Oparptr1.e + (0.1, -2.0);
+"oparptr[1][5] - Imaginary part" ljust at Oparptr1.e + (0.1, -2.5);
+
+"oparptr[2][0]" ljust at Oparptr2.e + (0.1, 0);
+"oparptr[2][1]" ljust at Oparptr2.e + (0.1, -0.5);
+"oparptr[2][2]" ljust at Oparptr2.e + (0.1, -1.0);
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                <para>For i.e., to directly access to the data, the user can use theses instructions :</para>
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
+
+...
 SCSINT32_COP *ptr_i;
-
 SCSINT32_COP cumsum_i;
-
 SCSCOMPLEX_COP *ptr_d;
-
+char* str;
 SCSREAL_COP cumsum_d;
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of an int32 object parameter*/
-
-ptr_i = (SCSINT32_COP *) block->oparptr[0];
-                     /*get the ptrs of a double object parameter*/
-
-ptr_d = (SCSCOMPLEX_COP *) block->oparptr[1];
-                     ...
-                     /*compute the cumsum of the int32 matrix*/
-
-cumsum_i = ptr_i[0]+ptr_i[1]+ptr_i[2]+ptr_i[3];
-                     ...
-                     /*compute the cumsum of the real part of the complex matrix*/
-
-cumsum_d = ptr_d[0]+ptr_d[1]+ptr_d[2];
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    One can also use the set of C macros :
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetRealOparPtrs(block,x)]]></programlisting>
-                <para>,  </para>
-                <programlisting role="code"><![CDATA[GetImagOparPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint8OparPtrs(block,x)]]></programlisting>
-                <para>,  </para>
-                <programlisting role="code"><![CDATA[Getint16OparPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint32OparPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint8OparPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint16OparPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint32OparPtrs(block,x)]]></programlisting>
-                <para>
-                </para>
-                <para>
-                    to have the appropriate pointer of the data to handle (<emphasis role="bold">x is numbered from 1 to nopar</emphasis>).
+{
+...
+    /*get the ptrs of an int32 object parameter*/
+    ptr_i = (SCSINT32_COP *) block->oparptr[0];
+    /*get the ptrs of a double object parameter*/
+    ptr_d = (SCSCOMPLEX_COP *) block->oparptr[1];
+    /*get the string*/
+    str = (char*) block->oparptr[2];
+    ...
+    /*compute the cumsum of the int32 matrix*/
+    cumsum_i = ptr_i[0]+ptr_i[1]+ptr_i[2]+ptr_i[3]; ...
+    /*compute the cumsum of the real part of the complex matrix*/
+    cumsum_d = ptr_d[0]+ptr_d[1]+ptr_d[2];
+    fprintf(stderr, str);
+...
+} 
+]]></programlisting>
+                <para>
+                    One can also use the set of C macros : <literal>GetRealOparPtrs(block,x)</literal>, <literal>GetImagOparPtrs(block,x)</literal>, <literal>Getint8OparPtrs(block,x)</literal>, <literal>Getint16OparPtrs(block,x)</literal>, <literal>Getint32OparPtrs(block,x)</literal>, <literal>Getuint8OparPtrs(block,x)</literal>, <literal>Getuint16OparPtrs(block,x)</literal>, <literal>Getuint32OparPtrs(block,x)</literal> to have the appropriate pointer of the data to handle (<emphasis role="bold">x is numbered from 1 to nopar</emphasis>).
                 </para>
                 <para>
                     For the previous example that gives :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
 SCSINT32_COP *ptr_i;
-
 SCSREAL_COP *ptr_dr;
-
 SCSREAL_COP *ptr_di;
-                     ...
+char* str;
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of an int32 object parameter*/
-
-ptr_i = Getint32OparPtrs(block,1);
-                     /*get the ptrs of a double object parameter*/
-
-ptr_dr = GetRealOparPtrs(block,2);
-
-ptr_di = GetImagOparPtrs(block,2);
-                     ...
-                     }
-                    ]]></programlisting>
+{
+...
+    /*get the ptrs of an int32 object parameter*/
+    ptr_i = Getint32OparPtrs(block,1);
+    /*get the ptrs of a double object parameter*/
+    ptr_dr = GetRealOparPtrs(block,2);
+    ptr_di = GetImagOparPtrs(block,2);
+    /*get the string*/
+    str = Getint8OparPtrs(block,3);
+...
+} 
+]]></programlisting>
                 <para>
-                    
                     Note that object parameters register is only accessible for reading. 
                 </para>
             </listitem>
@@ -1182,464 +1097,421 @@ ptr_di = GetImagOparPtrs(block,2);
                 <para>
                     <emphasis role="bold">block-&gt;nx :</emphasis> Integer that gives the length of the continus state register.
                 </para>
-                <para> One can't override the index when reading or writing data in the array , or with a C computational function. </para>
+                <para>
+                     One can't override the index <literal>block-&gt;nx-1</literal> when reading or writing data in the array , or with a C computational function. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;x :</emphasis> Array of double of size nx,1 corresponding to the continuous state register.
+                    <emphasis role="bold">block-&gt;x :</emphasis> Array of double of size [nx,1] corresponding to the continuous state register.
                 </para>
                 <para> That gives the result of the computation of the state derivative.</para>
                 <para> A value of a continuous state is readable (for i.e the first state) with the C instructions :
                 </para>
-                <programlisting role="code"><![CDATA[                  #include "scicos_block4.h"
-                  ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
 double x_1;
-                  ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                  {
-                  ...
-
-x_1=block->x[0];
-                  ...
-                  }
-                 ]]></programlisting>
+{
+...
+    x_1=block->x[0];
+...
+} 
+]]></programlisting>
                 <para>
-                    
-                    Note that on 
-                </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=4, user can write some initial conditions in that register.
+                    Note that on <literal>flag=4</literal>, user can write some initial conditions in that register.
                 </para>
                 <para>
-                    The pointer of that array can also be retrieve via the C macro 
-                </para>
-                <programlisting role="code"><![CDATA[GetState(block)]]></programlisting>
-                <para>.
+                    The pointer of that array can also be retrieve via the C macro <literal>GetState(block)</literal>.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;xd :</emphasis> Array of double of size nx,1 corresponding to the derivative of the continuous state register.
+                    <emphasis role="bold">block-&gt;xd :</emphasis> Array of double of size [nx,1] corresponding to the derivative of the continuous state register.
+                </para>
+                <para>
+                    When systems are explicitly given in terms of Ordinary Differential Equations (ODE), it can be explicitly expressed or implicitly used in the residual vector <literal>res</literal> when systems are expressed in terms of Differantial Algebraic Equations (DAE).
                 </para>
-                <para> When systems are explicitly given in terms of Ordinary Differential Equations (ODE), it can be explicitly expressed or implicitly used in the residual vector when systems are expressed in terms of Differantial Algebraic Equations (DAE).</para>
-                <para> Both systems must be programmed with .</para>
-                <para> For i.e the Lorenz attractor written as an ODE system with three state variables, of the form :
+                <para>
+                     Both systems must be programmed with <literal>flag=0</literal>.
+                </para>
+                <para>For i.e the Lorenz attractor written as an ODE system with three state variables, of the form :
                 </para>
+                <latex>
+                    $$
+                    \dot{x} = f(x,t)
+                    $$
+                </latex>
                 <para>
                     will be defined :
                 </para>
-                <programlisting role="code"><![CDATA[                   #include "scicos_block4.h"
-                   ...
-
-double *x = block->x;
-
-double *xd = block->xd;
-                   ...
-                   /* define parameters */
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
+/* define parameters */
 double a = 10;
-
 double b = 28;
-
 double c = 8/3;
-                   ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                   {
-                   ...
-
-if (flag == 0) {
-
-xd[0] = a*(x[1]-x[0]);
-
-xd[1] = x[1]*(b-x[2])-x[1];
-
-xd[2] = x[0]*x[1]-c*x[2];
-                   }
-                   ...
-                   }
-                  ]]></programlisting>
-                <para>
-                </para>
+{
+...
+    double *x = block->x;
+    double *xd = block->xd;
+
+    if (flag == 0) {
+        xd[0] = a*(x[1]-x[0]);
+        xd[1] = x[1]*(b-x[2])-x[1];
+        xd[2] = x[0]*x[1]-c*x[2];
+    }
+...
+} 
+]]></programlisting>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;res :</emphasis> Array of double of size nx,1 corresponding to Differential Algebraic Equation (DAE) residual.
+                    <emphasis role="bold">block-&gt;res :</emphasis> Array of double of size [nx,1] corresponding to Differential Algebraic Equation (DAE) residual.
                 </para>
                 <para> It is used to write the vector of systems that have the following form :</para>
+                <latex>
+                    $$
+                    f(x, \dot{x}, t) = 0
+                    $$
+                </latex>
                 <para>  For i.e the Lorenz attractor written as a DAE system with three state variables, will be defined :
                 </para>
-                <programlisting role="code"><![CDATA[                    #include "scicos_block4.h"
-                    ...
-
-double *x = block->x;
-
-double *xd = block->xd;
-
-double *res = block->res;
-                    ...
-                    /* define parameters */
+                <programlisting role="c"><![CDATA[ 
+#include "scicos_block4.h"
 
+...
+/* define parameters */
 double a = 10;
-
 double b = 28;
-
 double c = 8/3;
-                    ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                    {
-                    ...
-
-if (flag == 0) {
-
-res[0] =  - xd[0] + (a*(x[1]-x[0]));
-
-res[1] =  - xd[1] + (x[0]*(b-x[2])-x[1]);
-
-res[2] =  - xd[2] + (x[0]*x[1]-c*x[2]);
-                    }
-                    ...
-                    }
-                   ]]></programlisting>
-                <para>
-                </para>
+{
+...
+    double *x = block->x;
+    double *xd = block->xd;
+    double *res = block->res;
+    
+    if (flag == 0) {
+        res[0] = - xd[0] + (a*(x[1]-x[0]));
+        res[1] = - xd[1] + (x[0]*(b-x[2])-x[1]);
+        res[2] = - xd[2] + (x[0]*x[1]-c*x[2]);
+    }
+...
+}
+]]></programlisting>
             </listitem>
             <listitem>
                 <para>
                     <emphasis role="bold">block-&gt;nz :</emphasis> Integer that gives the length of the discrete state register.
                 </para>
-                <para> One can't override the index when reading data in the array with a C computational function.</para>
-                <para> This value is also accessible via the C macros . </para>
+                <para>
+                     One can't override the index <literal>block-&gt;nz-1</literal> when reading data in the array <literal>z</literal> with a C computational function.
+                </para>
+                <para>
+                     This value is also accessible via the C macros <literal>GetNdstate(block)</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;z :</emphasis> Array of double of size nz,1 corresponding to the discrete state register.
+                    <emphasis role="bold">block-&gt;z :</emphasis> Array of double of size [nz,1] corresponding to the discrete state register.
                 </para>
-                <para> A value of a discrete state is directly readable (for i.e the second state) with the C instructions :
+                <para>A value of a discrete state is directly readable (for i.e the second state) with the C instructions :
                 </para>
-                <programlisting role="code"><![CDATA[                  #include "scicos_block4.h"
-                  ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
 double z_2;
-                  ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                  {
-                  ...
-
-z_2=block->z[1];
-                  ...
-                  }
-                 ]]></programlisting>
+{
+...
+    z_2=block->z[1];
+...
+}
+]]></programlisting>
                 <para>
-                    
-                    Note that the state register should be only written for 
-                </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=4 and </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=2.
+                    Note that the state register should be only written for <literal>flag=4</literal> and <literal>flag=2</literal>
                 </para>
                 <para>
-                    The pointer of that array can also be retrieve via the C macro 
-                </para>
-                <programlisting role="code"><![CDATA[GetDstate(block)]]></programlisting>
-                <para>.
+                    The pointer of that array can also be retrieve via the C macro <literal>GetDstate(block)</literal>.
                 </para>
             </listitem>
             <listitem>
                 <para>
                     <emphasis role="bold">block-&gt;noz :</emphasis> Integer that gives the number of the discrete object states.
                 </para>
-                <para> One can't override the index when accessing data in the arrays , and in a C computational function.</para>
-                <para> This value is also accessible via the C macro . </para>
+                <para>
+                    One can't override the index <literal>block-&gt;noz-1</literal> when accessing data in the arrays <literal>ozsz</literal>, <literal>oztyp</literal> and <literal>ozptr</literal> in a C computational function.
+                </para>
+                <para>
+                    This value is also accessible via the C macro <literal>GetNoz(block)</literal>. 
+                </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;ozsz :</emphasis> An array of integer of size noz,2 that contains the dimensions of matrices of discrete object states.
+                    <emphasis role="bold">block-&gt;ozsz :</emphasis> An array of integer of size [noz,2] that contains the dimensions of matrices of discrete object states.
                 </para>
                 <para> The first column is for the first dimension and the second for the second dimension. For i.e. if we want the dimensions of the last object state, we'll use the instructions :
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
 int noz;
-
 int n,m;
-                     ...
-                     /*get the number of object state*/
-
-noz=block>noz;
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get number of row of the last object state*/
-
-n=block>ozsz[noz-1];
-                     /*get number of column of the last object state*/
-
-m=block>ozsz[2*noz-1];
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    The dimensions of object discrete states can be get with the following C macro :
-                    
-                </para>
-                <programlisting role="code"><![CDATA[                     GetOzSize(block,x,1); /*get first dimension of oz*/ 
-
-GetOzSize(block,x,2); /*get second dimension of oz*/ 
-                    ]]></programlisting>
-                <para>
-                    
-                    with 
-                </para>
-                <programlisting role="code"><![CDATA[x]]></programlisting>
-                <para>
-                    an integer that gives the index of the discrete object state, <emphasis role="bold">numbered
-                        from 1 to noz
-                    </emphasis>
-                    .
+{
+...
+    /*get the number of object state*/
+    noz=block>noz;
+    /*get number of row of the last object state*/
+    n=block>ozsz[noz-1];
+    /*get number of column of the last object state*/
+    m=block>ozsz[2*noz-1];
+...
+} 
+]]></programlisting>
+                <para>
+                    The dimensions of object discrete states can be get with the following C macro : <literal>GetOzSize(block,x,1)</literal> for the first dimension and <literal>GetOzSize(block,x,2)</literal> for the second dimension with <literal>x</literal> an integer that gives the index of the discrete object state, <emphasis role="bold">numbered from 1 to noz</emphasis>.
                 </para>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;oztyp :</emphasis> An array of integer of size noz,1 that contains the type of matrices of discrete object states.
+                    <emphasis role="bold">block-&gt;oztyp :</emphasis> An array of integer of size [noz,1] that contains the type of matrices of discrete object states.
                 </para>
-                <para> The following table gives the correspondence table for scicos type expressed in Scilab number, in C number and also corresponding C pointers and C macros used for :
-                    
-                    The type of discrete object state can also be got by the use of the C macro
+                <para>
+                     The following table gives the correspondence table for scicos type expressed in Scilab number, in C number and also corresponding C pointers and C macros used for <literal>ozptr</literal>:
                 </para>
-                <programlisting role="code"><![CDATA[GetOzType(block,x)]]></programlisting>
-                <para>. For i.e, if we want the C number type of the first
-                    discrete object state, we'll use the following C instructions:
-                    
+                <informaltable>
+                    <tr>
+                        <td colspan="2">Scilab</td><td colspan="3">C</td>
+                    </tr>
+                    <tr>
+                        <td>Type</td><td>Number</td><td>Number</td><td>Type</td><td>Macros</td>
+                    </tr>
+                    <tr>
+                        <td>Real</td><td>1</td><td>10</td><td>double</td><td>SCSREAL_OP</td>
+                    </tr>
+                    <tr>
+                        <td>complex</td><td>2</td><td>11</td><td>double</td><td>SCSCOMPLEX_COP</td>
+                    </tr>
+                    <tr>
+                        <td>int32</td><td>3</td><td>84</td><td>long</td><td>SCSINT32_OP</td>
+                    </tr>
+                    <tr>
+                        <td>int16</td><td>4</td><td>82</td><td>short</td><td>SCSINT16_OP</td>
+                    </tr>
+                    <tr>
+                        <td>int8</td><td>5</td><td>81</td><td>char</td><td>SCSINT8_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint32</td><td>6</td><td>814</td><td>unsigned long</td><td>SCSUINT32_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint16</td><td>7</td><td>812</td><td>unsigned short</td><td>SCSUINT16_OP</td>
+                    </tr>
+                    <tr>
+                        <td>uint8</td><td>8</td><td>811</td><td>unsigned char</td><td>SCSUINT8_OP</td>
+                    </tr>
+                    <tr>
+                        <td>all other data</td><td></td><td>-1</td><td>double</td><td>SCSUNKNOWN_COP</td>
+                    </tr>
+                </informaltable>
+                <para>
+                    The type of discrete object state can also be got by the use of the C macro <literal>GetOzType(block,x)</literal>. For i.e, if we want the C number type of the first discrete object state, we'll use the following C instructions:
                 </para>
-                <programlisting role="code"><![CDATA[                      #include "scicos_block4.h"
-                      ...
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
 
+...
 int oztyp_1;
-                      ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                      {
-                      ...
-                      /*get the number type of the first object state*/
-
-oztyp_1 = GetOzType(block,1);
-                     ...
-                     }
-                     ]]></programlisting>
-                <para>
-                </para>
+{
+...
+    /*get the number type of the first object state*/
+    oztyp_1 = GetOzType(block,1);
+...
+}
+]]></programlisting>
             </listitem>
             <listitem>
                 <para>
-                    <emphasis role="bold">block-&gt;ozptr :</emphasis> An array of pointers of size noz,1 that allow to directly acces to the data contained in the discrete object state.
+                    <emphasis role="bold">block-&gt;ozptr :</emphasis> An array of pointers of size [noz,1] that allow to a direct access to the data contained in the discrete object state.
                 </para>
                 <para>
                     Suppose that you have defined in the editor a block with the following<emphasis role="bold">odstate</emphasis> field in <link linkend="scicos_model">scicos_model</link> :
                 </para>
-                <programlisting role="code"><![CDATA[model.odstate=list(int32([1,2;3,4]),[1+%i %i 0.5]);]]></programlisting>
-                <para>
-                    
-                    Then we have two discrete object states, one is an 32-bit integer matrix with two rows and two
-                    columns and the second is a vector of complex numbers that can be understand as a matrix
-                    of size 1,3.
-                </para>
-                <para>
-                    At the C computational function level, the instructions 
-                </para>
-                <programlisting role="code"><![CDATA[block->ozsz[0]]]></programlisting>
-        <para>,
-                     </para>
-        <programlisting role="code"><![CDATA[block->ozsz[1]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->ozsz[2]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->ozsz[3]]]></programlisting>
-        <para> will respectively return the
-                     values 2,1,2,3 and the instructions </para>
-        <programlisting role="code"><![CDATA[block->oztyp[0]]]></programlisting>
-        <para>, </para>
-        <programlisting role="code"><![CDATA[block->oztyp[1]]]></programlisting>
-        <para> the values 11 and
-                     84.
-</para>
-        <para>                     </para>
-        <programlisting role="code"><![CDATA[block->ozptr]]></programlisting>
-                <para> will contain then two pointers, and should be viewed as arrays contained data of
-                    discrete object state as shown in the following figure :
-                    
-                    
-                    
-                    
-                    For i.e., to directly access to the data, the user can use theses instructions :
-                    
-                </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
-
+                <programlisting role="code"><![CDATA[
+model = scicos_model();
+model.odstate=list(int32([1,2;3,4]),[1+%i %i 0.5]);
+]]></programlisting>
+                <para>
+                    Then we have two discrete object states, one is an 32-bit integer matrix with two rows and two columns and the second is a vector of complex numbers that can be understand as a matrix of size [1,3].
+                </para>
+                <para>
+                    At the C computational function level, the instructions <literal>block-&gt;ozsz[0]</literal>, <literal>block-&gt;ozsz[1]</literal>, <literal>block-&gt;ozsz[2]</literal> and <literal>block-&gt;ozsz[3]</literal> will respectively return the values <literal>2,1,2,3</literal> and the instructions <literal>block-&gt;oztyp[0]</literal>, <literal>block-&gt;oztyp[1]</literal> the values <literal>11</literal> and <literal>84</literal>.
+                </para>
+                <para>
+                     <literal>block-&gt;ozptr</literal> will then contain two pointers, and should be viewed as arrays contained data of discrete object state as shown in the following figure :
+                </para>
+                <mediaobject>
+                    <imageobject>
+                        <imagedata fileref="../../../images/programming_scicos_blocks/c_computational_functions/en_US/C_struct_img12_en_US.gif"/>
+                    </imageobject>
+                    <textobject>
+                        <programlisting role="pic"><![CDATA[
+.PS
+down;
+Ozptr0ptr: box "long*";Ozptr1ptr: box "double*";
+
+Ozptr0: box "1" at Ozptr0ptr.e + (2.0, 3.0);box "2";box "3";box "4";
+move;
+Ozptr1: box "1"; box "0"; box "0.5"; box "1";box "1"; box "0";
+
+right;
+line at Ozptr0ptr.e; arc; line; line; line; arc cw; arrow;
+line at Ozptr1ptr.e; line; arrow;
+
+{"ozptr" at Ozptr0ptr.n + (0, 0.2);}
+{"ozptr[0]" at Ozptr0 .n + (0, 0.2);}
+{"ozptr[1]" at Ozptr1 .n + (0, 0.2);}
+
+"ozptr[0][0]" ljust at Ozptr0.e + (0.1, 0);
+"ozptr[0][1]" ljust at Ozptr0.e + (0.1, -0.5);
+"ozptr[0][2]" ljust at Ozptr0.e + (0.1, -1.0);
+"ozptr[0][3]" ljust at Ozptr0.e + (0.1, -1.5);
+
+"ozptr[1][0] - Real part" ljust at Ozptr1.e + (0.1, 0);
+"ozptr[1][1] - Real part" ljust at Ozptr1.e + (0.1, -0.5);
+"ozptr[1][2] - Real part" ljust at Ozptr1.e + (0.1, -1.0);
+"ozptr[1][3] - Imaginary part" ljust at Ozptr1.e + (0.1, -1.5);
+"ozptr[1][4] - Imaginary part" ljust at Ozptr1.e + (0.1, -2.0);
+"ozptr[1][5] - Imaginary part" ljust at Ozptr1.e + (0.1, -2.5);
+.PE
+                        ]]></programlisting>
+                    </textobject>
+                </mediaobject>
+                
+                <para>For i.e., to directly access to the data, the user can use theses instructions : </para>
+                <programlisting role="c"><![CDATA[
+#include "scicos_block4.h"
+
+...
 SCSINT32_COP *ptr_i;
-
 SCSINT32_COP cumsum_i;
-
 SCSCOMPLEX_COP *ptr_d;
-
 SCSREAL_COP cumsum_d;
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of an int32 discrete object state*/
-
-ptr_i = (SCSINT32_COP *) block->ozptr[0];
-                     /*get the ptrs of a double discrete object state*/
-
-ptr_d = (SCSCOMPLEX_COP *) block->ozptr[1];
-                     ...
-                     /*compute the cumsum of the int32 matrix*/
+{
+...
+    /*get the ptrs of an int32 discrete object state*/
+    ptr_i = (SCSINT32_COP *) block->ozptr[0];
+    /*get the ptrs of a double discrete object state*/
+    ptr_d = (SCSCOMPLEX_COP *) block->ozptr[1];
 
-cumsum_i = ptr_i[0]+ptr_i[1]+ptr_i[2]+ptr_i[3];
-                     ...
-                     /*compute the cumsum of the real part of the complex matrix*/
+    /*compute the cumsum of the int32 matrix*/
+    cumsum_i = ptr_i[0]+ptr_i[1]+ptr_i[2]+ptr_i[3];
 
-cumsum_d = ptr_d[0]+ptr_d[1]+ptr_d[2];
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    One can also use the set of C macros :
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[GetRealOzPtrs(block,x)]]></programlisting>
-                <para>,  </para>
-                <programlisting role="code"><![CDATA[GetImagOzPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint8OzPtrs(block,x)]]></programlisting>
-                <para>,  </para>
-                <programlisting role="code"><![CDATA[Getint16OzPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getint32OzPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint8OzPtrs(block,x)]]></programlisting>
-                <para>,
-                </para>
-                <para>                    </para>
-                <programlisting role="code"><![CDATA[Getuint16OzPtrs(block,x)]]></programlisting>
-                <para>, </para>
-                <programlisting role="code"><![CDATA[Getuint32OzPtrs(block,x)]]></programlisting>
-                <para> 
-                </para>
+    /*compute the cumsum of the real part of the complex matrix*/
+    cumsum_d = ptr_d[0]+ptr_d[1]+ptr_d[2];
+...
+}
+]]></programlisting>
                 <para>
-                    to have the appropriate pointer of the data to handle (<emphasis role="bold">x is numbered from 1 to noz</emphasis>).
+                    One can also use the set of C macros : <literal>GetRealOzPtrs(block,x)</literal>, <literal>GetImagOzPtrs(block,x)</literal>, <literal>Getint8OzPtrs(block,x)</literal>, <literal>Getint16OzPtrs(block,x)</literal>, <literal>Getint32OzPtrs(block,x)</literal>, <literal>Getuint8OzPtrs(block,x)</literal>, <literal>Getuint16OzPtrs(block,x)</literal>, <literal>Getuint32OzPtrs(block,x)</literal> to have the appropriate pointer of the data to handle (<emphasis role="bold">x is numbered from 1 to noz</emphasis>).
                 </para>
                 <para>
                     For the previous example that gives :
-                    
                 </para>
-                <programlisting role="code"><![CDATA[                     #include "scicos_block4.h"
-                     ...
-
+                <programlisting role="c"><![CDATA[
+ #include "scicos_block4.h"
+...
 SCSINT32_COP *ptr_i;
-
 SCSREAL_COP *ptr_dr;
-
 SCSREAL_COP *ptr_di;
-                     ...
+...
 
 void mycomputfunc(scicos_block *block,int flag)
-                     {
-                     ...
-                     /*get the ptrs of an int32 discrete object state*/
-
-ptr_i = Getint32OzPtrs(block,1);
-                     /*get the ptrs of a double discrete object state*/
-
-ptr_dr = GetRealOzPtrs(block,2);
-
-ptr_di = GetImagOzPtrs(block,2);
-                     ...
-                     }
-                    ]]></programlisting>
-                <para>
-                    
-                    Finally note that the discrete objects state should be only written for 
-                </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=4 and </para>
-                <programlisting role="code"><![CDATA[flag]]></programlisting>
-                <para>=2.
+{
+...
+    /*get the ptrs of an int32 discrete object state*/
+    ptr_i = Getint32OzPtrs(block,1);
+    /*get the ptrs of a double discrete object state*/
+    ptr_dr = GetRealOzPtrs(block,2);
+    ptr_di = GetImagOzPtrs(block,2);
+...
+} 
+]]></programlisting>
+                <para>
+                    Finally note that the discrete objects state should be only written for <literal>flag=4</literal> and <literal>flag=2</literal>.
                 </para>
             </listitem>
             <listitem>
                 <para>
                     <emphasis role="bold">block-&gt;work :</emphasis> A free pointer to set a working array for the block.
                 </para>
-                <para> The work pointer must be firstly allocated when = 4 and finally be free in the = 5.</para>
-                <para> Then a basic life cyle of that pointer in a C computational function should be :
+                <para>
+                &n