Some combinations of ruby and HOT2000 produced a perplexing error - "Could not parse Browse.RPT". These seem to be related to mismatches between encoding supported by various versions of Ruby, and non-UTF-8 characters that HOT2000 arbitrarily dumps into the Browse.Rpt file. These changes patch that error by forcing encoding to UTF8.
Some combinations of ruby and HOT2000 produced a perplexing error - "Could not parse Browse.RPT". These seem to be related to mismatches between encoding supported by various versions of Ruby, and non-UTF-8 characters that HOT2000 arbitrarily dumps into the Browse.Rpt file. These changes patch that error by forcing encoding to UTF8.