public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Phillip Smith <phillipadsmith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Curious: ODT reader
Date: Mon, 26 Jan 2015 14:16:02 -0800 (PST)	[thread overview]
Message-ID: <4fef1220-23ec-441c-9e42-41ef29d6f1ea@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1556 bytes --]

Hello,

Quick note to say thank you for this incredibly-useful library. I wish I 
had found it earlier. :)

I've searched through the Google Group archives and Github issues and I 
can't find an answer to the question of whether an odt reader is on the 
roadmap?

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.

There appears to be a suggestion for those needed this workflow (odt->other 
formats) of converting from odt to HTML, then using pandoc to convert that 
HTML to what-have-you. And there appear to be libraries in other languages 
for converting odt to html (e.g., https://github.com/imanel/odt2html). 
Thought it might not be elegant, would one idea be to provide a reader that 
wrapped that two-step process into pandoc for odt documents?

Many thanks in advance for your help in gaining a deeper understanding 
here. :)

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-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/4fef1220-23ec-441c-9e42-41ef29d6f1ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 2066 bytes --]

             reply	other threads:[~2015-01-26 22:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 22:16 Phillip Smith [this message]
     [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
     [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=4fef1220-23ec-441c-9e42-41ef29d6f1ea@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).