Mercurial > mxd2map
diff doku/source/functionality.txt @ 235:00a39e8b6eed
* INSTALL.txt: Added a paragraph to make the env-vars available in Apache
* doku/source/_templates/layout.html: defining a custom footer with the
version-string included
* doku/source/conf.py: adopt versionstring and copyright
* doku/source/functionality.txt: formating-cosmetics, correct icon
author | Stephan Holl <stephan.holl@intevation.de> |
---|---|
date | Fri, 05 Aug 2011 09:18:53 +0200 |
parents | df533a03ad9f |
children | d10fd4de02aa |
line wrap: on
line diff
--- a/doku/source/functionality.txt Fri Aug 05 08:41:42 2011 +0200 +++ b/doku/source/functionality.txt Fri Aug 05 09:18:53 2011 +0200 @@ -11,7 +11,7 @@ must have a valid and available data source and must not fit the :ref:`restriction-label` described in the appropriate section. -.. image:: ../funktionsweise/funktionsweise-MXD-konverter.png +.. image:: ../funktionsweise/funktionsweise-MXD2map.png :align: center :alt: MXD2map-Schema :width: 500px @@ -57,7 +57,9 @@ the ESRI fonts available. ArcGIS products install these fonts to the default windows font folder ``c:\\windows\\fonts``. To make them available for the converter there has to be a MapServer font set (see -http://mapserver.org/mapfile/fontset.html). The MXD2map converter comes with an +http://mapserver.org/mapfile/fontset.html). + +The MXD2map converter comes with an initial fontset containing all relevant ESRI fonts and the free font FreeSans. The font set file named fonts.txt can be edited and further fonts can be added. To use a font set, the file needs to be referenced in the MapServer template @@ -65,7 +67,6 @@ in the conversion process. The converter uses a separate symbol file to provide symbol sets to the - template to have initial symbols available. If no symbol file is referenced a new one is created by the converter if necessary. The resulting symbol set is written to the same directory as the output mapfile named @@ -116,7 +117,7 @@ * Other features * Umlauts are translated into its equivalents within LAYER-names, - CLASS-names and also mapfile-names. Though it is good standard not to - use them since they mostly cause problems when using them within - OWS-related services. - * + CLASS-names and also mapfile-names. Though it is good standard not to + use them since they mostly cause problems when using them within + OWS-related services. +