While in the second PDF, only the font of Non-Breaking Hyphen has changed. As you can see in the first PDF, the font of the entire sentence has changed from Times New Roman to Arial Unicode MS because of Non-Breaking Hyphen. One was generated without setting tFontSubstitutionCharGranularity() property and the other was generated after setting the tFontSubstitutionCharGranularity() property to true. The following screenshot compares the two output PDFs generated by the sample code below. To deal with this problem, Aspose.Cells provides tFontSubstitutionCharGranularity() property which should be set true so that only the font of the specific character which is not displayable is changed and the font for the rest of the word or sentence remains the same. ![]() However, this is undesirable behavior for some users and they want only that the specific character’s font must be changed instead of changing the font of the entire word or sentence. When such a character occurs inside some word or sentence which is in some specific font like Times New Roman, then Aspose.Cells changes the font of the entire word or sentence to font which could display this character like Arial Unicode to MS. Some font files have some but not all subsets with characters rotated by 90 degrees. This character cannot be displayed with Times New Roman, but it can be displayed with other fonts like Arial Unicode MS. ![]() One such Unicode character is Non-breaking Hyphen (U+2011) and its Unicode number is 8209. Some Unicode characters are not displayable by the user-specified font.
0 Comments
Leave a Reply. |