Bug#466330: Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?

2010-02-21 Thread Axel Beckert
On Sun, Feb 21, 2010 at 05:55:43PM +1100, Ben Finney wrote: > On 19-Feb-2010, Axel Beckert wrote: > > On Fri, Feb 19, 2010 at 09:18:28AM +1100, Ben Finney wrote: > > > One possible reason is that there appears to be no specification > > > on the parsing of Markdown format, other than ???what John >

Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?

2010-02-20 Thread Ben Finney
On 19-Feb-2010, Axel Beckert wrote: > On Fri, Feb 19, 2010 at 09:18:28AM +1100, Ben Finney wrote: > > One possible reason is that there appears to be no specification > > on the parsing of Markdown format, other than ???what John > > Gruber's /usr/bin/markdown does???. > > Sure there is: > > http

Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?

2010-02-19 Thread Axel Beckert
On Fri, Feb 19, 2010 at 09:18:28AM +1100, Ben Finney wrote: > > > Reading their copyright files, it seems like libtext-markdown-perl > > > is a fork of John Gruber's markdown, which seems like not much > > > maintained upstream (last release in 2004). > > > > Is there a reason why markdown should

Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?

2010-02-18 Thread Ben Finney
On 08-Feb-2010, Bernd Zeimetz wrote: > Damyan Ivanov wrote: > > Reading their copyright files, it seems like libtext-markdown-perl > > is a fork of John Gruber's markdown, which seems like not much > > maintained upstream (last release in 2004). > > Is there a reason why markdown should be kept in

Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?

2010-02-08 Thread Bernd Zeimetz
Damyan Ivanov wrote: > -=| Bernd Zeimetz, Mon, Feb 08, 2010 at 01:09:04PM +0100 |=- >> as we have three packages now which provide /usr/bin/markdown it >> could make >> sense to use alternatives here, although I didn't check if the three >> implementations are compatible enough. At least this woul