From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wes Hardaker Subject: Re: org-mode to iphone? Date: Thu, 22 Jan 2009 08:05:46 -0800 Message-ID: References: <49500D9A.2020309@sift.info> <20081222221038.GB22763@owl.prv.maya.com> <6F960FA4-8F11-48D0-9D51-C27CA1E77128@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LQ243-0007XG-2t for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 11:05:55 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LQ23z-0007Sl-O1 for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 11:05:54 -0500 Received: from [199.232.76.173] (port=57870 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LQ23z-0007SI-91 for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 11:05:51 -0500 Received: from dcn236-43.dcn.davis.ca.us ([168.150.236.43]:55300 helo=wes.hardakers.net) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LQ23y-0006AY-5o for emacs-orgmode@gnu.org; Thu, 22 Jan 2009 11:05:50 -0500 In-Reply-To: <6F960FA4-8F11-48D0-9D51-C27CA1E77128@uva.nl> (Carsten Dominik's message of "Thu, 22 Jan 2009 09:06:38 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org >>>>> On Thu, 22 Jan 2009 09:06:38 +0100, Carsten Dominik said: CD> So please get back to it when you find time and keep us CD> posted. I could tweak the HTML exporter where necessary CD> to make a good mobile access idea for Org-mode stuff CD> a reality. I've been meaning to write this up for a while, and I think this sort of idea is exactly what could benefit from it... I think there should be a generic exporter that contains simple customization rules for how to do an export. Something like: (setq org-export-templates '(("mediawiki" :heading1-prefix "= " :heading1-suffix " =" :heading2-prefix "== " :heading2-suffix " ==" :bold-prefix "'''" :bold-suffix "'''" :link-format "[%{url} %{link-text}]" :numbered-list-prefix "#" :numbered-list-suffix "\n" ))) I'm making stuff up on the fly above, but I think you get the idea. Most of the exporting formats that are needed could really be simplified down to something minimal like the above. It'd be much easier than continually rewriting much of the export process when a lot of it is the same across multiple back-ends. I'm not sure it could be applied everywhere. Certainly there are some very tricky elements to deal with (and the default, if not defined, should be to fall back to a straight text conversion). IE, I'm not sure the latex backend could be easily rewritten using something like the above (but hey, you never know). There are a number of things I'd like to export to something "unusual", and the above would allow that flexibility. Unfortunately, I don't have much time, and more importantly don't have the org skill at all to make it happen. Thoughts? -- "In the bathtub of history the truth is harder to hold than the soap, and much more difficult to find." -- Terry Pratchett