From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Again Cambria after updating to latest beta
Date: Thu, 09 Jun 2011 13:43:02 +0200 [thread overview]
Message-ID: <4DF0B1C6.3020505@elvenkind.com> (raw)
In-Reply-To: <1D8CA72C-919C-49EA-9F8B-515653853A22@boede.nl>
On 06/09/11 08:31, Willi Egger wrote:
> Hi all,
>
> Yesterday evening I was quite happy that after deleting and regenerating the cache and the formats I had Cambria up and running.
>
> This morning I updated Context to the latest beta. - Eventhough I generated the formats manually with context --make, I get the problem referred to yesterday. What I get you can see in the by the list administrator released mail from yesterday.
>
> I am stymied.
Steps to fix this:
1. rename CAMBRIA.TTC to cambria.ttc
2. empty the font cache.
The effect you see is a 2.048 shrink factor, and that happens
probably because context does not recognize .TTC as a TrueType
font with 2048 units.
Best wishes,
Taco
___________________________________________________________________________________
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-06-09 11:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 6:31 Willi Egger
2011-06-09 7:01 ` Hans Hagen
2011-06-09 7:13 ` Willi Egger
2011-06-09 8:18 ` Otared Kavian
2011-06-09 8:38 ` Willi Egger
2011-06-09 10:35 ` Herbert Voss
2011-06-09 9:15 ` Hans Hagen
2011-06-09 9:23 ` Hans Hagen
2011-06-09 11:43 ` Taco Hoekwater [this message]
2011-06-09 20:22 ` Willi Egger
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=4DF0B1C6.3020505@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).