<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello Jim,</p>
<p> 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.</p>
<p>Here are some guesses about what can cause the problem. I'm sure
this <br>
must be caused by some simple typo in a config. Let's double-check
this <br>
first before we get into deeper analysis.<br>
<br>
1. If you've recently migrated, make sure that you are editing
the<br>
config of the very instance you've just installed. There can
be two<br>
instances of XEP installed, say, in Program Files and Program
Files<br>
(x86). You mentioned an incorrect classpath, and this can be
the<br>
case if you have two XEPs installed.<br>
2. When you migrated to the new laptop, have you copied your
existing<br>
xep.xml config file from the old laptop to the new one,<br>
or you just left the default config as it was created by XEP<br>
installer? By default, the "Windows TrueType"group is
commented out<br>
in xep.xml config file. Could it be that you just make edits
within<br>
the comment block?<br>
3. Check if any other font belonging to the same font-groupworks
with<br>
XEP (there are several listed, and Tahoma is best for
checking). It<br>
can be a simple typo in path or filename which causes XEP not
find<br>
the file.<br>
4. Since a while, Windows 10 and other Microsoft products (e.g.
Office)<br>
does not include Arial Uni MS. So I assume you've obtained the
font<br>
elsewhere. Please make sure the TTF file is not broken. An
easy way<br>
to check is opening C:\Windows\Fonts directory and seeing if
it can<br>
be previewed. Alternatively, use any Windows editor and check
if it<br>
can use that font at all.<br>
We have checked with 'ARIALUNI.TTF'; size 23,275,81; md5sum<br>
91f4475d007aa64dd9a0e79927f3d095, and it worked fine.</p>
<p>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.<br>
</p>
<pre class="moz-signature" cols="72">Best regards,
Vladyslav Sivyakov, RenderX.</pre>
<div class="moz-cite-prefix">On 17.08.2020 03:05, Jim Melton wrote:<br>
</div>
<blockquote type="cite"
cite="mid:9055fb97-e019-7b2a-a1eb-eb2e6ed97d35@xmission.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<p><tt>Dear RenderX,</tt></p>
<p><tt>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.
<br>
</tt></p>
<p><tt>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. <br>
</tt></p>
<p><tt>The error that we get is:</tt></p>
<blockquote>
<p><tt>could not find any font family matching "ArialUnicodeMS";
replaced by Helvetica</tt></p>
</blockquote>
<p><tt>Both of our xep.xml files contain a font-group thus:</tt></p>
<p><tt> </tt> <span class="c9Y6TC"><</span><span
class="cLUY2">font-group </span><span class="c18YC0">xml:base=</span><span
class="c5M9S0"><a class="moz-txt-link-rfc2396E"
href="file:/C:/Windows/Fonts/" moz-do-not-send="true">"file:/C:/Windows/Fonts/"</a></span><span
class="c18YC0"> label=</span><span class="c5M9S0">"Windows
TrueType"</span><span class="c18YC0"> embed=</span><span
class="c5M9S0">"true"</span><span class="c18YC0"> subset=</span><span
class="c5M9S0">"true"</span><span class="c9Y6TC">></span> <br>
<style>
.c9Y6TC { color:#0000ff; }
.cLUY2 { color:#ea8f0f; }
.c18YC0 { color:#d00020; }
.c5M9S0 { color:#000090; }</style></p>
<p><tt>In that font-group, we both have the following:</tt></p>
<p> <span class="c9Y6TC"><</span><span class="cLUY2">font-family
</span><span class="c18YC0">name=</span><span class="c5M9S0">"ArialUnicodeMS"</span><span
class="c9Y6TC">></span><br>
<span class="c9Y6TC"><</span><span class="cLUY2">font</span><span
class="c9Y6TC">><</span><span class="cLUY2">font-data </span><span
class="c18YC0">ttf=</span><span class="c5M9S0">"ARIALUNI.ttf"</span><span
class="c18YC0">/</span><span class="c9Y6TC">><</span><span
class="cLUY2">/font</span><span class="c9Y6TC">></span><br>
<span class="c9Y6TC"><</span><span class="cLUY2">/font-family</span><span
class="c9Y6TC">></span><br>
<style>
.c9Y6TC { color:#0000ff; }
.cLUY2 { color:#ea8f0f; }
.c18YC0 { color:#d00020; }
.c5M9S0 { color:#000090; }</style></p>
<p><tt>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". <br>
</tt></p>
<p><tt>On my new laptop, I eventually created a new font-group:</tt></p>
<p> <span class="c9Y6TC"><</span><span class="cLUY2">font-group
</span><span class="c18YC0">xml:base=</span><span class="c5M9S0"><a
class="moz-txt-link-rfc2396E"
href="file:/D:/RenderX/fonts/ttf/" moz-do-not-send="true">"file:/D:/RenderX/fonts/ttf/"</a></span><span
class="c18YC0"> label=</span><span class="c5M9S0">"Windows
TrueType"</span><span class="c18YC0"> embed=</span><span
class="c5M9S0">"true"</span><span class="c18YC0"> subset=</span><span
class="c5M9S0">"true"</span><span class="c9Y6TC">></span> <br>
<style>
.c9Y6TC { color:#0000ff; }
.cLUY2 { color:#ea8f0f; }
.c18YC0 { color:#d00020; }
.c5M9S0 { color:#000090; }</style></p>
<p><tt>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. <br>
</tt></p>
<p><tt>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. <br>
</tt></p>
<p><tt>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?</tt></p>
<p><tt>Many thanks,<br>
Jim</tt></p>
<pre class="moz-signature" cols="72">--
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</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
(*) To unsubscribe, please visit <a class="moz-txt-link-freetext" href="http://lists.renderx.com/mailman/options/xep-support">http://lists.renderx.com/mailman/options/xep-support</a>
(*) By using the Service, you expressly agree to these Terms of Service <a class="moz-txt-link-freetext" href="http://w">http://w</a>
ww.renderx.com/terms-of-service.html</pre>
</blockquote>
</body>
</html>