public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: PhilMac <philmac-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc adding backslashes and grave accents when converting to md
Date: Tue, 19 Jul 2022 22:03:40 -0700 (PDT)	[thread overview]
Message-ID: <0e8fb0aa-d500-4152-ab39-a4314ab5d27dn@googlegroups.com> (raw)


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

I'm getting backslashes and grave accents in my files when converting to md 
from rtf. (These are files I previously exported from Apple's Pages app to 
RTF.) The backslashes come at the ends of lines and also before multiple 
periods (such as an ellipsis), and the grave accents surround characters 
including smart quotes and em-dashes and also appear at the start of most 
(but not all) lines in the document. The command I'm using to go from rtf 
to md  is:

for f in *.rtf; do pandoc --wrap=none "$f" -s -o "${f%.rtf}.md"; done
When I export the same files from Pages to docx and then convert to md, I 
don't get the grave accents, but I do get some backslashes at the ends of 
lines. I also get *[“]{dir="rtl"}* where there's a left double quotation 
mark and *[’]{dir="rtl"}* where there's a smart apostrophe (i.e. a right 
single quotation mark). This code is something in HTML 
<https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/dir> 
to do with scripts such as Arabic that are read right-to-left—I'm clueless 
as to what that has to do my documents, which use only English and were 
never in HTML. The command I'm using to go from docx to md is:

for f in *.docx; do pandoc --wrap=none -t markdown-smart "$f" -s -o 
"${f%.docx}.md"; done
(I have to use *-t markdown-smart*, or the smart quotes aren't preserved. 
But I have a similar issue if I leave it out: I get ["]{dir="rtl"} and 
*[']{dir="rtl"}**.)*


Does anyone have any thoughts on what might be going on? Clearly there are 
issues with these files—though not ones that are apparent in Pages—but I 
have no idea what the issues are.

-- 
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/0e8fb0aa-d500-4152-ab39-a4314ab5d27dn%40googlegroups.com.

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

                 reply	other threads:[~2022-07-20  5:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0e8fb0aa-d500-4152-ab39-a4314ab5d27dn@googlegroups.com \
    --to=philmac-97jfqw80gc6171pxa8y+qa@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).