XML file in ISO 8859-13 format suddenly not working

[PdFUser5000]

I have a flow, where the input is an XML file that is picked up by switch.

Code: Select all

<?xml version="1.0" encoding="ISO-8859-13"?>
<!-- created with JavaScript MetaXMLsave -->
<orderinfo>
	<customerID></customerID>
	<customerPath></customerPath>
	<orderID></orderID>
	<model>
	    <modelNo></modelNo>
	</model>
</orderinfo>

What has recently started to happen is that when a network address that is placed in customerPath has foreign symbols in it (ø, å, æ) is not parsed correctly by switch. The symbol is displayed wrong and switch returns an error, because the network path does not exist.

This was not an issue before and has appeared out of nowhere. I have not changed anything, except updated Switch to 2024 Fall version. When i open the xml file in Notepad, the symbol is also wrong, but when i open it in microsoft edge, it is displayed correctly. The correct language package is installed on the server and has not been altered in any way during this time.

I am not sure, if this is an windows issue or a Switch issue or where should i start to try fixing this. I can change the encoding versio, but that would be a last resort.

[NEOSA]

Hi,

We've been facing also some issues with some accented characters in network path / local paths where PDF files were not processed by Switch/PitStop Pro

Encoding at the server side (Windows 2K22, French locale and FR language - ReFS local storage + Samba Servers) has never changed. I'm not sure this append after a Switch Upgrade.

The decision we took was to use some App to cleanup variables / files & folders by removing/replacing chars with accents, diacritics, spaces, etc...

For sure, this issue is not the same as you described, but we try to avoid problems by fixing even XML content as "clean" as possible.

[evelynwang]

It seems that the issue related to character encoding in XML has appeared after you updated Switch. Can you try checking if Switch 2024 Fall has changed anything about how encoding is handled? Also, you can try switching to UTF-8 encoding to see if the issue is resolved, as UTF-8 has better support for special characters like ø, å, æ.color block jam level 426