From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Strange font issue with LuaTeX on Linux
Date: Wed, 03 Sep 2008 08:49:12 +0200 [thread overview]
Message-ID: <48BE3368.9020401@wxs.nl> (raw)
In-Reply-To: <loom.20080902T233358-415@post.gmane.org>
Mohamed Bana wrote:
> Sorry I didn't quiet understand that. Given this;
>
> $ mtxrun --script fonts --list --pattern=warnock
> warnockpro-bold WarnockPro-Bold WarnockPro-Bold.otf
> ....
looks like an old version, should be
warnockprobold WarnockPro-Bold <fullpathifsystemfont>/WarnockPro-Bold.otf
> which of the following are correct;
>
> 1. \definefontsynonym [WarnockPro-Regular] [name:warnockpro-bold]
best use
name:warnockprobold
although context will strip the - anyway
> 2. \definefontsynonym [WarnockPro-Regular] [name:WarnockPro-Bold]
> 3. \definefontsynonym [WarnockPro-Regular] [file:WarnockPro-Bold.otf]
> 4. \definefontsynonym [WarnockPro-Regular] [file:WarnockPro-Bold]
>
>
>> also, do you use the latest mtxrun, mtx-fonts and context? the first
>> entry in the list should show the stripped name
>
> I'm using cont-tmf.zip uploaded on 2008-08-05 18:50
> (http://www.pragma-ade.nl/download-1.htm) extracted to ~/texmf. I need this
> because I use TeXLive 2007.
can you try the beta? something was fixed
> Hans, why does it compile fine when I copy the fonts over to the working
> directory? There must be something wrong with the OSFONTDIR variable. BTW, I
> think you should switch over to linux and make life easier for us :)
it has nothing to do with linux (and actually i run linux on the servers
that serve tex processing for projects)
mtxrun --script fonts
operates on the tree and does not limit the search to the 'official'
locations, while context, when a font is loaded, does obey those
limitations
the current path is always taken as valid
Hans
ps. the latest beta really should work ok (tested at conference)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-09-03 6:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 17:35 abbg770
2008-09-02 18:32 ` Hans Hagen
2008-09-02 23:46 ` Mohamed Bana
2008-09-03 6:49 ` Hans Hagen [this message]
2008-09-03 17:10 ` Mohamed Bana
2008-09-03 20:52 ` Mojca Miklavec
2008-09-09 16:24 ` Mohamed Bana
2008-09-02 23:50 ` Mohamed Bana
-- strict thread matches above, loose matches on Subject: below --
2008-09-01 13:34 abbg770
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=48BE3368.9020401@wxs.nl \
--to=pragma@wxs.nl \
--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).