Incorrect punctuation in headers and body should be replaced

[alexgreen]

There are some pervasive typographic errors that plague Tyee headlines and body text.
Here's the most common ones that I've been seeing for years:

1. Double-hyphens should be replaced with em dashes
   See here in the subheader: http://preview.thetyee.ca/News/2016/06/06/Return-to-Fort-Mac/
   This might seem like a minor issue, but incorrect use of the written language damages the credibility of newspaper.
   For html codes and further explanation see here: http://www.accessc.com/articles/hyphen-en-dash-em-dash.html
2. The text uses a dumb quote mark, not a real quote mark. (http://webdesign.tutsplus.com/articles/start-using-quotation-marks-the-correct-way--webdesign-16905)

I'm not sure if the problem is that writers are using the wrong characters, or that the text is getting converted improperly somewhere down the line. I think we talked about this before, but didn't decide on a solution.
I looked into whether there's a CSS-based solution for replacing these but no dice, so I guess this may have to get replaced in the back end or via (hopefully not) javascript. Soon we'll need to start using proper punctuation marks as every other reputable publication does. Incorrect use of language doesn't reflect well on a newspaper's brand credibility.

[phillipadsmith]

This might seem like a minor issue, but incorrect use of the written language damages the credibility of newspaper.

There's another issue where we discussed this. Smartypants is a solution. I feel like it was already implemented at The Tyee at one point.

@MrBryan assign this to me if you want me to dig around and install SmartyPants as a library for Bricolage, and get it running as a filter on article text.

The key is, however, to see where those double-hyphens are actually originating. E.g., are they in the Word document that the poster is using? If so, we can just address it there.

Phillip.

[alexgreen]

This is related to #200

Since this issue is actually applies to punctuation in general I'm going to broaden the scope of the issue title and specify some common examples.

[MrBryan]

Since there are multiple posters and some are in turn getting form other authors i'm thinking it's best to address at bric phase. I don't mind doing it - let's say post launch... I know it's a shame to republish everything again but I think there are a number of items we will have to do that for, too, and this will add one more possible complication as we are paring issues down, much as our credibility remains in peril until then. That said if you really want to do it now I certainly won't protest.

[MrBryan]

looks like you said post launch anyways

[alexgreen]

Since our readers been suffering this for many years already I don't think this is a life-or-death issue so I wouldn't want it to block other things, but a redesign will prompt readers to look at things more closely (especially with the larger typography) so if there's time it would be great to do it.

[phillipadsmith]

More examples of double dash where there should be m-dashes: http://preview.thetyee.ca/News/2016/01/14/Westray-Act-Update/

[phillipadsmith]

Should be as simple as adding this Perl module to the PERL_LOADER section of the bricoalge.conf, restarting Bric, and then adding something along the lines of:

<%filter> 
$_ = Text::SmartyPants::process($_, 1); 
</%filter> 

... in page.mc to parse the raw text and return "smart" text.

[phillipadsmith]

Final word from Robyn: It was a legacy from years ago that nobody is willing to take responsibility for! ;-) We can convert and/or re-train posters. Probably easiest to just convert where we find those things in Bric.