public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Bastien DUMONT <bastien.dumont-VwIFZPTo/vqsTnJN9+BGXg@public.gmane.org>
To: 'Peter Vedal Utnes' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Error caused by document length
Date: Mon, 27 Feb 2023 16:39:49 +0000	[thread overview]
Message-ID: <Y/zc1XW7hY71aWqy@localhost> (raw)
In-Reply-To: <20942a45-0995-4a50-888a-cf25e9895920n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

If you narrow down the document to the offending sentences (or only one of them), does bibi fail to read the resulting EPUB? Such minimal source and EPUB documents would be easier to inspect, and the latter could even be included in a bug report for bibi.

Le Monday 27 February 2023 à 08:22:34AM, 'Peter Vedal Utnes' via pandoc-discuss a écrit :
> I have now done the elimination process, as suggested by Bastien, of replacing
> the working file, which was the EPUB of the research paper where I had swapped
> paragraphs 2-10 with "test test test", with the original paragraphs from the
> paper. It worked until I tried to restore a sentence in the middle of paragraph
> 3, going from above, or paragraph 6, going from below. When I insert the next
> sentence in either end, the document fails to convert (in a manner readable by
> bibi epub viewer). There does not seem to be unicode characters that might
> interfere. I have ran the debugger you suggest, John ,and there are indeed
> errors (metadata not filled in and a missing tag end) but I fixing these do not
> seem to work. 
> 
> Here are the seemingly innocuous sentences that fail from above and below,
> respectively: 1)  Over years I have experienced much Bronze in the form of
> articles in toll access (TA) journals that have been made freely available for
> reading – not open access, but “Free access” as some publishers call it. 2) One
> thing is to help editors to become aware of the issue, another is to find
> practical solutions for them to transition their scholarly content to OA – the
> rest of their content is really not of interest to us.
> 
> There seem to issues with a few other sentences in those 3 paragraphs too, but
> I can't see a pattern. 
> Here is the article in question, though it is only the PDF galley, my EPUB
> testing is on a private server: https://septentrio.uit.no/index.php/nopos/
> article/view/6665
> 
> 
> 
> mandag 27. februar 2023 kl. 17:08:31 UTC+1 skrev John MacFarlane:
> 
>     You could try running epubcheck on the epub produced by pandoc, to see if
>     it points to anything.
> 
> 
>     > On Feb 27, 2023, at 6:33 AM, 'Peter Vedal Utnes' via pandoc-discuss <
>     pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
>     >
>     > I just did some further testing, and replaced the sections that I would
>     otherwise have removed with as many words and paragraphs, but no signs,
>     only "test test test" etc. The document then works. So I was wrong about
>     the length: It must be some character or symbol producing the error (only
>     with pandoc, not other EPUB converters). Any idea how to further isolate
>     it, or how to circumvent with a pandoc command or template?
>     >
>     > Thanks for the help so far, Bernardo.
>     >
>     >
>     >
>     > mandag 27. februar 2023 kl. 15:23:57 UTC+1 skrev Peter Vedal Utnes:
>     > I am not sure what you mean by normalize in this context. I'll elaborate
>     in case this is what you mean: In the interest of removing variables that
>     might interfere with troubleshooting, I have copied the text from research
>     papers (not just one, but a few), pasted it in notepad, copied and pasted
>     it back into a new word-file (this is more thorough than "clear
>     formatting"), ran this "pure" file through pandoc and I get the error. If I
>     then randomly shorten the file, the error disappears. This is not the case
>     for my "test" file, but only for research papers, which is baffling. I can
>     only assume that pandoc responds to something like a character or in-text
>     references in particular contexts, or as was my original hypothesis, the
>     number of lines or columns in the EPUB.
>     >
>     > mandag 27. februar 2023 kl. 15:17:10 UTC+1 skrev bernardov...@gmail.com:
>     > Have you tried editing the original research paper in some minor way
>     (adding or removing a couple of characters) and then running it? This is a
>     completely wild guess, but maybe the text in the file is getting normalized
>     upon editing them, whereas the original research paper still contains the
>     unedited, unnormalized text.
>     >
>     > On Mon, Feb 27, 2023 at 10:48 AM 'Peter Vedal Utnes' via pandoc-discuss <
>     pandoc-...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> wrote:
>     > I thank you for the suggestion. It is proving somewhat hard to (dis)
>     confirm. I have made a testfile with just the word "test" pasted over and
>     over again, with and without various formatting and with the same length or
>     longer as the proper papers. This file consistently works. But when I
>     attempt to do it with a regular research paper, it only works if I shorten
>     it. Curiously, I can remove either half of the main text, or indeed
>     sections here and there, randomly, and it works, but not with all of them
>     present. I have combed it for special characters or tags, but cannot find
>     any.
>     >
>     > mandag 27. februar 2023 kl. 13:49:58 UTC+1 skrev Bernardo C. D. A.
>     Vasconcelos:
>     > I do not know the answer to this problem in particular, but perhaps it is
>     worth checking the main document and the bibliography for invisible control
>     characters (e.g. `\X{A0}`). They tend to cause all sorts of strange
>     problems that result in random error msgs.
>     >
>     > On Monday, February 27, 2023 at 8:16:20 AM UTC-3 Peter Vedal Utnes wrote:
>     > We have a workflow in Open Journal Systems where we use Pandoc to convert
>     word documents to EPUB, and then display them with an embedded EPUB app
>     (Bibi).
>     >
>     > Our resulting EPUBs work fine with both debuggers and viewers like
>     calibre. They work in Bibi, but only when they are reduced to a certain
>     length. Whenever the files exceed approx 100 lines or 600 words, Bibi
>     claims:
>     >
>     > TypeError: Cannot read properties of undefined (reading ‘getAttribute’)
>     >
>     > Meanwhile, the same documents works when converted to EPUB using other
>     converters, or when I reduce the length (length, not size in bytes-- I've
>     tried with graphics, still works). It suddenly works when I reduce the
>     length by removing pure paragraph text, even though all the formatted
>     elements (abstract, references, etc) are the same.
>     >
>     > I recognize that this problem is very specific to the interrelation
>     pandoc <-> Bibi, but I'd be grateful for general troubleshooting
>     suggestions.
>     >
>     > Thanks in advance,
>     >
>     > Peter
>     >
>     >
>     > --
>     > You received this message because you are subscribed to a topic in the
>     Google Groups "pandoc-discuss" group.
>     > To unsubscribe from this topic, visit [1]https://groups.google.com/d/
>     topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe.
>     > To unsubscribe from this group and all its topics, send an email to 
>     pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     > To view this discussion on the web visit [2]https://groups.google.com/d/
>     msgid/pandoc-discuss/
>     4bd152b5-32f7-4f4c-9a9b-0d20afebea84n%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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>     > To view this discussion on the web visit [3]https://groups.google.com/d/
>     msgid/pandoc-discuss/
>     bc147d77-69c9-4e5d-82a6-e149f662a823n%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 [4]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit [5]https://groups.google.com/d/msgid/
> pandoc-discuss/20942a45-0995-4a50-888a-cf25e9895920n%40googlegroups.com.
> 
> References:
> 
> [1] https://groups.google.com/d/topic/pandoc-discuss/hPUa1uWGS_k/unsubscribe
> [2] https://groups.google.com/d/msgid/pandoc-discuss/4bd152b5-32f7-4f4c-9a9b-0d20afebea84n%40googlegroups.com
> [3] https://groups.google.com/d/msgid/pandoc-discuss/bc147d77-69c9-4e5d-82a6-e149f662a823n%40googlegroups.com
> [4] mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> [5] https://groups.google.com/d/msgid/pandoc-discuss/20942a45-0995-4a50-888a-cf25e9895920n%40googlegroups.com?utm_medium=email&utm_source=footer

-- 
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/Y/zc1XW7hY71aWqy%40localhost.


  parent reply	other threads:[~2023-02-27 16:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 11:16 'Peter Vedal Utnes' via pandoc-discuss
     [not found] ` <7ed278f7-071b-4bcc-9f9a-e9dd5c09ee55n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 12:49   ` Bernardo C. D. A. Vasconcelos
     [not found]     ` <8f11cfaf-7c36-4cc6-9866-aa3741d965a4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 13:48       ` 'Peter Vedal Utnes' via pandoc-discuss
     [not found]         ` <4bd152b5-32f7-4f4c-9a9b-0d20afebea84n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 14:16           ` bernardovasconcelos-Re5JQEeQqe8AvxtiuMwx3w
     [not found]             ` <CAEJ71f529ORrJ+aaLU-8JFbE3uLvYkQdKcJjKSJb5mJSt+jOvA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-27 14:23               ` 'Peter Vedal Utnes' via pandoc-discuss
     [not found]                 ` <db7972f9-8881-4941-92ea-9b8f51c0c404n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 14:33                   ` 'Peter Vedal Utnes' via pandoc-discuss
     [not found]                     ` <bc147d77-69c9-4e5d-82a6-e149f662a823n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 14:54                       ` Bastien DUMONT
2023-02-27 15:45                         ` Bernardo C. D. A. Vasconcelos
2023-02-27 16:08                       ` John MacFarlane
     [not found]                         ` <0AFB3E23-B7C1-49E8-9F8A-12716F6A2C40-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-02-27 16:22                           ` 'Peter Vedal Utnes' via pandoc-discuss
     [not found]                             ` <20942a45-0995-4a50-888a-cf25e9895920n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 16:39                               ` Bastien DUMONT [this message]
2023-02-27 16:49                                 ` 'Peter Vedal Utnes' via pandoc-discuss
     [not found]                                   ` <a484697f-9076-4a13-acf1-a645fa611614n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-02-27 17:10                                     ` 'William Lupton' via pandoc-discuss
     [not found]                                       ` <CAEe_xxhpYFisSG6gMHRx=adVbGWOLGyS30t2G6VqnX7Sye1GEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-02-28 15:03                                         ` 'Peter Vedal Utnes' via pandoc-discuss

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=Y/zc1XW7hY71aWqy@localhost \
    --to=bastien.dumont-vwifzpto/vqstnjn9+bgxg@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).