2.1.7.0: DGIndex preprocessor puts BOM on d2v in codepage 65001(UTF-8)

[JJKylee]

Describe the bug
On Windows 10 x64 (Home), when the system codepage is set to 65001(UTF-8), the DGIndex preprocessor in StaxRip 2.1.7.0 puts BOM on the d2v output making its encoding UTF-8 with BOM, not UTF-8 without BOM.
This makes the d2v file unreadable by both DGIndex.exe GUI and MPEG2Source(DGDecode.dll). They refuse the BOM mark.
#424 shows what kind of errors show up in that case.

I confirmed this issue with both DGMPGDec 1.5.8 (currently the default DGIndex shipped with 2.1.7.0) and DGMPGDec 2.0.01.

DGIndex itself does NOT put BOM in any situation - either in GUI or in CLI via CMD or PowerShell or CMD call from PowerShell. Please refer to this thread about this issue on DG Tools Forum. Only StaxRip DGIndex preprocessor puts BOM.

This is pretty weird seeing that by contrast DGIndexNV preprocessor does not put BOM on the output dgi file in the same UTF-8 codepage system.

Expected behavior
There should be no BOM on the output d2v file generated by the DGIndex preprocessor.

How to reproduce the issue

1. Set the system codepage to UTF-8.
   

2. Restart Windows.

3. Start StaxRip 2.1.7.0 (unmodded version) and open any MPEG2 video file.
   

4. The same error occurs even if DGIndex is updated to the most recent version 2.0.01

Provide more information

If you change the text encoding of the output d2v file from UTF-8 with BOM to UTF-8 without BOM, the error is gone.