emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: David Mason <dmason@mozilla.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Experimental media-wiki export
Date: Sat, 28 May 2011 13:45:06 +0530	[thread overview]
Message-ID: <817h9b5je4.fsf@gmail.com> (raw)
In-Reply-To: <4DE000FC.8070906@mozilla.com> (David Mason's message of "Fri, 27 May 2011 15:52:28 -0400")

David Mason <dmason@mozilla.com> writes:

> I've found myself using the media-wiki export code in EXPERIMENTAL quite
> a bit - but it seems to have broken in the most recent builds.

May be this will help.
http://lists.gnu.org/archive/html/emacs-orgmode/2011-04/msg00316.html

> I'm curious what the status of that is - are there any plans to move it
> into the main codebase? Is anyone even maintaining it?

You have the option of exporting it to html or odt and have it converted
to mediawiki. Open/Libre Office seems to be one uber converter and you can use
it to export to mediawiki (by hand) or through commandline (use
unoconv). If you are unhappy with unoconv, you can write some basic
macros and have a made-to-order commandline that exports html/odt to
mediawiki.

I am attaching test org file and the corresponding mediawiki export
(generated via the html backend). I am not sure how good the mediawiki
export is.

> I find it is the best mediawiki export, especially for tables.

Btw, the attached test file has tables, both simple and complex.

On a related note, in all honesty, 

1. I think that Org shouldn't support all backends in the world as part
   of it's core. The previous statement equally applies to the org-odt
   backend. It would suffice if Org provides a generic exporter and
   people unhappy with existing converters or who have plenty of time in
   hand (like me) can author standalone modules that is in tune with ORg
   way of things and distribute it via GNU's ELPA.

2. I think Org should provide a way (out of the box) to post-process an
   exported file to one of the "other" formats using an external
   converter. LibreOffice, if not now, atleast in distant future would
   become the One True Converter to rule the world.

   Something like M-x org-export-as-other ....

Jambunathan K.

<#part type="text/plain" filename="~/src/org-jambu/contrib/odt/files/test.org" disposition=attachment description=test.org>
<#/part>

<#part type="text/plain" filename="~/src/org-jambu/contrib/odt/files/test.txt" disposition=inline description=test.mediawiki>
<#/part>


-- 

  reply	other threads:[~2011-05-28  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27 19:52 Experimental media-wiki export David Mason
2011-05-28  8:15 ` Jambunathan K [this message]
2011-05-28  8:21   ` Jambunathan K

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=817h9b5je4.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=dmason@mozilla.com \
    --cc=emacs-orgmode@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).