On Thu, 25 Oct 2007 22:22:46 -0600, Aditya Mahajan <[EMAIL PROTECTED]> 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 ___________________________________________________________________________________
