ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seeking a Deeper ConTeXt: Questions for	Initializing
Date: Mon, 25 May 2009 19:23:58 +0200	[thread overview]
Message-ID: <20090525172358.GA24988@phare.normalesup.org> (raw)
In-Reply-To: <4c1f1f860905250930g2e44f973y335be816c2883981@mail.gmail.com>

> These paragraphs seems to contradict. ConTeXt is useful if you use an
> environment more than once, but there are no ready-to-use ConTeXt
> environments.

  You're probably confused by the term "environment".  It means
something very specific in ConTeXt, see for example section 2.3 of
http://www.pragma-ade.com/general/manuals/cont-eni.pdf

  If by "environment" you mean some less down-to-earth, general document
layout, e.g. for articles, books, presentation slides or letters, then
yes, there are such ready-to-use layouts.  Not always in the ConTeXt
core, but they're there; for example, for letters you would use Wolfgang
Schuster's letter module; for presentation, one of the solutions is
Thomas Schmitz' and Aditya Mahajan's simple-presentation module, etc.

> Yes, I meant RDF. XML is a very important format. I find it odd that TeX can
> generate PDF but cannot output simple XML.

  Generating a document with a logical structure is really the opposite
of what TeX does, at least in my view: in today's trend, you write a TeX
document with a logical structure, and you generate PDF, a highly
specialized format for describing the layout of a printed or on-screen
page; it has rather few means of specifying logical structure (it's
coming, but rather poorly supported by PDF producer applications at the
moment).  The same is of course even more true of DVI.  Hence, what TeX
does is to take a logically structured document, and to make it into a
visually structured one.

  Note that I am not always convinced by the whole "separation of
content and layout" creed which is heard very often as a selling point
for LaTeX vs. MS Word etc., but there is some truth to it, and,
generally speaking, you're still going from semantic markup to visual
appearance, not the other way round.

>                                            So in order to have a semantical
> document I must write it in XML and then process it with ConTeXt?

  Pretty much.  ConTeXt is rather good at it.  You have a lot of tools
to process XML in the base code.  There is also a module to deal with
DocBook, but I think its development has stalled.

>                                                                   Is the
> capacity there (through LuaTeX perhaps) to write an XML generator?

  The goal is that at some point, you will be able to redefine LuaTeX's
backend, the same way you can act on the TeX engine at the moment.  This
will allow to control the output format entirely.

> While I would expect the reasons for wanting XML output would be obvious

  If I may, your statement might be biased by your own expectations.
There are thousand people out there who use some form of TeX without
even knowing about XML.  But I know why you want it.

  As far as LaTeX is concerned, there are quite a number of toolchains
that produce XML from some sort of restricted LaTeX markup.  I'm not
aware of anything similar for ConTeXt.

	Arthur
___________________________________________________________________________________
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
___________________________________________________________________________________


  parent reply	other threads:[~2009-05-25 17:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 17:17 John Haltiwanger
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 [this message]
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=20090525172358.GA24988@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).