I think this one has been queried a few times. We are testing unicode support and some font files that we are importing from google dont have certain unicode characters and as such princexml is replacing them with "?" - we have the font-family set to "Abeezee, Arial" - its not trying to fallback to the arial font which does contain the unicode glyph. Is this correct that its not trying the second font? Or am I missing something?
It should definitely be using the second font. Which Unicode character is involved? Perhaps it is not in Arial, either. There is a separate font called "Arial Unicode MS" which has a wider character range, if you have it installed.
Will test now with "Arial Unicode MS" and see where we get to. Is there a way to have a setting for fallback like @prince-glyph-fallback { font: "Arial Unicode MS"; }
This will automate the fallback as such so we dont have to manually set css
Okay this is an Arabic character. Different platforms have different fonts that support Arabic. For example, Times New Roman supports Arabic on Linux and Windows, but not on MacOS X.
Prince includes a fonts.css file in the style directory of the installation. This defines the default serif and sans-serif font families. You can add @font-face rules to this if you wish to use specific fonts. On Windows platforms, it already includes Arial Unicode MS as a last resort font.
its running on centos 6.6 and msttcorefonts is installed. I tried setting all the font-family inline css to Times New Roman but still get the ? and times new roman should support that?
Am i correct in saying the system will try use the font-family CSS fonts list first...if they all fail it will then try the prince sans-serif and serif fallback fonts and then as a last resort replace it with a "?" ?
So if i was to get a unicode fallback font and set @font-face serif and sans-serif to that i could make sure it finds it?
Strange...by putting this in the <head> section it fixed the problem and started to work
@font-face { font-family: sans-serif; src: local('Times New Roman') }
@font-face { font-family: serif; src: local('Times New Roman') }
Even despite that being inside of the fonts.css file that ships with the install. even putting times new roman as the css style it was broke. Pity dont know what was causing the problem though
There is a few @import happening from google fonts. I will debug using the svg and trying without @font-face in the head to see if it does a fallback as it was meant to. Will let you know tomorrow on this test