PRD-4843 - PRD-4.8 password encoding seed was different than PRD 5.0 seed as the 4.8 source code was encoded as ISO-8859-1 and the build process used UFT-8 causing the seed-string to get corrupted.

 Now, when loading a report from PRD 4.8 or older, we use a compatibility mode to use the same encoding bytes as in the compiled old version.
Merge pull request #403 from tmorgner/PRD-4843

PRD-4843 - PRD-4.8 password encoding seed was different than PRD 5.0 see...
Merge remote-tracking branch 'upstream/master'