ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonathan Kew <jonathan_kew@sil.org>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Hans Hagen <pragma@wxs.nl>, Dev Context <dev-context@ntg.nl>,
	Norbert Preining <preining@logic.at>,
	Will Robertson <wspr81@gmail.com>
Subject: Re: [dev-context] New context release
Date: Thu, 17 Apr 2008 08:53:52 +0100	[thread overview]
Message-ID: <7E7F608E-86A5-4C94-B725-F89CA1122058@sil.org> (raw)
In-Reply-To: <6faad9f00804161709m65a4874y4ccdfa24a702f383@mail.gmail.com>


On 17 Apr 2008, at 1:09 am, Mojca Miklavec wrote:

> On Thu, Apr 17, 2008 at 1:42 AM, Jonathan Kew wrote:
>> On 16 Apr 2008, at 7:56 pm, Norbert Preining wrote:
>>
>>  Given that there won't be TL2008 in lenny, I think it would be very
>> desirable to update xetex to a more recent version than 0.996 as  
>> shipped
>> with TL2007.
>
>> (I don't know much about the context situation).
>
> ConTeXt would be happy to have the \supressfontnotfounderror fix
> available (which means: happy to have a binary version of XeTeX later
> than the one in TL 2007),

OK, but for Debian it'll need to be provided as a source patch, we  
can't simply give them a binary.

JK

___________________________________________________________________________________
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-17  7:53 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               ` [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                       ` Jonathan Kew [this message]
2008-04-17  5:18                     ` [dev-context] " 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=7E7F608E-86A5-4C94-B725-F89CA1122058@sil.org \
    --to=jonathan_kew@sil.org \
    --cc=dev-context@ntg.nl \
    --cc=mojca.miklavec.lists@gmail.com \
    --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).