From fcf6dd89e3effeb085697ae5dc347b014f8e290f Mon Sep 17 00:00:00 2001 From: calvin Date: Mon, 15 Nov 2004 19:28:13 +0000 Subject: [PATCH] updated for 2.0 release git-svn-id: https://linkchecker.svn.sourceforge.net/svnroot/linkchecker/trunk/linkchecker@1989 e7d03fd6-7b0d-0410-9947-9c21f3af8025 --- doc/upgrading.html | 20 +++++++++++++++++--- doc/upgrading.txt | 16 ++++++++++++++++ 2 files changed, 33 insertions(+), 3 deletions(-) diff --git a/doc/upgrading.html b/doc/upgrading.html index 99c9be89..08a7cd7f 100644 --- a/doc/upgrading.html +++ b/doc/upgrading.html @@ -3,7 +3,7 @@ - + Upgrading @@ -32,8 +32,21 @@ window.onload = function() {

Upgrading

-

Migrating from 1.12.x to 1.13.0

+
+

Migrating from 1.x to 2.0

+

The --output and --file-output parameters can specify the encoding +now. You should check your scripts if they support the new option +syntax.

+

Some added checks might trigger new warnings, so automated scripts +or alarms can have more output than with 1.x releases.

+

All output (file and console) is now encoded according to a given +character set encoding which defaults to iso-8859-1. If you +relied that output was in a specific encoding, you might want to +use the output encoding option.

+
+
+

Migrating from 1.12.x to 1.13.0

Since lots of filenames have changed you should check that any manually installed versions prior to 1.13.0 are removed. Otherwise you will have startup problems.

@@ -53,9 +66,10 @@ exit value. For scripts to ignore exit values and therefore restore the old behaviour you can append a || true at the end of the command.

+
-Generated on: 2004-11-08 13:50 UTC. +Generated on: 2004-11-15 19:27 UTC.
diff --git a/doc/upgrading.txt b/doc/upgrading.txt index 29e19ab7..730c308d 100644 --- a/doc/upgrading.txt +++ b/doc/upgrading.txt @@ -5,6 +5,22 @@ Upgrading ========= +Migrating from 1.x to 2.0 +------------------------- + +The --output and --file-output parameters can specify the encoding +now. You should check your scripts if they support the new option +syntax. + +Some added checks might trigger new warnings, so automated scripts +or alarms can have more output than with 1.x releases. + +All output (file and console) is now encoded according to a given +character set encoding which defaults to iso-8859-1. If you +relied that output was in a specific encoding, you might want to +use the output encoding option. + + Migrating from 1.12.x to 1.13.0 -------------------------------