Blank spaces displayed when using japaese or chinese symbols

We are using aspose to merge pdfs into single pdf. If the headlines are in japanese or chinese, in the table of contents, headlines of the documents the japanese and chinese characters are shown as blank. The fonts required for the japanese,chinese characters are present on the server.

@tejaac

Would you please share some additional information like sample code snippet and sample files to replicate the issue in our environment. We will further proceed accordingly.

I am seeing this in the merged table of contents. I cannot share the actual files out of the organisation.

image.png (17.9 KB)
sampledocs.zip (523 Bytes)

@tejaac

There is non-English text in both text files that you shared. Do you mean that these characters are not being rendered correctly when merging two documents into one?

yes they are showing blank spaces, when the merging is done, In the table of contents.

@tejaac

We are checking it and will get back to you shortly.

also in the on-prem environment this is working fine. but in cloud only its showing blank spaces.

@tejaac

We are moving this thread to respective category where you will be assisted according to Cloud APIs.

i have a question though do we need to install anything else for cloud environment?

Hi, @tejaac
Can you share details (font names, curl requests or code snippets, cloud storage type) and steps to reproduce the issue?

Hi @kirill.novinskiy ,

We cannot share the files outside the organisation. but I already sent sample docs with the chinese text. The fonts we are using are MS Gothic Regular, MS PGothic Regular, MS UI Gothic Regular, Yu Gothic, Yu Gothic UI, SimSun Regular, SimSun-ExtB Regular, SimSun-ExtG Regular, Arial Unicode MS Regular for japanes and chinese characters. These are the same fonts on on-prem and cloud environments.

backgroud : We are merging 2 pdfs having chinese or Japanese Fonts into 1 pdf, and when its merged in the table of contents page the headlines of the documents are displayed but in the place of Japanese and Chinese characters blank spaces are being displayed. in the on-prem envrionment everything is working fine. In the cloud only its not working properly. We are using aspose.pdf 7.0 version dll for this.

@tejaac
We have noticed the reported issues and logged the following tickets in our issue tracking system for further investigation and rectification. We will notify you as soon as these issues are resolved.

PDFCLOUD-4715:Blank spaces displayed when using japaese or chinese languages.

Could you please let me know if there is any update on this? This is happening in cloud environment and we have all fonts in the fonts folder on the cloud environment

@tejaac
Yes, we are investigating the issue and have generated several test PDF documents based on the text documents you provided and merged them using the Aspose PDF Cloud API. We have not been able to reproduce the issue yet, but we are trying different options. You can speed up the process if you provide examples of PDF documents that do not display characters after merging and code snippet will be very helpful.

@tejaac
Hello, during the investigation two files were created based on the provided text files and they were merged using the PDF Cloud API. The result PDF document is attached as input PDF documents, all symbols are displayed correctly. Please provide more details to reproduce the problem.
sample2.pdf (499.0 KB)

sample1.pdf (208.7 KB)

output.pdf (706.9 KB)

I have a question for cloud we cannot use the aspose pdf that we are using for on prem? We need to use the aspose pdf cloud api instead of aspose.pdf for .net?

@tejaac
You can use either cloud or on-premise solution depending on your goals. Provide more details about what the problem is.

samplecode.zip (566 Bytes)

please find the sample code we are using when creating the pdf

@tejaac
Do I understand correctly that the file generated by the script is uploaded to the cloud and then merged with a similar file using the cloud API merge method?

no after merging both files this piece of codr is used to create table of contents, where the issue is happening.
we are not using cloud api, we are using on-prem aspose.pdf dll only