diff options
| author | TJ <linux@tjworld.net> | 2010-04-03 09:23:43 +0100 |
|---|---|---|
| committer | Richard Jones <rjones@redhat.com> | 2010-04-03 09:23:43 +0100 |
| commit | 235a9619ffe45d81805cf3527e55c9b7168a6385 (patch) | |
| tree | b46c36f714c10440423ddb3b29f1f78ea144392a | |
| parent | f39a03cafd776bde150817a81f547fdb2e585dde (diff) | |
| download | hivex-235a9619ffe45d81805cf3527e55c9b7168a6385.tar.gz hivex-235a9619ffe45d81805cf3527e55c9b7168a6385.tar.xz hivex-235a9619ffe45d81805cf3527e55c9b7168a6385.zip | |
Spelling: reencode -> re-encode.
| -rwxr-xr-x | regedit/hivexregedit | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/regedit/hivexregedit b/regedit/hivexregedit index 0ad1352..d177d4f 100755 --- a/regedit/hivexregedit +++ b/regedit/hivexregedit @@ -51,13 +51,13 @@ C<--export> exports a Registry key (recursively) into the regedit format. =head2 ENCODING -C<hivexregedit> expects that regedit files have already been reencoded +C<hivexregedit> expects that regedit files have already been re-encoded in the local encoding. Usually on Linux hosts, this means UTF-8 with Unix-style line endings. Since Windows regedit files are often in -UTF-16LE with Windows-style line endings, you may need to reencode the +UTF-16LE with Windows-style line endings, you may need to re-encode the whole file before or after processing. -To reencode a file from Windows format to Linux (before processing it +To re-encode a file from Windows format to Linux (before processing it with the C<--merge> option), you would do something like this: iconv -f utf-16le -t utf-8 < win.reg | dos2unix > linux.reg |