summaryrefslogtreecommitdiff
path: root/manual
diff options
context:
space:
mode:
authorStefan Bodewig <stefan.bodewig@innoq.com>2022-11-26 17:23:20 +0100
committerStefan Bodewig <stefan.bodewig@innoq.com>2022-11-26 17:23:20 +0100
commit22ef1323cc2e38505dcfde911939cd92b6539dd5 (patch)
tree83a40003f1274cbaeefafcdd229d2975b69d2ae5 /manual
parent3e6d6acc38a47aa66e629e519f482ee975dd0480 (diff)
downloadant-22ef1323cc2e38505dcfde911939cd92b6539dd5.tar.gz
warn against multi-byte encoding in tar
Diffstat (limited to 'manual')
-rw-r--r--manual/Tasks/tar.html5
1 files changed, 4 insertions, 1 deletions
diff --git a/manual/Tasks/tar.html b/manual/Tasks/tar.html
index 88d3c3a73..985625b32 100644
--- a/manual/Tasks/tar.html
+++ b/manual/Tasks/tar.html
@@ -133,7 +133,10 @@ to <q>gzip</q>, <q>bzip2</q>, or <q>xz</q>.</p>
<td>The character encoding to use for filenames inside the tar file. For a list of possible
values see
the <a href="https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html"
- target="_top">Supported Encodings</a>.<br/><em>Since Ant 1.9.5</em>
+ target="_top">Supported Encodings</a>. In general the tar format
+ expects names to use a single byte encoding and specifying a
+ multi-byte encoding here may lead to archives that cannot be
+ properly extracted by my tar tools.<br/><em>Since Ant 1.9.5</em>
<td>No; defaults to default JVM character encoding</td>
</tr>
</table>