Changeset 3678 for print

Timestamp:

12/02/10 14:39:45 (18 months ago)

Author:

elemoine

Message:

fix anchor links in the print docs, thanks asaunier for catching this, no functional change

Files:

• print/trunk/docs/configuration.txt (modified) (5 diffs)

print/trunk/docs/configuration.txt

@@ -84 +84 @@
 The outputFormats element lists the values formats that the server permits.  If omitted only 'pdf' is permitted.  If the single element '*' is present then all formats that the server can produce can be requested.  The formats the server can produce depends to a large degree on how the Java is configured.  PDF is supported on all systems but for image output formats JAI and ImageIO is used which means both must be on the server for them to be available.  You can get the list of supported formats by running the standalone client with the --clientConfig flag enabled (you will need to supply a yaml config file as well).  If you are using the servlet then do a get info request to see the list of formats (with the '*' as the outputFormats parameter in the config file).
 
-You can have as many layouts as you want. Their name must be unique and will be used on the client side. A layout can have a "titlePage" that will be added at the beginning of the generated document. It cannot contain any map. Same for the "lastPage", but for the end of the document. The "mainPage" section is mandatory and will be used once for each page requested. The details of a {PAGE_DEFINITION} section can be found `in another sub-section of this document <configuration.html#Page-definition>`_.
+You can have as many layouts as you want. Their name must be unique and will be used on the client side. A layout can have a "titlePage" that will be added at the beginning of the generated document. It cannot contain any map. Same for the "lastPage", but for the end of the document. The "mainPage" section is mandatory and will be used once for each page requested. The details of a {PAGE_DEFINITION} section can be found `in another sub-section of this document <configuration.html#page-definition>`_.
 
 If you want to let the user rotate the map (for a given layout), you have to set the "rotate" field to "true" in the corresponding "mainPage" section.
@@ -187 +187 @@
     ?     supportLegacyReader: false
 
-All fields are optional and can use global variables, as defined in the `Block definition <configuration.html#Block-definition>`_ chapter. Page specific variables are not accessible.
+All fields are optional and can use global variables, as defined in the `Block definition <configuration.html#block-definition>`_ chapter. Page specific variables are not accessible.
 
 Page definition
@@ -290 +290 @@
 * MacRoman 
 
-The "font" must refer to a standard PDF font or a `declared font <configuration.html#Fonts-definition>`_.
+The "font" must refer to a standard PDF font or a `declared font <configuration.html#fonts-definition>`_.
 
 Image block
@@ -454 +454 @@
               {...}
 
-Look `here <configuration.html#Table-configuration>`_ for how to specify the *tableConfig* field.
+Look `here <configuration.html#table-configuration>`_ for how to specify the *tableConfig* field.
 
 The *columnWeigth* (MF_V1.2 only) allows to define a weight for the column width. If you specify it for one column, you have to specify it for all of them. The width of a given column is tableWidth*columnWeight/sum(columnWeight).
@@ -533 +533 @@
 -------------------
 
-The `columns block <#Columnsblock>`_ and the `attributes block <#Attributesblock>`_ can take a table configuration object like that:
+The `columns block <#columns-block>`_ and the `attributes block <#attributes-block>`_ can take a table configuration object like that:
 
 .. code-block:: yaml