From: Robert Goldman <email@example.com>
To: firstname.lastname@example.org, email@example.com
Subject: Re: HOWTO export document to wiki text?
Date: Mon, 19 Jan 2009 09:40:38 -0600 [thread overview]
Message-ID: <49749EF6.firstname.lastname@example.org> (raw)
I have a start on a wiki syntax exporter that I took by modifying the
latex exporter (some wikis have quite extensive markup).
Here's what I would like to suggest:
1. There are an infuriatingly large number of different wiki syntaxes.
I'd like to suggest that we should avoid having to write a zillion
different standalone exporters.
2. Emacs lisp doesn't have object-oriented programming to help with
this, but we can simulate it with tables of functions. So, for example,
we could have vectors with entries for functions that format italicized
text for media-wiki, tiki wiki, etc.
3. A first job would be to make a list of all of the kinds of export
that we see in the latex exporter, and define a structure that provides
entries for all of these export types.
If we do the above, we can hijack the top-level export routine from,
e.g., latex export, and then plug in different tables for the different
Feel free to contact me off-line about this; I would be more than happy
to work with you on it.
next parent reply other threads:[~2009-01-19 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LOku5-0004vu-DT@box188.bluehost.com>
2009-01-19 15:40 ` Robert Goldman [this message]
2009-01-19 7:05 HOWTO export document to wiki text? Rustom Mody
2009-01-19 15:32 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2009-01-17 21:03 Uwe Koloska
2009-01-18 18:26 ` Matthew Lundin
2009-01-19 7:42 ` Ian Barton
2009-01-19 15:03 ` Matthew Lundin
2009-01-19 15:27 ` Sebastian Rose
2009-01-19 19:30 ` Ian Barton
2009-01-18 18:27 ` Eric Schulte
2009-01-19 16:23 ` Christian Egli
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).