From: Jambunathan K <kjambunathan@gmail.com>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: How do I convert org to OpenOffice?
Date: Wed, 03 Nov 2010 10:28:27 +0530 [thread overview]
Message-ID: <817hgvovf0.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTimJx_hX3trO-auTQ=aZou908nh_Zjcr31_1aYjH@mail.gmail.com> (Lennart Borgman's message of "Wed, 3 Nov 2010 02:06:20 +0100")
Hello Lennart
I uploaded a snapshot of org-7.3 and committed my workarea files to
repo.or.cz. For now, rely on the commits and the logs to get started
with what I have done till now.
Web Interface:
- http://repo.or.cz/w/org-mode/oo.git/
Push URL:
- ssh://repo.or.cz/srv/git/org-mode/oo.git
Read-only URL:
- git://repo.or.cz/org-mode/oo.git
- http://repo.or.cz/r/org-mode/oo.git
Admin URL:
- http://repo.or.cz/editproj.cgi?name=org-mode/oo
I will send the admin password separately to you (Lennart) and Matt
separately so that you can add yourself to committers.
>>> Interesting that two people are working on org->OpenOffice exporter. The
>>> other person is me.
>>>
>>> I made this announcement roughly one week in to the project.
>>> - http://lists.gnu.org/archive/html/emacs-orgmode/2010-10/msg00372.html
>>
>> Ah, very good. I missed that one. I started this thread a month ago
>> and hoped there where more people interested.
>
>
> Hi again Jambunathan,
>
>
> I just tried to test what you have written. Then I noticed that you
> have a separate file styles.xml.
> You have to place the styles somewhere, but I wonder if I do not like
> the idea used in muse-odt.el by Paul Rivier better. He instead uses a
> default.odt file from which he grabs the styles.xml.
> If you do it Paul's way the user can easily edit the styles from
> within LibreOffice (or OpenOffice.org if someone still wants to use
> that - when LibreOffice is released).
> I rewrote the zipping together from Paul's file in a way that should
> be easy to use with your solution otherwise.
I agree that working with a template file is more user-friendly than
working with an xml file.
Which codebase should we start from?
I started with org-html.el because it assured me a stable and
feature-rich base that is also XMLish.
One of the problems that I see with org-html.el route is that it is a
bit monolithic - there is a one big blob that does everything. The
side-effect of this is that our merges are most likely to conflict (even
if we work on two independent functional pieces)
If you look at org-odt.el, you will see that I have siphoned off the
Table Of Contents in to smaller routines, partly for my own
understanding and mostly because I wanted to break up the monolithic
structure of org-export-as-odt.
I also have a feeling that (my) org-odt.el has started becoming a beast
of it's own resembling less and less like org-html.el that it started
with.
Jambunathan K.
next prev parent reply other threads:[~2010-11-03 4:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 17:01 How do I convert org to OpenOffice? Lennart Borgman
2010-09-29 17:52 ` Charles Philip Chan
2010-09-29 18:20 ` Lennart Borgman
2010-09-29 18:34 ` Charles Philip Chan
2010-09-29 18:39 ` Charles Philip Chan
2010-09-29 19:43 ` Nick Dokos
2010-09-29 20:12 ` Charles Philip Chan
2010-09-29 20:59 ` Nick Dokos
2010-09-29 21:33 ` Matt Price
2010-09-29 22:40 ` Alan L Tyree
2010-11-02 17:53 ` Lennart Borgman
2010-11-02 19:08 ` Jambunathan K
2010-11-02 19:31 ` Matt Price
2010-11-03 5:37 ` Jambunathan K
2010-11-04 21:32 ` Matt Price
2010-11-05 6:03 ` Jambunathan K
2010-11-05 13:32 ` J. David Boyd
2010-11-05 13:49 ` Jambunathan K
2010-11-02 20:10 ` Lennart Borgman
2010-11-03 1:06 ` Lennart Borgman
2010-11-03 4:58 ` Jambunathan K [this message]
2010-09-30 12:41 ` Matt Lundin
2010-09-30 14:26 ` Christian Egli
2010-09-30 16:43 ` Matt Lundin
2010-10-06 15:21 ` Eric S Fraga
2010-10-06 21:10 ` Henri-Paul Indiogine
2010-10-07 7:08 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2010-09-30 3:25 Rustom Mody
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=817hgvovf0.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=nicholas.dokos@hp.com \
/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).