From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: (RSFS) font installation
Date: Thu, 17 Mar 2011 17:53:56 +0100 [thread overview]
Message-ID: <4D823CA4.8090808@gmx.de> (raw)
In-Reply-To: <C7DD11A0-64EA-46C3-8A92-6219CB38A82F@gmail.com>
So... I think I got somewhere now with the explanations from you and mathew.
It seems that the problem were the missing .afm files (as mtxrun wanted
those, not .pfm nor .pfb). I found two different solutions A and B:
(1) Install fonts (.pfm) in Windows
(2A) Put .afm files to C:\Windows\Fonts
(2B) Put the complete rsfs (containing the .afm and all the other stuff)
directory to texmf-fonts\fonts
(3) Run "mtxrun --script fonts --reload"
(4) Running "mtxrun --script fonts --list --all --pattern=rsfs" shows
the fonts
(Note the "--all", otherwise only one is printed)
There are two things now, that are somehow strange to me:
- In both versions, step (1) seems to be mandatory. I would expect, that
the rsfs directory in texmf-fonts\fonts should be enough, as mtxrun
clearly searches there and all the files are there, too. I don't
understand the problem here.
- If the .pfm and .pfb files are sufficient for Windows, why does mtxrun
specifically search for .afm files and not also for .pfm?
Anyhow, the fonts are finally listed/recognized by mtxrun.
Unfortunately, the example at
http://archive.contextgarden.net/message/20100414.122529.bc3ba584.en.html still
doesn't show me the rsfs font, only a default font. Probably I just have
to look into that (and the example from mathew) tomorrow.
Best regards and thanks so far,
Stefan.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-17 16:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 14:00 Stefan Müller
2011-03-16 15:58 ` mathew
2011-03-17 9:05 ` Stefan Müller
2011-03-17 12:40 ` Ulrike Fischer
2011-03-17 13:41 ` Stefan Müller
2011-03-17 16:12 ` Otared Kavian
2011-03-17 16:53 ` Stefan Müller [this message]
2011-03-17 15:04 ` mathew
2011-03-17 16:53 ` Stefan Müller
2011-03-18 2:42 ` mathew
2011-03-18 3:27 ` Khaled Hosny
2011-03-18 10:04 ` Hans Hagen
2011-03-18 14:40 ` mathew
2011-03-18 14:51 ` Hans Hagen
2011-03-18 16:01 ` mathew
2011-03-18 18:30 ` Hans Hagen
[not found] ` <AANLkTinWPdN-H6TPNato9PG7Fh0PzvfS0PkHXehzbt6J@mail.gmail.com>
2011-03-22 16:08 ` mathew
2011-03-22 16:55 ` Taco Hoekwater
2011-03-18 11:26 ` Stefan Müller
2011-03-18 11:39 ` Hans Hagen
2011-03-18 14:47 ` Stefan Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D823CA4.8090808@gmx.de \
--to=warrence.stm@gmx.de \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).