1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
From: Lev Lamberov <dogsleg@debian.org>
Subject: Fix typo
This patch fixes typo in documentation (accidentaly -> accidentally).
--- a/convmv
+++ b/convmv
@@ -56,7 +56,7 @@ does not affect rename operation itself.
=item B<--exec> command
execute the given command. You have to quote the command and #1 will be
-substituted by the old, #2 by the new filename. Using this option link
+substituted by the old, #2 by the new filename. Using this option link
targets will stay untouched. Have in mind that #1 and #2 will be quoted
by convmv already, you must not add extra quotation marks around them.
@@ -263,10 +263,10 @@ Use appropriate mount options instead!
=head2 How to undo double UTF-8 (or other) encoded filenames
Sometimes it might happen that you "double-encoded" certain filenames, for
-example the file names already were UTF-8 encoded and you accidently did
+example the file names already were UTF-8 encoded and you accidentlly did
another conversion from some charset to UTF-8. You can simply undo that by
converting that the other way round. The from-charset has to be UTF-8 and the
-to-charset has to be the from-charset you previously accidently used. If you
+to-charset has to be the from-charset you previously accidentlly used. If you
use the C<--fixdouble> option convmv will make sure that only files will be
processed that will still be UTF-8 encoded after conversion and it will leave
non-UTF-8 files untouched. You should check to get the correct results by doing
@@ -274,7 +274,7 @@ the conversion without C<--notest> befor
helpful, because the double utf-8 file names might screw up your terminal if
they are being printed - they often contain control sequences which do funny
things with your terminal window. If you are not sure about the charset which
-was accidently converted from, using C<--qfrom> is a good way to fiddle out the
+was accidentlly converted from, using C<--qfrom> is a good way to fiddle out the
required encoding without destroying the file names finally.
=head2 How to repair Samba files
@@ -313,7 +313,7 @@ You can support convmv by doing a donati
=head1 AUTHOR
Bjoern JACKE
-
+
Send mail to bjoern [at] j3e.de for bug reports and suggestions.
=cut
@@ -643,7 +643,7 @@ sub char_get_newname {
$newname=&$norm(decode_utf8($newname)) if ($to_is_utf8);
return $newname;
}
-
+
}
sub get_dir_base_change() {
@@ -1104,7 +1104,7 @@ sub cap2utf8() {
$oldname =~ s/(:([0-9a-f][0-9a-f]))/chr(hex($2))/eg;
}
return $oldname;
-}
+}
sub runparsable() {
@@ -1140,7 +1140,7 @@ sub check_for_broken_perl_release() {
return 0;
}
$error .= "decode_utf8(\$test) check failed\n";
-
+
eval 'decode_utf8($test, Encode::FB_CROAK);';
if (not $@) {
$error .= "eval 'decode_utf8(\$non-utf8, Encode::FB_CROAK);'; check failed.\n";
@@ -1186,7 +1186,7 @@ sub check_for_perl_bugs() {
$bugs .= "#49830 ";
# convmv 1.10-1.11 would not work here!
# broken UTF-8 is silently being converted to sane UTF-8 without throwing
- # an error.
+ # an error.
}
if ($bugs) {
print "Your Perl version has fleas $bugs\n";
|
