Khmer Font issue

Aspose.Cells Product Family
1

I’m using Aspose.Cells v23.3.0 for convert excel to image on window,but Khmer font could not display properly. I have installed Khmer font on Windows\Fonts file, and checked excel font is correct.

2

@yuuro can you please attach your source file for review and test.

3

ImageOrPrintOptions options = new ImageOrPrintOptions();
options.CheckWorkbookDefaultFont = true;
options.DefaultFont = “Khmer OS Content”;
options.IsCellAutoFit = true;
options.OnePagePerSheet = true;
options.ImageType = Drawing.ImageType.Jpeg;

SheetRender sr = new SheetRender(sheet, options);
sr.ToImage(0, output+ “.jpg”);

4

@yuuro,

Thanks for the sample code segment.

We also need your input Excel file. Please zip and attach it here. We will check your issue soon.

5

@yuuro
Please share Khmer font here too, we need it to check this issue.

6

iussefile.zip (16.3 KB)

7

file.zip (1.6 MB)

8

@yuuro,
After installing the font, we can obtain the correct results by running the following code. Please check the attachment.result.png (111.9 KB)

Workbook wb = new Workbook(filePath + "template.xlsx");
ImageOrPrintOptions options = new ImageOrPrintOptions();
options.CheckWorkbookDefaultFont = true;
options.DefaultFont = "Khmer OS Content";
options.IsCellAutoFit = true;
options.OnePagePerSheet = true;
options.ImageType = ImageType.Jpeg;
Worksheet sheet = wb.Worksheets[0];
SheetRender sr = new SheetRender(sheet, options);
sr.ToImage(0, filePath + "out.jpg");
9

did you add any sheetsettings code？

10

@yuuro,
I don’t have any other settings, just ran the sample code I posted in the post.

11

@yuuro
1, Could you get correct result as your excepted with codes in Khmer Font issue - #8 by John.He

2, If you has issue about adding some sheetsettings ,please share your sample project , we will check it soon.

12

I find the problem after version 22.9.0, It is available before this version

13

It’s ok, I have solved this problem. It doesn’t work on after version 22.9.0

14

@yuuro,
I’m glad your issue has been solved. If you have any questions, please feel free to contact us. Regarding the latest version 23.3, we are currently unable to reproduce the issue. Once we reproduce the issue, we will fix it as soon as possible.