From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: typescripts again (was to keep you busy ...)
Date: Sat, 08 Feb 2003 17:22:03 +0100 [thread overview]
Message-ID: <5.1.0.14.1.20030208171959.03091530@server-1> (raw)
In-Reply-To: <20030207145950.7CEAE45212@server2.fastmail.fm>
At 06:59 AM 2/7/2003 -0800, you wrote:
>On Fri, 07 Feb 2003 09:13:03 +0100, "Hans Hagen" <pragma@wxs.nl> said:
>
> >
> > this means that it cannot find it on th elocal path but the file is found
> > elsewhere (there are some 5 strategies for locating files in context)
> >
> > can you send me the file + test file?
>
>Which "file"? I'll assume the typescriptfile, etc...
your problem is related to a naming inconsistency:
you map serif's in a typescript called
[minionpro]
but in defining the typeface use:
[minionpro-osf]
so, either name the typescript -pro as well, or call it up using:
[minionpro,minionpro-osf]
Seems that halefway defining you lost the -osf -)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-02-08 16:22 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
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 [this message]
[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=5.1.0.14.1.20030208171959.03091530@server-1 \
--to=pragma@wxs.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).