DITA and XMetaL Discussion
XMetaL Community Forum › DITA and XMetaL Discussion › Could not find any font family matching…
AndrewinKC May 17, 2010 at 7:50 pm
Could not find any font family matching…May 17, 2010 at 7:50 pmParticipants 3Replies 4Last Activity 12 years, 10 months ago
One of our teammates has an issue where all fonts in the document are replaced with Helvetica. I reviewed the Output log file and found a few lines that referred to transform.fo2xmpf.xep. The log file also contains warnings stating it cannot find a font family matching (TimesNewRoman, Arial, and Inconsolota).
I tried removing and then reinstalling the Inconsolota font. Still got the same issue.
Does anyone have any ideas on what we can do to fix this???
AndrewinKCAndrewinKC May 17, 2010 at 7:51 pm
Reply to: Could not find any font family matching…May 17, 2010 at 7:51 pm
BTW – we are using XMetaL Author 5.5.Derek Read May 17, 2010 at 8:36 pm
Reply to: Could not find any font family matching…May 17, 2010 at 8:36 pm
If a font called “Inconsolota” is being suggested that means the DITA OT has already been customized (as it is not mentioned anywhere in the standard DITA files). I'm not sure about the “transform.fo2xmpf.xep” bit, however, the first place I would look is in this file to see if RenderX knows where to find your fonts:
%appdata%SoftQuadXMetaL Sharedrenderxxep.xmlAndrewinKC May 17, 2010 at 8:48 pm
Reply to: Could not find any font family matching…May 17, 2010 at 8:48 pm
Yes, we have customized the print transforms to look like the guides we create using MS-Word (and a custom template).
I'll take a look at the .xep file and compare it to the file on my PC (where everything seems to work fine).
Thanks!AndrewinKC May 18, 2010 at 11:41 am
Reply to: Could not find any font family matching…May 18, 2010 at 11:41 am
I found a number of differences between the xep.xml file from my machine and my coworker. I replaced the file from her machine with a copy from mine.
We'll see if this fixes the problem.
Thanks for the quick reply.
- You must be logged in to reply to this topic.