From: Jens-Uwe Morawski <morawski@gmx.net>
Subject: Re: typescripts again (was to keep you busy ...)
Date: Thu, 6 Feb 2003 17:53:54 +0100 [thread overview]
Message-ID: <20030206175354.579194dc.morawski@gmx.net> (raw)
In-Reply-To: <B7B2D0BB-39E2-11D7-9CD2-0050E4258255@fastmail.fm>
On Thu, 6 Feb 2003 09:53:13 -0500
"Bruce D'Arcus" <bdarcus@fastmail.fm> wrote:
>
> Thanks Jens. I still don't see anything obvious though (see below)....
>
> On Thursday, February 6, 2003, at 07:58 AM, Jens-Uwe Morawski wrote:
>
> > Thus, check if your type-script can be found; run
> > kpsewhich <your-typescript-file-name>
> > in your document-directory for example:
> > kpsewhich type-minion.tex
> >
> > and check for misspellings, since ConTeXt gives no error message
> > if you declare a typescript-file via
> > \usetypescriptfile[type-minionn]
> > but its name is type-minion.tex
>
> Here's what I get:
>
> bdarcus% kpsewhich type-OpenTypePro.tex
> /Users/bdarcus/Library/texmf/tex/context/user/type-OpenTypePro.tex
>
> And this is copied from my environment file:
>
> \usetypescriptfile[type-OpenTypePro]
>
> No typos, soo...???
>
>
>
> Here's the document source, BTW:
>
> \environment minionpro-osf.tex
Please, step by step! Thus, try it first without an environment-file.
In your TeX-file load the typescript using \usetypescriptfile, make
your \definetypeface definitions there (the definition for rm/serif
should be enough), setup your body-font and let us see what happens.
Jens
next prev parent reply other threads:[~2003-02-06 16:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.1.0.14.1.20030204001753.0345b738@server-1>
2003-02-04 0:28 ` to keep you busy Bruce D'Arcus
2003-02-04 12:35 ` Hans Hagen
2003-02-04 15:08 ` Bruce D'Arcus
2003-02-05 9:26 ` Hans Hagen
2003-02-05 18:12 ` typescripts again (was to keep you busy ...) Bruce D'Arcus
2003-02-05 21:00 ` Jens-Uwe Morawski
2003-02-05 21:13 ` Bruce D'Arcus
2003-02-06 1:55 ` Jens-Uwe Morawski
2003-02-06 2:40 ` Bruce D'Arcus
2003-02-06 12:58 ` Jens-Uwe Morawski
2003-02-06 14:53 ` Bruce D'Arcus
2003-02-06 14:58 ` Taco Hoekwater
2003-02-06 15:12 ` Bruce D'Arcus
2003-02-06 16:47 ` Hans Hagen
2003-02-06 16:53 ` Jens-Uwe Morawski [this message]
2003-02-06 17:25 ` Bruce D'Arcus
2003-02-06 21:03 ` Jens-Uwe Morawski
[not found] ` <20030207145950.7CEAE45212@server2.fastmail.fm>
2003-02-08 16:22 ` Hans Hagen
[not found] ` <5.1.0.14.1.20030207091156.0307f438@server-1>
[not found] ` <20030208192136.06028471E1@server2.fastmail.fm>
2003-02-08 19:38 ` Hans Hagen
2003-02-09 15:47 ` memory problems Bruce D'Arcus
2003-02-09 18:26 ` Hans Hagen
2003-02-09 19:45 ` finally! (memory problems) Bruce D'Arcus
2003-02-09 20:05 ` Sectionseparator? Roef Ragas
2003-02-09 20:37 ` Sectionseparator? Hans Hagen
2003-02-10 8:07 ` Sectionseparator? Roef Ragas
2003-02-09 22:06 ` finally! (memory problems) Hans Hagen
2003-02-09 23:09 ` Bruce D'Arcus
2003-02-10 9:28 ` Hans Hagen
2003-02-07 11:46 ` typescripts again (was to keep you busy ...) mari.voipio
2003-02-07 12:00 ` Adam Lindsay
2003-02-07 14:13 ` Hans Hagen
2003-02-07 9:28 ` Hans Hagen
2003-02-07 15:18 ` Bruce D'Arcus
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=20030206175354.579194dc.morawski@gmx.net \
--to=morawski@gmx.net \
--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).