From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: migrating to ConTeXt
Date: Mon, 24 Dec 2007 14:40:06 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.0.9999.0712241430560.14218@nqv-yncgbc> (raw)
In-Reply-To: <20071222110122.48a3408f@gaura-nitai.dyndns.org>
On Sat, 22 Dec 2007, Gour wrote:
> 5) I read LaTeX in proper ConTeXt pdf, but I'm interested is there some
> helper to convert classical LaTeX book (book class) to ConTeXt? I've two
> books which I'm considering to publish as one (~1000p) in the future, so
> any help in conversion would be nice.
I do this quite often (ConTeXt -> LaTeX), so I am just writing my thoughts
about this. A general purpose translator from ConTeXt to LaTeX is VERY
difficult, because of the nature of both macro languages. However, it is
relatively simple to convert a subset of one to the other. Currently, I
write most of my papers in ConTeXt. For the final version of the paper,
most journals want LaTeX. I know my style of writing ConTeXt, and can
easily convert 95% percent of it to LaTeX using regular expressions (and
have been thinking of exploring gema in more detail:
http://gema.sourceforge.net/). It is easier to do the rest by hand rather
than writing a script that takes care of all the corner cases. Usually it
takes me around 2 hours to convert a (30-40 page) paper from ConTeXt to
LaTeX. Since this needs to be done only once every six months or so, I
have not spent too much time trying to optimize my approach. I think that
the same will be true for conversion from LaTeX to ConTeXt. However, I
would suggest that you start by writing some ConTeXt documents by hand,
before you automate the conversion. This way, you will know what you want
to achieve from a conversion script.
Another option is to write a ConTeXt module that will allow you to
understand LaTeX. For most environments, this is simple. There are a few
examples on the wiki about this.
> 6) the most important issue - by looking at luaTeX docs & archives I
> noticed that it was mentioned there is some book on ConTeXt in
> preparation - I gave up on ConTeXt in the past due to this reason -
> lack of up-to-date documentation - didn't have enough time to try to
> sovle the puzzle by inspecting different 'magazines' etc. cause I was
> able to do the kob with LaTeX for which I've documentation in the form
> of paper books.
Actually, from a user's point of view, most things are included in the
ConTeXt manuals. They are not exhaustive or up-to-date, but do convey the
essential information. For most tasks you do not need to know the current
state of affairs in ConTeXt.
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-24 19:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 6:55 Gour
2007-12-22 9:13 ` luigi scarso
2007-12-22 10:01 ` Gour
2007-12-22 11:00 ` Jean Magnan de Bornier
2007-12-22 14:02 ` Gour
2007-12-22 13:33 ` Mojca Miklavec
2007-12-22 14:19 ` Gour
2007-12-22 20:09 ` Mojca Miklavec
2007-12-22 21:11 ` Gour
2007-12-23 12:57 ` Wolfgang Schuster
2007-12-23 15:39 ` Idris Samawi Hamid
2007-12-24 6:43 ` Gour
2007-12-24 8:29 ` Hans Hagen
2007-12-24 15:58 ` Gour
2007-12-24 14:58 ` Idris Samawi Hamid
2007-12-24 15:15 ` Wolfgang Schuster
2007-12-24 6:41 ` Gour
2007-12-24 19:40 ` Aditya Mahajan [this message]
2007-12-29 12:48 ` George N. White III
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.DEB.0.9999.0712241430560.14218@nqv-yncgbc \
--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).