public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Dirk Laurie <dirk.laurie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc and OPML
Date: Tue, 26 Mar 2013 07:22:58 +0200	[thread overview]
Message-ID: <CABcj=t=JeQA7MkZroBVTD+Dnybc6xTd5-1g3kbsVSjdUzvnw+Q@mail.gmail.com> (raw)
In-Reply-To: <20130326022137.GC9254-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>

2013/3/26 John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>:
> g++ Ryan Gray [Mar 25 13 18:14 ]:
>>    On Sunday, March 17, 2013 11:33:41 PM UTC-6, fiddlosopher wrote:
>>
>>      +++ John MacFarlane [Mar 17 13 21:01 ]:
>>      > I've added an opml branch on github that does the basics.
>>      >
>>      > I still haven't added support for a _note attribute, because
>>      > I'm not sure I understand how it is to be interpreted.
>>      >
>>      > The content of the attribute is a string.  But what format?
>>      > HTML? Markdown? Is there any standard for this?
>>      Multimarkdown just seems to put raw markdown inside the _note
>>      attribute.  But it seems to me that encoded HTML would be a
>>      better choice, since the spec is explicit about allowing that
>>      in the text attribute.
>>      (Of course, it would be converted to markdown in an opml ->
>>      markdown conversion.)
>>
>>    I think the idea for MMD was so that for apps that supported the
>>    attribute, you could edit (or create) the note (which contains the
>>    content of a section) in Markdown format rather than HTML in whatever
>>    app you opened or imported the OPML file in. This seems to be a
>>    sensible thing. Perhaps it would be easy enough to look at the first
>>    characters in the note to tell if it is HTML or plain text.
>
> Well, I ended up just parsing the contents of the note attribute as
> markdown.
>
> OPML is now supported (in the dev version) for both input and output.
> Try it out!

Wikipedia says:

   Exporting your data from an OPML file to another format can't be
   done without coding: no free tools are available to convert an OPML
   file to HTML,

Do we wait until Pandoc with OPML support is on Hackage?


  parent reply	other threads:[~2013-03-26  5:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 17:13 Chris Lott
     [not found] ` <CAHJRaA432JWGSsNMAan69yPtQKBTUrN1e6Ligg5=5UTOYipO8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-15 22:28   ` John MacFarlane
     [not found]     ` <20130315222848.GA8282-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2013-03-17 22:04       ` Chris Lott
     [not found]         ` <CAHJRaA6w_9TvXRg1bnbOopMTJDWfBsOMYyMGAuwCFXmMWy_Ung-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-17 22:47           ` John MacFarlane
     [not found]             ` <20130317224720.GB48086-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-03-17 23:06               ` Chris Lott
     [not found]                 ` <CAHJRaA6DnLxSDrSu_z-sBt0-pgBwo+BPKK9yRrNvqxC7srOMxQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-18  0:14                   ` John MacFarlane
     [not found]                     ` <20130318001423.GA8496-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2013-03-18  4:01                       ` John MacFarlane
     [not found]                         ` <20130318040154.GA54653-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-03-18  5:33                           ` John MacFarlane
     [not found]                             ` <20130318053341.GA14308-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2013-03-26  1:14                               ` Ryan Gray
     [not found]                                 ` <fe881274-9fea-4b2d-8e22-94f26394fc05-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-03-26  2:21                                   ` John MacFarlane
     [not found]                                     ` <20130326022137.GC9254-9Rnp8PDaXcadBw3G0RLmbRFnWt+6NQIA@public.gmane.org>
2013-03-26  5:22                                       ` Dirk Laurie [this message]
2013-04-07 18:00                                       ` Chris Lott
2013-03-26 15:33               ` BP Jonsson
     [not found]                 ` <5151BFB7.10200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-03-27  5:50                   ` John MacFarlane
2013-03-20  3:24           ` John MacFarlane
2013-05-29 20:07             ` David Oppenheimer
     [not found]               ` <loom.20130529T215912-867-eS7Uydv5nfjZ+VzJOa5vwg@public.gmane.org>
2013-05-29 20:19                 ` John MacFarlane
2013-05-30 19:50   ` David Oppenheimer
2013-06-26 21:15   ` jake london
     [not found]     ` <6137014c-5dbe-4242-a8d0-5cf4cde99593-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-06-26 21:47       ` Chris Lott
     [not found]         ` <CAHJRaA6zvQYuXHb=iyYxhg4x+EZ5fgoSZ05KLcaiw6qqrnUs_w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-26 22:38           ` John MacFarlane
2013-06-26 23:54           ` jake london
2013-06-26 23:56   ` jake london

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='CABcj=t=JeQA7MkZroBVTD+Dnybc6xTd5-1g3kbsVSjdUzvnw+Q@mail.gmail.com' \
    --to=dirk.laurie-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).