summaryrefslogtreecommitdiff
path: root/Master/tlpkg/libexec
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2017-03-24 22:27:21 +0000
committerKarl Berry <karl@freefriends.org>2017-03-24 22:27:21 +0000
commit638c484cd54573bf377234d46c5d564c53421bb5 (patch)
tree7a6a70c3f015fe7401ccf7b46708ca706987bbde /Master/tlpkg/libexec
parent2e8a37ac84488349711473be01df0db39db5445c (diff)
mweights (24mar17)
git-svn-id: svn://tug.org/texlive/trunk@43594 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/tlpkg/libexec')
-rwxr-xr-xMaster/tlpkg/libexec/ctan2tds9
1 files changed, 7 insertions, 2 deletions
diff --git a/Master/tlpkg/libexec/ctan2tds b/Master/tlpkg/libexec/ctan2tds
index c2f7faf3f70..7849efcbd69 100755
--- a/Master/tlpkg/libexec/ctan2tds
+++ b/Master/tlpkg/libexec/ctan2tds
@@ -3061,15 +3061,20 @@ for (@ARGV) {
}
-# we do not want to deal with anything but "normal" characters, a subset
+# We do not want to deal with anything but "normal" characters, a subset
# of 7-bit ASCII. The file names appear in too many contexts for
# anything else to reliably work.
#
+# Nothing in tlpdb itself restricts the characters used (except for
+# spaces and newlines), but we want to be cautious here. That
+# discrepancy seems ok?
+#
sub sanitize_file_names {
my ($dir) = @_;
# -0 in case of spaces or other chars in filenames, which would be
# parsed into words by the shell otherwise.
- &SYSTEM ("find $dir -print0 | xargs -0 /l/bin/rename 's![^-_A-Za-z0-9.,/+]!!g'");
+ &SYSTEM ("find $dir -print0 \
+ | xargs -0 /l/bin/rename 's![^-_A-Za-z0-9.,/+]!!g'");
}