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
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
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
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
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
* 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
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
