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. (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? 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.domi...@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
