From: Adam Wood <adam.michael.wood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: output html entities?
Date: Fri, 9 Jan 2015 11:53:46 -0800 (PST) [thread overview]
Message-ID: <e5aaeeee-0d20-414c-a90f-7e67b347fb5a@googlegroups.com> (raw)
In-Reply-To: <14386839.2417.1295205524913.JavaMail.geo-discussion-forums@yqcj39>
[-- Attachment #1.1: Type: text/plain, Size: 2907 bytes --]
Well this is 3 years later, but I happened to be looking into something and
ran across it.
So... I can't tell if Mark was being facetious or not in his disavowal of
any desire to have html entities for curly quotes, emdashes, etc.
I still strongly prefer it, especially for certain cases where I don't have
control over the display environment. (I write for other people, and
sometimes other people have bad html character set declarations --- also
commenting systems, feeds, etc.)
My solution has been to execute pandoc from within a bash script I wrote
that goes back afterwards and uses sed to replace characters with their
appropriate entity.
(I also use it to direct the output to an appropriate directory, with a
filename based on the original, and with all the other options I want ---
rather than trying to remember and have to type a million flags and options
and two file names into the command line)
kfile="$1.kramdown"
hfile="../html/$1.html"
pandoc -f markdown-auto_identifiers -S -o $hfile $kfile
sed -i '' -e "s/’/\’/g" -e "s/‘/\‘/g" -e 's/“/\“/g' -e
's/”/\”/g' -e 's/—/\—/g' -e's/–/\–/g' $hfile
open -a "Sublime Text" $hfile
On Sunday, January 16, 2011 at 11:18:44 AM UTC-8, Mark (my words) wrote:
>
> Well, I’m embarrassed.
>
> I have been out of the loop for a *long* time. Back in the day I saw the
> debate go from not using special characters, to using named entities, to
> numerical entities, and back and forth. And now—
>
> Are we actually to a point were we can use real raw characters?!
> It strikes me as a fantastic magic.
>
> Bruce is right, we should be living in the present and planning for the
> future. My bizarre need for human readable machine language is antiquated
> and needless and moot—you can’t get much closer to human-readable than
> straight-out unicode.
>
> Now I’m feeling rather silly for hacking up the Multimarkdown source code
> to spit out named-entites now, but it was a lot of fun.
>
> And yeah, I’d installed the latest Tidy a couple months back but haven’t
> had the time to screw with it until now, again more magic, that project has
> come a long way too!
>
>
> Thanks guys for your patient advice.
>
>
> -Mark
>
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/e5aaeeee-0d20-414c-a90f-7e67b347fb5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 4156 bytes --]
next prev parent reply other threads:[~2015-01-09 19:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-15 19:14 Mark (my words)
2011-01-15 21:38 ` John MacFarlane
[not found] ` <20110115213823.GA42115-8pRoOo7FpFbPoI0UbmHJ02ZHpeb/A1Y/@public.gmane.org>
2011-01-16 0:46 ` Mark (my words)
2011-01-16 2:59 ` John MacFarlane
2011-01-16 15:28 ` Bruce
[not found] ` <4c92e083-7e37-4c00-8e5b-01d96f24dcab-avJ8sObw66XHdqrNY7FC6GB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
2011-01-16 15:42 ` Bruce
[not found] ` <1b63e5cd-5fe8-424e-a246-c5e39cd2e3b4-G0pd0bfxH2K3V1BluC5fqGB/v6IoIuQBVpNB7YpNyf8@public.gmane.org>
2011-01-16 19:18 ` Mark (my words)
2015-01-09 19:53 ` Adam Wood [this message]
[not found] ` <e5aaeeee-0d20-414c-a90f-7e67b347fb5a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-01-09 20:14 ` Matthew Pickering
2015-01-09 20:33 ` Daniel Staal
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=e5aaeeee-0d20-414c-a90f-7e67b347fb5a@googlegroups.com \
--to=adam.michael.wood-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).