tag:support.markedapp.com,2011-09-11:/discussions/problems/148391-no-typographical-apostrophes-and-quotation-marks-in-this-latest-marked-2Marked: Discussion 2018-08-07T21:48:43Ztag:support.markedapp.com,2011-09-11:Comment/458384692018-08-03T21:02:44Z2018-08-03T21:02:44Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Hi Peter,</p>
<p>Do you have Preferences->Style "Generate typographically correct quotes<br>
and punctuation" checked?</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/458384692018-08-04T15:51:13Z2018-08-04T15:51:13Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Hi Brett,</p>
<p>Yes. Here's a quick screenshot -</p></div>Petertag:support.markedapp.com,2011-09-11:Comment/458384692018-08-06T13:16:35Z2018-08-06T13:16:35Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>I'm going to recommend deleting your preference file. Unfortunately that<br>
means re-setting up Marked, but my best guess is that something<br>
corrupted and it's not registering the preference for smart typography.</p>
<p>The file is located at<br>
~/Library/Containers/com.brettterpstra.marked2/Data/Library/Preferences/com.brettterpstra.marked2.plist. Delete that and all of the cache files that have the same name but<br>
random extensions. Empty the trash and reboot your machine (to clear out<br>
cached preferences). Then launch Marked 2 again and see if the issue is<br>
resolved.</p>
<p>Instead of deleting in the instructions above, you can also move the<br>
file to your Desktop (just the .plist, still delete the random extension<br>
files) and test after a reboot. If it changes nothing you can quit<br>
Marked and move the file back into place to restore your previous<br>
preferences.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/458384692018-08-06T20:06:04Z2018-08-06T20:06:05Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Hi Brett,</p>
<p>OK, just deleted +/or moved that stuff. Tried without restarting the computer, no change. I'll need to wait to restart, so I'll get back later on that. If necessary I can (can't I) delete the app and re dl it from Mac store.</p>
<p>I think something like this happened in the Yosemite era, but you had already posted an update by the time I sent a note to you.</p>
<p>Thanks,</p>
<p>Peter</p></div>Petertag:support.markedapp.com,2011-09-11:Comment/458384692018-08-06T20:10:19Z2018-08-06T20:10:33Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>The restart is needed as current versions of macOS cache preferences so<br>
heavily that as soon as you delete the file it writes the old<br>
preferences back to disk upon next launch. So do test with the reboot<br>
before giving up on that.</p>
<p>Reinstalling the application won't really affect this; if it's a<br>
preference issue, those will persist between installations.</p>
<p>The only other thing I can think of is a possible encoding issue in the<br>
document. Can you post a sample document that you can verify does not<br>
get its typography "smartened?"</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/458384692018-08-07T20:41:22Z2018-08-07T20:41:23Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Hi Brett,</p>
<p>After deleting everything except the app itself and restarting, nothing had changed, but I did some experimenting ... and it's not your fault. I found the culprit. Explanation follows.</p>
<p>I opened a previously fine .md file in Marked 2 - it was fine in Marked 2, as before. I examined these two files - the current one that had been the problem and the earlier file - to see if there was a difference anywhere. Was it the asterisks in the title? No. I tried removing one apostrophe, then replacing it (in TextWrangler) and Marked 2 made the correct replacement. That was the problem. I replaced all the apostrophes and quote marks and Marked 2 did its thing perfectly.</p>
<p>Here's what happened. I used the new/newish Highland app to compose the draft of this story, then copied and pasted it into TextWrangler (I use BBedit too, but that is reserved for another project). Highland uses some kind of non-plain apostrophes and quote marks. There's no preference in Highland indicating this and it's supposed to be a markdown editor. While I hand replaced the apostrophes and quotes in the experiment, I see that I could also have used TextWrangler's "straighten quotes" for this and that would work. I'll have to remember that if I use Highland again for this kind of thing.</p>
<p>So all is well and you don't have to do any update for this. Apologies to you for the concern this caused. I hope the explanation was helpful and you can make use of it somehow.</p>
<p>Further workflow info IYI: I'm currently using one of the static site generators for the basics, page and index/list files. It works but I do not like its built-in markdown converter. I always replace the body of the article with the Marked 2 html (and edit again with class names etc).</p>
<p>Thanks,<br>
Peter</p>
<p>ps. wrote this before seeing your reply.</p></div>Petertag:support.markedapp.com,2011-09-11:Comment/458384692018-08-07T20:57:58Z2018-08-07T20:57:58Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Thanks for the update! I'm actually working on Highland 2 support at<br>
this moment, so I'll see if I can get any info from them on this.</p>
<p>-Brett</p></div>Bretttag:support.markedapp.com,2011-09-11:Comment/458384692018-08-07T21:48:42Z2018-08-07T21:48:43Zno typographical apostrophes and quotation marks in this latest Marked 2<div><p>Thanks Brett. Hope that works out with Highland 2. They probably were not expecting this kind of use for the app.</p>
<p>I did just see they have footnotes on their roadmap - that is something only Marked 2 does as far as I have seen.</p>
<p>Peter</p></div>Peter