aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjvoisin <julien.voisin@dustri.org>2020-02-08 14:01:13 +0100
committerjvoisin <julien.voisin@dustri.org>2020-02-08 14:01:13 +0100
commitebe06cb8a9f24f38ef93fb80b2c068fabf200c83 (patch)
tree80ef986f3374582ec6d8fe47faae9e1b86843f51
parent6dd48de4ef86ac67912332fede615bd72bcd12fc (diff)
downloadexternal_mat2-ebe06cb8a9f24f38ef93fb80b2c068fabf200c83.tar.gz
external_mat2-ebe06cb8a9f24f38ef93fb80b2c068fabf200c83.tar.bz2
external_mat2-ebe06cb8a9f24f38ef93fb80b2c068fabf200c83.zip
Add an example of possible quality loss in the manpage
-rw-r--r--doc/mat2.17
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/mat2.1 b/doc/mat2.1
index 2dcad8f..6da4191 100644
--- a/doc/mat2.1
+++ b/doc/mat2.1
@@ -74,9 +74,10 @@ be cleaned or not.
.PP
Moreover, mat2 goes to great lengths to make sure that as much metadata as
possible are removed. This might sometimes result in a loss of quality of the
-processed files. If you're experiencing this, you might want to give the
-lightweigtht cleaning mode a try, but keep in mind by doing so, some metadata
-\fBwon't be cleaned\fR.
+processed files. For example, textual based pdf file converted into image
+based means you'll be no longer able to copy text from pdf them. If you're
+experiencing this, you might want to give the lightweigtht cleaning mode a try,
+but keep in mind by doing so, some metadata \fBwon't be cleaned\fR.
.SH BUGS