public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: danny <thesanketshete-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: How do i replace { with unicode characeter
Date: Sun, 16 May 2021 03:32:52 -0700 (PDT)	[thread overview]
Message-ID: <1c9abd0c-12a2-4fe1-be1e-a2e720076ba8n@googlegroups.com> (raw)


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

 <https://stackoverflow.com/posts/67555448/timeline>

I have converted Github flavored markdown file to HTML using pandoc.

Pandoc is replacing special characters with unicode characters. I want to 
replace two more characters { } with unicode characters because I am using 
that HTML inside JSON objects value and without unicode characters for { 
}it shows an error. But there is no error after replacing them with unicode 
characters.

Is there any way to replace { } with the unicode characters while 
converting the file from Markdown to HTML?

-- 
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/1c9abd0c-12a2-4fe1-be1e-a2e720076ba8n%40googlegroups.com.

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

             reply	other threads:[~2021-05-16 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-16 10:32 danny [this message]
     [not found] ` <1c9abd0c-12a2-4fe1-be1e-a2e720076ba8n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-05-16 19:40   ` 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=1c9abd0c-12a2-4fe1-be1e-a2e720076ba8n@googlegroups.com \
    --to=thesanketshete-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).