public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Kolen Cheung <christian.kolen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: HTML files grayed out when trying to import
Date: Tue, 24 Oct 2017 12:56:01 -0700 (PDT)	[thread overview]
Message-ID: <faf5be3b-510e-42d5-b405-b6b7e91d2c17@googlegroups.com> (raw)
In-Reply-To: <20171024164616.GB90469@protagoras>

[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]

He’s talking about Typora. It is at least the 2nd time (that I know of) people confused between Typora and pandoc. I guess we might need to talk to the typora developer to ask him to make it clear to its users/customers that typora is not pandoc, and any support should be directed towards him.

Typora’s author wrote his own parser and uses an AST and markdown that is sort of compatible with pandoc. But typora is not open-source. pandoc is an optional dependency of typora, if installed, allowing the users to have outputs that typora didn’t covered natively. However, since the author defines its own markdown and parser to parse it to its own AST, pandoc might choke on its input.

I tested Typora when it was newly launched. I was evaluating if it is a good GUI for pandoc. In the end I found out that it isn’t, exactly because of the custom markdown and AST thing (that sort of compatible to pandoc) and has no way to uses pandoc’s own one (because of the rendering engine relies on their own markdown to AST, persumbly for speed). I don’t know if it has changed since, but doubt it.

-- 
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/faf5be3b-510e-42d5-b405-b6b7e91d2c17%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

      reply	other threads:[~2017-10-24 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-24 13:20 Ed Byford
     [not found] ` <b4807b57-8741-4cf6-b139-2c6c1bb098ac-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-24 16:46   ` John MACFARLANE
2017-10-24 19:56     ` Kolen Cheung [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=faf5be3b-510e-42d5-b405-b6b7e91d2c17@googlegroups.com \
    --to=christian.kolen-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).