ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Victor Eijkhout <victor@eijkhout.net>
To: ntg-context@ntg.nl
Subject: Re: suggestions for context documentation
Date: Tue, 9 Mar 2010 07:25:39 -0600	[thread overview]
Message-ID: <D3C06D1F-1239-4399-9FAC-E8C032F05C2E@eijkhout.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]

> \startitem Even an old manual can quite well describe
> functionality as much didn't change. It's only with \MKIV\ that
> some compatibility is dropped and only for obscure features. Of
> course I could trick users by regenerating a manual with a newer
> date. I often use the excellent book \quote {\TEX\ by Topic} which
> is already quite old and does not cover \ETEX, \PDFTEX, \LUATEX\
> or whatever but what is told in it is still true. I never look at
> it thinking it being old. \stopitem

Hans,

thanks for the compliments.

Let me point out that the source of TeX by Topic is available under  
the Gnu Public Documentation License, so anyone should feel free to  
add modern TeX additions to it. Personally I feel that the eTeX &  
pdTeX additions are mature enough that they could be added, of course  
with suitable markers to indicate their non-standardness. I don't have  
the time for this, but I'd welcome a collaboration with anyone that  
wants to invest the time.

Victor.


[-- Attachment #1.2: Type: text/html, Size: 1305 bytes --]

[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________

             reply	other threads:[~2010-03-09 13:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 13:25 Victor Eijkhout [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-05 10:33 richard.stephens
     [not found] <mailman.647.1267779271.26807.ntg-context@ntg.nl>
2010-03-05 10:01 ` richard.stephens
2010-03-05 10:51   ` Patrick Gundlach
2010-03-05 12:50   ` Thomas A. Schmitz
2010-03-05 13:41     ` Jörg Hagmann
2010-03-05 16:17     ` Willi Egger
2010-03-08 12:31   ` Hans Hagen
2010-03-08 14:51     ` Alan BRASLAU
2010-03-05  2:10 Michael Saunders
     [not found] ` <771da05a1003041822r1b056820jd198170aee3ab95@mail.gmail.com>
2010-03-05  2:23   ` James Fisher
2010-03-05  4:34 ` Wolfgang Schuster
2010-03-05  5:14   ` Khaled Hosny
2010-03-05  5:19 ` Vnpenguin
2010-03-05  8:39 ` luigi scarso
2010-03-05  8:54 ` R. Bastian
2010-03-05 13:40 ` Marcin Borkowski
2010-03-04 21:31 Michael Saunders
2010-03-04 21:37 ` luigi scarso
2010-03-04 21:40 ` Aditya Mahajan
2010-03-04 22:01   ` James Fisher
2010-03-04 23:05     ` Aditya Mahajan
2010-03-04 23:13       ` James Fisher
2010-03-04 23:18         ` Aditya Mahajan
2010-03-04 14:41 Peter Münster
2010-03-04 16:46 ` James Fisher

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=D3C06D1F-1239-4399-9FAC-E8C032F05C2E@eijkhout.net \
    --to=victor@eijkhout.net \
    --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).