summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorDimitri van Heesch <dimitri@stack.nl>2003-06-15 18:25:48 (GMT)
committerDimitri van Heesch <dimitri@stack.nl>2003-06-15 18:25:48 (GMT)
commit80108293f1f4808c02d28d2d1620563437433a56 (patch)
tree567da63962a903f646bb092a950026c75a8369d8 /doc
parentdae59054d3387840f0f4b4bf8f237fee0591a5b1 (diff)
downloadDoxygen-80108293f1f4808c02d28d2d1620563437433a56.zip
Doxygen-80108293f1f4808c02d28d2d1620563437433a56.tar.gz
Doxygen-80108293f1f4808c02d28d2d1620563437433a56.tar.bz2
Release-1.3.2
Diffstat (limited to 'doc')
-rw-r--r--doc/config.doc4
-rw-r--r--doc/external.doc6
-rw-r--r--doc/faq.doc10
-rw-r--r--doc/language.doc22
4 files changed, 21 insertions, 21 deletions
diff --git a/doc/config.doc b/doc/config.doc
index b86d145..5087d35 100644
--- a/doc/config.doc
+++ b/doc/config.doc
@@ -1411,9 +1411,9 @@ TAGFILES = file1=loc1 "file2 = loc2" ... </pre>
If the \c CLASS_DIAGRAMS tag is set to \c YES (the default) doxygen will
generate a class diagram (in HTML and \f$\mbox{\LaTeX}\f$) for classes with base or
super classes. Setting the tag to \c NO turns the diagrams off.
- Note that this option is superseded by the HAVE_DOT option below.
+ Note that this option is superceded by the HAVE_DOT option below.
This is only a fallback. It is recommended to install and use dot,
- since it yield more powerful graphs.
+ since it yields more powerful graphs.
\anchor cfg_have_dot
<dt>\c HAVE_DOT <dd>
diff --git a/doc/external.doc b/doc/external.doc
index 6e92d2d..9f21593 100644
--- a/doc/external.doc
+++ b/doc/external.doc
@@ -41,7 +41,7 @@ reasons to not include all sources for these with every run of doxygen:
copy of it with your project's documentation. When the author forbids
redistribution, this is necessary. If the author requires compliance
with some license condition as a precondition of redistribution, and
- you do now want to be bound by those conditions, referring to their
+ you do not want to be bound by those conditions, referring to their
copy of their documentation is preferable to including a copy.
</dl>
@@ -126,8 +126,8 @@ if you want to create a tag file for the Qt documentation.
The tool \c doxytag depends on the particular structure
of the generated output and on some special markers that are generated by
-doxygen. Since this type of extraction is brittle and error prone I
-suggest you to only use this approach if there is no alternative. The
+doxygen. Since this type of extraction is brittle and error-prone I
+suggest you only use this approach if there is no alternative. The
doxytag tool may even become obsolete in the future.
\htmlonly
diff --git a/doc/faq.doc b/doc/faq.doc
index 74dc805..d9f3f6d 100644
--- a/doc/faq.doc
+++ b/doc/faq.doc
@@ -195,15 +195,15 @@ remove the % and keep the word unlinked.
No, not as such; doxygen needs to understand the structure of what it reads.
If you don't mind spending some time on it, there are several options:
-- If the grammer of X is close to C or C++, then it is probably not too hard to
+- If the grammar of X is close to C or C++, then it is probably not too hard to
tweak src/scanner.l a bit so the language is supported. This is done
for all other languages directly supported by doxygen
(i.e. Java, IDL, C#, PHP).
-- If the grammer of X is somewhat different than you can write an input
+- If the grammar of X is somewhat different than you can write an input
filter that translates X into something similar enough to C/C++ for
doxygen to understand (this approach is taken for VB, Object Pascal, and
Javascript, see http://www.stack.nl/~dimitri/doxygen/download.html#helpers).
-- If the grammer is completely different one could write a parser for X and
+- If the grammar is completely different one could write a parser for X and
write a backend that produces a similar syntax tree as is done by
src/scanner.l (and also by src/tagreader.cpp while reading tag files).
@@ -218,8 +218,8 @@ where this might happen is if you have lines in your code with more than
16K characters.
If you have run into such a case and want me to fix it, you
-should send me a code fragment that triggers the message. The workaround
-the problem put some line-breaks into your file, split it up into smaller
+should send me a code fragment that triggers the message. To work around
+the problem, put some line-breaks into your file, split it up into smaller
parts, or exclude it from the input using EXCLUDE.
<li><b>When running make in the latex dir I get "TeX capacity exceeded". Now what?</b>
diff --git a/doc/language.doc b/doc/language.doc
index bb6cc00..69bf6eb 100644
--- a/doc/language.doc
+++ b/doc/language.doc
@@ -25,7 +25,7 @@ Doxygen has built-in support for multiple languages. This means
that the text fragments that doxygen generates can be produced in
languages other than English (the default) at configuration time.
-Currently (version 1.3-20030430), 28 languages
+Currently (version 1.3.1-20030609), 28 languages
are supported (sorted alphabetically):
Brazilian Portuguese, Catalan, Chinese, Chinese Traditional, Croatian,
Czech, Danish, Dutch, English, Finnish,
@@ -55,7 +55,7 @@ when the translator was updated.
<TD>Brazilian Portuguese</TD>
<TD>Fabio "FJTC" Jun Takada Chino</TD>
<TD>chino@NOSPAM.icmc.sc.usp.br</TD>
- <TD>up-to-date</TD>
+ <TD>1.3.1</TD>
</TR>
<TR BGCOLOR="#ffffff">
<TD>Catalan</TD>
@@ -79,7 +79,7 @@ when the translator was updated.
<TD>Croatian</TD>
<TD>Boris Bralo</TD>
<TD>boris.bralo@NOSPAM.zg.tel.hr</TD>
- <TD>up-to-date</TD>
+ <TD>1.3.1</TD>
</TR>
<TR BGCOLOR="#ffffff">
<TD>Czech</TD>
@@ -115,13 +115,13 @@ when the translator was updated.
<TD>French</TD>
<TD>Xavier Outhier</TD>
<TD>xouthier@NOSPAM.yahoo.fr</TD>
- <TD>up-to-date</TD>
+ <TD>1.3.1</TD>
</TR>
<TR BGCOLOR="#ffffff">
<TD>German</TD>
<TD>Jens Seidel</TD>
<TD>jensseidel@NOSPAM.users.sf.net</TD>
- <TD>up-to-date</TD>
+ <TD>1.3.1</TD>
</TR>
<TR BGCOLOR="#ffffff">
<TD>Greek</TD>
@@ -169,7 +169,7 @@ when the translator was updated.
<TD>Portuguese</TD>
<TD>Rui Godinho Lopes</TD>
<TD>ruiglopes@NOSPAM.yahoo.com</TD>
- <TD>1.2.18</TD>
+ <TD>1.3.1</TD>
</TR>
<TR BGCOLOR="#ffffff">
<TD>Romanian</TD>
@@ -230,7 +230,7 @@ when the translator was updated.
{\bf Language} & {\bf Maintainer} & {\bf Contact address} & {\bf Status} \\
\hline
\hline
- Brazilian Portuguese & Fabio "FJTC" Jun Takada Chino & {\tt chino@icmc.sc.usp.br} & up-to-date \\
+ Brazilian Portuguese & Fabio "FJTC" Jun Takada Chino & {\tt chino@icmc.sc.usp.br} & 1.3.1 \\
\hline
Catalan & Albert Mora & {\tt amora@iua.upf.es} & 1.2.17 \\
\hline
@@ -239,7 +239,7 @@ when the translator was updated.
\hline
Chinese Traditional & Gary Lee & {\tt garylee@ecosine.com.tw} & 1.2.16 \\
\hline
- Croatian & Boris Bralo & {\tt boris.bralo@zg.tel.hr} & up-to-date \\
+ Croatian & Boris Bralo & {\tt boris.bralo@zg.tel.hr} & 1.3.1 \\
\hline
Czech & Petr P\v{r}ikryl & {\tt prikrylp@skil.cz} & up-to-date \\
\hline
@@ -251,9 +251,9 @@ when the translator was updated.
\hline
Finnish & Olli Korhonen & {\tt Olli.Korhonen@ccc.fi} & obsolete \\
\hline
- French & Xavier Outhier & {\tt xouthier@yahoo.fr} & up-to-date \\
+ French & Xavier Outhier & {\tt xouthier@yahoo.fr} & 1.3.1 \\
\hline
- German & Jens Seidel & {\tt jensseidel@users.sf.net} & up-to-date \\
+ German & Jens Seidel & {\tt jensseidel@users.sf.net} & 1.3.1 \\
\hline
Greek & Harry Kalogirou & {\tt harkal@rainbow.cs.unipi.gr} & 1.2.11 \\
\hline
@@ -272,7 +272,7 @@ when the translator was updated.
Polish & Piotr Kaminski & {\tt Piotr.Kaminski@ctm.gdynia.pl} & strange \\
& Grzegorz Kowal & {\tt g\_kowal@poczta.onet.pl} & \\
\hline
- Portuguese & Rui Godinho Lopes & {\tt ruiglopes@yahoo.com} & 1.2.18 \\
+ Portuguese & Rui Godinho Lopes & {\tt ruiglopes@yahoo.com} & 1.3.1 \\
\hline
Romanian & Alexandru Iosup & {\tt aiosup@yahoo.com} & 1.2.16 \\
\hline