summaryrefslogtreecommitdiffstats
path: root/doc/faq.doc
diff options
context:
space:
mode:
authorDimitri van Heesch <doxygen@gmail.com>2019-12-26 14:40:50 (GMT)
committerGitHub <noreply@github.com>2019-12-26 14:40:50 (GMT)
commitd1e058b9c1f93aa0a986dbc8a754c5eabd747e27 (patch)
tree5dadd9d3fae88b0d9e37182ea073e60ebe3197a5 /doc/faq.doc
parentc42c0ae66542e4e154c2646fc725890554208d89 (diff)
parenta5c98ade388f4f18ec30476ca706760a8129c73f (diff)
downloadDoxygen-d1e058b9c1f93aa0a986dbc8a754c5eabd747e27.zip
Doxygen-d1e058b9c1f93aa0a986dbc8a754c5eabd747e27.tar.gz
Doxygen-d1e058b9c1f93aa0a986dbc8a754c5eabd747e27.tar.bz2
Merge branch 'master' into feature/bug_fenced_code
Diffstat (limited to 'doc/faq.doc')
-rw-r--r--doc/faq.doc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/faq.doc b/doc/faq.doc
index 0ba9450..8a3aee8 100644
--- a/doc/faq.doc
+++ b/doc/faq.doc
@@ -216,7 +216,7 @@ If you don't mind spending some time on it, there are several options:
- 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.doxygen.org/download.html#helpers).
+ JavaScript, see http://www.doxygen.org/download.html#helpers).
- 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
\c src/scanner.l (and also by \c src/tagreader.cpp while reading tag files).