Tangentially, I notice that this post by Waylan uses a link syntax which
doesn't seem to be defined by
http://daringfireball.net/projects/markdown/syntax#link but seems to
work in some implementations at http://babelmark.bobtfish.net/ - that is,
from the git repo [1]
instead of
from the git repo
Joseph Lorenzo Hall wrote on 2008/03/02 18:26:
On Sun, Mar 2, 2008 at 10:00 AM, John Fraser [EMAIL PROTECTED] wrote:
Tightening up indentation rules is definitely a breaking change, and I
don't see any payoff for users here. If anything, we should be making
indentation rules more
Waylan Limberg wrote on 2008/02/29 15:56:
With all this discussion about evolving the spec, I think we want to
remember the philosophy behind Markdown to begin with. Go re-read the
Overview[1] of the syntax rules.
... snip ...
Take the discussion a short time ago on this list regarding
Joseph Lorenzo Hall wrote on 2008/02/29 17:14:
On Fri, Feb 29, 2008 at 8:52 AM, Thomas Nichols [EMAIL PROTECTED] wrote:
Having a spec/ruleset/syntax definition seems an admirable goal; does
this necessarily imply that, for example, you should not be able to
begin a list item with zero
Joseph Lorenzo Hall wrote on 2008/02/29 17:14:
As a slightly-OT aside, there's another view on this spaces before a
list item issue that sees it as a bug.
When I write a list of references in a academic paper, I do so with
list items. I do a hanging indent where the rest of the reference is
Waylan Limberg wrote on 2008/03/01 6:12:
Hmm, I don't remember reading that before. Was it always there?
Not sure. Been there for a cuple of years at least, I think.
Anyway, to be honest this has been the hardest thing about markdown
for me to wrap my head around (and probably why I
Aristotle Pagaltzis wrote on 2008/02/04 13:44:
* Thomas Nichols [EMAIL PROTECTED] [2008-02-04 14:10]:
When this came up on the list before I think there was a
consensus that `text/x-markdown` is usable -- possibly with a
URI to identify the Markdown syntax used.
Did I understand
Michel Fortin wrote:
Le 2007-06-20 à 5:51, Thomas Nichols a écrit :
Having a mime type of 'text/x-markdown' and a profile URI
declared by the author of the language grammar (e.g.
http://maruku.org/0.5;) seems an economical solution, and would follow
the pattern for [XML namespaces][xml
Andrea Censi wrote:
Excellent, thank you very much; using fragment identifiers for versions
works for me. Andrea, would you be happy with
http://maruku.org/syntax
http://maruku.org/syntax#0.5
as profiles?
OK for me.
It's better with a final slash:
http://maruku.org/syntax/#ver
Phil Mocek wrote:
On Thu, Jun 21, 2007 at 02:45:08PM +0100, Thomas Nichols wrote:
Ok -- so your primary profile would be
http://maruku.org/syntax/
and the current spec would have a profile of
http://maruku.org/syntax/#0.5
is that correct?
This would allow us to chop the fragment
A. Pagaltzis wrote:
* Michel Fortin [EMAIL PROTECTED] [2007-06-16 15:15]:
Le 2007-06-16 à 2:57, A. Pagaltzis a écrit :
* Michel Fortin [EMAIL PROTECTED] [2007-06-16 01:30]:
Specifically, what happens if I change the page URL to PHP
Markdown Extra some day?
Sam Angove wrote:
On 6/15/07, Thomas Nichols [EMAIL PROTECTED] wrote:
Using the experimental types indicated by 'x.' and 'x-' might also be
a possibility in the short term, but is not recommended; a properly
registered mime type in the main tree would provide a clear
standardisation
Hi,
I'm in the process of adding support for Markdown to a minimal CMS in
Rails, [Railfrog][railfrog], which uses mime types to select appropriate
processing. I have had a look through the archives but have not been
able to see that a consensus has emerged as to what such a mime type for
Markdown
13 matches
Mail list logo
