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: context export
Date: Sun, 7 Nov 2010 16:05:42 -0500 (EST)	[thread overview]
Message-ID: <alpine.LNX.2.01.1011071555410.12558@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20101107193412.7ae57ee0@arcor.com>

On Sun, 7 Nov 2010, Manfred Lotz wrote:

> Hi Hans,
>
> On Sun, 07 Nov 2010 16:23:37 +0100
> Hans Hagen <pragma@wxs.nl> wrote:
>
>> Hi Manfred,
>>
>> some reading ... it should not be to hard to map the xml onto
>> html ... relevant details are in attributes
>>
>
> Hmm, but I would need to have a dtd or schema file in order write a
> transformation (xslt or so) to html.


No. I think that Hans meant that you should be able to generate an html 
document directly out of context (instead of the xml document that is 
currently generated).

> The other possibility would be to make the html creation an iterative
> process along the creation of the context document. I'd would prefer
> the first possibility, though.

Another possibility is to just write html (rather xhtml) and process it 
directly in ConTeXt. See the XML manual and Thomas's MyWay on processing 
XHML.

> Instead of using xslt I also could code the transformation in Lua. What
> xml lib do you recommend to use in Lua?

I don't know about the lua librarties.

> Currently, I have no time to code the xml --> htmp conversion.

In the long run, if you want multiple formats for a document that is 
slightly complicated, translating the input to xml is the easiest 
solution.

> However, considering above ideas I could start with markdown as
> discussed in the other thread which has limitations but gives me a
> context source for free as a starting point.

You can also consider richer ascii markups: rst and asciidoc. 
Unfortunately, pandoc only has partial support for rst, and the default 
tools for rst and asciidoc do not export to context.

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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2010-11-07 21:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 18:34 Manfred Lotz
2010-11-07 21:05 ` Aditya Mahajan [this message]

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.LNX.2.01.1011071555410.12558@ybpnyubfg.ybpnyqbznva \
    --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).