public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Filip Wojtelewicz <majk2020-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Issue with File Attachments when Converting to MediaWiki Format in Pandoc
Date: Tue, 25 Apr 2023 15:57:42 +0200	[thread overview]
Message-ID: <CAL+11QHLLiQ5UAeF5gRYX+LTddDKRv8rR7ezLeiPK6A695orvQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

Dear Pandoc Support Team,

I am writing to report an issue I encountered while using Pandoc to convert
a document to MediaWiki format. Specifically, I am having trouble with the
META:FILEATTACHMENT syntax not being properly recognized and converted.

I am using Pandoc 3.1.2 on Linux. When I try to convert a file like
0MetaRun.txt that I am including with this email, everything works fine.
However, when I try to convert a file like MetaBug.txt, the terminal
freezes. I have waited for approximately an hour, but it was still frozen.
I am unsure where the issue lies.

Could you please advise me on how to properly use the META:FILEATTACHMENT
syntax for MediaWiki format conversion? I would greatly appreciate any
guidance or suggestions you can provide.

Thank you for your time and attention to this matter.

Best regards,

Filip Wojtelewicz

-- 
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/CAL%2B11QHLLiQ5UAeF5gRYX%2BLTddDKRv8rR7ezLeiPK6A695orvQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 1764 bytes --]

             reply	other threads:[~2023-04-25 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 13:57 Filip Wojtelewicz [this message]
     [not found] ` <CAL+11QHLLiQ5UAeF5gRYX+LTddDKRv8rR7ezLeiPK6A695orvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-04-25 17:00   ` John MacFarlane
     [not found]     ` <78F79D18-975F-4F6E-AF24-820558FB882E-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-04-26  6:33       ` Filip Wojtelewicz
     [not found]         ` <f3490c88-cb2c-4403-9174-53a2a7d8333dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-04-26 19:14           ` 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=CAL+11QHLLiQ5UAeF5gRYX+LTddDKRv8rR7ezLeiPK6A695orvQ@mail.gmail.com \
    --to=majk2020-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).