From: TJ Date: Sat, 3 Apr 2010 08:23:43 +0000 (+0100) Subject: Spelling: reencode -> re-encode. X-Git-Tag: 1.2.2~5 X-Git-Url: http://git.annexia.org/?a=commitdiff_plain;h=235a9619ffe45d81805cf3527e55c9b7168a6385;p=hivex.git Spelling: reencode -> re-encode. --- 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 expects that regedit files have already been reencoded +C 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