--- a/doku/source/restrictions.txt	Mon Jul 11 14:28:38 2011 +0200
+++ b/doku/source/restrictions.txt	Mon Jul 18 15:12:24 2011 +0200
@@ -7,7 +7,38 @@
 Supported datasources:
 
  * ArcSDE-passwords cannot be read since they are encrypted. The converter
- exports the string "define me" which needs to be replaced later on in the
- resulting mapfile
+   exports the string "define me" which needs to be replaced later on in the
+   resulting mapfile
 
- * 
+ * Since the MapServer cannot use a file geodatabase datasource the converter
+   does not support this datasource and will not transform the MXD-file at all.
+
+ * Raster data is not supported by the converter yet.
+
+Symbol support:
+
+ * Line symbols with pattern cannot be combined with marker symbols. The
+   converter reads all symbols and writes the corresponding styles to the
+   resulting mapfile but the marker symbols are rendered without any gap.
+
+   * Workarround:
+     For small marker symbols it is recommended to use a line symbol in
+     combination with pattern (in ArcGIS called template) to create the
+     symbology.
+     The reason why marker symbols cannot be used in combination with a template
+     is the difficulty to interpret the read attributes like marks and gaps and
+     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.
+
+ * Picture symbols are not supported by the converter.
+
+ * In ArcGIS maps default symbols can be defined as fallback. Since MapServer
+   does not support such fallback symbols or styles the converter does not
+   read these default symbols.
+
+ * In ArcGIS predefined symbols like bars or pie charts can be used to display
+   values. The converter does not support these symbols.
+