The following is logged when trying to print italicized Arabic and Farsi characters on Windows 10 and Windows Server 2016.

Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0645, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0627, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0647, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+064A, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0623, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0633, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062A, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0644, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0643, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0635, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062D, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0642, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0628, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+061F, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0630, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0646, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062C, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0639, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0631, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+064B, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0648, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0641, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062E, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0629, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062F, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0637, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+063A, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0649, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+062B, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0632, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+060C, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0636, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0625, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0621, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0634, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0626, fallback to '?'
Tue Jul 30 15:49:07 2019: page 1: warning: no font for Arabic character U+0622, fallback to '?'

Are italics relevant to Arabic or Farsi?

If italics are relevant could I get some guidance on how to resolve this issue?

1. TestDoc_AR_US.html‎ 12.5 kB ‎
   Here is the file I am using for testing.

Is non-italic Arabic text working for you?

Hi Mike... yes non italic works fine. If I change the i tags to spans it also works (I assume I can update styles to add the italics). The downside of this work around is we will have to covert the i tags to spans upon print for the affected languages.

Which version of Prince are you using?

Hi Mike,

We are using the .NET Wrapper, version 2.0.0.0. I will see if I can find the version of the engine, it doesn't show up in the properties when I right click the exe file. However, we see this same behavior with the latest version of prince as well.

I attached an example which can be used to reproduce the issue.

Edited 6 Aug 2019 by mprice

We are currently using version 12.2 in production.

Edited 6 Aug 2019 by mprice

Thanks, I'm just puzzling over why this isn't working as I could have sworn we addressed the italic Arabic issue years ago.

Edited 7 Aug 2019 by mikeday

Apparently not, but there is a possible solution we are exploring. In the meantime I'm afraid it will be necessary to either disable italics for the Arabic text, or specify a specific Arabic font family.

Mike,

Thanks for the feedback. Do you have any recommendations on an Arabic font family for Windows?

Actually we have a fix for this issue now and can provide an updated Prince build shortly.

This is fantastic. How do I get hold of the new build?

The latest build is now available and includes the fix.

Thanks Mike! I'll give it a go and report back.