From: Hans Hagen <pragma@wxs.nl>
To: Norbert Preining <preining@logic.at>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Dev Context <dev-context@ntg.nl>,
Taco Hoekwater <taco@elvenkind.com>
Subject: Re: [dev-context] New context release
Date: Wed, 16 Apr 2008 19:02:13 +0200 [thread overview]
Message-ID: <48063115.9000105@wxs.nl> (raw)
In-Reply-To: <20080416165559.GJ6680@gamma.logic.tuwien.ac.at>
Norbert Preining wrote:
> On Mi, 16 Apr 2008, Hans Hagen wrote:
>> indeed we need the latest although in the luatex version there is a kind
>> of fallback name subsystem,
>
> Aehmmmmm.... what does this mean??? So either you need it, or there is a
> fallback system ... semantics are sometimes dangerous ;-)
well, it may work with the old fonts (depends on how old), in
font-syn.tex you will find
fonts.names.new_to_old = {
["lmroman10-capsregular"] = "lmromancaps10-oblique",
["lmroman10-capsoblique"] = "lmromancaps10-regular",
["lmroman10-demi"] = "lmromandemi10-oblique",
["lmroman10-demioblique"] = "lmromandemi10-regular",
["lmroman8-oblique"] = "lmromanslant8-regular",
["lmroman9-oblique"] = "lmromanslant9-regular",
["lmroman10-oblique"] = "lmromanslant10-regular",
["lmroman12-oblique"] = "lmromanslant12-regular",
etc. so older fonts are ok for context/luatex; while for xetex new fonts
are needed.
> So if we ship the old or the new one there is no problem with the one or
> the other?
not for luatex/context
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-04-16 17:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 9:21 mkiv new zips luigi scarso
2008-04-16 16:01 ` New context release Taco Hoekwater
2008-04-16 16:35 ` [dev-context] " Norbert Preining
2008-04-16 16:52 ` Hans Hagen
2008-04-16 16:55 ` Norbert Preining
2008-04-16 17:02 ` Hans Hagen [this message]
2008-04-16 17:08 ` Norbert Preining
2008-04-16 17:21 ` Norbert Preining
2008-04-16 17:56 ` [dev-context] " Mojca Miklavec
2008-04-16 18:56 ` Norbert Preining
[not found] ` <6faad9f00804161607g18d006b2j15484afb7612c64a@mail.gmail.com>
2008-04-16 23:42 ` [dev-context] " Jonathan Kew
2008-04-17 0:09 ` Mojca Miklavec
2008-04-17 7:53 ` [dev-context] " Jonathan Kew
2008-04-17 5:18 ` Norbert Preining
2008-04-17 5:26 ` Will Robertson
2008-04-17 5:38 ` Norbert Preining
2008-04-17 6:19 ` Will Robertson
2008-04-17 6:23 ` Norbert Preining
2008-04-17 8:22 ` [dev-context] " Jonathan Kew
2008-04-17 9:14 ` Norbert Preining
2008-04-16 20:35 ` Jan-Erik Hägglöf
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=48063115.9000105@wxs.nl \
--to=pragma@wxs.nl \
--cc=dev-context@ntg.nl \
--cc=ntg-context@ntg.nl \
--cc=preining@logic.at \
--cc=taco@elvenkind.com \
/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).