Referencing a richtext field in an advanced PDF template causes XML parsing errors when it encounters the '&' ampersand character, or tag attributes with dashes in their names, or unsupported tags. What's the right way to sanitize this or bypass the errors?

AI generated answer (using internal Slack threads):

Based on the conversations, the issue of XML parsing errors when encountering the '&' ampersand character, tag attributes with dashes in their names, or unsupported tags in a richtext field in an advanced PDF template can be addressed in several ways: 1. Use the

?replace('&','&')

function on the text string in the PDF. This function replaces the '&' character with its XML equivalent. This solution is applied directly in the PDF and does not require pre-PDF modifications. 2. Use the

xml.escape

or

xml.encode

functions. These functions escape or encode special characters that may cause issues in XML parsing. However, these are blanket solutions and may modify characters that you do not want to be changed. 3. Use the

?xml

function on the field causing issues. This function escapes XML special characters. 4. Use the

<outputformat>

directive to handle special characters. This directive allows you to specify the output format of the template, which can help handle special characters. 5. Use the

?replace("&", "-")

function to replace the '&' character with a dash. This function is applied directly in the template. Remember to consider the specific requirements of your use case when choosing a solution. Some solutions may modify characters that you do not want to be changed, while others may not handle all special characters. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******