fpdoc.1 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147
  1. .TH fpdoc 1 "9 march 2002" "Free Pascal" "Free Pascal unit documentation generator"
  2. .SH NAME
  3. fpdoc \- The FPC Pascal unit documentation generator.
  4. .SH SYNOPSIS
  5. \fBfpdoc\fP --input=inputcommand [--output=output] [--format=fmt]
  6. [--descr=descriptionfile] [--show-private] [--hide-protected]
  7. [--lang=language] [--content=contentfile] [--import=importfile]
  8. [--package=packagename] [--html-search=searchpage]
  9. .SH Description
  10. .B fpdoc
  11. scans a Free Pascal unit source file and generates documentation for it.
  12. The documentation can be in various formats (currently HTML and LaTeX)
  13. It can read various description files which contain the description for the
  14. various symbols found in the unit file.
  15. .SH Usage
  16. You can invoke
  17. .B fpdoc
  18. with as the only required argument the 'input' argument. It should at least
  19. contain the name of the unit file for which documentation should be
  20. generated.
  21. .SH Options
  22. .B fpdoc
  23. has several options, most of them optional, defaults will be used in most
  24. cases.
  25. .TP
  26. .BI \-\-content
  27. This option tells
  28. .B fpdoc
  29. to generate a content file. A content file contains a list of all the
  30. possible anchors (labels) in the generated documentation file, and can be
  31. used to create cross-links in documentation for different units, using the
  32. .B --import
  33. option.
  34. .TP
  35. .BI \-\-descr=descfile
  36. This option specifies the name of a description file
  37. .B descfile
  38. that contains the actual documentation for the unit.
  39. This option can be given several times, for several description files.
  40. .TP
  41. .BI \-\-format=fmt
  42. Specifies the format
  43. .B fmt
  44. in which the documentation will be generated. Currenly,
  45. the following formats are known:
  46. .RS
  47. .TP
  48. .I htm
  49. HTML with 8.3 conforming filenames.
  50. .TP
  51. .I html
  52. HTML with long filenames.
  53. .TP
  54. .I xhtml
  55. XHTML with long files,ames.
  56. .TP
  57. .I latex
  58. LaTex, which uses the fpc.sty style used by the Free Pascal documentation.
  59. .TP xml-struct
  60. Structured XML.
  61. .RE
  62. .TP
  63. .BI \-\-hide\-protected
  64. By default, the documentation will include descriptions and listings of
  65. protected fields and methods in classes or objects. This option changes this
  66. behaviour; if it is specified, no documentation will be generated for these
  67. methods. Note that public methods or properties that refer to these
  68. protected method will then have a dangling (i.e. unavailable) link.
  69. .TP
  70. .BI \-\-html\-search=link
  71. Adds an entry for an HTML search page at location
  72. .B link
  73. in the headers of the generated HTML pages. There is no search page
  74. provided, this should be made and provided by the user.
  75. .TP
  76. .BI \-\-import=impfile
  77. imports a content file
  78. .B impfile
  79. from another documentation set. This can be used to
  80. resolve references to elements within this other documentation file;
  81. .TP
  82. .B \-\-input=cmd
  83. This option tells
  84. .B fpdoc
  85. what input file should be used. The argument
  86. .B cmd
  87. can be just a filename, but can
  88. also be a complete compiler command-line with options that concern the
  89. scanning of the pascal source: defines, include files, syntax options,
  90. as they would be specified to the free pascal compiler when compiling
  91. the file. If a complete command is used, then it should be enclosed in
  92. single or double quotes, so the shell will not break them in parts.
  93. It is possible to specify multiple input commands; they will be treated one
  94. by one, and documentation will be generated for each of them.
  95. .TP
  96. .BI \-\-lang=language
  97. Sets the language for the output file. This will mainly set the strings used
  98. for the headers in various parts of the documentation files (by default
  99. they're in english). Currently, valid options are
  100. .RS
  101. .TP
  102. .I de
  103. German.
  104. .TP
  105. .I fr
  106. French.
  107. .TP
  108. .I nl
  109. Dutch.
  110. .RE
  111. .TP
  112. .BI \-\-latex\-highlight
  113. Switches on an internam latex syntax highlighter. This is not yet
  114. implemented. By default, syntax highlighting is provided by the syntax
  115. package that comes with fpc.
  116. .TP
  117. .BI \-\-output=name
  118. This option tells
  119. .B fpdoc
  120. where the output file should be generated. How this option is interpreted
  121. depends on the format that is used. For latex,
  122. .B name
  123. is interpreted as the
  124. filename for the tex file. For all other formats,
  125. .B name
  126. is interpreted as
  127. the directory where all documentation files will be written. The directory
  128. will be created if it does not yet exist.
  129. .TP
  130. .BI \-\-show\-private
  131. By default, no documentation is generated for private methods or fields.
  132. This option causes
  133. .B fpdoc
  134. to generate documentation for these methods as well.
  135. .SH SEE ALSO
  136. .IP
  137. .BR ppc386 (1)
  138. .BR latex (1)