ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Doc to ConTeXt [was Re:  HTML to ConTeXt]
Date: Fri, 26 Oct 2007 05:37:52 -0600	[thread overview]
Message-ID: <op.t0sylef3nx1yh1@your-b27fb1c401> (raw)
In-Reply-To: <alpine.WNT.0.9999.0710251825340.1268@nqvgln>

On Thu, 25 Oct 2007 22:22:46 -0600, Aditya Mahajan <adityam@umich.edu>  
wrote:

>> This looks very promising. Perhaps some of us can help the developers to
>> improve the ConTeXt support.
>>
> I will explore pandoc in more detail in the future. I am more
> interested in it from the point of view of understanding Haskell
> parsers, but improving the context output will definitely not hurt.

Ah, you're missing a big point in your discovery ;-)

As I told Andrea: For relatively simple documents (like the kind we use in  
academic journals) it seems we can now

1) convert doc to odt using OOo
2) convert odt to markdown using

http://wiki.services.openoffice.org/wiki/Odt2txt.py

3) use the pandoc utility to convert markdown to ConTeXt.

As for the pandoc list, we may be able to influence the final ConTeXt  
output by making suggestions, reporting bugs etc.

If we can convert Odt2txt.py to lua maybe this workflow can be partly  
integrated into ConTeXt itself someday.*****

The pandoc developer seems interested in improving ConTeXt support (see my  
forwarded mail) so this is a good opportunity for all those who need a  
decent doc=>context workflow.

Best wishes
Idris

*****Or maybe we can just port Odt2txt.py to give direct ConTeXt output  
and forget the markdown layer entirely. Any ideas on how hard that would  
be?

-- 
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___________________________________________________________________________________
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-10-26 11:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 14:50 HTML to ConTeXt Aditya Mahajan
2007-10-25 20:17 ` Idris Samawi Hamid
2007-10-26  4:22   ` Aditya Mahajan
2007-10-26 11:37     ` Idris Samawi Hamid [this message]
2007-11-10  1:30       ` Doc to ConTeXt [was Re: HTML to ConTeXt] Andrea Valle
2007-11-10  3:14         ` Idris Samawi Hamid
2007-11-10 11:25           ` Andrea Valle
2007-11-10 12:09             ` Andrea Valle
2007-11-10  3:33         ` Idris Samawi Hamid
2007-11-10 11:59           ` Andrea Valle
2007-11-10 14:07             ` Idris Samawi Hamid
2007-11-10 14:11               ` Andrea Valle
2007-11-10 19:08                 ` Hans Hagen
2007-11-10  5:44         ` Saji Njarackalazhikam Hameed
2007-11-10 13:10           ` Andrea Valle
     [not found]         ` <6faad9f00711100331h547664c6l97d2c3b82c16d8dd@mail.gmail.com>
2007-11-10 12:30           ` Andrea Valle

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=op.t0sylef3nx1yh1@your-b27fb1c401 \
    --to=ishamid@colostate.edu \
    --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).