From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Postscript Type1 fonts & MK IV - [SOLVED]
Date: Tue, 31 Aug 2010 11:35:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1008311134200.6877@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20100831112021.GA1987@khaled-laptop>
On Tue, 31 Aug 2010, Khaled Hosny wrote:
> On Tue, Aug 31, 2010 at 11:19:50AM +0200, Taco Hoekwater wrote:
>> On 08/31/2010 09:31 AM, Taco Hoekwater wrote:
>>> On 08/31/2010 08:27 AM, John Magolske wrote:
>>>> * Khaled Hosny<khaledhosny@eglug.org> [100830 18:29]:
>>>>> Try Taco's suggestion, I myself got unpredictable results with ~/.fonts,
>>>>> try instead ~/texmf/fonts/{afm,type1} or even ~/texmf/fonts/data
>>>
>>> We should try to find what is causing the erratic behavior of ~/.fonts
>>
>> Perhaps it is all just because the default $OSFONTDIR does not contain
>> ~/.fonts ? I tried this:
>>
>> export OSFONTDIR=/usr/share/fonts:~/.fonts
>
> Mine is:
>
> export OSFONTDIR='$HOME/.fonts//:/usr/share/fonts//'
Mine is (in setuptex)
OSFONTDIR="$HOME/.fonts;/usr/share/fonts;"
export OSFONTDIR
I had some troubles with OSFONTDIR and opentype fonts in the past. Perhaps
I should use : and trailing // and test again.
Aditya
___________________________________________________________________________________
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:[~2010-08-31 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 23:16 Postscript Type1 fonts & MK IV John Magolske
2010-08-28 2:59 ` Wolfgang Schuster
2010-08-28 8:30 ` Hans Hagen
2010-08-29 6:50 ` John Magolske
2010-08-29 7:17 ` Taco Hoekwater
2010-08-29 8:11 ` John Magolske
2010-08-29 8:15 ` Taco Hoekwater
2010-08-29 8:23 ` Khaled Hosny
2010-08-30 6:17 ` John Magolske
2010-08-30 9:38 ` Khaled Hosny
2010-08-31 6:27 ` Postscript Type1 fonts & MK IV - [SOLVED] John Magolske
2010-08-31 7:31 ` Taco Hoekwater
2010-08-31 9:19 ` Taco Hoekwater
2010-08-31 11:20 ` Khaled Hosny
2010-08-31 15:35 ` Aditya Mahajan [this message]
2010-08-31 11:22 ` Khaled Hosny
2010-09-02 5:52 ` John Magolske
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=alpine.LNX.2.01.1008311134200.6877@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).