Oh, that’s a different issue altogether then, I think.
I can send a simple API query to return the “™” string, and I believe it actually is valid as an XML character in the value returned -
<BESAPI xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="BESAPI.xsd">
How it’s processed by your XML client, though, may vary depending on what kind of encoding you choose when saving the XML file or passing it along upstream.
In fact we can embed the ™ character as part of a Fixlet Title as well. When I export that in the Console, it’s saved as UTF-8 which recognizes that TM character directly
<?xml version="1.0" encoding="UTF-8"?>
<BES xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="BES.xsd">
<Title>Test Trademark ™</Title>
Most of the API work I do is in Python, which uses utf-8 for its strings by default anyway…are you using some language that expects ASCII, or latin-1, or something else besides UTF-8? It may require some encoding in your application