--- a/doku/source/functionality.txt	Wed Aug 10 15:00:40 2011 +0200
+++ b/doku/source/functionality.txt	Fri Aug 12 09:15:34 2011 +0200
@@ -76,6 +76,9 @@
 Features
 --------
 
+MXD2map is optimized to work best with MapServer 6.x. Therfore the new
+MapServer features (symbolhandling, styling etc) are built in.
+
 MXD2map currently supportes the following features:
 
  * Datasources:
@@ -88,26 +91,29 @@
    * Simple marker symbols
    * Character marker symbols
    * Arrow marker symbols
+   * Picture marker symbols (also trancparency is supported if set in MXD)
    * Symbols based on TTF-characters of special cartographic fonts
    * Any combination of character marker symbols
    * Linesymbols with pattern and cartographic attributes
    * Polygons filled with solid color and outline
    * Polygons filled with a hatch and hatched outline
 
+
  * Layer types:
 
    * Featurelayer (vectors) as POINT, LINESTRING and POLYGON
    * Classifications with unique values
    * Classifications with class breaks
    * Group-members are concatinated to group.layername. This ensures having discrete layernames
-   * ArcGIS-layergroups are represented as WMS Named layers, which are WMS-layers without a title (so not requestable throuhg GetMap)
+   * ArcGIS-layergroups are represented as WMS Named layers, which are WMS-layers without a title (so not requestable through GetMap)
    * all definition-queries for filtering the data on Layer- and classification-level
 
  * Further map attributes:
 
-   * Projections and units based on the EPSG-table
+   * Projections and units based on the EPSG-table (if set in MXD)
    * Min/max scale denominations at layer and label-level
-   * Map extents
+   * Global Map extent
+   * Layer extent and SRS
    * Simple labeling
    * Filter and expressions
    * ArcSDE Jointables
@@ -120,4 +126,7 @@
      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.
-   
+   * Creation of distinct layer-names by concatinating group- and
+     layernames to WMS-titles. This comes handy mostly in ArcGIS
+     layergroups.
+

--- a/doku/source/restrictions.txt	Wed Aug 10 15:00:40 2011 +0200
+++ b/doku/source/restrictions.txt	Fri Aug 12 09:15:34 2011 +0200
@@ -1,11 +1,14 @@
-.. index:: restrictions, label, Raster, SDE, workaround, picture-symols
+.. index:: restrictions, label, Raster, ArcSDE, SDE, workaround, picture-symols, windows, ArcEngine
 .. _restriction-label:
 
 ------------
 Restrictions
 ------------
 
-Currently there are some restrictions in the usage of the converter:
+Currently there are some restrictions in the usage of the converter. One
+of the main restrictions is the fact that the converter currently only
+runs on Windows. This is due to the fact that the needed ArcEngine did
+never reliably work on Linux. This was tested with ArcEngine 10.0.
 
 Supported datasources:
 
@@ -36,17 +39,12 @@
      write the appropriate symbols with the appropiate gap to the mapfile.
 
  * The converter sets the width to 1 for line symbols that have a width
-   smaller than 1. Outlines with a width smaller than 1 are drawn in the fill
-   color of the ploygon and the width is set to 1.
+   smaller than 1. 
 
    .. tip::
      To avoid lines and line colors (specially outlines) to be handled by the
      converter, use integer numbers for line width only.
 
- * Picture symbols are not supported by the converter since ArcGIS embedds
-   the image directly into the MXDfile. This might be supported in the
-   near future.
-
  * In ArcGIS maps default symbols can be defined as fallback within classifications. 
    Since MapServer does not support such fallback symbols or styles
    within classifications the converter does not read these default symbols.
@@ -56,9 +54,6 @@
 
 Layer support:
 
- * Group-layers are represented as WMS Named Layers (not requestable via
-   GetMap-Request). WMS-clients can recognize them as
-   'organisation-layers'.
  * Expressions for label are parsed by an internal parser in ArcGIS. The
    interpretation of this expressions is very limited though.
    Therefore label expressions may not contain any special functions or must fit