From: Phillip Smith <phillipadsmith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Cc: phillipadsmith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: Curious: ODT reader
Date: Tue, 27 Jan 2015 12:00:20 -0800 (PST) [thread overview]
Message-ID: <e8873929-e613-43f6-98f9-a760a6e33772@googlegroups.com> (raw)
In-Reply-To: <87ppa0rxyd.fsf-4GNroTWusrE@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 4433 bytes --]
My responses seem to be getting delayed or grey listed for several hours,
so I'm just going to re-post directly from the Google Groups interface here
(apologies if you receive a duplicate tomorrow):
On Tuesday, January 27, 2015 at 8:27:07 AM UTC-8, Jesse Rosenthal wrote:
>
> Hi Phillip,
>
> I'm actually the author of the docx reader. I wrote it because I wanted
> to use it. I'd guess that's the case for most of the readers in pandoc.
>
> Which is to say that I don't think there's any technical limitation to
> constructing such a reader. It would likely follow the same basic
> pattern as the docx reader: unzip, parse, convert. It would in fact
> probably be a bit easier than the docx reader because lists etc seem
> much more sensible in ODT due to proper nesting. I just don't think
> anyone has had sufficient desrie (or the combination of desire and
> haskell chops) to make it happen.
>
> By the way, before I wrote the docx reader, I prototyped it in python,
> and wrote a python script that output pandoc json. If you don't want to
> work in haskell you could look around for an ODT reader in another
> language and go from there.
>
> Best,
> Jesse
>
Hi Jesse,
That's very helpful context to have.
I have been looking at the other libraries here,
http://www.opendocumentformat.org/developers/ … and I'd be curious to see
an example of the "pandoc JSON" if you could point me to one (and/or your
python prototype).
It does look like an interesting problem to solve, haskell aside. ;)
However, the team I'm working with at the moment is quite small, and we
are heavily committed (like everyone!).
I see that the idea of a "bounty" has been raised before on this list. Our
project is well funded and this would be a worthwhile investment.
Before I go searching for someone to write this reader out in the wild, is
there anyone on this list that would be interested in taking it on? If so,
please drop me a note off-list.
Phillip.
> Phillip Smith <phillip...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org <javascript:>> writes:
>
> > On 2015-01-26, at 2:42 PM, Raniere Silva <ran...-Xhq86aZylhRTIXuwt5Zssw@public.gmane.org
> <javascript:>> wrote:
> >
> >> Hi Phillip,
> >>
> >>> I'm completely ignorant here, having just starting using pandoc, but
> -- if
> >>> it's not a waste of time to explain it to me -- I'd be curious to
> >>> understand how an odt reader could be added.
> >>
> >> At src/Text/Pandoc/Readers/ you will find the source code of all
> readers.
> >> If you take a look at src/Text/Pandoc/Readers/Docx{/,.hs} you will see
> the
> >> source code of the DOCX reader. You can use it as a start point for the
> ODT
> >> reader.
> >
> > Hi Raniere,
> >
> > Many thanks for your response. I did have a look at the DOCX reader
> earlier.
> >
> > Let me perhaps re-phrase my question: What have been the barriers that
> have prevented an odt reader from being added before?
> >
> > I'm curious why so many readers are available, but not odt? Are there
> obstacles that are well-known and hard to overcome?
> >
> > Many thanks in advance,
> >
> > Phillip.
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <javascript:>.
> > To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> <javascript:>.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/7EE5FAC3-481F-468F-AFE1-E898FC1E5387%40gmail.com.
>
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e8873929-e613-43f6-98f9-a760a6e33772%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 6820 bytes --]
next prev parent reply other threads:[~2015-01-27 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 22:16 Phillip Smith
[not found] ` <4fef1220-23ec-441c-9e42-41ef29d6f1ea-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-26 22:42 ` Raniere Silva
2015-01-26 22:36 ` Phillip Smith
[not found] ` <7EE5FAC3-481F-468F-AFE1-E898FC1E5387-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-27 16:27 ` Jesse Rosenthal
[not found] ` <87ppa0rxyd.fsf-4GNroTWusrE@public.gmane.org>
2015-01-27 16:53 ` Phillip Smith
2015-01-27 20:00 ` Phillip Smith [this message]
[not found] ` <e8873929-e613-43f6-98f9-a760a6e33772-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-27 23:28 ` kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg
[not found] ` <49b6d469-ce18-4ca6-a340-426122681018-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-27 23:57 ` Phillip Smith
2015-01-27 18:10 ` John MacFarlane
[not found] ` <20150127181016.GB5844-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2015-01-27 18:19 ` Phillip Smith
2015-01-27 20:01 ` Phillip Smith
[not found] ` <cb88bfc2-97c1-4d3d-a7d3-3140b8086cb5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-27 20:08 ` Jesse Rosenthal
2015-01-27 23:52 ` kurt.pfeifle-gM/Ye1E23mwN+BqQ9rBEUg
[not found] ` <eff8dcfa-a407-4ef6-8c3e-0c740ef3a56a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-28 0:06 ` Phillip Smith
2015-01-27 16:17 ` John MacFarlane
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e8873929-e613-43f6-98f9-a760a6e33772@googlegroups.com \
--to=phillipadsmith-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).