ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Brooks Moses <bmoses@stanford.edu>
Subject: LaTeX \newcommands in ConTeXt.
Date: Sun, 24 Jul 2005 23:15:21 -0700	[thread overview]
Message-ID: <4.3.1.2.20050724224715.01aeab60@cits1.stanford.edu> (raw)

I've recently been doing a little work on implementing a few LaTeX kernel 
bits in ConTeXt, to simplify porting LaTeX code over.  It's now at a point 
where a few of the pieces might actually be useful, and certainly to a 
point where some comments would be welcomed, so I've put up a version of it 
online, in this directory:

     http://dpdx.net/context/latex-compat/

What you'll find there is a fair number of module files, along with a 
couple of "latextest" files that I've been using to try out the 
results.  latextext.tex is to be compiled in ConTeXt; latextext-latex.tex 
is to be compiled in LaTeX for purposes of comparison.

In any case, I think the implementation of \newcommand (and its relatives) 
is about up to "beta" level.  Ditto with LaTeX lengths.  And there's a 
working LaTeX-like counter implementation, based on ConTeXt counters 
underneath.  (It's not yet hooked into ConTeXt's counters for footnotes and 
equations and pages, though; I'm not really sure how to do that.)

Also, environments are working, in a sort of hackish way.  The "array" 
environment works, but again a bit hackish; I'm planning to clean that up 
soon, so both of those will get major revisions.

I'd particularly appreciate any comments on the \newcommand and counters 
implementations -- those are in the t-ltcmds and t-ltcnts modules, though 
\newcommand also depends on t-lterrs and t-ltbase.

- Brooks

             reply	other threads:[~2005-07-25  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25  6:15 Brooks Moses [this message]
2005-07-25 23:28 ` Hans Hagen
2005-07-26  1:03   ` Brooks Moses
2005-07-26  7:08     ` Hans Hagen
2005-09-23 17:01 ` Patrick Gundlach

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=4.3.1.2.20050724224715.01aeab60@cits1.stanford.edu \
    --to=bmoses@stanford.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).