### Eclipse Workspace Patch 1.0
#P org.eclipse.jdt.doc.isv
Index: guide/jdt_api_compile.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm,v
retrieving revision 1.84
diff -u -r1.84 jdt_api_compile.htm
--- guide/jdt_api_compile.htm	1 Jun 2010 16:05:11 -0000	1.84
+++ guide/jdt_api_compile.htm	2 Jun 2010 14:01:49 -0000
@@ -160,7 +160,20 @@
 <td valign=top width="250">-encoding &lt;encoding name&gt;</td>
 <td colspan="3">Specify default encoding for all source files. Custom encoding can also be specified on a per file basis by suffixing each input source file/folder name with <font color="#3366FF">[&lt;encoding name&gt;]</font>. 
 For example <font color="#3366FF">X.java[utf8]</font> would specify the <code>UTF-8</code> encoding for the compilation unit
-X.java located in the current user directory.<p>If multiple default source file encodings are specified, the last one will be used.</p></td>
+X.java located in the current user directory.<p>If multiple default source file encodings are specified, the last one will be used.</p>
+<p>For example:</p>
+<ul>
+<li>
+<font color="#3366FF"><code>... -encoding UTF-8 X.java[Cp1252] Y.java[UTF-16] Z.java ....</code></font><br>
+All source files will be read using UTF-8 encoding (this includes <font color="#3366FF">Z.java</font>). <font color="#3366FF">X.java</font> 
+will be read using Cp1252 encoding and <font color="#3366FF">Y.java</font> will be used
+using UTF-16 encoding.
+</li>
+<li>
+<font color="#3366FF"><code>... -encoding UTF-8 -encoding UTF-16 ....</code></font><br>
+All source files will be read using UTF-16 encoding. The -encoding option for UTF-8 is ignored.
+</li>
+</ul></td>
 </tr>
 <tr>
 <th colspan="4">Compliance options</th>