Converting Document to PDF containing Japanese characters results in blocks

Aspose.Words Product Family
1

Hi,

We are going through the final test cycle before releasing our product and unfortunately we have found a problem impacting one of the key audiences of our product.

It appears that when loading an MS-Word file (See attached) that contains Japanese characters (and possibly other double byte languages as well) and saving it as PDF (See attached) all Japanese characters become squares.

We are using the latest Aspose.Words 6.1.0.0 and the new PDF Renderer.

The document uses the ‘MS Mincho’ font for the Japanese text. This font is available on the machine doing the conversions. We have tested it on Windows Server 2008 as well as Windows Server 2003.

The same happens when we convert a plain ‘notepad’ txt file containing japanese text. Both files have been attached as well.

BTW, Is there any chance my other issues / posting from jarit@xs4all.nl can be moved to this new company account (jritmeijer@muhimbi.com)?

Regards,

Jeroen

2

This issue appears to be related:

Aspose.Words V6.0.1 issue: Save to PDF fails

3

Hi
Thanks for your request. Yes, this is the same problem. I will notify you as soon as it is fixed.
Best regards.

4

So, is this for all ‘double byte’ languages? Do you have a list of languages impacted by this as we will need to inform our customers?

5

Hi

Thanks for your inquiry. I cannot provide you a list of languages, because some documents are converted without issues and some documents are converted with squares instead hieroglyphs. We will further investigate the problem and provide you more information.
Best regards.

6

The issues you have found earlier (filed as 7458) have been fixed in this update.

This message was posted using Notification2Forum from Downloads module by alexey.noskov.

7

This appears to work. However, we have found a new issue, which we have reported at.
https://forum.aspose.com/t/japanese-text-doesnt-break-to-the-next-line-in-table-cells/94442

8

We are currently carrying out regression tests and it appears that this issue (7458) still happens on Windows Server 2003. It apears to work fine on Windows Server 2008.
Note that on boths systems the correct fonts (msmincho) are installed

9

Hi

Thanks for your request. I cannot reproduce the problem on my side. I tested conversion on Win 2003 server and all works fine. Could you please attach “msmincho” font installed on your Win 2003, maybe there is some difference.
Best regards.

10

Attached is the font installed on our 2003 servers, which is a default US Version of Windows Server 2003, with Asian support enabled.

We have also tried installing the fonts from our 2008 server on this machine, but we didn’t see any difference. Is there perhaps some other configuration we missed?

11

Hi

Thank you for additional information. Aspose.Words does not support TTC (True Type Collection) fonts during converting to PDF and Rendering. Therefore, this font cannot be the reason of the problem.
However, I managed to reproduce the problem on my side. It seems there is no TTF font “MS Mincho” on your Win 2003 server. Please try to install attached font on your server and let me know whether this helps.
Best regards.

12

I have no access to that server at the moment, but to the best of my knowledge it is a clean Windows Server 2003 installation.

So, if I understand correctly I need to tell my customers to install all fonts that they commonly use in their document on the server in TrueType format? What will happen when a font is not present, will it attempt to do any kind of font substitution?

13

Yes, all fonts used in your document should be installed as True Type or Open Type fonts. If Aspose.Words cannot find some font, it tries to find an alternative font, if it cannot find an alternative font – it uses default font (Times New Roman).

Best regards.