From: h h extern <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: next version
Date: Sun, 09 Jan 2005 21:19:10 +0100 [thread overview]
Message-ID: <41E191BE.1040905@wxs.nl> (raw)
In-Reply-To: <20050107220631.25631@news.comp.lancs.ac.uk>
Adam Lindsay wrote:
> Okay, here's a question: what's the plan for ec-lmr*.tfm files?
indeed a problem, i will provide an extra a typescript that maps the ec-lm*
files onto cork-lm-*; in addition to that i will ship copies of ec-lm* as well
as il2-lm* and pl0-lm* [or maybe polish can move to qx-lm*]; given that context
is the only system using the encoding-name scheme, and since i have lots of ec-*
files around, i see no reason to change ec-* to cork-*
[an option is to have something \ec that expands to ec or cork but i dislike that]
> Your latin-modern typescripts accept ec, but the tfm files are called cork.
> (I'm only wondering about this now for antt support.)
for the ant, use ec- since that's what texfont provides
> I know of two approaches. Which would you recommend?
>
> \starttypescript [serif] [antykwa-torunska] [texnansi,qx,ec]
> \definefontsynonym [AntykwaTorunska-Bold]
> [\typescriptthree-anttb] [encoding=\typescriptthree]
> \stoptypescript
easier and faster
> \starttypescript [serif] [antykwa-torunska] [ec]
> \definefontsynonym [ec-anttb] [cork-anttb]
> \stoptypescript
>
> % or...
>
> \starttypescript [serif] [antykwa-torunska] [texnansi,qx]
> \definefontsynonym [AntykwaTorunska-Bold]
> [\typescriptthree-anttb] [encoding=\typescriptthree]
> \stoptypescript
>
> \starttypescript [serif] [antykwa-torunska] [ec]
> \definefontsynonym [AntykwaTorunska-Bold][cork-anttb][encoding=ec]
> \stoptypescript
slower, the less typescripts we have ... same for lm fonts, the less the better
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-01-09 20:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 16:44 Hans Hagen
2005-01-06 16:54 ` Nikolai Weibull
2005-01-06 17:32 ` Hans Hagen
2005-01-07 22:06 ` Adam Lindsay
2005-01-09 20:19 ` h h extern [this message]
2005-01-10 17:12 ` Adam Lindsay
2005-01-06 16:58 ` Adam Lindsay
2005-01-07 21:09 ` Hans van der Meer
2005-01-07 21:38 ` Tobias Burnus
2005-01-07 21:49 ` Peter Münster
2005-01-08 10:23 ` m-letter.tex (first page, input file) Rob Ermers
2005-01-09 20:22 ` next version h h extern
2005-01-11 14:20 ` can I upgrade yet? Gary
2005-01-11 14:33 ` Hans Hagen
2005-01-11 14:45 ` Gary
2005-01-11 17:00 ` Hans Hagen
2005-01-11 15:52 ` Gary
2005-01-11 17:02 ` Hans Hagen
2005-01-12 15:22 ` Gary
2005-01-13 18:48 ` m-letter backslash codes in xml database Rob Ermers
2005-01-14 16:44 ` h h extern
2005-01-15 1:31 ` Rob Ermers
2005-01-15 13:21 ` Adam Lindsay
2005-01-16 10:12 ` (resolved) " Rob Ermers
2005-01-16 10:45 ` Adam Lindsay
2005-01-17 10:03 ` Hans Hagen
2005-01-11 14:43 ` can I upgrade yet? Matthew Huggett
2022-01-08 12:48 next version Hans Hagen via ntg-context
2022-02-07 23:59 ` Denis Maier via ntg-context
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=41E191BE.1040905@wxs.nl \
--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).