XSL used to export XML, replace function causing issues
Here’s the issue: in the process of exporting XML using XSL, extended characters (like fancy quotes and em-dashes) are being replaced incorrectly. Basically, while replacing the character with it's corresponding HTML entity, the character plus two more characters get replaced.
The problem is caused by a difference between the way Adobe is handling XSL in older versions 2014 vs. 2018 or newer. Attached you will find an example export of the 2014 export and the 2018 export using the exact same XSL. Notice that in the 2018 TWO characters after every special character are getting replaced. I have also attached the XSL we use to transform the file
1
vote
Jessie
shared this idea