ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: first steps
Date: Wed, 09 Apr 2008 17:57:29 +0200	[thread overview]
Message-ID: <47FCE769.7090007@elvenkind.com> (raw)
In-Reply-To: <47FCE608.3070009@wxs.nl>

Hans Hagen wrote:
> Mojca Miklavec wrote:
>>>  Here's a minimal example for Hans & Taco:
>>>
>>>  \usetypescriptfile[type-gyr]
>>>
>>> \usetypescript[palatino]
>>>  \setupbodyfont[palatino,12pt]
>>>  \starttext
>>>  ab\ccaron
>>>  \stoptext
> 
> i cannot reproduce the crash/problems on my machine
> 
>> The output of XeTeX is to be expected, but I don't know why the map
>> file is loaded at all.
> 
> you mean that for xetex map files are loaded? if we can assumt that 
> xetex users use open type fonts we can avoid that (at some point we can 
> drop transition from type1/otf)

Well, that's the thing: it seems to us that whenever context finds PFB 
files for the tex-gyre fonts (qplr.tfm&pfb in this case), it will use
those, totally ignoring any opentype fonts that are also installed.




___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-04-09 15:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 14:41 Wolfgang Werners-Lucchini
2008-04-07 15:19 ` Taco Hoekwater
2008-04-08 21:51 ` Mojca Miklavec
2008-04-09  7:48   ` Taco Hoekwater
2008-04-09  9:47     ` Mojca Miklavec
2008-04-09  9:52       ` Mojca Miklavec
2008-04-09 10:17         ` Taco Hoekwater
2008-04-09 10:30           ` Mojca Miklavec
2008-04-09 15:51         ` Hans Hagen
2008-04-09 15:57           ` Taco Hoekwater [this message]
2008-04-09 16:34             ` Hans Hagen
2008-04-09 17:11               ` Taco Hoekwater
2008-04-09 17:59                 ` Hans Hagen
2008-04-09 19:05                   ` Hans van der Meer
2008-04-09 19:53                     ` Taco Hoekwater
2008-04-09 23:15                     ` Hans Hagen
2008-04-09 17:42             ` Hans Hagen
2008-04-09 20:00               ` Taco Hoekwater
2008-04-09 20:36           ` Mojca Miklavec
2008-04-09 23:08             ` Hans Hagen
     [not found] <mailman.4454.1207592564.4340.ntg-context@ntg.nl>
2008-04-07 21:34 ` Wolfgang Werners-Lucchini
2008-04-08  7:42   ` Taco Hoekwater
     [not found] <mailman.1.1207648802.28836.ntg-context@ntg.nl>
2008-04-08 21:31 ` Wolfgang Werners-Lucchini
     [not found] <mailman.4552.1207729500.4340.ntg-context@ntg.nl>
2008-04-09 10:55 ` Wolfgang Werners-Lucchini
2008-04-09 14:54   ` Taco Hoekwater
     [not found] <mailman.1.1207821601.10731.ntg-context@ntg.nl>
2008-04-10 16:14 ` Wolfgang Werners-Lucchini

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=47FCE769.7090007@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).