From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: XOXO output Date: Tue, 4 Apr 2006 13:38:10 +0200 Message-ID: <38e09805380801af24216bbd878ac376@science.uva.nl> References: <043b729fad3b50297372c536319cc9c5@science.uva.nl> <87acbt5kcx.fsf@tapsellferrier.co.uk> <878xqm95wh.fsf@tapsellferrier.co.uk> <15095aae75a043309d3c653356318bc8@science.uva.nl> <871wwdbofv.fsf@tapsellferrier.co.uk> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FQjrT-00049e-Fr for emacs-orgmode@gnu.org; Tue, 04 Apr 2006 07:38:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FQjrR-00047e-QV for emacs-orgmode@gnu.org; Tue, 04 Apr 2006 07:38:15 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FQjrR-00047Q-Lz for emacs-orgmode@gnu.org; Tue, 04 Apr 2006 07:38:13 -0400 Received: from [146.50.4.51] (helo=imap.science.uva.nl) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FQjui-0007lk-JU for emacs-orgmode@gnu.org; Tue, 04 Apr 2006 07:41:36 -0400 In-Reply-To: <871wwdbofv.fsf@tapsellferrier.co.uk> 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: Nic Cc: emacs-orgmode@gnu.org On Apr 4, 2006, at 12:55, Nic wrote: > > No... that's not quite what I've said. The reason that XOXO export is > good is because it's easy to transform later (say with XSLT but also > specialized SAX or SXML processes would work). > > >> But I guess that transformation code would actually have to >> be custom written and understand all of the properties of Org-mode >> files. So I am still wondering if it would be useful to have ev >> erything that is Org-mode specific translated into something more >> general. > > This is the reason I haven't yet updated my XOXO exporter to output > other things. > > XOXO is *just* an outline specification. So how should an XOXO output > handle org mode tables or schedules? > > I think that XOXO output is really just part of what I want which is a > minimal output format. Markup centric it would not include any > formatting or extraneous information (as yours does now). OK. I think that would be very useful indeed. I guess there are two ways forward with this. - We try to modify the HTML output routine so that we can simply set a switch which output format it is going to be. I think that is going to be hard, because the switch would have to be tested in many many places. - We copy the org-export-as-html routine and then modify it to remove all the extra formatting junk I have in there (which was born not out of desire to be abstract, but just out of the wish "I would like to look at this thing in a web browser..."). This would have the advantage that all the parsing and structure information is there for you to use, but we would still have an independent and possibly more compact routine. > > So XOXO would be used for outline markup but straight tables would be > used for org mode tables and hCalendar would be used for dates and > times and things like that. > > See http://microformats.org/wiki/Main_Page for more info. > > I think what I'll do is take a look at your new exporter and see if I > can replicate what it does but with microformat markup instead of your > current markup. Go right ahead. Should I delay putting XOXO code into org.el then? - Carsten -- Carsten Dominik Sterrenkundig Instituut "Anton Pannekoek" Universiteit van Amsterdam Kruislaan 403 NL-1098SJ Amsterdam phone: +31 20 525 7477