Added formatter file for documentation.

fortiss-std-env/settings/README

@@ -4,27 +4,33 @@ Changing the first file requires all users to update their local copy manually.
 Changing the Eclipse preference files takes effect after users update their
 checked out copy.
 
-File				Description
-config				Subversion configuration to be copied to your personal subversion
-					directory (e.g. ~/.subversion/config, %USERPROFILE%\Application Data\Subversion\config)
-					@see_also "https://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html"
+File				          Description
+----                          -----------
 
-org.eclipse.jdt.core.prefs
-org.eclipse.jdt.ui.prefs
-					Eclipse Java Properties to be used in each fortiss plugin. This changes project settings
-					of the project, so everyone who checked out that project works with the same setting.
-					INSTALL: in order to enable these settings for your plugin, follow these steps:
-					  1. Make sure the plugin folders ".settings" sub-folder is also checked in.
-					  2. If the sub-folder contains these two files, delete them (from the repository, too).
-					  3. Add or change the svn property "svn:externals" of ".settings" folder to include the
-					     following two lines (this creates a file link to the two files contained in this
-					     README's folder):
-					       ^/fortiss-std-env/settings/org.eclipse.jdt.core.prefs org.eclipse.jdt.core.prefs
-						   ^/fortiss-std-env/settings/org.eclipse.jdt.ui.prefs org.eclipse.jdt.ui.prefs
+config                        Subversion configuration to be copied to your personal subversion
+                              directory (e.g. ~/.subversion/config, %USERPROFILE%\Application Data\Subversion\config)
+                              @see_also "https://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html"
+
+org.eclipse.jdt.core.prefs    Eclipse Java Properties to be used in each fortiss plugin. This changes project settings
+org.eclipse.jdt.ui.prefs      of the project, so everyone who checked out that project works with the same setting.
+                              INSTALL: in order to enable these settings for your plugin, follow these steps:
+                                1. Make sure the plugin folders ".settings" sub-folder is also checked in.
+                                2. If the sub-folder contains these two files, delete them (from the repository, too).
+                                3. Add or change the svn property "svn:externals" of ".settings" folder to include the
+                                   following two lines (this creates a file link to the two files contained in this
+                                   README's folder):
+                                     ^/fortiss-std-env/settings/org.eclipse.jdt.core.prefs org.eclipse.jdt.core.prefs
+                                     ^/fortiss-std-env/settings/org.eclipse.jdt.ui.prefs org.eclipse.jdt.ui.prefs
 						   
-dropins/*.jar
-					Development support tools, which were bundled with ConQAT development tools, but are no
-					longer maintained by the ConQAT development team.
-					INSTALL: Copy the *.jar files into your Eclipse installation's "dropins" folder.
-					Restart Eclipse and issue a full rebuild using the Clean operation.
+dropins/*.jar                 Development support tools, which were bundled with ConQAT development tools, but are no
+                              longer maintained by the ConQAT development team.
+                              INSTALL: Copy the *.jar files into your Eclipse installation's "dropins" folder.
+                              Restart Eclipse and issue a full rebuild using the Clean operation.
 
+fortiss-*-codestyle           These files (fortiss-java-codestyle, fortiss-c-codestyle, ...) contain the eclipse
+                              code-formatter rules used by AF3. For consistency EVERY developer shall use these
+                              rules. However, a manual import is not necessary, since the rules are also contained
+                              in org.eclipse.jdt.* (see above).
+                              Although not necessary, a manual import is performed the following way (example for java):
+                                'Window' -> 'Preferences' -> 'Java' -> 'Code Style' -> 'Formatter' -> 'Import'
+                              Then please make sure, that the new rule-set 'fortiss' is selected as the active profile.