![]() In his email John graciously indicated that he would "probably" approve a name like "Strict Markdown" or "Pedantic Markdown". Shut down the domain, and don't redirect it.Īll fair. We corrected this immediately when it was brought to our attention. You'll note that I took care to manually capitalize Markdown in the parts of the spec I copied to the blog post and home page – but I neglected to mention this to John MacFarlane as I should have. This was an oversight on our part – and also my fault because I did notice Markdown wasn't capitalized as I copied snippets of the spec to the homepage and blog post, and I definitely thought it was odd, too. John Gruber was also very upset, and I think rightfully so, that the word Markdown was not capitalized throughout the spec. That was not our intent, it was more of an aspirational element of "what if, together, we could eventually.". Standard does have certain particular computer science meanings, as in IETF Standard, ECMA Standard. ![]() If the name we chose made inappropriate overtures about Standard Markdown being anything more than a highly specified flavor of Markdown, I apologize. We were simply trying to pick a name that correctly and accurately reflected our goal – to build an unambiguous flavor of Markdown. I assure you that we did not choose the name to make you, or anyone else, angry. It was a bit of a surprise to get an email last night, addressed to both me and John MacFarlane, from John Gruber indicating that the name Standard Markdown was "infuriating". So I changed them to match Standard Markdown, and that's what we launched with. We were building Yet Another Flavor of Markdown, one designed to remove ambiguity by specifying a standard, while preserving as much as possible the spirit of Markdown and compatibility with existing documents.īefore we went live, I asked for feedback internally, and one of the bits of feedback I got was that it was inconsistent to say Standard Flavored Markdown on the homepage and blog when the spec says Standard Markdown throughout. So I originally wrote the blog post and the homepage using that terminology – "Standard Flavored Markdown" – and even kept that as the title of the blog post to signify our intent. … that John seemed OK with the name "GitHub Flavored Markdown". Strict Markdown? XMarkdown? Markdown Pro? Markdown Super Hyper Turbo Pro Alpha Diamond Edition?Īs we were finalizing the name, we noticed on this podcast, at 1:15 … There was lots of internal discussion about what to name our project. There was no response, so we assumed that John Gruber was either OK with the project (and its name), or didn't care. Since John MacFarlane was the primary author of most of the work, we suggested that he be the one to reach out. As we got closer to being ready for public feedback, we emailed John on August 19th with a link to the Standard Markdown spec, asking him for his feedback. We invited John Gruber, the original creator of Markdown, to join the project via email in November 2012, but never heard back. We've been working on the Standard Markdown project for about two years now. Let me open with an apology to John Gruber for my previous blog post. When I have a moment, I’ll try dealing with them myself, though I’m very far from being macro-savvy.Standard Markdown is now Common Markdown I don’t know if you want to spend the time sorting out these small issues in case anyone else is interested in using it, but, just in case, I attach a nonsense document for you to play with. ![]() Although your macro replaces single with double carriage returns, it doesn’t do so at the end of the line preceding a bullet list, at least not my bullet lists.I haven’t yet tried removing those line from your macro style definitions, but will try. I think that is the problem because doesn’t have either font or font-size specified in the styles. I still don’t get headings or bold/italics converted, but I think the reason is that in the style-sheet for your macro, the style statements are all defined as 12 pt and bold and italic with the latter defined as Courier Prime-presumably that is what you are using-and my styles have different sizes and either Adobe Garamond Pro or Times New Roman.As I said, for macro, I need to substitute double carriage returns for the single carriage returns used in the RTF, together with a couple of other tweaks… very easy, and it doesn’t add paragraph spacing within the bullet lists.įor your macro, having inserted the # before that comment, it runs, but: I’ve again tried the two macros on the same document. I forgot a # in front of the comment line. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |