<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 2017-04-06 09:27, Jonathan Kew wrote:<br>
</p>
<blockquote type="cite"
cite="mid:b3853435-1168-87d5-a8dc-6934fd65160a@gmail.com">On
06/04/2017 15:53, Zdenek Wagner wrote:
<br>
<blockquote type="cite">2017-04-06 15:31 GMT+02:00 Ulrike Fischer
<a class="moz-txt-link-rfc2396E" href="mailto:news3@nililand.de"><news3@nililand.de></a>:
<br>
<blockquote type="cite">Am Thu, 6 Apr 2017 07:10:06 -0600
schrieb Bobby de Vos:
<br>
<br>
<blockquote type="cite">On 2017-04-06 02:39, Ulrike Fischer
wrote:
<br>
<blockquote type="cite">On the whole I would agree with the
debian answer: applications like
<br>
xetex/xdvipdfmx shouldn't try to use fonts it can't
handle.
<br>
</blockquote>
<br>
Thank you for your response. I will file a bug with Debian
at some point.
<br>
</blockquote>
<br>
Why Debian? I meant it is more a xetex problem so I would add
a bug
<br>
report there.
<br>
<br>
</blockquote>
This is certainly not a Debian bug, the font is installed as it
should be.
<br>
The problem is that it is not supported by XeTeX/xdvipdfmx and
it is a question
<br>
what XeTeX should do if fontconfig offers an unsupported font
<br>
</blockquote>
<br>
Well... while I agree that we should do something in XeTeX to
handle this, I also think it is a poor decision on Debian's side
to mix .woff files, which are explicitly intended for web
deployment, alongside .otf files that are expected to be available
in the local GUI desktop environment. These are two distinct
categories of resource, and it would be more appropriate to keep
them separate.
<br>
<br>
More generally, I think it's a bad idea for a distro or package or
whatever to install multiple copies of the "same" font (e.g. both
TrueType and Type1 formats) with the same name where fontconfig
will find them both.
<br>
</blockquote>
<br>
I talked with Keith, the author of fontconfig while at DebConf, and
he agrees that multiple copies of the same font should not be
installed where fontconfig can find them.<br>
<br>
He also thinks fontconfig/freetype should be enhanced so TrueType
(and I would add OpenType) fonts are prioritized before WOFF.<br>
<br>
Either of these changes would solve the issue I have reported. He
went on to say that xdvipdfmx should handle WOFF. Maybe a font
designed would only release a WOFF, and a TrueType would not be
available. A few more details are at<br>
<br>
<a class="moz-txt-link-freetext" href="https://sourceforge.net/p/xetex/bugs/139/">https://sourceforge.net/p/xetex/bugs/139/</a><br>
<br>
Bobby<br>
<br>
<div class="moz-signature">-- <br>
Bobby de Vos<br>
<em><a class="moz-txt-link-abbreviated" href="mailto:devos.bobby@gmail.com">devos.bobby@gmail.com</a></em><br>
</div>
</body>
</html>