From: Feng Shu <tumashu@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Wanted: Caretaker of the ODT backend
Date: Tue, 24 Sep 2013 22:43:04 +0800 [thread overview]
Message-ID: <87r4ceuvpj.fsf@news.tumashu-localhost.org> (raw)
In-Reply-To: <2F5692AA-B782-4AAD-972A-48E62FE748AB@gmail.com> (Carsten Dominik's message of "Tue, 24 Sep 2013 15:36:08 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
> Hi Christian,
>
> On 24.9.2013, at 15:18, Christian Moe <mail@christianmoe.com> wrote:
>
>>
>> Hi,
>>
>> I don't have the developer skillz.
>>
>> Otherwise I'd be happy to help out any way I can, e.g. tracking issues
>> and requests, digging into ODT format, replicating bugs and testing
>> patches on a more systematic basis.
>
> Thanks, this would be great.
>
>>
>> (The latter two assuming I can root out the setup/installation weirdness
>> that seems to affect my local ODT export.)
>>
>> I see Jambunathan has placed his patches in the public domain under a
>> GPL-compatible CC0 license. Other considerations aside, doesn't that
>> mean they could be applied in Org?
>
> Putting them under CC0 means that we could use them, and that Emacs
> could in principle use them as well. However, Emacs has made the *choice*
> to only include stuff for which they have the copyright assignment to
> the FSF. (Stefan does reiterate this in the thread following Jambunathans
> message). Since Org is distributed as part of Emacs, this also applies
> to us.
>
> I have looked at the patches.
>
> 1. Implement an alternative format for description lists. Description
> lists are, I think, already "supported" by the odt exporter, even
> though odt does not seem to support them natively.
> 2. As far as I can see, this mainly implements a simpler way to access
> attributes internally. It does not fix any bug I would know about.
> 3. Introduces some kind of new way to force page breaks. I don't
> see why we need it.
> 4. adds jabref support. Sounds interesting, but I don't know if anyone
> here uses it or would like to use it.
I use this feature now. In my opinion, this is very cool.
I use org-mode to write paper draft and export the draft to odf file instead of pdf file, the
reason is that I can't develop a suitable latex style
for our university... so ox-jabref.el + ox-odt.el become a
easy approach.
>
> So I don't think any of this is required at this moment. But it would
> be great if you could keep en eye out for mailing list requests and
> bug reports around this exporter and try to get things fixed when necessary.
>
> Thanks!
>
> - Carsten
>
>
>>
>> Yours,
>> Christian
>>
>>
>> Carsten Dominik writes:
>>
>>> Hi eager Org mode contributors
>>>
>>> One more try - it would be really nice to find a volunteer for this task.
>>> I can do this myself - but it would take time away from other tasks.
>>>
>>> - Carsten
>>>
>>> On 18.9.2013, at 06:38, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am looking for someone who knows about the internals of the ODT
>>>> file format, and who would have time to become the responsible
>>>> person for ox-odt.el. Since we cannot take patches from the
>>>> original author (Jambunathan) anymore, this module is currently
>>>> orphaned.
>>>>
>>>> There are a few recent patches Jambunathan has made and published here:
>>>>
>>>> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15384>>>
>>>> We cannot take them (due to FSF rules and for other reasons as
>>>> well) - but the new maintainer can take a look at them and see if
>>>> there is functionality or bug fixes we need and re-implment those.
>>>> For the rest I would hope that you can watch the mailing list and
>>>> Emacs bug reports for issues related to this backend and try to
>>>> fix them, obviously with support from the mailing list.
>>>> Also,maybe there are ideas for additional functionality?
>>>>
>>>> Please write to me if you are interested.
>>>>
>>>> Thank you.
>>>>
>>>> - Carsten
>>
--
prev parent reply other threads:[~2013-09-24 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 4:38 Wanted: Caretaker of the ODT backend Carsten Dominik
2013-09-24 12:13 ` Carsten Dominik
2013-09-24 13:18 ` Christian Moe
2013-09-24 13:36 ` Carsten Dominik
2013-09-24 14:43 ` Feng Shu [this message]
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=87r4ceuvpj.fsf@news.tumashu-localhost.org \
--to=tumashu@gmail.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).