ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "John R. Culleton" <john@wexfordpress.com>
To: ntg-context@ntg.nl
Subject: Re: Write once layout everwhere (?)
Date: Mon, 11 Jun 2007 08:26:12 -0400	[thread overview]
Message-ID: <200706110826.13550.john@wexfordpress.com> (raw)
In-Reply-To: <alpine.WNT.0.99.0706102328350.3396@nqvgln>

On Sunday 10 June 2007 23:49, Aditya Mahajan wrote:
> On Sun, 10 Jun 2007, Pepe Barbe wrote:
> > 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).
> >
I don't think it is possible to come up with an "universal elixir" 
that does any format from source and is efficient to use. Plain text 
is the exchange medium I use.  XML is too cumbersome to code by hand. 
Therefore I have solutions for specific situations. For example when 
a customer presents me with a non-fiction document already laid out 
in MSWord, I first save it as rtf. Then I run it through the program 
rtf2latex2e. This gives me an executable LaTeX file, with all the 
font changes etc. preserved. The I edit it in Gvim, using mass 
changes to convert LaTeX tags to an equivalent Context format. Some, 
like all the begin/end tags I just delete en masse. 

It is easy to go from the output of Context to plain text.  There are 
plenty of pdf to ascii converters in GhostScript and PSUtils etc.   
The only big problem comes when there are columns involved. 
In that situation cut and paste from a pdf viewer window to an editor 
window can be helpful.


-- 
John Culleton
Able Indexing and Typesetting
Precision typesetting (tm) at reasonable cost.
Satisfaction guaranteed. 
http://wexfordpress.com

___________________________________________________________________________________
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:[~2007-06-11 12:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [not found] <mailman.429.1181527849.2368.ntg-context@ntg.nl>
2007-06-11 10:46 ` Duncan Hothersall

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=200706110826.13550.john@wexfordpress.com \
    --to=john@wexfordpress.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).