public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: David Peng <davidpenn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: problems with markdown to epub
Date: Tue, 2 Nov 2021 18:19:17 -0700 (PDT)	[thread overview]
Message-ID: <77fa1b8f-2ae4-4b15-afc2-22be2c4b0bc9n@googlegroups.com> (raw)


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

Dear all,

I am trying to use pandoc to convert a large markdown file (14M, English, 
utf-8) to epub with several issues:

1. large memory consumption (more than 100GB) and exit with "killed:9".
2. I try to divide the file into 2 or 4, but the first part still fails 
with "killed: 9".
3. For part that can be converted, some sections are missing.

If help, I can upload my source markdown to the forum.

I am using pandoc 2.16 mac os version. My OS has been just upgraded to 
Monterey (12.0.1).

Thanks,

David

-- 
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/77fa1b8f-2ae4-4b15-afc2-22be2c4b0bc9n%40googlegroups.com.

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

             reply	other threads:[~2021-11-03  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03  1:19 David Peng [this message]
     [not found] ` <77fa1b8f-2ae4-4b15-afc2-22be2c4b0bc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-03  1:23   ` David Peng
     [not found]     ` <7f50bf64-2655-4d0a-a1ef-75fba7219f1dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-11-03  3:57       ` John MacFarlane
2021-11-03  2:35   ` 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=77fa1b8f-2ae4-4b15-afc2-22be2c4b0bc9n@googlegroups.com \
    --to=davidpenn-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).