From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: ConTeXt versioning model critique
Date: Sat, 14 Apr 2007 23:19:36 +0200 [thread overview]
Message-ID: <fe8d59da0704141419p6cf22408s6b59f14a4b52a7c8@mail.gmail.com> (raw)
In-Reply-To: <46213DFC.6000903@wxs.nl>
On 4/14/07, Hans Hagen <pragma@wxs.nl> wrote:
> Ulf Martin wrote:
> > I wonder how people (esp. at Pragma) currently deal with this.
> for projects where we use relatively new features (which evolve) we use
> frozen trees;
Confirm
One tree of 2002 ("still-crazy-after-all-these-years").
Another of 2004.
Switch to last pdftex/context sometimes second quarter of this year;
switch to luatex at the end of next year.
Why switch ?
Last versions. are better (speed and features);
pdf spec. change .
>
> with regards to commands and such ... context is just (supposed to be)
> downward compatible; even kind of obsolete is still there; with regards
> to different solutions to problems, we often provide control usign low
> level mode indicators
On average, my macros are not completly portable from one tree to another,
but I'm sure that this depend from my poor coding tecnique for 95% .
5% is made by spaces and fonts .
>
> concerning xetex ... keep in mind that there xetex is the moving target
> (changes/extensions in interface) and to some extend this was true for
> pdftex as well, but there we could silently adapt
> > Also remember that Knuth originally intended TeX to be an "eternal"
> > formatting system (thus we have at least the option to expand all macros
> > into plain TeX and keep that as the source file).
> >
> plain tex is just a format and unsuitable as expanded format
>
> well, i have some experimental code that dumps the expanded token list
> into a file; nu fun ... a 50 page moderately complex doc becomes some 25
> meg -)
pdf has some sort of compression .
Do \pdfcompresslevel=0 \pdfobjcompresslevel=0
make some differences in your 50page document?
> Sanjoy has set up an advanced test system ... so anything that you
> contribute can go in there
I will install on my machine.
luigi
next prev parent reply other threads:[~2007-04-14 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1176544802.32527.ntg-context@ntg.nl>
2007-04-14 11:29 ` Vyatcheslav Yatskovsky
2007-04-14 15:03 ` Ulf Martin
2007-04-14 20:47 ` Hans Hagen
2007-04-14 21:19 ` luigi scarso [this message]
2007-04-20 12:31 ` fdu.xiaojf
2007-04-20 13:17 ` Taco Hoekwater
2007-04-23 1:15 ` fdu.xiaojf
2007-04-20 20:57 ` Hans Hagen
2007-04-20 21:42 ` Table of contents and 2UP or 2SIDE Horacio Suarez
2007-04-21 6:23 ` Hans Hagen
2007-04-14 12:28 ` Some progress with XeTeX Vyatcheslav Yatskovsky
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=fe8d59da0704141419p6cf22408s6b59f14a4b52a7c8@mail.gmail.com \
--to=luigi.scarso@gmail.com \
--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).