ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Duncan Hothersall <dh@capdm.com>
To: ntg-context@ntg.nl
Subject: Re: Write once layout everwhere (?)
Date: Mon, 11 Jun 2007 11:46:12 +0100	[thread overview]
Message-ID: <466D27F4.7050909@capdm.com> (raw)
In-Reply-To: <mailman.429.1181527849.2368.ntg-context@ntg.nl>

Hi Pepe,

If you want your content to remain maintainable and manageable for a 
long period (e.g. decades), if you can afford it, and if you have a 
sufficiently large amount of content, then I strongly recommend 
investing the time and effort in an XML-based solution.

My experience is in large scale educational/commercial applications, in 
which managing content in XML and using tools like ConTeXt to create 
beautiful print output, and alternate tools to create web output from 
the same source, is a very good solution. I can certainly let you know 
the technology we use, but some of it is commercial and expensive, and 
other bits are just complicated! I did a talk at the user group meeting 
which was kinda about this: http://context.aanhet.net/epen2007/share/duncan/

The first question to ask yourself is how much effort is your content 
worth. The rest of the answers flow from that, in my experience. :-)

Duncan
> Hello,
>
> I have used ConTeXt in the past and I have been very pleased with it
> and the results obtained, much more than LaTeX.
>
> Now I am looking into a solution that would allow me to layout the
> content ConTeXt and in other formats that ConTeXt does not (Forgive my
> ignorance, if I am wrong) output, like HTML, Plain Text, or RTF (Those
> are the formats that I can think of that are interesting to me
> currently).
>
> Reading the Wiki one of those solutions would be XML, but I know very
> little about the subject, so this email is to ask about experiences in
> similar endeavors, other solutions for the same problem and how
> practical this is.
>
> I suppose that I would use this for general writing and for academic
> as well (Maths and engineering).
>
> Thanks,
> Pepe
>   
>   
___________________________________________________________________________________
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:[~2007-06-11 10:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.429.1181527849.2368.ntg-context@ntg.nl>
2007-06-11 10:46 ` Duncan Hothersall [this message]
2007-06-10 22:31 Pepe Barbe
2007-06-11  3:49 ` Aditya Mahajan
2007-06-11  5:16   ` luigi scarso
2007-06-11 12:26   ` John R. Culleton
2007-06-11 13:15     ` Aditya Mahajan
2007-06-11 12:26   ` Thomas A. Schmitz
2007-06-11 13:09     ` Aditya Mahajan
2007-06-11 13:34       ` Wolfgang Schuster
2007-06-11 15:42         ` Aditya Mahajan
2007-06-11 19:35           ` nico
2007-06-11 20:19             ` Aditya Mahajan
2007-06-11 20:28 ` nico

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=466D27F4.7050909@capdm.com \
    --to=dh@capdm.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).