From: "tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <tridral-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Preserving characters in ODT to MD conversion
Date: Fri, 16 Apr 2021 11:13:36 -0700 (PDT) [thread overview]
Message-ID: <a2ce8a3e-b35b-4343-84ee-d6d75e592f67n@googlegroups.com> (raw)
In-Reply-To: <m2tuo7fd7p.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1687 bytes --]
Dear John,
Thank you again for your timely assistance. That worked perfectly
best regards,
'ö-Dzin
On Thursday, 15 April 2021 at 22:30:19 UTC+1 John MacFarlane wrote:
>
> Use -t markdown-smart
>
>
> "tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>
> > I have a file containing opening and closing quotation marks and
> ellipses.
> > These become 'flattened' when converting from ODT to MD so that
> > ’‘ (open and closing single quotes) both become '
> > ”“ (open and closing double quotes) both become "
> > … (ellipsis) becomes ... (three separate dots)
> > Is it possible to preserve these characters in the conversion?
> >
> > I've looked at the manual and I've not found how to do it.
> >
> > Thank you for any help.
> >
> > --
> > 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
> https://groups.google.com/d/msgid/pandoc-discuss/3997d029-711c-4b1b-9077-9e0dd2fbfed2n%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-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/a2ce8a3e-b35b-4343-84ee-d6d75e592f67n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2890 bytes --]
prev parent reply other threads:[~2021-04-16 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 17:26 tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <3997d029-711c-4b1b-9077-9e0dd2fbfed2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-15 21:30 ` John MacFarlane
[not found] ` <m2tuo7fd7p.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-04-16 18:13 ` tri...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
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=a2ce8a3e-b35b-4343-84ee-d6d75e592f67n@googlegroups.com \
--to=tridral-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).