diff options
| author | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2000-10-15 15:32:16 (GMT) |
|---|---|---|
| committer | dimitri <dimitri@afe2bf4a-e733-0410-8a33-86f594647bc7> | 2000-10-15 15:32:16 (GMT) |
| commit | 868208ab61ca3aa6f506076f60de2745eaa8a6be (patch) | |
| tree | 7824ba2a5c9f1fe6ddc8633a13cc7d1e7a6c79a3 /doc/starting.doc | |
| parent | 499475795ed160e3a1e9cb571adc1ad86dc6a8ba (diff) | |
| download | Doxygen-868208ab61ca3aa6f506076f60de2745eaa8a6be.zip Doxygen-868208ab61ca3aa6f506076f60de2745eaa8a6be.tar.gz Doxygen-868208ab61ca3aa6f506076f60de2745eaa8a6be.tar.bz2 | |
Release-1.2.2-20001015
Diffstat (limited to 'doc/starting.doc')
| -rw-r--r-- | doc/starting.doc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/starting.doc b/doc/starting.doc index b518838..70dfc50 100644 --- a/doc/starting.doc +++ b/doc/starting.doc @@ -131,7 +131,7 @@ of compiling the generated documentation, \c doxygen writes a \c Makefile into the \c latex directory. By typing \c make in the \c latex directory the dvi file \c refman.dvi will be generated (provided that you have a make tool called -<code>make</code> ofcourse). This file can then be viewed using \c xdvi or +<code>make</code> of course). This file can then be viewed using \c xdvi or converted into a postscript file \c refman.ps by typing <code>make ps</code> (this requires <code>dvips</code>). To put 2 pages on one physical page use <code>make ps_2on1</code> instead. @@ -152,7 +152,7 @@ capabilities of the man page format, so some information \subsection step3 Step 3: Documenting the sources Although documenting the source is presented as step 3, in a new project -this should ofcourse be step 1. Here I assume +this should of course be step 1. Here I assume you already have some code and you want doxygen to generate a nice document describing the API and maybe the internals as well. |