iSphere Compare Editor replacing characters with junk

I love the iSphere compare editor and use it a lot. Every time I merge
some changes into a member and save the member, the Compare Editor corrupts
my source. I'm trying to figure out a way to keep it from doing so.

Many source members use what I will call the "overline" character as a
divider line comment, usually preceding a procedure, like this:

*______________________________
* Calculate some value.
*¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
p procname...

When displayed in the compare editor, it displays correctly. After saving
with the compare editor I find this:

*______________________________
* Calculate some value.
*¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
p procname...

The "overline" character was originally placed into the source member on
the i using SEU and it is x'BC' down there. The mangled line is a series
of x'62' and x'BC' characters, exactly twice as many characters as
originally there if the line length allows it to get that big, otherwise it
is just truncated.

In some places I have also seen the copyright sign "@" in the source code,
again entered in the i in SEU as x'B4'. After saving with the compare
editor, is is stored as x'62B4' instead. and looks like "©". Really hurts
when that was a one character constant '@' and now it is two characters 'Â
©'.

I use Windows 10, United States, English, my IBMi source files are all
CCSID(37). I can open and edit and save using the LPEX just fine without
corruption. I copy members around all day between libraries and files
using CPYF and RDi functions and nothing ever happens to them, they're fine.

I had mentioned a similar oddity this on this message board some years ago
regarding the LPEX editor when using "Save as...", but that just replaced
ALL the "overline" characters with the weird little substitution character
and I never got any help but to "stop using that character" (that character
is in thousands of members, so too late for that). Also the LPEX editor
doesn't seem to do that anymore, or I can't make it do that anymore, so I
thought I would ask again.