From e91013f6e5be9b2c10c2d698bdeb88e611f7ccca Mon Sep 17 00:00:00 2001 From: Emmanuel Venisse Date: Thu, 7 Jul 2005 12:58:23 +0000 Subject: [PATCH] we need extensions for figure filename. It's a difference with the original APT format, but we can't know where images are stored for check the existence of files when we generate the output. git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@209597 13f79535-47bb-0310-9956-ffa450edef68 --- maven-site/src/site/apt/apt-format.apt | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/maven-site/src/site/apt/apt-format.apt b/maven-site/src/site/apt/apt-format.apt index 60c5d64bbe..3a92493ede 100644 --- a/maven-site/src/site/apt/apt-format.apt +++ b/maven-site/src/site/apt/apt-format.apt @@ -290,24 +290,14 @@ Verbatim square brackets. The figure name is optionally followed by some text: the figure caption. - The figure name is the pathname of the file containing the figure but - without an extension. Example: if your figure is contained in - <<>>, the figure name is - <<>>. + The figure name is the pathname of the file containing the figure with an + extension. Example: <<>>. If the figure name comes from a relative pathname (recommended practice) rather than from an absolute pathname, this relative pathname is taken to be relative to the directory of the current APT document (a la HTML) rather than relative to the current working directory. - Why not leave the file extension in the figure name? This is better - explained by an example. You need to convert an APT document to PostScript - and your figure name is <<>>. A APT processor will - first try to load <<>>. When the desired format - is not found, a APT processor tries to convert one of the existing - formats. In our example, the APT processor tries to convert - <<>> to encapsulated PostScript. - *** Table ~~~~~~~~~