Markdown Discuss - Jan 2012 - Markdown-Discuss Digest, Vol 106, Issue 4

> The only problem as I see it is that three dashes produce a long dash 
> and a hyphen rather than an em-dash, although two dashes seem to work 
> well. But investigating that will have to wait for the morrow!
I'm afraid you are confusing two different replies. SmartyPants looks for
two hyphens (or tee dashes) and turns them into an em dash. The three dashes is
for another implementation of Markdown. (There are a variety of
"flavors" or "distros" or "forks" or whatever of
it.)

john

On Saturday 14 January 2012 01:15 AM, John Laudun wrote:
>> The only problem as I see it is that three dashes produce a long
>> dash and a hyphen rather than an em-dash, although two dashes seem
>> to work well. But investigating that will have to wait for the
>> morrow!
>
> I'm afraid you are confusing two different replies. SmartyPants looks
> for two hyphens (or tee dashes) and turns them into an em dash. The
> three dashes is for another implementation of Markdown. (There are a
> variety of "flavors" or "distros" or "forks"
or whatever of it.)
>
> john
I took a look at SmartyPants.pl and saw

# Configurable variables:
my $smartypants_attr = "1";  # Blosxom and BBEdit users: change this
to
configure.
                              #  1 =>  "--" for em-dashes; no
en-dash
support
                              #  2 =>  "---" for em-dashes;
"--" for
en-dashes
                              #  3 =>  "--" for em-dashes;
"---" for
en-dashes
                              #  See docs for more configuration options.

and changed it to:

# Configurable variables:
# Changed by Chandra on 14 Jan 2012 from 1 to 2
my $smartypants_attr = "2";  # Blosxom and BBEdit users: change this
to
configure.
                              #  1 =>  "--" for em-dashes; no
en-dash
support
                              #  2 =>  "---" for em-dashes;
"--" for
en-dashes
                              #  3 =>  "--" for em-dashes;
"---" for
en-dashes
                              #  See docs for more configuration options.

and the "old school" en- and em-dsahes wrok as expected. This has been
a
quick rather than an educated fix, but it works on the command line with 
pipes in Linux.

I am yet to explore what libtext-typography-perl does in this context.

Thanks.

Chandra