Changeset 696
- Timestamp:
- 09/07/10 20:48:50 (21 months ago)
- Files:
-
- 1 modified
-
trunk/reference/idldoc-reference.rst (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/reference/idldoc-reference.rst
r695 r696 1 IDLdoc 3.3 Reference 2 ==================== 1 IDLdoc 3.3 Reference Guide 2 ========================== 3 3 4 4 :Author: Michael Galloy … … 7 7 8 8 9 I DLdoc installation9 Installation 10 10 ------------------- 11 11 12 To install IDLdoc, simply unzip and place the IDLdoc distribution in your IDL path. Do not separate the contents of the distribution; the code looks for files in locations relative to itself. 13 14 15 IDLdoc routine keywords 16 ----------------------- 12 To install IDLdoc, simply unzip and place the IDLdoc `.sav` file, or the `src/` directory if you are installing the IDLdoc source distribution, in your IDL path. 13 14 Do not separate the contents of the distribution; the code looks for files in locations relative to itself. 15 16 17 `IDLDOC` routine keywords 18 ------------------------- 17 19 18 20 There are quite a few keywords to IDLdoc to set various specifications for the output. Also see the "Customizing Output" section for using templates for customized output. … … 76 78 ------------- 77 79 80 TODO: what is a format style? legacy format styles "IDLdoc", "IDL"; not recommended for new comments 81 78 82 79 83 rst format style … … 575 579 TODO: describe rst markup style 576 580 581 #. links, both kinds 582 #. code blocks 583 #. headers 584 #. image directive 585 #. embed directive 586 #. title directive 587 577 588 verbatim markup style 578 589 ~~~~~~~~~~~~~~~~~~~~~ … … 594 605 Instead of modifying the existing templates, it is best to copy the templates and specify their location with the `TEMPLATE_LOCATION` keyword to `IDLDOC`. If you have multiple template families, the `TEMPLATE_PREFIX` keyword can be used to specify a string that prefixes each filename of the template family. For example, IDLdoc itself uses the "latex-" prefix to specify the templates used to produce LaTeX output. 595 606 596 If IDLdoc is intended to produce some type of output besides HTML, the `COMMENT_STYLE` keyword must be used to specify the engine to produce that type of output. For example, IDLdoc provides the "latex" comment style to produce LaTeX output. Creating new comment style engines is beyond the scope of this reference guide.607 If IDLdoc is intended to produce some type of output besides HTML, the `COMMENT_STYLE` keyword must be used to specify the engine to produce that type of output. IDLdoc provides the "html", "latex", and "rst" comment styles. Creating new comment style engines is beyond the scope of this reference guide.
