Documentation.

h2/src/docsrc/html/build.html

@@ -185,6 +185,7 @@ If you like to provide patches, please consider the following guidelines to simp
 </li><li>A template of the Eclipse settings are in
     <code>src/installer/eclipse.settings/*</code>. If you want to use them,
     you need to copy them to the <code>.settings</code> directory.
+    The formatting options (<code>eclipseCodeStyle</code>) are also included.
 </li><li>Please provide test cases and integrate them into the test suite.
     For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>.
     For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or

h2/src/docsrc/text/_docs_en.utf8.txt

@@ -1286,7 +1286,7 @@ Only use Java 1.5 features (do not use Java 1.6) (see <a href="#environment">Env
 Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>. 
 
 @build_1061_li
-A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. 
+A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. The formatting options (<code>eclipseCodeStyle</code>) are also included. 
 
 @build_1062_li
 Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>. For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code>. 

h2/src/docsrc/text/_docs_ja.utf8.txt

@@ -1286,7 +1286,7 @@ Centralリポジトリの利用
 #Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>. 
 
 @build_1061_li
-#A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. 
+#A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. The formatting options (<code>eclipseCodeStyle</code>) are also included. 
 
 @build_1062_li
 #Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>. For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code>. 

h2/src/docsrc/textbase/_docs_en.properties

@@ -427,7 +427,7 @@ build_1057_h2=Providing Patches
 build_1058_p=\ If you like to provide patches, please consider the following guidelines to simplify merging them\: 
 build_1059_li=Only use Java 1.5 features (do not use Java 1.6) (see <a href\="\#environment">Environment</a>). 
 build_1060_li=Follow the coding style used in the project, and use Checkstyle (see above) to verify. For example, do not use tabs (use spaces instead). The checkstyle configuration is in <code>src/installer/checkstyle.xml</code>. 
-build_1061_li=A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. 
+build_1061_li=A template of the Eclipse settings are in <code>src/installer/eclipse.settings/*</code>. If you want to use them, you need to copy them to the <code>.settings</code> directory. The formatting options (<code>eclipseCodeStyle</code>) are also included. 
 build_1062_li=Please provide test cases and integrate them into the test suite. For Java level tests, see <code>src/test/org/h2/test/TestAll.java</code>. For SQL level tests, see <code>src/test/org/h2/test/test.in.txt</code> or <code>testSimple.in.txt</code>. 
 build_1063_li=The test cases should cover at least 90% of the changed and new code; use a code coverage tool to verify that (see above). or use the build target <code>coverage</code>. 
 build_1064_li=Verify that you did not break other features\: run the test cases by executing <code>build test</code>. 

h2/src/tools/org/h2/build/doc/dictionary.txt

@@ -630,3 +630,7 @@ decompressed expansion ziv abbreviated augments omitted gain
 subtracted maxed logical lempel increases sibling impersonate proper remembers
 moon centric adeptia workflows generalized bpchar binaries incremental poor
 slowly prefs precedence mat verbose nonce complicate speedup replay
+profiles superinterfaces conventions brace indentations increments
+explicitconstructorcall switchstatements members parens alignment declarations
+jdt continuation codegen parenthesized tabulation ellipsis imple inits guardian
+postfix