ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seeking a Deeper ConTeXt: Questions for	Initializing
Date: Mon, 25 May 2009 18:39:20 +0200	[thread overview]
Message-ID: <4A1AC9B8.3050807@wxs.nl> (raw)
In-Reply-To: <4c1f1f860905250930g2e44f973y335be816c2883981@mail.gmail.com>

John Haltiwanger wrote:
> On Sun, May 24, 2009 at 2:35 PM, Henning Hraban Ramm <hraban@fiee.net>wrote:
> 
>> Am 2009-05-24 um 19:17 schrieb John Haltiwanger:
>>
>>  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.)
>>>
>> Normally you use environment files for coherent projects (magazines, books)
>> or sets of similar documents (letters, presentations).
>>
>> The difference in usage between a LaTeX document class and a ConTeXt
>> environment is neglectable IMO. The real difference is that most LaTeX users
>> just *use* some document class unchanged, because LaTeX doesn't encourage
>> defining your own, while there are nearly no ready-to-use ConTeXt
>> environments available and most ConTeXt users want write their own anyway.
>>
>> For one-off documents I put everything in one file (and perhaps copy setup
>> bits from other one-off files or environments).
>>
>> If *I* require a special layout for a single document, I normally use
>> InDesign. The effort of "programming" a setup or an environment pays off
>> only if you use it more often IMO.
>>
> 
> 
> 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.

setting up a style for a paper takes a few commands: \setuplayout, 
\setuphead, \setupheadertexts ... and then structure in your document 
can do the rest; however, if we have styles of (say) 40 lines of code, 
users want a different font, diferen theaders etc and patch those 40 
lines which then gives 80 lines most of which are redundant

i've seen that happen a lot: copy an old style, then patch 50%, copy 
that file, patch again, and eventually one gets a big style that is 90% 
code that does more harm than good

as context does need a style to start with, you can just start working 
and then every time you wonder if it should look different, you add a 
few lines to the preamble or style (more fun that way too)

> I am not averse to rolling my own, I am just confused why, if environments
> are so powerful and flexible (flexible meaning one can easily change things,
> unlike document classes), there are no pre-rolled environments available. I
> am thinking here of standardized thesis environments for universities, or a
> nice letter environment to demonstrate the beauty of TeX.

sure, but all organizations want it slightly different
> 
>  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.
>>
> 
> XML is no target format for any TeX implementation.
>> XML is a source format, and a good one if you want to process (typeset) it
>> with ConTeXt (and perhaps make HTML from the same source).
>>
>> What do you mean with RDF? This one?: http://www.w3.org/RDF/
>> Or did you mean RTF?
> 
> 
> Yes, I meant RDF. XML is a very important format. I find it odd that TeX can
> generate PDF but cannot output simple XML. So in order to have a semantical
> document I must write it in XML and then process it with ConTeXt? Is the
> capacity there (through LuaTeX perhaps) to write an XML generator?

sure, but how useful is it to have a representation of (e.g.) a node 
list that makes up a paragraph in xml format? no app can do something 
with it

maybe at some point the adobe and microsoft xml output formats become an 
option (which then involves resources like fonts and graphics as well so 
  it's pretty bulky and one might wonder what gain there is)

> While I would expect the reasons for wanting XML output would be obvious, a
> concrete example is that at least one journal is deprecating LaTeX because
> it wants to archive all of its articles in XML.

in which case it keeps the input in xml and converts to other formats 
(coule be tex in the case of rendering print)


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-25 16:39 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 [this message]
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=4A1AC9B8.3050807@wxs.nl \
    --to=pragma@wxs.nl \
    --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).