eForm ouput dose not show Japanese characters but English
[Issue]
We can create eForm PDF but Japanease characters do not show on mapping field. Please see attached outputs.
Moreover, strangely we could could see Japanease characters if we click on editable filed on PDF but not able to see it witout clicking it.
[Questions] * Please check this with SME
Q1. Is it OK to use PDFescape (https://www.pdfescape.com/) to create PDF tempate? We do not have Adobe editor and using this free ware for this since we do not have licese of Adobe.
Q2. PerformFieldFlattering check of Code-Pega-eForm.ConcatenateEforms work with double-bytes characters? This is because once we use PerformFieldFlattering check, then we can not see Japanese characters at all on PDF. It disapears totally.
[Details]
We use 1) Call Code-Pega-eForm.GetEFormFromRuleFileEForm , 2) Call GenerateEform, 3) Call Code-Pega-eForm.ConcatenateEforms, 4) Call Work-.AttachEForm and there are no error and running fine.
The problem is only output PDF. We need to pass Japanese characters to output PDF.
I found following document and it mentioned about fonts however, I am not sure where we can set fonts in the template file.
https://collaborate.pega.com/question/pdf-eforms-generation-does-not-work-russian-characters
[Issue]
We can create eForm PDF but Japanease characters do not show on mapping field. Please see attached outputs.
Moreover, strangely we could could see Japanease characters if we click on editable filed on PDF but not able to see it witout clicking it.
[Questions] * Please check this with SME
Q1. Is it OK to use PDFescape (https://www.pdfescape.com/) to create PDF tempate? We do not have Adobe editor and using this free ware for this since we do not have licese of Adobe.
Q2. PerformFieldFlattering check of Code-Pega-eForm.ConcatenateEforms work with double-bytes characters? This is because once we use PerformFieldFlattering check, then we can not see Japanese characters at all on PDF. It disapears totally.
[Details]
We use 1) Call Code-Pega-eForm.GetEFormFromRuleFileEForm , 2) Call GenerateEform, 3) Call Code-Pega-eForm.ConcatenateEforms, 4) Call Work-.AttachEForm and there are no error and running fine.
The problem is only output PDF. We need to pass Japanese characters to output PDF.
I found following document and it mentioned about fonts however, I am not sure where we can set fonts in the template file.
https://collaborate.pega.com/question/pdf-eforms-generation-does-not-work-russian-characters
***Updated by Moderator: Lochan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option; updated Category***
Accepted Solution
Pegasystems Inc.
IN
Hello,
Upon reviewing the corresponding SR, we see that it has been resolved. SA-27342 was created as a result of the investigation. Please reference that if you have the same question.
Regards,
Lochan | Online Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US
What version of Pega are you using when you have this issue?
Can you confirm that:the japanese characters are missing only when flattening is performed?
It seems like the fields' read-only style could be causing the problem. If the PDF template does not define these styles, I can only assume that a default style is applied... and that might not support the characters?
Pegasystems Inc.
AU
>What version of Pega are you using when you have this issue?
A: Pega 7.2.0
>Can you confirm that:the japanese characters are missing only when flattening is performed?
A: As I have mentioned (see 2016Aug02-PDF-JPIssue-output.jpg), there are 2 issues.
Issue 1: Japanese characters are hidden behind fields in eFrom PDF with Editable mode. And not able to print out because of these are hidden.
Issue 2: Japanese characters are not showing in eForm PDF with ReadOnly mode.
I had attached the template file (New_Test3.pdf) for this issue, which was created by PDFescape.
Appricate your advice if you have any idea. I will check this issue more, then I might submit SR if this seems to be a bug.
Accepted Solution
Pegasystems Inc.
IN
Hello,
Upon reviewing the corresponding SR, we see that it has been resolved. SA-27342 was created as a result of the investigation. Please reference that if you have the same question.
Regards,
Lochan | Online Community Moderator | Pegasystems Inc.