From: Martin Hepp <mfhepp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Formatted PDF from CSV data
Date: Wed, 28 Sep 2022 02:59:09 +0200 [thread overview]
Message-ID: <8C6563EB-32FD-4BD8-9D14-96894855FF1C@gmail.com> (raw)
In-Reply-To: <7db8040f-dd62-416f-a3d7-a88c1e257d9en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1704 bytes --]
I would read the CSV in Python, print/write basic Markdown from there to a file, and then use Pandoc for producing a PDF.
It’s probably 5-10 lines of Python code.
Best wishes
Martin
> On 27. Sep 2022, at 23:07, Gianluca Carbone <gianlucarbone96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> Hi everyone,
>
> I try to create a Structured PDF (Title, headers, dates, and other stuff) starting from a CSV file which contain an header and responses. This CSV was generated by a Google Forms Questions and Answer, and starting from that one I want to create a simple formatted document.
>
> Anyone have some ideas on which characteristcs of pandoc can I use to obtain this results?
>
> As example, i share with you some screen of the desidered results
>
> CSV file:
>
> PDF (output) file
>
>
> Thank you so much for your help!
> --
> 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/7db8040f-dd62-416f-a3d7-a88c1e257d9en%40googlegroups.com.
--
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/8C6563EB-32FD-4BD8-9D14-96894855FF1C%40gmail.com.
[-- Attachment #2.1: Type: text/html, Size: 3116 bytes --]
[-- Attachment #2.2: example1.png --]
[-- Type: image/png, Size: 4996 bytes --]
[-- Attachment #2.3: example2.png --]
[-- Type: image/png, Size: 35434 bytes --]
[-- Attachment #2.4: example2.png --]
[-- Type: image/png, Size: 35434 bytes --]
[-- Attachment #2.5: example1.png --]
[-- Type: image/png, Size: 4996 bytes --]
next prev parent reply other threads:[~2022-09-28 0:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 21:06 Gianluca Carbone
[not found] ` <7db8040f-dd62-416f-a3d7-a88c1e257d9en-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-28 0:59 ` Martin Hepp [this message]
2022-09-28 10:38 ` Thomas Chevrier
[not found] ` <0df46ea0-a6a6-4abc-a6df-2e48fe895fb2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-09-29 16:53 ` Martin Hepp
[not found] ` <51C50E26-9499-4EDB-8E59-82877AB3B2CF-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-12 10:11 ` Gianluca Carbone
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=8C6563EB-32FD-4BD8-9D14-96894855FF1C@gmail.com \
--to=mfhepp-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).