From: Jacopo Apunto <jacopander-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Use json-ld schema.org format as input
Date: Sun, 21 Jul 2019 03:55:01 -0700 (PDT) [thread overview]
Message-ID: <a81bbb0b-4cde-4249-ade9-6f365e994be5@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1160 bytes --]
Hi everyone,
I am trying to use pandoc to create a pdf file from a json file formatted
following the schema.org structured data format. Let's take, as example,
this: https://schema.org/Recipe
Unfortunately, the output of
pandoc -o recipe.pdf recipe.json --template custom
is "JSON parse error".
For what I understand, pandoc handles a particular json format but I wasn't
able to find proper documentation on how to structure it.
I was looking at this example, but it seems to be a different approach:
https://pandoc.org/using-the-pandoc-api.html#builder
Do you have any suggestion on how to achieve this?
I was also thinking of writing a converter from schema.org to markdown and
yaml frontmatter and then serve it to pandoc.
Thanks!
Jacopo
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a81bbb0b-4cde-4249-ade9-6f365e994be5%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2472 bytes --]
next reply other threads:[~2019-07-21 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 10:55 Jacopo Apunto [this message]
[not found] ` <a81bbb0b-4cde-4249-ade9-6f365e994be5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-07-21 16:30 ` John MacFarlane
[not found] ` <m27e8bgxk5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-07-22 8:14 ` Agustín Martín
2019-07-22 12:14 ` Rich Traube
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=a81bbb0b-4cde-4249-ade9-6f365e994be5@googlegroups.com \
--to=jacopander-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).