In our testing we have noticed that the Mandarin character 姵 does not appear to be supported by version 7.6. At runtime we see a box instead of this character, no matter which font is in use. Previously we were able to use Arial Unicode MS to generate missing characters like this one, but now we’ve noticed that where that font is in use, our data doesn’t actually appear at runtime.
Hi Elizabeth,
Hi Elizabeth,
//Create pdf document<o:p></o:p>
Aspose.Pdf.Generator.Pdf pdf1 = new Aspose.Pdf.Generator.Pdf();
//Add a section into the pdf document
Aspose.Pdf.Generator.Section sec1 = pdf1.Sections.Add();
// create text object with Maradian characters
Text text1 = new Aspose.Pdf.Generator.Text("Hello World 筆記本在這邊。");
//set font for text object
text1.TextInfo.FontName = "Arial Unicode MS";
//Add a text paragraph into the section
sec1.Paragraphs.Add(text1);
pdf1.SetUnicode();
//Save the document
pdf1.Save("c:/pdftest/Mandarian_Characters_HelloWorld.pdf");
Hi codewarior,
<span style=“font-size:10.0pt;line-height:115%;font-family:
“PMingLiU”,“serif”;mso-bidi-font-family:PMingLiU”><o:p></o:p>
eplumley:Hi codewarior,Thanks kindly for your response - can you please try the specific character 姵? We are having an issue with that specific character, regardless of the font used.Hi Elizabeth,I have again tested the scenario using upcoming release version of Aspose.Pdf for .NET 7.7.0 and as per my observations, the character is properly appearing in resultant PDF file. See attached PDF file.In case the problem still persists, please feel free to contact.PS, We plan to release the new version in current week.
Thanks kindly. Did you check against 7.6 as well?
Hi Elizabeth,
Hello again;
Hi there,
Please accept our apology for delayed response. I have tested the scenario again with your source document but unfortunately I'm unable to reproduce the issue. Could you please provide a sample project here for reproducing the issue? So we test it at our side and provide you more information accordingly.
Sorry for the inconvenience faced.
Best Regards,
Confirmed this is corrected in version 7.7.
Hi Elizabeth,