Add support for non-latin characters

Non-latin characters support in form fields, including signature, was actually introduced to on-premise customers in the fall of 2015 and should be available to our cloud customers any day now with the upcoming deployment of the Spring 2016 release. Of course the Signing and Sending user interfaces have been available in a number of languages for some time, however the eSignLive front end Application didn’t support entering and rendering form fields data (including signatures) in non-latin character sets/fonts in both the actual documents and the evidence summary. The product was enhanced to leverage the transaction level language attribute (available programmatically). A transaction flagged as Simplified Chinese for e.g. would ensure that the Document Engine uses the installed default Simplified Chinese font.

Of course the Signing and Sending user interfaces have been available in a number of languages for some time, however the eSignLive front end Application didn’t support entering and rendering form fields data (including signatures) in non-latin character sets/fonts in both the actual documents and the evidence summary.

Just a quick note. I noticed, that non-latin characters are working while signing the document. The signed PDF is fine. The only issue left is the summary (see attachment).