Re: [Python-markdown-discuss] Python-Markdown 2.0 Release Candidate

[Ron G. <ro...@fl...>]

On Mar 23, 2009, at 3:27 PM, Yuri Takhteyev wrote:

>>> 1.  The wikilink behavior has changed in a non-backwards- 
>>> compatible way.
>>>  Before, [[WikiLink]] and [[wiki link]] were equivalent.  Now they  
>>> are not.
>>>  Personally, I preferred the old way.
>
> The new way is closer to what Wikipedia does, which is a big plus

Perhaps, but if that's the goal then actually doing it the way  
Wikipedia does it would be even better than just being "way closer."   
Wikipedia contracts multiple spaces down to one, but markdown.py  
doesn't.  Wikipedia allows wikilinks that start with an underscore;  
markdown.py doesn't.

In general, I think the wikilink canonicalization algorithm ought to  
have the property that two wikilinks that look like the "ought" to be  
the same actually are the same.  [[WikiLink]] and [[wiki link]] are  
perhaps arguable, but [[wiki link]] and [[wiki  link]] aren't IMO.

> I think. However, perhaps it would make sense to make this  
> configurable.

That would be fine with me.  Maybe this could even subsume base_url  
and end_url.

>
>> Well, the reason is that this (PHP) is an already existing and highly
>> distributed implementation. The idea is that one should be able to
>> pass the same source documents through any implementation and get  
>> back
>> the same result. So, I went with an already existing implementation.
>
> I agree with this completely. I think it would be great to have a set
> of extensions that get us as close as possible to PHP Markdown Extra.

That's a fine goal, but what's wrong with being a superset of PHP MD  
Extra?

rg