public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Chris LAM <fdq09eca-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: converting a .bib file into grouped table with custom attributes
Date: Sun, 12 Jul 2020 18:58:18 -0700 (PDT)	[thread overview]
Message-ID: <c86cfb53-1149-4b81-a93d-d40a058c5785o@googlegroups.com> (raw)


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

Dear all,

I am having a *.bib* file with the following format 
@article{ploberger2017one,
  title={One belt, One road--China’s new grand strategy},
  author={Ploberger, Christian},
  journal={Journal of Chinese Economic and Business Studies},
  volume={15},
  number={3},
  pages={289--305},
  year={2017},
  publisher={Taylor \& Francis},
  datasrc={Est dolore Lorem},
  type={labour},
  review={
    - consectetur eu magna adipisicing excepteur nisi aliqua in. 
    - Adipisicing ipsum nostrud adipisicing eiusmod sit.
    - Occaecat minim aute ex culpa dolor. 
    - Cupidatat dolore exercitation et ullamco non eu et enim.
  },
  findings={
    - consectetur eu magna adipisicing excepteur nisi aliqua in. 
    - Adipisicing ipsum nostrud adipisicing eiusmod sit.
    - Occaecat minim aute ex culpa dolor. 
    - Cupidatat dolore exercitation et ullamco non eu et enim.
  }
}
note that datasrc, type, review, findings are custom attribute.

I have got over 100 entries in this format and I would like to *convert 
them into a table in a landscape .docx* with the following template

type | year | author | datasrc | review | findings

can pandoc save me from the heavy lifting?

Thank you.


-- 
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/c86cfb53-1149-4b81-a93d-d40a058c5785o%40googlegroups.com.

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

             reply	other threads:[~2020-07-13  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13  1:58 Chris LAM [this message]
     [not found] ` <c86cfb53-1149-4b81-a93d-d40a058c5785o-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-07-13  5:18   ` 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=c86cfb53-1149-4b81-a93d-d40a058c5785o@googlegroups.com \
    --to=fdq09eca-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).