Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Special characters not properly handled in RichTextEditor



Special characters getting converted to ASCII values and HTML tags are appended on submit from RichTextEditor. On submitting responses from a RichTextEditor containing special characters (E.g. Single quote(‘), double quotes (“) ) and words from other languages like- interés, información and so on, the special characters are getting replaced by their corresponding ASCII values when mapped to a text type property also, HTML tags are getting appended.
E.g. - interés- interés
Información- Información

Error Messages

Not applicable

Steps to Reproduce

1. Add a pxRichTextEditor control in a section within a dynamic layout and map it to a Text type property.
2. Add a text containing special characters (E.g. Apreciamos su interés en e’l programa’, Para obtener mas información favor de ingresar la pagina””)
3. Submit.
4. Check the property value from clipboard.

Root Cause

A defect in Pegasystems’ code or rules


This is an expected behaviour.

CKEditor is the RichTextEditor that is provided as OOTB in PRPC. Since the CKEditor markup is built on client by the third party CKEditor JavaScript, CKEditor UI translations are done in a different manner.

Test this by going on the demo website:
1) Enter the Spanish content and click on the Source button.

Published August 26, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us