From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt standalone - in what situations is it better?
Date: Thu, 24 Oct 2013 10:15:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1310241009370.27245@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <52690ED2.40402@sil.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1746 bytes --]
On Thu, 24 Oct 2013, Lars Huttar wrote:
> Hello,
> I was looking into simplefonts
> (http://wiki.contextgarden.net/simplefonts) and noticed the clause
>
>> if you’re running ConTeXt Standalone
>> <http://wiki.contextgarden.net/ConTeXt_Standalone> (which is a better
>> option)
>
> Well I'm using TeXLive, but am happy to take good advice, so I looked at
> http://wiki.contextgarden.net/ConTeXt_Standalone to see why it would be
> a better option.
> The basic reason I can see is that Standalone is updated more frequently.
Three or four years ago, when ConTeXt was moving from MkII to MkIV,
you had to run through hoops to get context working with TL. Since the
last two years, ConTeXt works out of the box in TL.
> So if you're using bleeding-edge features of ConTeXt (including recent
> fixes to simplefonts?), I can see wanting to use Standalone and have
> access to the latest features and fixes.
>
> On the other hand, if you're working on a large production project that
> has to be careful of stability, is there any advantage to Standalone
> over TeXLive? Sure, you can keep a standalone version frozen in place,
> but then that seems equivalent to staying with an existing version of
> TeXLive.
No. In some sense, it is better to use the frozen version that is part of
TL rather than an arbitrary beta version from standalone. Every once in a
while, the beta version has bugs (those are usually fixed in a matter of
hours). But it can be tricky to decide which version to freeze for a long
term production environment.
On the other hand, the version of ConTeXt that ships with TL is tested
more thoroughly. So, there is some guarantee that it will not include any
serious bugs.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2013-10-24 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 12:13 Lars Huttar
2013-10-24 12:57 ` Mojca Miklavec
2013-10-24 14:10 ` john Culleton
2013-10-24 14:18 ` Aditya Mahajan
2013-10-24 21:16 ` Wolfgang Schuster
2013-10-24 14:15 ` Aditya Mahajan [this message]
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=alpine.LNX.2.02.1310241009370.27245@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).