ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Haltiwanger <john.haltiwanger@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Seeking a Deeper ConTeXt: Questions for Initializing
Date: Sun, 24 May 2009 13:17:13 -0400	[thread overview]
Message-ID: <4c1f1f860905241017s40033f7crde553d358a24b57f@mail.gmail.com> (raw)


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

Hello,

My name is John and I'm a nearly brand new TeX convert. All it took was one
letter I wanted to look nice and now I know I will never craft an important
document in another format again.

Now, an obvious entry point is LaTeX, and indeed my first TeX document used
this macro package. However, I couldn't help but stumble across the ConTeXt
project in my investigation of the TeX landscape. The seemingly distinct
separation of style from content, evidenced by the print versus the screen
versions of some of the manuals, instantly endeared me.

Within the same week, I found the comp.text.tex newsgroup. Lo and behold
there was a quite active thread on LuaTeX, which I had just finished reading
a presentation and a couple papers on the night before. On of the issues
being discussed was the lack of a LaTeX document class for "thesis". This
also involved discussion of LaTeX's shortcomings.


I wrote into the thread that based on my (albeit completely theoretical)
understanding, ConTeXt would be a wiser choice as a macro for any new
department to begin requiring TeX documents. This was based on my vague
understanding of the separation of environment from the content, as it were,
and also on the multiple outputs available for the manuals. Since I see
screen formatting as equally important, if not more, than paper formatting,
it only made sense to me that the equivalent of a unversity specific
documentclass in LaTeX would be a simple environment file in ConTeXt.


This leads me to some questions I have about how great a fit for me ConTeXt
actually is.


1) Can environment files be used across documents, or is it generally
understood that every ConTeXt document requires its own environment
formatting? (The latter is the view of someone on c.t.t, who said his
perception of ConTeXt was that it was for typesetting individual documents
and had less application beyond that domain.)


2) What is the state of XML output for ConTeXt files? I have to say I will
find it hard to justify using TeX for documents if it means they are not
translatable to XML easily. I'm also interested in any RDF support ConTeXt
might have.


I am just beginning my journey into TeX, and wish to learn the best macro
package available. To me it seems like this is ConTeXt hands down, however
the two questions above will indeed determine ConTeXt's actual utility in my
case.


Regards,

John C. Haltiwanger


P.S. For my first question, it seems easy to assume that if you can process
XML files into standardized ConTeXt documents, the same would go for
processing ConTeXt into standardized ConTeXt documents. But the question is
too large not to ask.

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

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2009-05-24 17:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 17:17 John Haltiwanger [this message]
2009-05-24 18:35 ` Henning Hraban Ramm
2009-05-25 16:30   ` John Haltiwanger
2009-05-25 16:39     ` Hans Hagen
2009-05-25 16:53       ` John Haltiwanger
2009-05-25 16:59         ` Hans Hagen
2009-05-26 15:54       ` Bruce D'Arcus
2009-05-26 21:26         ` John Haltiwanger
2009-05-26 22:08           ` luigi scarso
2009-05-26 23:07           ` Bruce D'Arcus
2009-05-25 16:50     ` Wolfgang Schuster
2009-05-25 17:00       ` John Haltiwanger
2009-05-25 17:12         ` Mohamed Bana
2009-05-25 17:24         ` Hans Hagen
2009-05-25 17:51           ` John Haltiwanger
2009-05-25 18:00             ` Arthur Reutenauer
2009-05-25 18:09               ` John Haltiwanger
2009-05-25 18:21                 ` Arthur Reutenauer
2009-05-25 18:24                   ` John Haltiwanger
2009-05-25 18:55                 ` Hans Hagen
2009-05-25 21:09                   ` luigi scarso
2009-05-25 21:14                     ` Hans Hagen
2009-05-25 21:16                     ` Arthur Reutenauer
2009-05-25 20:25             ` Mohamed Bana
2009-05-25 21:02               ` John Haltiwanger
2009-05-26 22:27               ` Wolfgang Schuster
2009-05-25 17:23     ` Arthur Reutenauer
2009-05-25 18:26     ` Aditya Mahajan
2009-05-25 18:35       ` John Haltiwanger

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=4c1f1f860905241017s40033f7crde553d358a24b57f@mail.gmail.com \
    --to=john.haltiwanger@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).