On 08/06/2022 09:55, Ulrike Fischer wrote:
Sorry but I think it is one of the nice features of a modern tex
system that it creates tfm or pk fonts on the fly.
That's fine; we can agree to differ on such philosophical points.
xetex is doing that internally too for your open type fonts: it is
Am Wed, 8 Jun 2022 09:43:19 +0100 schrieb Philip Taylor (Hellenic
Institute):
> On 08/06/2022 08:51, Ulrike Fischer wrote:
>> Am Tue, 7 Jun 2022 11:44:28 +0100 schrieb Philip Taylor (Hellenic
>> Institute):
>>
>>> As I /never/ want XeTeX to attempt to create a seemingly-missing TFM
>>> file, can
On 08/06/2022 08:51, Ulrike Fischer wrote:
Am Tue, 7 Jun 2022 11:44:28 +0100 schrieb Philip Taylor (Hellenic
Institute):
As I /never/ want XeTeX to attempt to create a seemingly-missing TFM
file, can I configure XeTeX and/or TeXworks to inhibit this undesired
behaviour ?
Perhaps by setting
On 08/06/2022 08:51, Ulrike Fischer wrote:
Perhaps by setting MKTEXTFM = 0, but I never tried if xetex honors that.
Yes, a great improvement thank you —
D:\ XeTeX Font-error
This is XeTeX, Version 3.141592653-2.6-0.94 (TeX Live 2022)
(preloaded format=xetex)
restricted \write18
Am Tue, 7 Jun 2022 11:44:28 +0100 schrieb Philip Taylor (Hellenic
Institute):
> As I /never/ want XeTeX to attempt to create a seemingly-missing TFM
> file, can I configure XeTeX and/or TeXworks to inhibit this undesired
> behaviour ?
Perhaps by setting MKTEXTFM = 0, but I never tried if
Hello Philip
I've sometimes encountered inexplicable behaviour like this, and if there's
the slightest hint of a problem with plain XeTeX locating and loading a
font in a particular way, I load it directly from the font file itself,
e.g.:
Using XeTeX as my only TeX typesetting engine, I also use only OTF/TTF
fonts. After a faulty copy-and-paste, I found that I had inadvertently
written :
\font \fnf = \font \fb "Gill Sans MT" scaled 400
which led to the unexpected diagnostic :
Usage: mktextfm [--destdir destdir] name
!
