Fixing bug 2810228 : updating cpd documentation.
git-svn-id: https://pmd.svn.sourceforge.net/svnroot/pmd/branches/pmd/4.2.x@6965 51baf565-9d33-0410-a72c-fc3788e3496d
This commit is contained in:
parent
0e1bf46e07
commit
bbc1d2a02f
@ -53,7 +53,7 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td valign="top">encoding</td>
|
||||
<td valign="top">The character set encoding (e.g., UTF-8) to use when reading the source code files; defaults to locale setting.</td>
|
||||
<td valign="top">The character set encoding (e.g., UTF-8) to use when reading the source code files, but also when producing the report. A piece of warning, even if you set properly the encoding value, let's say to UTF-8, but you are running CPD encoded with CP1252, you may end up with not UTF-8 file. Indeed, CPD copy piece of source code in its report directly, therefore, the source files keep their encoding.</td>
|
||||
<td valign="top" align="center">No</td>
|
||||
</tr>
|
||||
<tr>
|
||||
|
Loading…
x
Reference in New Issue
Block a user