ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: cont-enp.pdf on lulu
Date: Mon, 28 Jul 2008 22:36:38 +0200	[thread overview]
Message-ID: <488E2DD6.6080001@wxs.nl> (raw)
In-Reply-To: <E0B81000-DBB9-46F8-A91E-A6E033491EEA@rna.nl>

Gerben Wierda wrote:

> Somehow, this might be applied to ConTeXt I think ;-). Three out of  
> four afaic...

well, it's one reason why we have multiple smaller manuals (often made 
in sync with the specific feature)

anyhow ... taco and i only have one livetime, 24h/day etc etc

currently we spend quite some time on luatex/mp/mkiv (if not we could as 
well stop using tex in the near future) alongside our regular jobs ... 
we simply have not much more time available ... on the other hand, we 
don't intend to stop soon, so eventually ...

btw, quite some documentation about latex is *not* written by the 
author(s) so it's not entirely fair to expect that taco and i write all 
of it -)

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-07-28 20:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-21 23:58 abbg770
2008-07-22  0:37 ` John Culleton
2008-07-25 20:07   ` Gerben Wierda
2008-07-25 22:42     ` luigi scarso
2008-07-25 23:31     ` Aditya Mahajan
2008-07-26  2:38       ` Gerben Wierda
2008-07-27 19:40         ` David
2008-07-28  9:50           ` Gerben Wierda
2008-07-28 10:46             ` Taco Hoekwater
2008-07-28 12:48               ` Gerben Wierda
2008-07-28 12:57                 ` Taco Hoekwater
2008-07-28 14:11                   ` Aditya Mahajan
2008-07-28 23:07                 ` Uwe Koloska
2008-07-28 14:20           ` Hans Hagen
2008-07-28 15:44             ` Gerben Wierda
2008-07-28 20:36               ` Hans Hagen [this message]
2008-07-29  9:02                 ` Gerben Wierda
2008-07-29 12:44                   ` Aditya Mahajan
2008-07-29 20:01                     ` Gerben Wierda
2008-07-29 18:05                   ` Hans Hagen
2008-07-29 19:54                     ` Gerben Wierda
2008-07-30 16:21                     ` Fabrice Popineau
2008-07-31 16:17                       ` Hans Hagen

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=488E2DD6.6080001@wxs.nl \
    --to=pragma@wxs.nl \
    --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).