I have seeing a behavior in recent months that I am less convinced is my doing.

Occasionally, when I export a configuration (using the "Export Configurations" maintenance step), recently-modified text fields will have Windows line terminators embedded in them, for example:

<description>If not set to 'true', the scheduler for the builds will be disabled.^M
^M
Enabled by default on production server.</description>

But not all fields; only the ones which have been changed. The unchanged fields are fine.
This impacts us because it shows up as an unexplained difference when we check these XML files into Perforce.

I used to think this was because I had pasted text into the field using a Windows-based browser (normally I work on Mac). However, very carefully re-entering the field from the Mac browser resulted in the same result when exporting. The only way to get rid of these seems to be to export, modify the XML by hand, and then import it back in. Which really isn't a scalable solution.

Is it possible some database change in recent upgrades is changing this behavior? Can it be changed back?