ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "Norbert Preining" <preining@logic.at>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>, Dev Context <dev-context@ntg.nl>,
	Will Robertson <wspr81@gmail.com>,
	Jonathan Kew <jonathan_kew@sil.org>
Subject: Re: [dev-context] New context release
Date: Wed, 16 Apr 2008 19:56:08 +0200	[thread overview]
Message-ID: <6faad9f00804161056w4c67f606r8b2b4c50e4bbcfe2@mail.gmail.com> (raw)
In-Reply-To: <20080416172128.GO6680@gamma.logic.tuwien.ac.at>

On Wed, Apr 16, 2008 at 7:21 PM, Norbert Preining wrote:
> On Mi, 16 Apr 2008, Norbert Preining wrote:
>  > - for context/luatex: ok with old and new ones
>  > - for context/xetex: new ones are necessary

True.

>  > Ok, I will think about updating the lmodern fonts, too, but renaming the
>
>  Hmm, according to Ralf updating the lmodern is a no-go because that
>  would need euenc/fontspec updates, which would need ... devilish.
>  (See bugs.debian.org/469437)
>
>  I guess we have to live with this for lenny. And for the next we will
>  have TL2008 with new xetex/luatex and can ship new context and fonts.
>
>  Or do you have another suggestion???

ConTeXt + XeTeX will be broken without the latest LM fonts. ConTeX +
LuaTeX works OK.

For XeLaTeX you indeed need to update fontspec, but if you're
reluctant to upgrade the rest of XeTeX, a fix of fontspec to support
the latest LM fonts is so minor, that it's really not worth having a
broken ConTeXt+XeTeX. fontspec might need only a few name fixes,
that's all.

Maybe Jonathan and Will have something more to say about which version
of XeTeX and fontspec might be best to consider to make its way into
Debian, but a humble request from my side - please do upgrade LM.
(MikTeX has done that already.)

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-04-16 17:56 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         ` [dev-context] " Hans Hagen
2008-04-16 17:08           ` Norbert Preining
2008-04-16 17:21             ` Norbert Preining
2008-04-16 17:56               ` Mojca Miklavec [this message]
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=6faad9f00804161056w4c67f606r8b2b4c50e4bbcfe2@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=dev-context@ntg.nl \
    --cc=jonathan_kew@sil.org \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.nl \
    --cc=preining@logic.at \
    --cc=wspr81@gmail.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).