From: "W. Egger" <w.egger@boede.nl>
Cc: "ntg-context" <ntg-context@ntg.nl>
Subject: Re: font question
Date: Wed, 20 Feb 2002 19:47:28 +0100 [thread overview]
Message-ID: <006101c1ba41$9bae0c40$0100a8c0@digitpaint.nl> (raw)
In-Reply-To: <003501c1b98d$61679470$0200a8c0@arnhem.chello.nl>
Hi Frans,
Don't dispare! - I know, that it cost a lot of time but you will see it is
worth to do it. With my small knowledg I got on this issue, I suggest, that
you will prepare a set of typescripts according e.g. to the Sabon example of
Bill. The font mechanism only works when those scripts are present! - If you
want I could send you some other example files which I have written for
fonts for different Corel type 1 fonts.
Sterkte Willi
----- Original Message -----
From: Frans Goddijn <frans@goddijn.com>
To: <ntg-context@ntg.nl>
Sent: Tuesday, February 19, 2002 10:27 PM
Subject: Re: font question
> Thanks, Willi, for this link! I've looked it over and on
> first sight it impresses me with its clarity and at the same
> time it intimidates me to see how immensely complicated it
> is... It's like reading a very well designed book about high
> maths, the pages seem to say "look, this is simple and fun!"
> but when I read the actual text I can't unserstand a single
> line :=)
>
> I'll give it a decent try even though I'm sure it's
> hopeless.
>
> Groet!
>
> Frans
>
> frans@goddijn.com
> www.goddijn.com
>
> ----- Original Message -----
> From: Willi Egger
> To: Frans Goddijn
> Sent: Tuesday, February 19, 2002 7:51 PM
> Subject: Re: font question
>
>
> Hi Frans,
>
> To me it looks like that you have your files on the right
> spots. As far as I
> can understand the new font-mechanism, you should prepare
> typescriptfiles
> and define typefaces in order to use the owned fonts. I
> suggest, that you
> pay a visit to Bill McCLain's homepage, where he in details
> explains how to
> make the fonts work. There is also an example of a bought
> fotn (Sabon).
>
> http://home.salamander.com/~wmcclain/context-help.html
>
> Groet en Grüße (Weniger Grütze) Willi
>
>
>
next prev parent reply other threads:[~2002-02-20 18:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 15:04 Frans Goddijn
2002-02-19 16:32 ` Bill McClain
2002-02-19 17:22 ` Frans Goddijn
2002-02-19 18:31 ` Bill McClain
[not found] ` <003701c1b976$6ab1c800$0100a8c0@digitpaint.nl>
2002-02-19 21:27 ` Frans Goddijn
2002-02-20 12:39 ` Bill McClain
2002-02-20 18:47 ` W. Egger [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 19:42 Font question Marcin Borkowski
2008-02-29 20:54 ` Hans Hagen
2008-02-29 22:31 ` Marcin Borkowski
2008-02-29 22:57 ` Hans Hagen
2008-03-01 0:17 ` Marcin Borkowski
2008-03-01 0:22 ` Idris Samawi Hamid
2008-03-02 8:48 ` Marcin Borkowski
2008-03-02 13:08 ` Mojca Miklavec
2008-03-02 13:20 ` Wolfgang Schuster
2008-03-04 20:58 ` Marcin Borkowski
2008-03-04 21:09 ` Wolfgang Schuster
2008-03-04 21:49 ` Marcin Borkowski
2008-03-05 8:40 ` Hans Hagen
2008-03-04 22:55 ` Marcin Borkowski
2008-03-05 6:55 ` Thomas A. Schmitz
2008-03-05 14:23 ` Marcin Borkowski
2008-03-05 9:17 ` Taco Hoekwater
2008-03-05 14:29 ` Marcin Borkowski
2008-03-11 14:07 ` Marcin Borkowski
2005-12-12 15:32 Font Question Henry Blodgiitt
2005-12-07 22:46 Aditya Mahajan
2005-12-07 23:45 ` Adam Lindsay
2005-12-08 0:05 ` Aditya Mahajan
2005-12-07 23:55 ` Hans Hagen
2001-08-02 17:01 Marco Kuhlmann
2001-08-03 14:01 ` Hans Hagen
2001-08-05 21:02 ` Marco Kuhlmann
2001-08-06 7:42 ` Hans Hagen
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='006101c1ba41$9bae0c40$0100a8c0@digitpaint.nl' \
--to=w.egger@boede.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).