ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonathan Kew <jonathan_kew@sil.org>
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>,
	Mojca Miklavec <mojca.miklavec.lists@gmail.com>,
	Will Robertson <wspr81@gmail.com>
Subject: Re: [dev-context] New context release
Date: Thu, 17 Apr 2008 09:22:55 +0100	[thread overview]
Message-ID: <D1014EEA-41CF-4F52-B27D-DDDAAC3771AC@sil.org> (raw)
In-Reply-To: <20080417062330.GN9094@gamma.logic.tuwien.ac.at>

On 17 Apr 2008, at 7:23 am, Norbert Preining wrote:

> On Do, 17 Apr 2008, Will Robertson wrote:
>> Sorry, I didn't know how you went about actually creating this  
>> package.
>
> The packages are created from the actual TeX Live release, or better
> from the security branch of the subversion repository, the tag  
> 2007.1 or
> how it is called.

There's a tag "2007.0", which matches the actual release DVD, and  
there's a "branch2007" which has had a few bug fixes applied (mostly  
bugfixes in xetex, also apparently some security fixes in dviljk).

What I suggest is that I review xetex bug-fixes since the 2007  
release, and back-port the most important ones to branch2007 in TeX  
Live; we can also include the \suppressfontnotfounderror or whatever  
it's called, for the sake of the new context. But we won't try to  
include any of the major new features (like Graphite font support, or  
the new ICU version, etc), which would make for a massive patch.

This would give you a "xetex 0.996-patch2" in Lenny (what's in  
branch2007 is currently 0.996-patch1), should work for both context  
and non-context users, and should be non-invasive as far as the rest  
of TL is concerned.

If I do this, and create a tag "2007.1" in TL with the updated  
branch2007 version, are you able to use this as the base for your  
package? I presume you don't use the actual binaries from TL Master/ 
bin anyway, so what matters is what we have in the source tree.

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  8:22 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                       ` [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                               ` Jonathan Kew [this message]
2008-04-17  9:14                                 ` [dev-context] " 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=D1014EEA-41CF-4F52-B27D-DDDAAC3771AC@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).