From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Milan Bracke
<milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Proposed improvement to treat more images in docx
Date: Wed, 28 Apr 2021 13:21:24 -0700 [thread overview]
Message-ID: <m2czuedut7.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <f3fcee77-b7ea-4fe9-88ca-c4b22bab9d8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
I can't think of any objections!
Milan Bracke <milan.bracke-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi,
>
> Currently, when parsing a docx, a v:imagedata tag inside a
> w:r/w:object/v:shape
> is ignored. But it could be treated the same as a v:imagedata inside a
> w:r/w:pict, both represent images linked by the r:id attribute.
>
> In fact, we now use a pre-processing to transform a
> w:r/w:object/v:shape/v:imagedata to a w:r/w:pict/v:imagedata before
> transforming
> with Pandoc and we have tested this on many documents.
>
> So we would like to implement an improvement to treat both the same. Do you
> have
> any objections or feedback? We'll make a pull request soon.
>
> --
> 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/f3fcee77-b7ea-4fe9-88ca-c4b22bab9d8an%40googlegroups.com.
prev parent reply other threads:[~2021-04-28 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 15:20 Milan Bracke
[not found] ` <f3fcee77-b7ea-4fe9-88ca-c4b22bab9d8an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-28 20:21 ` John MacFarlane [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=m2czuedut7.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=milan.bracke-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).