Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?
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 > > > Gruber's /usr/bin/markdown does???. > > > > Sure there is: > > > > http://daringfireball.net/projects/markdown/syntax > > Sorry, I didn't mean ???a set of examples and prose explanation???. I > means a specification of the language, i.e. a formal grammar. I see. Sorry for the misunderstanding. > From what I gather, Markdown lacks one > http://www.cforcoding.com/2010/01/markdown-headings-grief-and-unknown.html>. Thanks for that link. Interestingly in the single comment to that blog-post, there is a hint to a PEG grammar for markdown and the parser based on it: http://github.com/jgm/peg-markdown/blob/master/markdown_parser.leg Could that help? It's not by Gruber, but IMHO it's a starting point. Regards, Axel -- Axel Beckert - a...@deuxchevaux.org, a...@noone.org - http://noone.org/abe/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?
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://daringfireball.net/projects/markdown/syntax Sorry, I didn't mean “a set of examples and prose explanation”. I means a specification of the language, i.e. a formal grammar. From what I gather, Markdown lacks one http://www.cforcoding.com/2010/01/markdown-headings-grief-and-unknown.html>. -- \“There are no significant bugs in our released software that | `\ any significant number of users want fixed.” —Bill Gates, | _o__) 1995-10-23 | Ben Finney signature.asc Description: Digital signature
Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?
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 be kept in the archive then? > > 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://daringfireball.net/projects/markdown/syntax Regards, Axel -- Axel Beckert - a...@deuxchevaux.org, a...@noone.org - http://noone.org/abe/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?
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 the archive then? 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”. When two non-Gruber implementations differ in their behaviour, how do we tell what's right? -- \ “My classmates would copulate with anything that moved, but I | `\ never saw any reason to limit myself.” —Emo Philips | _o__) | Ben Finney signature.asc Description: Digital signature
Bug#567378: [Python-modules-team] Bug#567378: Using alternatives for /usr/bin/markdown?
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 would be a better >> solution >> than what the perl module does now - conflicting against the markdown >> package. >> Probably people want to be able to use both versions? >> >> Any opinions on that? > > Nt really an oppinion, rather just some data: > > The contents of 'markdown' and 'libtext-markdown-perl' look very > similar: > [...] > > 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 the archive then? Migrating to to libtext-markdown-perl sounds like the best idea. I'm CCing the RFA bug for markdown to let people know about that. We could make markdown a package which depends on libtext-markdown-perl | python-markdown to migrate to an uptodate version and handle /usr/bin/markdown by alternatives. The other option would be to drop /usr/bin/markdown from the python package, I don't have a proper opinion on that the best thing is yet. -- Bernd ZeimetzDebian GNU/Linux Developer http://bzed.dehttp://www.debian.org GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
