ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Michael Murphy <michael.murphy@uni-ulm.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xits font in ~/.fonts
Date: Tue, 17 Aug 2010 18:27:05 +0200	[thread overview]
Message-ID: <4C6AB859.80305@uni-ulm.de> (raw)
In-Reply-To: <4C6AB31F.2030109@wxs.nl>

I also had problems at first with the XITS fonts, especially with the 
built-in typescripts.

First, make sure that you have put the fonts somewhere ConTeXt can find 
them, and run

mtxrun --script font --reload

You can check that they have installed properly by running

mtxrun --script font --list --all --pattern=xits*

and you should see a list of the fonts. Then, copy the typescript from 
the XITS font zip file which you can get from Khaled's website. Put this 
in the root directory of your .tex file (or in a suitable place in the 
ConTeXt tree) and load it in your preamble with

\usetypescriptfile[type-xits]

I then loaded the font with

\usetypescript[xits]
\setupbodyfont[xits]

You might get conflict with the internal typescipt (although I didn't, 
if I remember correctly); if so, rename [xits] in the typescript to 
[my-xits], then do

\usetypescript[my-xits]
\setupbodyfont[my-xits]

On 17/08/2010 18:04, Hans Hagen wrote:
> On 17-8-2010 6:01, Khaled Hosny wrote:
>> On Tue, Aug 17, 2010 at 05:26:19PM +0200, Hans Hagen wrote:
>>> On 17-8-2010 4:53, Khaled Hosny wrote:
>>>> On Tue, Aug 17, 2010 at 03:08:23PM +0200, Hans Hagen wrote:
>>>>> On 17-8-2010 3:00, Khaled Hosny wrote:
>>>>>
>>>>>> The typescript uses file names, however ConTeXt can not load system
>>>>>> fonts by filename. Hans, I think it would be nice to be able to load
>>>>>> fonts by either font name or file name regardless of where they
>>>>>> reside
>>>>>> (I'm not sure how easy is that, though, with luaotfload and kpse
>>>>>> setting
>>>>>> OSFONTDIR is all what I need, since kpathsea appends it to its font
>>>>>> searching paths).
>>>>>
>>>>> \starttext
>>>>>
>>>>> \definedfont[vera at 50pt] test
>>>>> \definedfont[file:vera.ttf at 100pt] test
>>>>>
>>>>> \stoptext
>>>>>
>>>>> works quite ok on my machine and the log reports:
>>>>>
>>>>> <c:/windows/fonts/vera.ttf>
>>>>>
>>>>> so it must be something in the typescripts .. maybe the old names?
>>>>
>>>> This works for me, but not with .otf fonts.
>>>
>>> \starttext
>>>
>>> \definedfont[file:STIXGeneral at 100pt] test
>>>
>>> \stoptext
>>>
>>> <c:/windows/fonts/STIXGeneral.otf>
>>
>> I'm getting unpredictable results here, some fonts are found and some
>> are not, but I can't identify a pattern, I thought it is related to
>> symbolic links but could not prove it (replacing symlinks by a copy, and
>> updating the databases but still the font is not found by file name).
>
> files in OSFONTDIR normally are located runtime (no database) .. depends
> a bit on the configuration
>
> Hans
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>

-- 
Michael Murphy MPhys

Institute für Quanteninformationsverarbeitung
Universität Ulm
Albert-Einstein-Allee 11
89081 Ulm Deutschland
tel +49 731 50 22931
fax +49 731 50 22839

www.quantenbit.de
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2010-08-17 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 16:44 Aditya Mahajan
2010-08-17 13:00 ` Khaled Hosny
2010-08-17 13:08   ` Hans Hagen
2010-08-17 14:53     ` Khaled Hosny
2010-08-17 15:26       ` Hans Hagen
2010-08-17 16:01         ` Khaled Hosny
2010-08-17 16:04           ` Hans Hagen
2010-08-17 16:27             ` Michael Murphy [this message]
2010-08-18 10:57             ` Khaled Hosny
2010-08-18 11:01               ` Taco Hoekwater
2010-08-18 11:06                 ` Khaled Hosny
2010-08-18 19:03                   ` Thomas A. Schmitz
2010-08-18 20:07                     ` Aditya Mahajan
2010-08-18 22:30                       ` Hans Hagen
2010-08-18 22:35                     ` Hans Hagen
2010-08-18 22:36                     ` Hans Hagen
2010-08-18 22:48                       ` Aditya Mahajan
2010-08-18 22:50                         ` Hans Hagen
2010-08-18 22:57                         ` Khaled Hosny
2010-08-18 11:04               ` Martin Althoff
2010-08-17 23:51         ` Aditya Mahajan

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=4C6AB859.80305@uni-ulm.de \
    --to=michael.murphy@uni-ulm.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).