Re: [ANN] Babelmark
On 24 Mar 2008, at 03:11, Michel Fortin wrote: Le 2008-03-22 à 17:27, Michel Fortin a écrit : 2-tier list indented by three spaces: http://michelf.com/projects/babelmark/?markdown=*+what%27s+up%3F% 0D%0A+++*+ok Now, on this one, I must say I have mixed feelings, since python-markdown is the only implementation that follows Markdown Syntax and treats the item indented by three spaces as being at the same level. Makes me feel like a naive fool for following the spec. :) Well, you've been following the official spec; no one should call you a fool for that. But it certainly doesn't give much leverage to the idea of keeping the spec as it is. It should be mentioned that, in addition to Python Markdown, both markdown.lua and Pandoc seem to follow the spec regarding list indentation. I've transplanted Babelmark, and got all the implementations running online. I've also added support for Discount (David Parson's C markdown implementation announced recently). http://babelmark.bobtfish.net/?markdown=*+what%27s+up%3F%0D%0A+++* +oknormalize=on Cheers Tom ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
Agreed. Assuming that it's minimal effort to leave both in, I think it's better to leave as many options in babelmark as possible. When I add a new feature or fix something in MultiMarkdown, it may break something else, or it may work differently in my implementation than in Tomas'. By having these different flavors in one place, it will make it much easier to keep small unintentional drifts from occurring between dialects. Ideally, the only differences would occur as related to syntax features that are implemented in one dialect, and not in another. Another benefit is the ability to merge similar features that are implemented differently. For example, when Michel added footnote support to PHP Markdown Extra that was almost the same as the approach I had used in MultiMarkdown, it was easy for me to change the XHTML syntax so that they were compatible (though it appears they have drifted apart again...) F- On Mar 23, 2008, at 8:13 AM, Tomas Doran wrote: Yes, please also keep Text::MultiMarkdown. This is actually *much more* different to fletcher's MultiMarkdown than Text::Markdown is to Markdown.pl - as with my refactoring, MultiMarkdown is able to just overload / hook into Text::Markdown (as I've created the relevant hook points), as opposed to being a copy paste of original markdown with bits stuck on the side.. (No offense meant here - I'm only able to do this as I'm *also* maintaining a fork of Markdown). Again, I'm aiming form *zero difference* between Text::MultiMarkdown and 'official' MultiMarkdown, except for bugs that I've fixed (so we shouldn't *expect* difference, and if it's found, and I don't have an explicit test in my distribution to cover it - it's a bug in my code and I *will fix it*).. My code does pass all of Fletcher's test suite, so I'm sure it's pretty similar. ;) As previously noted, s/MultiMarkdown/Markdown/g; s/Fletcher/John/g; in the paragraph above is also be true. Cheers Tom -- Fletcher T. Penney [EMAIL PROTECTED] On two occasions I have been asked [by members of Parliament], 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question. - Charles Babbage smime.p7s Description: S/MIME cryptographic signature ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
One problem with babelmark - the CSS is such that a long line of output (or input) forces the body off the left side of the page. For an example, try the following text in the babelmark text source: Test footnote.[^1][]. [^1]: This is a footnote. F- -- Fletcher T. Penney [EMAIL PROTECTED] Failure is the condiment that gives success its flavor. - Truman Capote smime.p7s Description: S/MIME cryptographic signature ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
On Sun, Mar 23, 2008 at 5:44 AM, Fletcher T. Penney [EMAIL PROTECTED] wrote: One problem with babelmark - the CSS is such that a long line of output (or input) forces the body off the left side of the page. For an example, try the following text in the babelmark text source: Test footnote.[^1][]. [^1]: This is a footnote. or this: http://michelf.com/projects/babelmark/?markdown=aa ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
Unfortunatly, my web host doesn't do Ruby, nor Java, C# or Lua, so the online version is missing a couple of interesting implementations. If your host allows you to ssh and has make, then building Lua is very simple: mkdir ~/lua # or some other directory wget http://sputnik.freewisdom.org/files/easy-lua-install-2007-01-18 bash easy-lua-install-2007-01-18 --without-readline --prefix=/home/yuri/lua/ cd share/lua/5.1/ wget www.frykholm.se/files/markdown.lua ~/lua/bin/lua This will get you the interactive prompt: Lua 5.1.2 Copyright (C) 1994-2007 Lua.org, PUC-Rio requiremarkdown =markdown(oh _hai_) poh emhai/em/p Locally on my computer Babelmark also do BlueCloth, Maruku, MarkdownJ, markdown.lua, and Pandoc. I'm very sorry if your Markdown implementation can't be part of Babelmark online, but if anyone has a better host to offer for Babelmark, ideally with support for all of these, I'd gladly send him the scripts. I can try and see how far I get on webfaction. Can you send me the scripts? - yuri -- http://sputnik.freewisdom.org/ ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
* Tomas Doran [EMAIL PROTECTED] [2008-03-23 13:10]: I've got [Devel::Cover] to measure coverage, and it (on [my trunk], which is close to 1.0.17) says that my coverage is almost perfect: Filestmt bran condsub time total -- -- -- -- -- -- blib/lib/Text/Markdown.pm 99.8 94.2 72.0 100.0 100.0 87.0 96.9 Which is *just wrong* - as I know there are piles of corner cases that my tests don't adequately cover. :( Probably a lesson to point out that automated coverage analysis isn't too useful in some cases... [Devel::Cover]: http://search.cpan.org/~pjcj/Devel-Cover-0.63/lib/Devel/Cover.pm [my trunk]: http://svn.kulp.ch/cpan/text_multimarkdown/trunk/ Yes, well. If you write one test case that causes the code to perform a particular pattern match, then the match expression is considered covered… even if uses a 500-line regex that parses an entire file format. This problem basically occurs whenever a separate language is embedded into the main code: SQL queries, XPath 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/ ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
Re: [ANN] Babelmark
Le 2008-03-22 à 17:27, Michel Fortin a écrit : 2-tier list indented by three spaces: http://michelf.com/projects/babelmark/?markdown=*+what%27s+up%3F%0D%0A+++*+ok Now, on this one, I must say I have mixed feelings, since python-markdown is the only implementation that follows Markdown Syntax and treats the item indented by three spaces as being at the same level. Makes me feel like a naive fool for following the spec. :) Well, you've been following the official spec; no one should call you a fool for that. But it certainly doesn't give much leverage to the idea of keeping the spec as it is. It should be mentioned that, in addition to Python Markdown, both markdown.lua and Pandoc seem to follow the spec regarding list indentation. Michel Fortin [EMAIL PROTECTED] http://michelf.com/ ___ Markdown-Discuss mailing list Markdown-Discuss@six.pairlist.net http://six.pairlist.net/mailman/listinfo/markdown-discuss
