TDMLRunner loads external file with different encoding

4 of the tests in the NITF schema project contain text segments that when the expected results are loaded by TDMLRunner something is happening that is causing the text to change when it is loaded by TDMLRunner.

For example, test_i_3114e has a TextSegment that contains some strangely encoded text values, that when parsed show up like so:

229␣␣␣␣␣?␊

However, when this same line is loaded by the TDMLRunner as an expected result, it becomes:

229␣␣␣␣␣￥␍␊

Just to be clear that this is indeed an issue with how the TDMLRunner loads the expected results file, you can parse the data from this test and use the output as the expected result and when TDMLRunner compares the files, it will fail due to these sort of encoding related issues.