public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Importing docx getting out of memory error
Date: Wed, 17 Dec 2014 22:05:31 +0100	[thread overview]
Message-ID: <5491F01B.1020800@web.de> (raw)
In-Reply-To: <0be5cec5-bc75-4f68-82ef-98329bcf8014-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

On 12/17/2014 09:27 PM, russurquhart1 wrote:
> Hi,
> 
> I haven't seen this problem before with other docx files. It seems it
> might be just this file.The file is almost 3 Mb, i would think that
> wouldn't necessarily be the problem.
> 
> I can send it to you, but this is a company file so i don't know if i'd
> like posting it up here?

Hi Russ,

posting coporate files in public mailing list seems not to be a good idea.

I don’t think John wants to start a “pandocleaks” site ;-).

> If that's the only way to fix the problem, let me send it to you privately?

I’m not the right person, I’m afraid (I cannot code).

Maybe it would make sense to elaborate a sample file. I mean, how about
opening the file and start removing parts while you test whether you get
the error?

The sample file should be minimal, so the file cannot have less contents
without throwing the error.

And after you replace the remaing text with any non-revealing
information, it would be probably safe to post that sample file on a
public mailing list.

Just in case it helps,


Pablo
-- 
http://www.ousia.tk

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/5491F01B.1020800%40web.de.
For more options, visit https://groups.google.com/d/optout.


  parent reply	other threads:[~2014-12-17 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17 19:51 russurquhart1
     [not found] ` <83ef4a3a-5d91-4adc-8bb0-a4dc2fbc2807-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-17 20:12   ` Pablo Rodríguez
2014-12-17 20:27   ` russurquhart1
     [not found]     ` <0be5cec5-bc75-4f68-82ef-98329bcf8014-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-17 21:05       ` Pablo Rodríguez [this message]
2014-12-18  8:50   ` juh
     [not found]     ` <54929572.7060708-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2014-12-18  9:01       ` Matthew Pickering
2014-12-18 16:44       ` russurquhart1
     [not found]         ` <9eb2e6a1-eee3-453c-8d66-879f1f753fe0-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2014-12-18 23:37           ` Matthew Pickering

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=5491F01B.1020800@web.de \
    --to=oinos-s0/gaf8tv78@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).