From dc6eb0ddcf9253192a5a9ea7f606441f818fb381 Mon Sep 17 00:00:00 2001 From: William Victor Mote Date: Fri, 25 Apr 2003 16:40:52 +0000 Subject: [PATCH] Fix bad links/spelling of "extensions". git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196347 13f79535-47bb-0310-9956-ffa450edef68 --- src/documentation/content/xdocs/design/parsing.xml | 2 +- src/documentation/content/xdocs/dev/extensions.xml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/documentation/content/xdocs/design/parsing.xml b/src/documentation/content/xdocs/design/parsing.xml index 05c5d0ebc..d2e38d47a 100644 --- a/src/documentation/content/xdocs/design/parsing.xml +++ b/src/documentation/content/xdocs/design/parsing.xml @@ -36,7 +36,7 @@ Instead, FOP takes SAX events and builds its own tree-like structure. Why?

Namespaces

To allow for extensions to the XSL-FO language, FOP provides a mechanism for handling foreign namespaces.

See User Extensions for a discussion of standard extensions shipped with FOP, and their related namespaces.

-

See Developer Extensions for a discussion of the mechanisms in place to allow developers to add their own extensions, including how to tell FOP about the foreign namespace.

+

See Developer Extensions for a discussion of the mechanisms in place to allow developers to add their own extensions, including how to tell FOP about the foreign namespace.

diff --git a/src/documentation/content/xdocs/dev/extensions.xml b/src/documentation/content/xdocs/dev/extensions.xml index ef458ef7e..a188d4ad9 100644 --- a/src/documentation/content/xdocs/dev/extensions.xml +++ b/src/documentation/content/xdocs/dev/extensions.xml @@ -9,7 +9,7 @@
Overview -

For documentation of standard FOP extenstions, see the User FOP Extensions document.

+

For documentation of standard FOP extensions, see the User FOP Extensions document.

If the default funtionality of FOP needs to be extended for some reason then you can write an extension. -- 2.39.5