Re: Markdown MIME type?
* 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 that correctly? Yes, you did. Using a type with a subtype starting with `x-` is permissible, and in absence of a registered MIME type, the only thing that third parties can do. Note [RFC 4288, section 3.4][1], though: However, with the simplified registration procedures described above for vendor and personal trees, it should rarely, if ever, be necessary to use unregistered experimental types. Therefore, use of both x- and x. forms is discouraged. [1]: http://tools.ietf.org/html/rfc4288#section-3.4 Regards, -- Aristotle Pagaltzis // http://plasmasturm.org/ ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: Markdown MIME type?
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 that correctly? Yes, you did. Using a type with a subtype starting with `x-` is permissible, and in absence of a registered MIME type, the only thing that third parties can do. Note [RFCÂ 4288, section 3.4][1], though: However, with the simplified registration procedures described above for vendor and personal trees, it should rarely, if ever, be necessary to use unregistered experimental types. Therefore, use of both x- and x. forms is discouraged. [1]: http://tools.ietf.org/html/rfc4288#section-3.4 Regards, Yup, I remembered that -- their definition of simplified may differ from mine ;-) This from Sam Angove is informative: http://six.pairlist.net/pipermail/markdown-discuss/2007-June/000646.html Andrea Censi confirmed that [Maruku documents could be identified by profiles][] and use: text/x-markdown; profile=http://maruku.org/syntax/#ver; though there was some ensuing discussion about the legitimacy of fragment identifiers for this purpose (or at least of parsing them, instead of considering the URIs to be opaque). If we could reach consensus about mime-type / profile, we could perhaps submit them to Mozilla/Opera as recognised types to be rendered as text/plain if no helper is installed? [Maruku documents could be identified by profiles]: http://six.pairlist.net/pipermail/markdown-discuss/2007-June/000661.html -- Thomas. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: Collaboration made simple with bracket notation
On Mon, 2008-01-21 at 23:41 -0800, david parsons wrote:
I'm fairly late to the game (and I wrote a C markdown before I
started reading this list, so I'm not exactly in the mainstream) but
the syntax described on humanized seems incredibly noisy. Wouldn't
the editorial corrections markup fit better as a footnote?
I'd think that something like [text](ed: change -- why), like so:
They called to say that [they're](ed: was `their` -- be
careful with their and they're) coming over in
[a](ed: was `an` -- `an` is only before a vowel) quarter-hour.
might be a little more readable than the thicket of []'s that
Mr. Raskin proposed.
I like this variation:
They called to say that the{-ir}{+y're}{be careful with their and
they're} coming over in a{-n}{`an` is only before a vowel}
quarter-hour.
Also for author names and dates: [EMAIL PROTECTED] 2008-02-04}
___
Markdown-Discuss mailing list
Markdown-Discuss@six.pairlist.net
http://six.pairlist.net/mailman/listinfo/markdown-discuss
