From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTexT conversion to html/rtf/odt
Date: Sat, 6 Nov 2010 17:00:38 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1011061655200.12550@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20101106203359.208dccb6@arcor.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1867 bytes --]
On Sat, 6 Nov 2010, Manfred Lotz wrote:
> I'm in a situation where I have to do some documentation which should
> be available in html and rtf/odt (would be nice to have).
There is an experimental feature of converting ConTeXt to XML. You can
then process XML using standard XML tools to get HTML.
> I do not need any fancy stuff, just simple things: ordered,
> unordered lists, verbatim, tables etc.
\setupbackend[export=yes]
> \starttext
>
> \section{Some section}
>
> \startitemize[1]
> \item bla bla
> \stopitemize
>
> \stoptext
Run "context filename". This will create a filename.export file in your
current directory that looks like this:
<?xml version='1.0' standalone='yes' ?>
<!-- input filename : back -->
<!-- processing date : Sat Nov 6 16:55:02 2010 -->
<!-- context version : 2010.10.14 13:14 -->
<!-- exporter version : 0.10 -->
<document language='en' file='back' date='Sat Nov 6 16:55:02 2010'
context='2010.10.14 13:14' version='0.10'>
<section detail='section'>
<sectionnumber>1</sectionnumber>
<sectiontitle>Some section</sectiontitle>
<sectioncontent>
<itemgroup detail='itemize' symbol='1'>
<item>
<itemtag><math><mrow><mo>•</mo></mrow></math></itemtag>
<itemcontent>bla bla</itemcontent>
</item>
</itemgroup>
</sectioncontent>
</section>
</document>
> work for ConTeXt and then I would like to know what other alternatives
> I have. Also regarding rtf or/and odt.
Since you do not need any fancy features, a simpler option is to use
markdown as your starting format and use pandoc to convert it to context,
html, and odt. However, creating even slightly complicated tables in
markdown is a pain, unless your editor supports an ascii table mode.
Aditya
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-06 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-06 19:33 Manfred Lotz
2010-11-06 21:00 ` Aditya Mahajan [this message]
2010-11-07 10:18 ` John Haltiwanger
2010-11-07 20:50 ` Aditya Mahajan
2010-11-07 10:54 ` Manfred Lotz
2010-11-07 11:09 ` luigi scarso
2010-11-07 11:12 ` Hans Hagen
2010-11-07 11:02 ` luigi scarso
2010-11-07 9:51 ` Mojca Miklavec
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.1011061655200.12550@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).