ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: HTML to ConTeXt
Date: Fri, 26 Oct 2007 00:22:46 -0400 (EDT)	[thread overview]
Message-ID: <alpine.WNT.0.9999.0710251825340.1268@nqvgln> (raw)
In-Reply-To: <op.t0rrys1hnx1yh1@your-b27fb1c401>

On Thu, 25 Oct 2007, Idris Samawi Hamid wrote:

> Hi Aditya,
>
> On Thu, 25 Oct 2007 08:50:03 -0600, Aditya Mahajan <adityam@umich.edu>
> wrote:
>
>> This is interesting. A website that converts html to context
>> (actually uses markdown behind the scenes).
>>
>> http://johnmacfarlane.net/pandoc/html2x.html
>>
>> This is how the context wiki looks like.
>>
>> http://johnmacfarlane.net/cgi-bin/html2x.pl?url=http%3A%2F%2Fwiki.contextgarden.net%2FMain_Page&format=context
>>
>> The program is written in haskell and is also available for download.
>> You can use it to convert markdown to context. I had been looking for
>> this for a while, when multiple formats are needed. Write in markdown
>> and generate html or context. I do not completely like the context
>> output it generates (for example
>> http://johnmacfarlane.net/pandoc/README gets converted to
>> http://johnmacfarlane.net/pandoc/example11.tex.html)
>
> 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.

Aditya
___________________________________________________________________________________
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  4:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 14:50 Aditya Mahajan
2007-10-25 20:17 ` Idris Samawi Hamid
2007-10-26  4:22   ` Aditya Mahajan [this message]
2007-10-26 11:37     ` Doc to ConTeXt [was Re: HTML to ConTeXt] Idris Samawi Hamid
2007-11-10  1:30       ` 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
  -- strict thread matches above, loose matches on Subject: below --
2005-01-15 15:12 html to context ishamid
2005-01-15 15:23 ` Adam Lindsay
2005-01-15 15:24 ` Patrick Gundlach

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=alpine.WNT.0.9999.0710251825340.1268@nqvgln \
    --to=adityam@umich.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).