From: "John O'Regan" <john.a.oregan-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc output to stdout
Date: Wed, 19 Jul 2017 19:06:57 +0100 [thread overview]
Message-ID: <CALwjjMjQDADwEYGPoM0mHqtdauQPKadgEJ4xuW=DDsAdLovTYg@mail.gmail.com> (raw)
In-Reply-To: <b2bbef60-8140-41e9-bba9-a80f84bb776c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Hi Mirjalol,
Yes, .docx and .pdf files use a binary format and writing them to
STDOUT isn't a good idea.
You'll have to first create your .docx file using Pandoc, and then
read in the file using a programming language. Pandoc is scriptable
and can be easily incorporated into programs, but to programatically
edit the contents of a .docx file requires expertise in the .docx file
format... and infinite patience! :)
Please explain in more detail what you're trying to do and we'll see
if we can find a simpler solution to your problem.
BFN!
John
next prev parent reply other threads:[~2017-07-19 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 10:56 Mirjalol Norqulov
[not found] ` <3e6f4efa-c3d5-4fd0-8692-38ecd6484ad8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-19 11:43 ` John O'Regan
[not found] ` <CALwjjMiABu3rX8P=kNic4B-n-yXLC-XtuSLCguvcr2p_kTHmKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-19 17:13 ` Mirjalol Norqulov
2017-07-19 17:26 ` Mirjalol Norqulov
[not found] ` <b2bbef60-8140-41e9-bba9-a80f84bb776c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-19 18:06 ` John O'Regan [this message]
[not found] ` <CALwjjMjQDADwEYGPoM0mHqtdauQPKadgEJ4xuW=DDsAdLovTYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-20 2:52 ` Mirjalol Norqulov
[not found] ` <f824b8a8-acef-4d19-9d88-f302b1681172-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-20 5:11 ` Ivan Lazar Miljenovic
2017-07-21 21:24 ` Kolen Cheung
2017-07-19 21:09 ` Albert Krewinkel
2017-07-23 8:02 ` 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='CALwjjMjQDADwEYGPoM0mHqtdauQPKadgEJ4xuW=DDsAdLovTYg@mail.gmail.com' \
--to=john.a.oregan-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).