summaryrefslogtreecommitdiffstats
path: root/doc/faq.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/faq.doc
parentdae59054d3387840f0f4b4bf8f237fee0591a5b1 (diff)
downloadDoxygen-80108293f1f4808c02d28d2d1620563437433a56.zip
Doxygen-80108293f1f4808c02d28d2d1620563437433a56.tar.gz
Doxygen-80108293f1f4808c02d28d2d1620563437433a56.tar.bz2
Release-1.3.2
Diffstat (limited to 'doc/faq.doc')
-rw-r--r--doc/faq.doc10
1 files changed, 5 insertions, 5 deletions
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>