ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Hagmann Jörg" <joerg.hagmann@unibas.ch>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt-- does it make sense for my needs?
Date: Wed, 14 Dec 2011 15:31:05 +0100	[thread overview]
Message-ID: <36BB22D8-E46B-4F36-89B0-A2E26B5A504C@unibas.ch> (raw)
In-Reply-To: <CALBOmsZ5h-iY7N2yTBseEnn-oTVXUVpnujLQ2eAQCP36+KYcYA@mail.gmail.com>


On Dec 14, 2011, at 1:31 PM, Mojca Miklavec wrote:

> On Wed, Dec 14, 2011 at 07:14, Chris Lott wrote:
>> 
>> 3) PDF is my primary medium of exchange, though I would like to
>> efficiently exchange docs with colleagues, which might mean getting
>> them into something they can open with their beloved Microsoft Word...
>> is there an RTF output for ConTeXt? this isn't super-high on my list,
>> but it would be nice.
> 
> ConTeXt only support XHTML to some extent. Now that xhtml backend is
> done, creating support for rtf should be a lot easier to do than
> before xhtml export was there, but unless some substantial funding is
> found, it is unlikely to ever be implemented. Honestly I see no reason
> why anyone would want to have RTF. Even if your colleagues get a
> document in RTF and fix a few things, it won't at all be easy to
> integrate that back. tex4ht most probably offers export to RTF, but
> since author's death it is nearly impossible to request any
> substantial feature. I bet that ConTeXt doesn't work with tex4ht any
> more.
> 
> Roger suggested markdown/pandoc. It is limited to some extent, but if
> you are happy with its set of features, you could probably use it for
> export into both RTF and XHMTL. Of course then you can forget about
> lua sugars in ConTeXt ...

Another possibility is to use org-mode in Emacs, export to Latex and from there to ConTeXt. In my case, the last step is accomplished by a home-brewed ruby script which covers the most common layout commands (and I'm mentioning that here in the hope that somebody who is more competent will eventually write something useful; or maybe pandoc does that, too?).

This setup allows me to have everything belonging to a project in one textfile, e.g.:

* Heading

Notes, Ideas

Lists:
- item 1
- item 2

Tables:
| one | two | three |

Dates:
** TODO <2011-12-14 Wed 15:10>
which I can collect in an agenda

* Manuscript

This section contains a manuscript which I can separately export as:
- textfile
- Latex file
- HTML file
- odt file (for LibreOffice, where it can be saved as a Microsoft doc)

More sophisticated ConTeXt commands that are not provided for can be enclosed in

#+BEGIN_LaTeX
\Context command
#+END_LaTeX

or put behind

#+LATEX: \Context command

They will show up in the final ConTeXt version, but will not, of course, be translated into html, odt etc.

** Subsection :noexport:

This section is part of "Manuscript", but will not be exported.

There are many more features, see http://orgmode.org/

Hope this helps, Jörg
___________________________________________________________________________________
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:[~2011-12-14 14:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  6:14 Chris Lott
2011-12-14  8:09 ` Pontus Lurcock
2011-12-14 11:22 ` Roger Mason
2011-12-14 15:14   ` Chris Lott
2011-12-18 15:39   ` Bruce
2011-12-14 12:31 ` Mojca Miklavec
2011-12-14 14:31   ` Hagmann Jörg [this message]
2011-12-14 15:38     ` Chris Lott
2011-12-14 15:53       ` Hagmann Jörg
2011-12-14 20:32     ` Peter Münster
2011-12-15  7:40       ` Jean Magnan de Bornier
2011-12-15 10:58         ` Hagmann Jörg

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=36BB22D8-E46B-4F36-89B0-A2E26B5A504C@unibas.ch \
    --to=joerg.hagmann@unibas.ch \
    --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).