[xep-support] Re: Inexplicable problem with font family

From: Vladyslav Sivyakov <vsivyakov_at_ADDRESS_REMOVED>
Date: Wed Aug 26 2020 - 11:19:40 PDT

Hello Jim,

Not sure if you received our answer to your request for a professional
support, so copying here to let you know and to inform other readers who
may have encountered a similar problem.

Here are some guesses about what can cause the problem. I'm sure this
must be caused by some simple typo in a config. Let's double-check this
first before we get into deeper analysis.

  1.   If you've recently migrated, make sure that you are editing the
     config of the very instance you've just installed. There can be two
     instances of XEP installed, say, in Program Files and Program Files
     (x86). You mentioned an incorrect classpath, and this can be the
     case if you have two XEPs installed.
  2. When you migrated to the new laptop, have you copied your existing
     xep.xml config file from the old laptop to the new one,
     or you just left the default config as it was created by XEP
     installer? By default, the "Windows TrueType"group is commented out
     in xep.xml config file. Could it be that you just make edits within
     the comment block?
  3. Check if any other font belonging to the same font-groupworks with
     XEP (there are several listed, and Tahoma is best for checking). It
     can be a simple typo in path or filename which causes XEP not find
     the file.
  4. Since a while, Windows 10 and other Microsoft products (e.g. Office)
     does not include Arial Uni MS. So I assume you've obtained the font
     elsewhere. Please make sure the TTF file is not broken. An easy way
     to check is opening C:\Windows\Fonts directory and seeing if it can
     be previewed. Alternatively, use any Windows editor and check if it
     can use that font at all.
     We have checked with 'ARIALUNI.TTF'; size 23,275,81; md5sum
     91f4475d007aa64dd9a0e79927f3d095, and it worked fine.

Also, we can reproduce this problem if you send us your configuration
files. Please just make sure you're sending it to our support system,
not in a public mailing list.

Best regards,
Vladyslav Sivyakov, RenderX.

On 17.08.2020 03:05, Jim Melton wrote:
> Dear RenderX,
> I have used XEP for a couple of decades to produce an ISO/IEC
> international standard; your organization was kind enough to provide
> me and a small handful of my fellow editors (in ISO/IEC JTC 1/SC 32) a
> license to use XEP all these years.
> Very recently, two of us (me and Jörn Bartels, copied on this message)
> have acquired and configured new laptop computers.  Both of us
> encountered a very strange problem that caused an error message to be
> issued whenever we attempt to transform a .fo file into .pdf if the
> document uses Arial Unicode MS.
> The error that we get is:
> could not find any font family matching "ArialUnicodeMS"; replaced
> by Helvetica
> Both of our xep.xml files contain a font-group thus:
> <font-group xml:base="file:/C:/Windows/Fonts/"label="Windows
> TrueType"embed="true"subset="true">
> In that font-group, we both have the following:
> <font-family name="ArialUnicodeMS">
> <font><font-data ttf="ARIALUNI.ttf"/></font>
> </font-family>
> Both of us definitely have this font, using that exact font name
> (including capitalization), instlled in ...\windows\fonts\  The
> installed font shows in that directory as "Arial Unicode MS Regular".
> On my new laptop, I eventually created a new font-group:
> <font-group xml:base="file:/D:/RenderX/fonts/ttf/"label="Windows
> TrueType"embed="true"subset="true">
> and moved the font-family lines (shown above) into that new
> font-group; I also coped the font file ARIALUNI.ttf into the directory
> D:\RenderX\fonts\ttf\.  This "cured" the problem on my laptop,
> although I absolutely cannot figure out why.
> Unfortunately, my colleague Jörn Bartels did exactly the same thing on
> his new laptop, and he continues to have the problem of getting that
> error message.
> Can you help us figure out WHY this happens only on our new Windows 10
> laptops and HOW we can fix the problem on Jörn's computer?
> Many thanks,
>    Jim
> --
> Jim Melton SheltieJim at xmission dot com
> -------------------------------------------
> Owner and Captain:
> Passport 40 #018 Dream SeQueL
> Co-Owner and Co-Captain:
> Passport 42 #040 Turtle Blues
> -------------------------------------------
> Shelties since 1969; ASSA member since 1992
> _______________________________________________
> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
> (*) By using the Service, you expressly agree to these Terms of Service http://w
> ww.renderx.com/terms-of-service.html

(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
Received on Wed Aug 26 11:20:54 2020

This archive was generated by hypermail 2.1.8 : Wed Aug 26 2020 - 11:21:09 PDT