Styling Markdown approaches

Sherwood Botsford sgbotsford at
Sat Apr 20 23:40:00 EDT 2013

The reason there are Aleph{null} implementations is that while good, it
hasn't been good enough to keep people from just inserting raw html when
they ran into a limit.

If I followed the letter of the syntax rules, there would be no point in my
using markdown. EVERYTHING in my pages is in a div. The top level
description of my pages is
<div id="menu">
<div id="content>

Inside those divs, are picture and pullquote divs.

As you said, the purpose of MD is to make writing (and reading, and editing
and proofing) easy. Ok. Easier. Writing is never easy. And the last
thing I need is a bunch of <a href=*(*@+F*C^(S*(_S(*#$$&$@#> tags getting
in my way.

Normally I want MD to be interpreted inside HTML tags. I have difficulting
coming up with a case for NOT having them interpreted.

Much as I froth at times about MD, it sure beats writing in html.


Sorry. You poked the bear. Back to my hibernation...


Sherwood of Sherwood's Forests

Sherwood Botsford
Sherwood's Forests --
50042 Range Rd 31
Warburg, Alberta T0C 2T0

On 20 April 2013 16:05, Waylan Limberg <waylan at> wrote:

> I think the syntax rules regarding raw html [1] shed some light on this

> issue:


> > Markdown is not a replacement for HTML, or even close

> > to it. Its syntax is very small, corresponding only to a very

> > small subset of HTML tags. The idea is not to create a

> > syntax that makes it easier to insert HTML tags. In my

> > opinion, HTML tags are already easy to insert. The idea

> > for Markdown is to make it easy to read, write, and edit

> > prose. HTML is a publishing format; Markdown is a writing

> > format. Thus, Markdown’s formatting syntax only addresses

> > issues that can be conveyed in plain text.

> >

> > For any markup that is not covered by Markdown’s syntax,

> > you simply use HTML itself. There’s no need to preface it

> > or delimit it to indicate that you’re switching from Markdown

> > to HTML; you just use the tags.


> In other words, if you want a *publishing* format, use raw HTML. If

> you want to wrap some text in a div to add styling hooks, fine. But if

> you want to format the contents of that div, then use HTML for that

> also. After all, "Markdown is not a replacement for HTML."


> Yes, some markdown implementations have added some optional extras,

> but those extras generally fit into the philosophy quoted above (see

> definition lists). That said, I have seen some pretty horrid requests

> for extending the syntax as the maintainer of the Python-Markdown

> project (which has an extensive API for writing extensions). While I

> agree that user defined extensions are an appropriate way to go, one

> should always be careful when introducing new syntax. John

> MacFarlane's FAQ [2] is evidence of that.


> [1]:

> [2]:


> --

> ----

> \X/ /-\ `/ |_ /-\ |\|

> Waylan Limberg

> _______________________________________________

> Markdown-Discuss mailing list

> Markdown-Discuss at



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the Markdown-Discuss mailing list