From: "Jörg Hagmann" <joerg.hagmann@unibas.ch>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: muse, pandoc and context
Date: Wed, 03 Dec 2008 16:59:49 +0100 [thread overview]
Message-ID: <4936ACF5.9080007@unibas.ch> (raw)
In-Reply-To: <871vwploxw.fsf@gaura-nitai.no-ip.org>
Hi Jean and Gour,
Thanks for the comments. I would prefer muse, but
superscripts/subscripts are extremely common in biology, not just for
chemical formula, and maybe there are more things missing I didn't come
across so far. On the other hand, tables didn't work well in markdown
--> pandoc --> context. If there is no way from reST to context, it's no
use to me.
Conclusion: there seems to be no good solution...
Cheers, Jörg
Gour wrote:
>>>>>> "Jörg" == Jörg Hagmann <joerg.hagmann@unibas.ch> writes:
>>>>>>
>
> Hello,
>
> Jörg> Dear list members,
>
> Jörg> Despite using a text editor (emacs) and context almost
> Jörg> exclusively, I need a way to communicate with other members of the
> Jörg> institute.
>
> I was in the similar boat - using Emacs with muse markup but wanting to
> have something which is more 'standard'- it's not that everyone is using
> Emacs (yet) :-)
>
> Jörg> I'm evaluating two possibilities: 1. Writing in markdown and using
> Jörg> pandoc for conversion to either context or something openable by a
> Jörg> word processor.
>
> I tried with markdown and gave it up - it's too limiting for my writing
> needs.
>
> Jörg> I would like to know the following: - Has anybody done the same
> Jörg> and come to a conclusion? Reasons? - Is my impression correct
> Jörg> that with muse one has fewer possibilities such as
> Jörg> sub/superscripts?
>
> I've settled on reST which is richer markup (see
> e.g. http://docutils.sourceforge.net/docs/ref/rst/roles.html#subscript)
> which is more standard than 'muse' and it enables easy conversion to
> *.html (e.g. sphinx produces nice output from *.reST), and there is even
> direct conversion to pdf with rst2pdf. Of course, you can enjoy rst-mode
> as well.
>
> In regard to the ConTeXt side of the equation, I hope that Pandoc will
> get full parser for reST and then it will be possible to use it produce
> nice ConTeXt as well (see Pandoc' archive) or we should write and/or ask
> (I did) for ConTeXt back-end in docutils ;)
>
>
> Sincerely,
> Gour
>
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-12-03 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:02 Jörg Hagmann
2008-12-02 16:06 ` Jean Magnan de Bornier
2008-12-02 16:44 ` Jörg Hagmann
2008-12-02 18:22 ` Jean Magnan de Bornier
2008-12-03 7:04 ` Gour
2008-12-03 15:59 ` Jörg Hagmann [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=4936ACF5.9080007@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).