We are using Arial Unicode MS without issue in Prince 9, but are testing Prince 10 and the font is no longer being rendered.

We have tried setting the specific .ttf file via @font-face, specifying the precise location of the file in /usr/share/fonts/ and confirming file permissions are the same, all to no avail.

Is there a new step or configuration required for Prince 10 to make this work?

There should be no issue with Arial Unicode MS, can you run Prince with the --debug option and attach the output log?

Here's the output.
I can see that the font hasn't been matched, but I'm not sure why, as it's in the same location and same filename as our Prince 9 server.

prince: debug: loading license: /usr/lib/prince/license/license.dat
prince: loading document: /usr/lib/prince/license/license.dat
prince: debug: loaded resource: /usr/lib/prince/license/license.dat
prince: debug: loaded resource: type: no
prince: loading style sheet: /usr/lib/prince/style/fonts.css
prince: debug: loaded resource: /usr/lib/prince/style/fonts.css
prince: debug: loaded resource: type: no
prince: Loading document...
prince: debug: starting prefetch threads
prince: loading XML input: test.php
prince: loading document: test.php
prince: debug: loaded resource: test.php
prince: debug: loaded resource: type: no
prince: debug: loaded document: test.php
prince: debug: sniffed doctype: XML
prince: Applying style sheets...
prince: loading style sheet: /usr/lib/prince/style/xhtml-ns.css
prince: debug: loaded resource: /usr/lib/prince/style/xhtml-ns.css
prince: debug: loaded resource: type: no
prince: loading style sheet: /usr/lib/prince/style/common.css
prince: debug: loaded resource: /usr/lib/prince/style/common.css
prince: debug: loaded resource: type: no
prince: loading style sheet: /usr/lib/prince/style/hyph.css
prince: debug: loaded resource: /usr/lib/prince/style/hyph.css
prince: debug: loaded resource: type: no
prince: loading style sheet: /usr/lib/prince/style/mathml.css
prince: debug: loaded resource: /usr/lib/prince/style/mathml.css
prince: debug: loaded resource: type: no
prince: loading style sheet: /usr/lib/prince/style/svg.css
prince: debug: loaded resource: /usr/lib/prince/style/svg.css
prince: debug: loaded resource: type: no
prince: loading style sheet: style.css
prince: debug: loaded resource: style.css
prince: debug: loaded resource: type: no
prince: Preparing document...
prince: debug: stopping prefetch threads
prince: Converting document...
prince: debug: pack
prince: debug: font request: Arial Unicode MS
prince: debug: font scan: Arial Unicode MS
prince: debug: font scan: Arial Unicode MS, 0 matches
prince: debug: font scan: Times New Roman
prince: debug: font scan: Times New Roman, 8 matches
prince: debug: font scan: DejaVu Serif
prince: debug: font scan: DejaVu Serif, 2 matches
prince: debug: font scan: DejaVu LGC Serif
prince: debug: font scan: DejaVu LGC Serif, 0 matches
prince: debug: font scan: Liberation Serif
prince: debug: font scan: Liberation Serif, 4 matches
prince: debug: font scan: OpenSymbol
prince: debug: font scan: OpenSymbol, 0 matches
prince: debug: font scan: AR PL UMing CN
prince: debug: font scan: AR PL UMing CN, 0 matches
prince: debug: font scan: AR PL SungtiL GB
prince: debug: font scan: AR PL SungtiL GB, 0 matches
prince: debug: font scan: Kochi Mincho
prince: debug: font scan: Kochi Mincho, 2 matches
prince: debug: font scan: Lohit Hindi
prince: debug: font scan: Lohit Hindi, 0 matches
prince: debug: font scan: Ani
prince: debug: font scan: Ani, 0 matches
prince: debug: font scan: Mukti Narrow
prince: debug: font scan: Mukti Narrow, 0 matches
prince: debug: font scan: Lohit Punjabi
prince: debug: font scan: Lohit Punjabi, 0 matches
prince: debug: font scan: Lohit Gujarati
prince: debug: font scan: Lohit Gujarati, 0 matches
prince: debug: font scan: Lohit Tamil
prince: debug: font scan: Lohit Tamil, 0 matches
prince: debug: font scan: Lohit Telugu
prince: debug: font scan: Lohit Telugu, 0 matches
prince: debug: font scan: Lohit Kannada
prince: debug: font scan: Lohit Kannada, 0 matches
prince: debug: font scan: MalOtf
prince: debug: font scan: MalOtf, 0 matches
prince: debug: font scan: Lohit Oriya
prince: debug: font scan: Lohit Oriya, 0 matches
prince: debug: font scan: Garuda
prince: debug: font scan: Garuda, 0 matches
prince: used font: Times New Roman, Regular
prince: debug: writing output: test.pdf
prince: Finished: success

Edited 22 Sep 2015 by elvanto

Does "Arial Unicode MS" show up if you run fc-list?

Do you get similar results with a very simple document, eg.

<html>
<body style="font-family: Arial Unicode MS">
Hello
</body>
</html>

I ran 'fc-list' it showed up successfully!
I ran another test using both the example you provided and using a separate stylesheet like I tried previously and it worked both times.

Whatever the issue, it now seems to be resolved.
Thanks for your help!

debug: loaded resource: type: no
does this mean that the resource did not load?
I am working with some .tif files.
I got my .tif files loaded okay. l was given the wrong folder. But I still wonder what the 'no' type means. It gives me the impression that there is something wrong but apparently that is not right.

Jim Albright
Wycliffe Bible Translators

Edited 22 Mar 2016 by jim_albright

That just means no content-type header was available or specified, typically for local file resources, not remote HTTP resources.

Saying something beyond the cryptic 'no' would be helpful.

Jim Albright
Wycliffe Bible Translators

Well it is a debug message, they are all very cryptic!

Perhaps we can reword it to make it clearer.