Aspose Docker onPremise approach is not rendering the characters properly

Aspose.Words Cloud Product Family
1

Hi, We are trying to convert a document to pdf, enabling the opentypesupport to true

Using cloud : nodejs module, its working fine,

But for the onPremise approach its not rendering the characters properly:
http://aspose-words-cloud.document-service-backend-qa.svc.cluster.local/v4/words/convert?format=pdf&fileNameFieldValue=sourceFilename&opentypesupport=true

we upgraded the docker image to 24.9
image: docker.io/aspose/words-cloud:24.9

Please suggest what to do on this, We have KhmerUI.ttf, LeelawadeUI.ttf fonts in the fonts folder aswell

the pdf we got from onPremise approach:
test-combodian-70bb2490d9726318-n5pu44.pdf (123.0 KB)

the pdf supposed to look like:
TestWordsCloud2686 Out.pdf (167.9 KB)

the docx file used for this:
INVOICE TEMPLATE 1 - Edited (1).docx (67.7 KB)

2

What OS do you use? Please share your setup where you run our service for us to test in the same environment.

3

apiVersion: apps/v1
kind: Deployment
metadata:
name: aspose-words-cloud
spec:
replicas: 2
selector:
matchLabels:
app: aspose-words-cloud
template:
metadata:
labels:
app: aspose-words-cloud
spec:
volumes:
- name: aspose-mount
persistentVolumeClaim:
claimName: asposePVC
containers:
- name: aspose-words-cloud
image: docker.io/aspose/words-cloud:24.9
imagePullPolicy: Always
# envFrom:
# - configMapRef:
# name: asposewordscloudappconfig
env:
- name: LicensePrivateKey
valueFrom:
secretKeyRef:
name: document-service-secrets
key: LicensePrivateKey
- name: LicensePublicKey
valueFrom:
secretKeyRef:
name: document-service-secrets
key: LicensePublicKey
resources:
requests:
cpu: requestCPU
memory: requestMemory
limits:
cpu: limitCPU
memory: limitMemory
ports:
- containerPort: 80
volumeMounts:
- mountPath: “/fonts”
name: aspose-mount
subPath: backend/data/appdata/fonts
- mountPath: “/data”
name: aspose-mount
subPath: backend/data/appdata/data

we deploy this pod seperately in linux environment

4

Thanks for sharing the information; what distribution do you use as Linux? Ubuntu? Debian?

5

We are using Ubuntu 22.04.4 LTS

6

Thank you for sharing additional information. We will test it on Ubuntu 22.04

7

Hi Team, did we find the solution for this?

8

Not yet, could you please send me your versions of Fonts you use via DM.

9

fonts.zip (349.4 KB)

10

Thank you for sharing the fonts.

11

I found out that the problem is not in the fonts you share but in other fonts in your document, like Arial and Calibri(body). That’s why you get incorrect results; once I uploaded this font, it started rendering fine but still has differences.
I attached result document from our ubuntu machine
sourceFilename.pdf (162.3 KB)

12

Yes the pdf is as expected,

what addidtional settings needs to be configured?

we added the flag:
http://aspose-words-cloud.document-service-backend-qa.svc.cluster.local/v4/words/convert?format=pdf&fileNameFieldValue=sourceFilename&opentypesupport=true

we upgraded the docker image to 24.9
image: docker.io/aspose/words-cloud:24.9

13

There is nothing to configure. You should add Arial and Calibri fonts to the fonts folder along with your other fonts.

14

I am not able to render some of the characters properly after adding all the fonts, its the same response without the opentypesupport = true

what should i do?

15

I tested with these fonts, you should check if they work for you, and for sure, you have to set opentypesupport=true
arial.zip (3.7 MB)

fonnts.com-219496.zip (2.5 MB)