ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: next version
Date: Fri, 7 Jan 2005 22:06:31 +0000	[thread overview]
Message-ID: <20050107220631.25631@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <41DD762B.6090301@wxs.nl>

Hans Hagen said this at Thu, 6 Jan 2005 18:32:27 +0100:

>>>- csr/plr/aer/vnr will be dropped in favor of lmr (also makes minimals
>>>smaller)
>> 
>> 
>> What will this entail, exactly?
>
>less font files because latin modern has all those glyphs in it (once
>vietnamese 
>is in there some 600 glyphs per font); for speed and consistency i may add a 
>bunch of <encoding>-lmr*.tfm files but users will not notice it;

Okay, here's a question: what's the plan for ec-lmr*.tfm files?

Your latin-modern typescripts accept ec, but the tfm files are called cork.
(I'm only wondering about this now for antt support.)

I know of two approaches. Which would you recommend?

\starttypescript [serif] [antykwa-torunska] [texnansi,qx,ec]
  \definefontsynonym [AntykwaTorunska-Bold]
          [\typescriptthree-anttb]     [encoding=\typescriptthree]
\stoptypescript

\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

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay, Computing Dept.     atl@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2005-01-07 22:06 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 [this message]
2005-01-09 20:19       ` h h extern
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=20050107220631.25631@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).