Re: Leading/trailing whitespace in inline

Now, it might be possible to salvage your proposal by introducing an exception, that trimming spaces from code spans only applies when more than a single backtick is used as the delimiter. But that would make the rules more complicated, and it only allows you to

Re: Proposal for (source-side) hyphenation support

aped new-line chars so far, used it > to ignore the line break. That’s exactly what Fletcher just said MultiMarkdown already does. > We should fix MultiMarkdown then ;) just kidding What’s there to fix? Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> __

Re: Original Markdown.pl v1.0.1 Script (Anno 2004) Unzipped and Archived for Easy Browsing on Github

e been intending to ping John about this, as well as to put out a public call for anyone who happens to still have other releases, but that hasn’t happened yet. Nevertheless, what’s there is at least a start. Regards, -- Aristotle Pagaltzis // <http://plasma

Re: does fireball markdown support anchor links?

are desired, their derivation *must* be performed by code from the environment which has sufficient information to be able to do that. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discus

Re: does fireball markdown support anchor links?

> the thing about "manually specified" anchors is that they will show > all kinds of idiosyncrasies. so not only are they work to create, but > they are also inconsistent, thus undependable, meaning you have to > look at each one to see what it is, so they have almost _no_ redeeming > qualities at

Re: Opinions on in-band variation signaling

ns. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

Re: Markdown within block-level elements

orm is probably enough” I would just punt on that. Great, now you just need to convince some sufficient number of Markdown converter authors/maintainers to support this extension. :-) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/>

Re: Markdown within block-level elements

’s. There is no “ecosystem” about that. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net https://pairlist6.pair.net/mailman/listinfo/markdown-discuss

Re: It's a Markdown processor, right?

, but > unlike translator are actually used by the existing implementations. That would exclude parsers, indexers, etc. whose output is not another form of the document. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___

Re: It's a Markdown processor, right?

hooses (it could use parsing, or not). I would argue that the only sufficiently generic term that will apply to software in all of these cases is, in fact, “processor”. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Mark

Re: Markdown internal metadata Re: Markdown validity

ady have directories full of files with nothing but Markdown in them. 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 validity Re: Agreeing on "Historical Markdown"

invalid HTML then you’ll simply get HTML that’s invalid in the same way, to then be interpreted by the browser however the browser may. My guess is that the majority of implementations behave equivalently to this, though depending on their design they could differ completely. Regards, --

Re: text/markdown effort in IETF (invite)

s fenced code blocks. (I feel this is especially so for backtick fences. Tilda fences seem to have some remote likelihood of being used as an innocuous part of a non-fenced-code-block document.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> __

Re: text/markdown effort in IETF (invite)

* Sean Leonard [2014-07-10 06:30]: > On 7/9/2014 8:06 PM, Aristotle Pagaltzis wrote: > > Yet guessing wrong is largely without consequence. > > > > There are really no syntax features that affect the document’s > > rendering non-locally. If part of a document is w

Re: text/markdown effort in IETF (invite)

ion – what process do they have to go through before they can assign a truthful MIME type to their documents? Metadata is hard. Let’s go shopping. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing l

Re: text/markdown effort in IETF (invite)

ovide a means for the user to view the source Markdown document in unformatted form. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: RFC: Remove Paragraph Tags between Tags

ay to get just a bare block of tags with nothing around them. It’s not a use that it was designed for. If you are writing the CMS yourself then I’d suggest using Markdown and doing something like .replace('^', '') on the output. If not, then try to find if you can turn of Markdo

Re: Github-style fenced code blocks

ike them. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: attribute blocks for definition lists

* Andy Lee [2013-07-01 18:55]: > Out of curiosity, do I understand correctly that > > term > : definition > > is already in common usage when people write plain text? I was not > aware of that, so if so, I may start adopting it in my own emails etc. I’ve never seen it in email. _

Re: Problem with links in Markdown

L for the link in question, i.e. write it as . It’s a wart, but can be lived with. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Styling Markdown approaches

* Sherwood Botsford [2013-04-20 16:20]: > It's actually worse than that, because for me MMD is actually a module > in Template Toolkit. So my information is MD markup wrapped in > a preface and epilog of template toolkit. [% FILTER replace('<[^/>][^>]*\K>', ' markdown="1">') # Perl 5.10+ required

Re: Styling Markdown approaches

* Sherwood Botsford [2013-04-19 16:05]: > * Aristotle Pagaltzis [2013-04-19 13:30]: > > * Sherwood Botsford [2013-04-18 17:20]: > > > (I wish that this was a toggle that could be set in a .mmdrc file. > > > There are a lot of things that I wish I could set in an .mmdr

Re: Styling Markdown approaches

* Sherwood Botsford [2013-04-18 17:20]: > (I wish that this was a toggle that could be set in a .mmdrc file. > There are a lot of things that I wish I could set in an .mmdrc file.) That would be bad for Markdown. ___ Markdown-Discuss mailing list Markdo

Re: Community Group for Markdown Standardization

ne feature that is likely to be added which has no direct support in HTML, precisely because of that lack of direct expressibility in HTML, namely footnotes. (Or has HTML 5 provided a solution here (and one that isn’t still evolving)?) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: New List of implementations.

* Sherwood Botsford [2012-10-31 20:45]: > Would it not make more sense to add this to the wikipedia page > either as a section of the present page, or as a linked page? No. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.p

Re: Disabling certain stuff for my forum

* Tony [2012-08-13 01:50]: > I think I'll just go for CSS now Arguably that is the correct solution to your problem anyway. It’s not the marking up of text as headings that is causing the problem, it is (abuse of) the presentation of headings, and CSS is how to fix that. _

Re: ToDo List Notation

* Clint Laskowski [2011-12-11 16:15]: > Thoughts? You are looking for orgmode. Markdown is the wrong tool. ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: let's get this established, one way or the other, once and for all

* Thomas Humiston [2011-12-07 20:40]: > * Richard Caldwell [2011-12-05 05:55]: > > I've created an email filter to discard emails > > I set mine to flag them with color. I have them automatically marked as read on receipt. And mailing list mail goes into folders immediately, not to my inbox. Net

Re: doesn't that make you wonder?

* bowerb...@aol.com [2011-10-16 21:40]: > how will i ever be able to manage without your valuable input? You don’t need it. You’ll take the world by storm same as you did the last five times you created a revolution. With or without my participation, the outcome won’t differ.

Re: fuck yeah markdown

* bowerb...@aol.com [2011-10-15 22:00]: > brett has accomplished more in the last three months than this > listserve accomplished in the last three years. Well, we can agree he has achieved more in three months than you have in a decade of talking. ___

Re: godspeed, steve

* bowerb...@aol.com [2011-10-06 18:40]: > christian sciberras said: > >inappropriate > > and i would expect that you did not "intend" for that to sound quite > so insensitive either; still, you are making it increasingly difficult > for me to choose not to interpret it that way. Do interpret

Re: An Observation

* Michel Fortin [2011-05-14 23:40]: > Le 2011-05-14 à 15:55, Aristotle Pagaltzis a écrit : >> An anatomy of a loss of interest: >> >>2004 279 >>2005 153 >>2006 78 >>2007 25 (21 in the first half of the year) >>20086 (

Re: An Observation

t triggering emphasis on word-internal underscores.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: What does Markdown do with HTML comments? Recommendation on Markdown file extension?

* Waylan Limberg [2011-05-05 03:25]: > However, most projects I'm aware of use '.md' or '.markdown'. `.mkd` and `.mkdn` are also popular. I’ve seen `.mdwn` also, and I think even `.mdn` though I’m not sure about that one. Regards, -- Aristotle Pagaltzi

Re: ol start with a specific number?

to the textarea in some web app, which also advertises Markdown support. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Any way to get syntax-highlighted code blocks with Text::MultiMarkdown?

* Dr. Drang [2010-12-07 18:10]: > On Mon, Dec 6, 2010 at 10:45 AM, Aristotle Pagaltzis wrote: > > There is no need to wedge any of this into Markdown itself. > > I'm not suggesting the purity of standard Markdown be sullied > by my barbarous addition. Oh no. No ivory tow

Re: Any way to get syntax-highlighted code blocks with Text::MultiMarkdown?

arkdown spits out HTML. Any highlighter that can fish `` and `` out of HTML and highlight it will work on the Markdown’s output. There is no need to wedge any of this into Markdown itself. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> _

Re: markdown do not support Strikethrough ?

, just omit them from your supported subset of HTML. That way you support real Markdown, not a crippled Markdown-lookalike syntax. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.

Re: using markdown in a forum?

haven’t done enough research: qr{ \A [ \t]* (:? https? :// | / ) }ix With this, simply-written site-local absolute links are OK in addition to HTTP links. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discus

Re: using markdown in a forum?

r smaller/bigger text, people will abuse them for setting large or small text that’s not a headline. For similar reasons, I’d also whitelist `tt`. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing

Re: using markdown in a forum?

or `*foo*`, as indeed it shouldn’t. And it’s not impossible to write a 100% solid filter if you use a *white*list applied to a real HTML parser. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown

Re: Markdown development

of good and bad to Betamax’ mix of good and bad. End of story. It’s like saying webmail is inferior to desktop mail clients. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six

Re: Markdown development

hould be somehow included. The problem with tables as I see it is as above: I think that tables fundamentally cannot be both easy to edit and easy to read within the constraints of plaintext. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> __

Re: Markdown development

be done badly, and so should not be done at all.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Media type for markdown?

* Dietrich Epp [2010-03-06 22:40]: > I think it's about time that markdown had its own IANA media > type. Most people just use text/x-markdown, I think. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Dis

Re: Markdown development

with a good enough sense for its spirit and enough of a voice to gain the authority to have his or her mandates followed. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.

Re: Markdown development

e > matches any run of ticks, not just the one or two that I read > from the standard. According to the spec it *is* supposed to match any number of ticks – but they are supposed to be the *same* number on both ends. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___

Re: multiline header

* Waylan Limberg [2010-03-02 18:25]: > To be honest, I can't think of any elegant way to do multi-line > setext headers, Exactly. > but multi-line hash headers should be easy. I’ll agree with that. Regards, -- Aristotle Pagaltzis // <http:

Re: multiline header

semantic, says who? More importantly, the problem was not to display a header across two lines in the rendered document, it was being able to write the header across several lines in the source document (and still have a single tag in the rende

Re: tables with Unicode box drawing characters?

* Suraj Kurapati [2009-09-09 06:20]: > What if Markdown used Unicode characters to express tables > in this manner? Then I would still write my tables using HTML tags. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Mark

Re: Query about emphasis

t easier to read for a human.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: A Modest Definition List Proposal (David E. Wheeler)

* Aristotle Pagaltzis [2009-02-28 16:18]: > You can make a lot easier to write with a very simple tweak: Sorry for the noise. Someday I’ll consistently remember to read the whole thread before following my impulse to respond. Regards, -- Aristotle Pagaltzis // <http://plasmastu

Re: A Modest Definition List Proposal (David E. Wheeler)

5 | Illust. | An illustration | line breaks are not | | andn I think you | possible in a table | | know what I mena.| That is æsthetically less pleasing, but it’s no less legible, and it’s most definitely *far* less ted

Re: Cpp-Markdown 1.00

access already add it? Done. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: A Modest Definition List Proposal

* David E. Wheeler [2009-02-19 02:00]: > Yeah, okay. […] D’oh! Oh yeah! Told you it is a thorny problem. :-( It *looks* simple, yeah… Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdow

Re: A Modest Definition List Proposal

possibly entirely unaware!) writers of Markdown. Thorny problem. :-( Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: use re 'eval' error

* Louis-David Mitterrand <[EMAIL PROTECTED]> [2008-10-23 13:55]: > What is the fix? You have to patch Text::Markdown to add that line to the block the regex is in. I see you have already filed a bug against Text::Markdown, excellent. Regards, -- Aristotle Pagaltzis // <http://pla

Re: list corner case

e less ambiguous? Is forcing the author to become less ambiguous even a goal of Markdown? > this position has enough rigor that you cannot destroy it. i'd > say it's far better to say "i don't prefer it" and move on. I see. Regards, -- Aristotle Pagaltzis //

Re: list corner case

* Albert Skye <[EMAIL PROTECTED]> [2008-09-09 08:00]: > Markdown syntax presents a strong pattern of using blank lines > to separate elements. > Does it? > I hadn’t noticed. Regards, -- Aristotle Pagaltzis // <h

Re: list corner case

an find no way to reconcile the above with your claim that ambiguous writer’s intent puts a source document outside the realm of Markdown’s philosophy of publishability. [1]: http://daringfireball.net/2004/03/dive_into_markdown Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: list corner case

ersonally, I'm the type that's going to renumber the items > anyway If you kept Markdown documents in a version control system, you would avoid that. :-) (Renumbering items when shifting them around can cause a lot of noise in diffs from spurious changes.) Regards

Re: list corner case

contest. But in actual discussion here on list, as far as I saw, with the exception of “Bowerbird” who made up option D, everyone voted for C, with some of us calling A a reasonable secondary option. (Did I misread the discussion?) Regards, -- Ari

Re: list corner case

* Waylan Limberg <[EMAIL PROTECTED]> [2008-09-08 17:15]: > On Sun, Sep 7, 2008 at 10:14 PM, Aristotle Pagaltzis <[EMAIL PROTECTED]> > wrote: >> Any inferred nesting would have to subordinate them to an implied >> 3rd item in the surrounding unordered list that

Re: list corner case

ectly". >> >> [...] >> >> i think, in the long run, that makes it easier for people, >> because it demands that they be clear in their thought. >> >> if they are ambiguous about what they want, do nothing! > > This entirely contradicts Markdown’s p

Re: list corner case

ot as an unordered list with an ordered list nested inside its 2nd item. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Syntax Questions

l be correct. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Syntax Questions

report a bug and they can’t test whether their bugfix breaks previously working stuff? Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: Syntax Questions

* Jurgens du Toit <[EMAIL PROTECTED]> [2008-07-17 14:25]: > Is it a bug or a feature that the following two texts get > formatted differently? That’s on purpose. To make a list, it needs to be in a separate paragraph. Regards, -- Aristotle Pagaltzis // <http://

Re: mkhtml.py: writing HTML documents in Markdown

* Kragen Javier Sitaker <[EMAIL PROTECTED]> [2008-06-08 18:00]: > On Sat, 7 Jun 2008 17:42:53 +0200, Aristotle Pagaltzis wrote: > > * Kragen Javier Sitaker <[EMAIL PROTECTED]> [2008-06-07 09:40]: > > > Stylesheeting comes naturally. I just put a `

Re: mkhtml.py: writing HTML documents in Markdown

[Note to markdown-discuss readers: for context see ] * Kragen Javier Sitaker <[EMAIL PROTECTED]> [2008-06-07 09:40]: > Stylesheeting comes naturally. I just put a `

Re: Optional features (was: Markdown Extra Specification (First Draft))

* Yuri Takhteyev <[EMAIL PROTECTED]> [2008-05-24 21:35]: > * Aristotle Pagaltzis <[EMAIL PROTECTED]> [2008-05-24 11:15]: > > If your XHTML parser has a streaming input mode, you can > > couple your Markdown converter directly to the XHTML parser > > and feed the HT

Re: Optional features (was: Markdown Extra Specification (First Draft))

* Yuri Takhteyev <[EMAIL PROTECTED]> [2008-05-23 08:35]: > * Aristotle Pagaltzis <[EMAIL PROTECTED]> [2008-05-23 05:40]: > > I also agree with your opposition to them; if anything, one > > should filter the *output* of a Markdown-to-HTML conversion > > so that it

Re: Optional features (was: Markdown Extra Specification (First Draft))

so why disallow those tags? OTOH disallowing literal tags in the input means you cannot write a `` with a `cite` attribute, since Markdown provides no syntax for that. Scrubbing the input indiscriminately therefore removes functionality for no benefit at all. Regards, -- Aristotle Pag

Optional features (was: Markdown Extra Specification (First Draft))

down documents to work in all Markdown and Markdown Extra processors. The scope of the problem is much smaller in such a scenario, enough so to be perfectly tractable. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Di

Re: Feature Request External label resolution

exactly cheap. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

On ampersands in query strings (was: HTML entities in URLs and urlencoding)

hem! You need to set an unbreak-me config option to make it recognise the semicolon.) Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: [ANN] Babelmark

ath expressions, templates in some template mini-language, whatever. If the coverage metric doesn’t cross the language barrier right along with the code, it breaks down at these points. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___

Re: [ANN] Babelmark

* Michel Fortin <[EMAIL PROTECTED]> [2008-03-22 22:30]: > The more implementations can pass each other's testsuite the > better interoperability we'll have achieved. (Assuming, of course, that the test suite covers enough edge and corner cases.) Regards, -- Aristo

Re: [ANN] Babelmark

* Yuri Takhteyev <[EMAIL PROTECTED]> [2008-03-22 19:00]: > (BTW, where does one get Markdown.pl 1.0.2 beta? Markdown > website says that the last version is 1.0.1, of 2004.) http://daringfireball.net/projects/downloads/Markdown_1.0.2b8.tbz Regards, -- Aristotle Pagalt

Re: forking Markdown.pl?

the races. That seems like a perfectly suitable model to handle Markdown.pl. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: on the philosophical aspects of a specification

down. What’s the point? We already have one; John Gruber wrote it. Interoperability problems crop up in the edge cases, not the unproblematic stuff. That is what’s important to specify. * Waylan Limberg <[EMAIL PROTECTED]> [2008-03-06 17:00]: > Aristotle Pagaltzis wrote: > > a human r

Re: on the philosophical aspects of a specification

it translate to this: hello dear boy Really. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: on the philosophical aspects of a specification

a human would have trouble figuring out what structure some piece of text is supposed to signify, the computer can be forgiven for likewise failing to infer a useful meaning. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: on the philosophical aspects of a specification

the user continue? Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: spaces and newlines before list markers (was: evolving the spec)

* Yuri Takhteyev <[EMAIL PROTECTED]> [2008-03-03 02:20]: > What about setting "value" on each "li" instead? Equally deprecated. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Di

Re: spaces and newlines before list markers (was: evolving the spec)

case Markdown should do what is sensible, validation be damned. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss

Re: evolving the spec (was: forking Markdown.pl?)

; will already be a > big step forward. Not very, honestly. If the group fails to produce a grammar specification, it would help more to try and make a really big test suite than it would to write more English. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___

Re: evolving the spec (was: forking Markdown.pl?)

and backward compatibility should be abandoned so that we can have the freedom to reduce the flexibility of the syntax. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.n

Re: forking Markdown.pl?

there is no fork. Therefore: > I'm not volunteering (I'd be horrible)... just seeing if it's > time to have that discussion. If you’re not volunteering and no one else does, then “having that discussion” is pretty pointless. Regards, -- Aristotl

Re: Syntax for extensions

tags something like so:  and then use script to replace any `` URIs in the output that have the `replace:` scheme with whatever post-determined URI is appropriate. You don’t need to meddle with Markdown at all. Regards, -- Aristotle Pagaltzis // &

Re: Markdown MIME type?

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/> _

Re: Markdown MIME type?

tools.ietf.org/html/rfc2046 Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss