Test case

ADDR

, so I have to "numb" that behavior first. PmWiki
uses '*' or '#' at the beginning of the line to start the
lists--repeating (e.g. ** item) for indented lists.

Ben Wilson

[1]: http://www.pmwiki.org

On 5/2/06, A. Pagaltzis  wrote:
> * Anton J Aylward  [2006-05-02 19:35]:
> > Is there any way to do macros in Markdown? Or do you have any
> > other suggestions?
>
> You can hack this on top of Markdown as it is, as long as you
> don't need to nest macros inside links. Then you can write this:
>
> >     You are  %%USERNAME%%
> >     Logged in at %%LOGINTIME%%
> >
> >     Your browser is %%HTTP{"User-Agent"}%%
> >     You are accessing from %%REMOTE_ADDR%%:%%REMOTE_PORT%%
> >
> >     The time is now  %%TIME(timezone=%%USER{%%TZ%%}%%, fmt="HH:MM:SS")%%
>
> like this:
>
>     You are [USERNAME](macro:)
>     Logged in at [LOGINTIME](macro:)
>
>     Your browser is [HTTP{"User-Agent"}](macro:)
>     You are accessing from [REMOTE_ADDR](macro:):[REMOTE_PORT](macro:)
>
>     The time is now [TIME(timezone=USER{TZ},fmt="HH:MM:SS")](macro:)
>
> Markdown makes this out of it:
>
>     You are USERNAME
>     Logged in at LOGINTIME
>
>     Your browser is HTTP{"User-Agent"}
>     You are accessing from REMOTEADDR:REMOTEPORT
>
>     The time is now TIME(timezone=USER{TZ},fmt="HH:MM:SS")
>
> Then you can you go in there and replace `` tags with a `href`
> of `macro:` by the result of evaluating their textual content.
>
> Hmm, you'd have to be careful about your underscores and
> asterisks; not to mention there's a bug there in Markdown?
>
> Regards,
> --
> Aristotle Pagaltzis // 
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

--
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From waylan at gmail.com  Tue May  2 15:26:31 2006
From: waylan at gmail.com (Waylan Limberg)
Date: Tue May  2 15:26:35 2006
Subject: Bug: invalid nesting of inline markup across link labels
In-Reply-To: <20060502191503.GY2690@klangraum>
References: <20060502191503.GY2690@klangraum>
Message-ID: 

For comparison, Python-Markdown[1] results in this:

     foo*bar baz*quux

[1]: http://www.freewisdom.org/projects/python-markdown/

On 5/2/06, A. Pagaltzis  wrote:
> Hi John,
>
> there's a bug in Markdown.pl:
>
>     [foo*bar](#) [baz*quux](#)
>
> This expands to the following:
>
>     foobar bazquux
>
> Those `*` should either be disregarded or the tags should nest
> correctly:
>
> 1.    foo*bar baz*quux
> 2.    foobar bazquux
>
> Of course, the second option is a lot more complex to implement
> and at the same time unlikely to be what the user actually meant.
>
> Regards,
> --
> Aristotle Pagaltzis // 
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

--
----
Waylan Limberg
waylan@gmail.com
From gruber at fedora.net  Wed May  3 20:11:28 2006
From: gruber at fedora.net (John Gruber)
Date: Wed May  3 20:11:31 2006
Subject: Bug: invalid nesting of inline markup across link labels
In-Reply-To: <20060502191503.GY2690@klangraum>
Message-ID: 

A. Pagaltzis  wrote on 5/2/06 at 9:15 PM:

> there?s a bug in Markdown.pl:
> 
>     [foo*bar](#) [baz*quux](#)
> 
> This expands to the following:
> 
>     foobar bazquux
> 
> Those `*` should either be disregarded or the tags should nest
> correctly:
> 
> 1.    foo*bar baz*quux
> 2.    foobar bazquux
> 
> Of course, the second option is a lot more complex to implement
> and at the same time unlikely to be what the user actually meant.

Good catch.

I think the first solution is better.

-J.G.
From gruber at fedora.net  Wed May  3 20:16:27 2006
From: gruber at fedora.net (John Gruber)
Date: Wed May  3 20:16:30 2006
Subject: SmartyPants 1.6 multiply remarks
In-Reply-To: <34885CDB-9BBC-4530-9AD9-8BC683C37575@michelf.com>
Message-ID: 

Michel Fortin  wrote on 2/13/06 at 6:13 PM:

> > 4 x 2  ->  4 × 2  in EducateExtras, too.
> 
> Which is a great idea. But I'm not sure about how it works currently.  
> All goes well in these two cases:
> 
>      800x600
>      5 x 5
> 
> But maybe it's not a so good idea that it also replace the x with a  
> multiply for this:
> 
>      2006 x11
>      120x 31y 6z
> 
> Three dimensions doesn't work either (only the first x is changed):
> 
>      4 x 2 x 3
> 
> And finally, maybe `\x` should be added to the list of character  
> escapes.

These are all great catches. I'll fix them for the next beta. Now
that I can work on this stuff during the day, I'll try to release
a new SmartyPants and Markdown soon.

-J.G.
From walt.dickinson at gmail.com  Thu May  4 00:49:11 2006
From: walt.dickinson at gmail.com (Walt Dickinson)
Date: Thu May  4 00:49:56 2006
Subject: SmartyPants 1.6 multiply remarks
In-Reply-To: 
References: 
Message-ID: 

On May 3, 2006, at 5:16 PM, John Gruber wrote:

> These are all great catches. I'll fix them for the next beta. Now
> that I can work on this stuff during the day, I'll try to release
> a new SmartyPants and Markdown soon.

News like this makes me even happier I just became a Daring Fireball  
subscriber. :)

Walt

From lists at mostrom.pp.se  Sat May  6 08:56:34 2006
From: lists at mostrom.pp.se (=?UTF-8?Q?Jan_Erik_Mostr=C3=B6?= =?UTF-8?Q?m?=)
Date: Sat May  6 08:56:37 2006
Subject: definition lists
Message-ID: 

I haven't followed the discussion for a while but I seem to remember that
there was a discussion of how definition list should look like.

Has there been any decision of what syntax to use? (I don't actually need a
script for doing the markdown => HTML conversion right now, but I would like
to be able to write definitions lists)

                        jem
-- 
Jan Erik Mostr?m, www.mostrom.pp.se
From me at aaronsw.com  Sat May  6 08:58:13 2006
From: me at aaronsw.com (Aaron Swartz)
Date: Sat May  6 08:58:16 2006
Subject: definition lists
In-Reply-To: 
References: 
Message-ID: 

http://www.michelf.com/projects/php-markdown/extra/#def-list
From elfin at elfden.co.uk  Sat May  6 17:02:41 2006
From: elfin at elfden.co.uk (Rich Pedley)
Date: Sat May  6 17:11:33 2006
Subject: php markdown toolbar
In-Reply-To: <4835FB67-DCD9-493D-9C39-65A1AA0F6ED1@relativesanity.com>
References: <442D1DC9.3060307@elfden.co.uk> <444F4CB4.3020302@elfden.co.uk>
	<4835FB67-DCD9-493D-9C39-65A1AA0F6ED1@relativesanity.com>
Message-ID: <445D0EF1.4040200@elfden.co.uk>

On 26/04/2006 16:05, Jonathan Barrett wrote:

http://www.elfden.co.uk/wip/markdown/index.php

has been updated, to include a 'preview', and to emphasis that I even 
removed the submit button...

php is required specifically for the accesskeys - and *possibly* the 
preview though I _think_ it could be transposed to other scripting 
languages.

If all goes well I'll release the scripts as a downloadable package by 
the end of the month.

Rich

From aja at si.on.ca  Sat May  6 20:49:36 2006
From: aja at si.on.ca (Anton J Aylward)
Date: Sat May  6 20:49:40 2006
Subject: Macros?
In-Reply-To: <20060502190740.GX2690@klangraum>
References: <4457976C.3040706@si.on.ca> <20060502190740.GX2690@klangraum>
Message-ID: <445D4420.30901@si.on.ca>

Either I don't understand your response or you didn't understand my
question.  Certainly I can't see how your answer relates to the question I
thought I was asking.

Let me try again.

If I'm user Ruby's RDoc (or Perls TT, but different syntax)
I can write a _template_ such as:

   You are  <%= session.username %>
   Logged in at <%= session.logintime %>

   Your browser is <%= cgi.['HTTP_USER_AGENT'] %>
   You are accessing from <%= cgi.['REMOTE_ADDR'] . cgi.['REMOTE_PORT'] %>

   The time is now  <%= (time.now +
                         session.user.timezone).strftime("%H:%M:%S") %>

BUT !!
That is a template.

I want to be able to put the macros in the data of a blog or wiki so that
when the template reads..

        .....

       ......

                <%= render(page.body) %>

         ......

any of the macros that the user has inserted into the blog/wiki page will
get expanded.  See my example of the stuff between '%%' in the original
message.

Which means that macro expansion has to be done in the 'render'.

Now it may happen that one of the macros invokes a function in the
blog/wiki (perhaps a plugin) that, rather than generate HTML, generates
markup (down/cloth/whatever) code.

I can see a way to do this with the render function being a two-step
   1. Expand macros
   2. process the result using Markdown

That is fine if the macros are simple and only do things like text
insertion.  If they are more comprehensive then they may need to do
additional logic.

Consider a %%TOC%% or %%TOC{params..}%% macro. that builds a nested list of
 markup references to the actual heading.
Take a look at
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/134005
and tell me what YOU think is wrong with it.
I can think of a few things.

   1. It doesn't deal with  and other 'verbatim' sections
      correctly
   2. It doesn't deal with the situations where HTML headings are in the
      body.
   3. It doesn't deal with situations where other macros might generate
      headings

Consider a full text search in a wiki page:

     %%FULLTEXTSEARCH{
                       searchtext="[jJ]ust\w+[oO]ne\w+[tT]ing"
                       regex="yes"
                       fmt="* [result.spacedout](result.url)"
                     }%%

Oh, and make that able to do nested searches as well

OK, now consider a case where the parameter to a macro has to be rendered
first.

Realistically, I can only see macros working with something a bit more ...
controlled?   What spring to mind is the render-chain mechanism used in the
 perl-based wiki "CGI::Kwiki".  The plugins that do 'macro' work and the
rest of the basic markup rendering are in the form of an ordered (read
prioritized) list.   Of course the TOC will be near the end of the chain.

(This strikes me as a nice idea since conditionally included macros that
need javascript support can flag that the javascrip needs to be loaded,
rather than have a fixed header that includes all the javascrip that could
possibly be required!)

So how to use Markdown (or textile or redcloth or whatever) in this
context?  Possibly repeated calls to Markdown with different restrictions.
 But that seems a hell of an overhead.

I don't know if this better expresses thoughts and examples better.

A. Pagaltzis wrote:
> * Anton J Aylward  [2006-05-02 19:35]:
> 
>>Is there any way to do macros in Markdown? Or do you have any
>>other suggestions?
> 
> You can hack this on top of Markdown as it is, as long as you
> don?t need to nest macros inside links. Then you can write this:
> 
>>    You are  %%USERNAME%%
>>    Logged in at %%LOGINTIME%%
>>
>>    Your browser is %%HTTP{"User-Agent"}%%
>>    You are accessing from %%REMOTE_ADDR%%:%%REMOTE_PORT%%
>>
>>    The time is now  %%TIME(timezone=%%USER{%%TZ%%}%%, fmt="HH:MM:SS")%%
> 
> 
> like this:
> 
>     You are [USERNAME](macro:)
>     Logged in at [LOGINTIME](macro:)
> 
>     Your browser is [HTTP{"User-Agent"}](macro:)
>     You are accessing from [REMOTE_ADDR](macro:):[REMOTE_PORT](macro:)
> 
>     The time is now [TIME(timezone=USER{TZ},fmt="HH:MM:SS")](macro:)
> 
> Markdown makes this out of it:
> 
>     You are USERNAME
>     Logged in at LOGINTIME
> 
>     Your browser is HTTP{?User-Agent?}
>     You are accessing from REMOTEADDR:REMOTEPORT
> 
>     The time is now TIME(timezone=USER{TZ},fmt=?HH:MM:SS?)
> 
> Then you can you go in there and replace `` tags with a `href`
> of `macro:` by the result of evaluating their textual content.
> 
> Hmm, you?d have to be careful about your underscores and
> asterisks; not to mention there?s a bug there in Markdown?
> 
> Regards,
From dausha at gmail.com  Sun May  7 01:00:26 2006
From: dausha at gmail.com (Ben Wilson)
Date: Sun May  7 01:00:28 2006
Subject: Announcement: Markdown-0.1 for PmWiki
Message-ID: 

Okay, it's pretty alpha, but it is a start. I have published
"Markdown," which is a recipe that helps integrate Markdown syntax
with PmWiki.[1] My goal is that, when finished, there will be
something pretty close to a PHP-based wiki that relies on Markdown
syntax.

I have been involved with PmWiki for a couple years now. It has
matured into a very potent, customizeable wiki engine. PmWiki provides
markup for integrating other pages into a given page, listing pages
based on criteria, and the like--all via fairly elegant wiki markup.

The problem for me was that I use a custom tool to edit my wiki pages.
Specifically, I took notes for law school using a python-based tool
that let me edit using vim (my preferred editor) and publish to the
web. This provides archival and version control. The point is, there
are some pages I have only ever seen using the markup. PmWiki's markup
leaves a few things to be desired. For example, lists are (until
recently) left-flush with multiple markers (i.e. '*' or '#') to
indicate nesting. (A recent "undocumented feature" of PmWiki allows
nested lists provided the are aligned with the first character of the
parent list item.) Also, I prefer the '===' and '---' based headings,
as opposed to PmWiki's '!!' heading markup.

I had earlier mixed the Markdown syntax haphazardly (as opposed to now
which is only hazardly) with PmWiki code, notably the heading syntax
(not the Atx format). That caused problems with the
PageTableOfContents recipe. I generally kept some of PmWiki's markup
and added Markdown's for backward compatibility as well as
compatibility with PmWiki's rich customization library.[2]

It renders blockquotes work nearly as expected (each row prefixed with
'> '), but this recipe does not nest the block quotes (yet). I only
worked on this today after a few earlier abortive attempts, so if
things act a bit screwy, let me know.

[1]: http://pmwiki.org/wiki/Cookbook/Markdown
[2]: http://pmwiki.org/wiki/Cookbook
--
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From michel.fortin at michelf.com  Sun May  7 19:47:22 2006
From: michel.fortin at michelf.com (Michel Fortin)
Date: Sun May  7 19:47:26 2006
Subject: Macros?
In-Reply-To: <445D4420.30901@si.on.ca>
References: <4457976C.3040706@si.on.ca> <20060502190740.GX2690@klangraum>
	<445D4420.30901@si.on.ca>
Message-ID: 

Le 6 mai 2006 ? 20:49, Anton J Aylward a ?crit :

> Realistically, I can only see macros working with something a bit  
> more ...
> controlled?   What spring to mind is the render-chain mechanism  
> used in the
>  perl-based wiki "CGI::Kwiki".  The plugins that do 'macro' work  
> and the
> rest of the basic markup rendering are in the form of an ordered (read
> prioritized) list.   Of course the TOC will be near the end of the  
> chain.

I'm not sure I understand everything, but it seems that your problem  
is that you have two kinds of macros (those that require HTML- 
converted text and those that generate Markdown markup). Maybe you  
just need a way to tell them apart so you can run each macro  
processor either before or after Markdown.

Does that make any sense?

Michel Fortin
michel.fortin@michelf.com
http://www.michelf.com/

From wolf2k5 at gmail.com  Mon May  8 03:32:53 2006
From: wolf2k5 at gmail.com (wolf2k5)
Date: Mon May  8 03:32:55 2006
Subject: Announcement: Markdown-0.1 for PmWiki
In-Reply-To: 
References: 
Message-ID: <8d8ba2bb0605080032m71e2131ex23ff42c85fd96be5@mail.gmail.com>

On 5/7/06, Ben Wilson  wrote:
> Okay, it's pretty alpha, but it is a start. I have published
> "Markdown," which is a recipe that helps integrate Markdown syntax
> with PmWiki.[1] My goal is that, when finished, there will be
> something pretty close to a PHP-based wiki that relies on Markdown
> syntax.

This is great news, I've been waiting for this since a long time.

I'll give it a try asap.

Thanks.
From dausha at gmail.com  Mon May  8 11:35:01 2006
From: dausha at gmail.com (Ben Wilson)
Date: Mon May  8 11:35:36 2006
Subject: Announcement: Markdown-0.1 for PmWiki
In-Reply-To: <8d8ba2bb0605080032m71e2131ex23ff42c85fd96be5@mail.gmail.com>
References: 
	<8d8ba2bb0605080032m71e2131ex23ff42c85fd96be5@mail.gmail.com>
Message-ID: 

I have encountered a small bug that I will try to ferret out in the
near future (probably after May 15). I used PHP Markdown as the core
for most of the Markdown behavior. The list function will sometimes
run my web server beyond its 30 second processing limit. Thus far, I
have only encountered the problem when saving a page after editing.

Specifically, I had a page with a few paragraphs of text and a few
(unordered) lists. That page would hang. Conversely, I was able to
edit and re-post my course notes in Statutory Construction without
problem. The former was less than one page printed, the latter well
over 30 pages--mostly lists of various sorts.

Before I can resolve this, I need to be able to reproduce the bug.
However, I have not been able to. If anybody tries this and runs in to
a similar problem, please inform me (dausha et gmail.com) so I can
build a test.

Regards,
Ben Wilson

On 5/8/06, wolf2k5  wrote:
> On 5/7/06, Ben Wilson  wrote:
> > Okay, it's pretty alpha, but it is a start. I have published
> > "Markdown," which is a recipe that helps integrate Markdown syntax
> > with PmWiki.[1] My goal is that, when finished, there will be
> > something pretty close to a PHP-based wiki that relies on Markdown
> > syntax.
>
> This is great news, I've been waiting for this since a long time.
>
> I'll give it a try asap.
>
> Thanks.
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

--
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From elfin at elfden.co.uk  Tue May  9 07:19:45 2006
From: elfin at elfden.co.uk (Rich Pedley)
Date: Tue May  9 07:21:04 2006
Subject: php markdown toolbar
In-Reply-To: <445D0EF1.4040200@elfden.co.uk>
References: <442D1DC9.3060307@elfden.co.uk>
	<444F4CB4.3020302@elfden.co.uk>	<4835FB67-DCD9-493D-9C39-65A1AA0F6ED1@relativesanity.com>
	<445D0EF1.4040200@elfden.co.uk>
Message-ID: <44607AD1.4070400@elfden.co.uk>

The toolbar has now been released:

http://www.quirm.net/category.php?id=20

the old work in progress demo has now been deleted.

Rich

From robdumas at gmail.com  Tue May  9 17:20:53 2006
From: robdumas at gmail.com (Robert Dumas)
Date: Tue May  9 17:21:00 2006
Subject: php markdown toolbar
In-Reply-To: <44607AD1.4070400@elfden.co.uk>
References: <442D1DC9.3060307@elfden.co.uk>
	<444F4CB4.3020302@elfden.co.uk>	<4835FB67-DCD9-493D-9C39-65A1AA0F6ED1@relativesanity.com>
	<445D0EF1.4040200@elfden.co.uk> <44607AD1.4070400@elfden.co.uk>
Message-ID: <34A3E981-0668-46E2-A4E8-CBBE49D11472@gmail.com>

Does the PHP Markdown work with bulletin board systems, like PHPBB or  
vBulletin? is there a version of Markdown for these systems?
On May 9, 2006, at 7:19 AM, Rich Pedley wrote:

> The toolbar has now been released:
>
> http://www.quirm.net/category.php?id=20
>
> the old work in progress demo has now been deleted.
>
> Rich
>
>
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss

--------------------------------------------------------
Robert Dumas
robdumas@gmail.com

From elfin at elfden.co.uk  Wed May 10 04:56:13 2006
From: elfin at elfden.co.uk (Rich Pedley)
Date: Wed May 10 05:06:24 2006
Subject: php markdown toolbar
In-Reply-To: <34A3E981-0668-46E2-A4E8-CBBE49D11472@gmail.com>
References: <442D1DC9.3060307@elfden.co.uk>
	<444F4CB4.3020302@elfden.co.uk>	<4835FB67-DCD9-493D-9C39-65A1AA0F6ED1@relativesanity.com>
	<445D0EF1.4040200@elfden.co.uk> <44607AD1.4070400@elfden.co.uk>
	<34A3E981-0668-46E2-A4E8-CBBE49D11472@gmail.com>
Message-ID: <4461AAAD.4060604@elfden.co.uk>

On 09/05/2006 22:20, Robert Dumas wrote:
> Does the PHP Markdown work with bulletin board systems, like PHPBB or  
> vBulletin? is there a version of Markdown for these systems?

regarding:

>> http://www.quirm.net/category.php?id=20

ahh good point - something that I should add to the page.

The toolbar is user configurable so if you want it to add [b][/b] or 
 then that it is entirely possible.

I'll amend the instructions on the site.
Note to self: add instructions for accesskeys.

Rich

From dausha at gmail.com  Fri May 12 09:46:30 2006
From: dausha at gmail.com (Ben Wilson)
Date: Fri May 12 09:46:34 2006
Subject: Announcement: Markdown-0.1 for PmWiki
In-Reply-To: 
References: 
	<8d8ba2bb0605080032m71e2131ex23ff42c85fd96be5@mail.gmail.com>

Message-ID: 

Okay, I've started to hunt down the problem. I thought the problem was
with the bullets in the unordered lists. However, it seems to be the
use of the astericks in '**bolden**' markup in combination. I'm also
reapproaching how to manage the markup by having it work more closely
with PmWiki's inherent markup system. I hope to release the corrected
code next week.

Ben

On 5/8/06, Ben Wilson  wrote:
> I have encountered a small bug that I will try to ferret out in the
> near future (probably after May 15). I used PHP Markdown as the core
> for most of the Markdown behavior. The list function will sometimes
> run my web server beyond its 30 second processing limit. Thus far, I
> have only encountered the problem when saving a page after editing.
>
> Specifically, I had a page with a few paragraphs of text and a few
> (unordered) lists. That page would hang. Conversely, I was able to
> edit and re-post my course notes in Statutory Construction without
> problem. The former was less than one page printed, the latter well
> over 30 pages--mostly lists of various sorts.
>
> Before I can resolve this, I need to be able to reproduce the bug.
> However, I have not been able to. If anybody tries this and runs in to
> a similar problem, please inform me (dausha et gmail.com) so I can
> build a test.
>
> Regards,
> Ben Wilson
>
> On 5/8/06, wolf2k5  wrote:
> > On 5/7/06, Ben Wilson  wrote:
> > > Okay, it's pretty alpha, but it is a start. I have published
> > > "Markdown," which is a recipe that helps integrate Markdown syntax
> > > with PmWiki.[1] My goal is that, when finished, there will be
> > > something pretty close to a PHP-based wiki that relies on Markdown
> > > syntax.
> >
> > This is great news, I've been waiting for this since a long time.
> >
> > I'll give it a try asap.
> >
> > Thanks.
> > _______________________________________________
> > Markdown-Discuss mailing list
> > Markdown-Discuss@six.pairlist.net
> > http://six.pairlist.net/mailman/listinfo/markdown-discuss
> >
>
>
> --
> Ben Wilson
> " Mundus vult decipi, ergo decipiatur"
>

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From dausha at gmail.com  Fri May 12 18:53:26 2006
From: dausha at gmail.com (Ben Wilson)
Date: Fri May 12 18:53:29 2006
Subject: A Single Test File?
Message-ID: 

I was wondering if there is a single text file that contains all the
markup in a way that one can visually check to see if a markdown
script is succeeding. I know there's a Perl test suite, but I'm
looking for just one source file.

Thanks.

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From waylan at gmail.com  Sat May 13 19:32:51 2006
From: waylan at gmail.com (Waylan Limberg)
Date: Sat May 13 19:32:53 2006
Subject: A Single Test File?
In-Reply-To: 
References: 
Message-ID: 

The official syntax docs are available as source[1]. It may not test
everything, but there are many examples that will give you some basic
tests for every feature. It's a start.

[1]: http://daringfireball.net/projects/markdown/syntax.text

On 5/12/06, Ben Wilson  wrote:
> I was wondering if there is a single text file that contains all the
> markup in a way that one can visually check to see if a markdown
> script is succeeding. I know there's a Perl test suite, but I'm
> looking for just one source file.
>
> Thanks.
>
> --
> Ben Wilson
> " Mundus vult decipi, ergo decipiatur"
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

-- 
----
Waylan Limberg
waylan@gmail.com
From dausha at gmail.com  Sat May 13 21:05:42 2006
From: dausha at gmail.com (Ben Wilson)
Date: Sat May 13 21:05:44 2006
Subject: A Single Test File?
In-Reply-To: 
References: 

Message-ID: 

I had thought of using that. But, I would want to clean up the HTML
out of it first. I was just hoping somebody had a ready-to-go file.
:-) I suppose I'll be the one. ;-)

Ben

On 5/13/06, Waylan Limberg  wrote:
> The official syntax docs are available as source[1]. It may not test
> everything, but there are many examples that will give you some basic
> tests for every feature. It's a start.
>
> [1]: http://daringfireball.net/projects/markdown/syntax.text
>
> On 5/12/06, Ben Wilson  wrote:
> > I was wondering if there is a single text file that contains all the
> > markup in a way that one can visually check to see if a markdown
> > script is succeeding. I know there's a Perl test suite, but I'm
> > looking for just one source file.
> >
> > Thanks.
> >
> > --
> > Ben Wilson
> > " Mundus vult decipi, ergo decipiatur"
> > _______________________________________________
> > Markdown-Discuss mailing list
> > Markdown-Discuss@six.pairlist.net
> > http://six.pairlist.net/mailman/listinfo/markdown-discuss
> >
>
>
> --
> ----
> Waylan Limberg
> waylan@gmail.com
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From m.kalderon at ucl.ac.uk  Sat May 13 21:25:00 2006
From: m.kalderon at ucl.ac.uk (Mark Eli Kalderon)
Date: Sat May 13 21:25:12 2006
Subject: A Single Test File?
In-Reply-To: 
References: 

Message-ID: <738083B9-D027-46FC-9AF7-491CA915B1F3@ucl.ac.uk>

John Gruber has a test suite. Not a single file, but useful nontheless:

http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip

Best, Mark
On 14 May 2006, at 02:05, Ben Wilson wrote:

> I had thought of using that. But, I would want to clean up the HTML
> out of it first. I was just hoping somebody had a ready-to-go file.
> :-) I suppose I'll be the one. ;-)
>
> Ben
>
> On 5/13/06, Waylan Limberg  wrote:
>> The official syntax docs are available as source[1]. It may not test
>> everything, but there are many examples that will give you some basic
>> tests for every feature. It's a start.
>>
>> [1]: http://daringfireball.net/projects/markdown/syntax.text
>>
>> On 5/12/06, Ben Wilson  wrote:
>> > I was wondering if there is a single text file that contains all  
>> the
>> > markup in a way that one can visually check to see if a markdown
>> > script is succeeding. I know there's a Perl test suite, but I'm
>> > looking for just one source file.
>> >
>> > Thanks.
>> >
>> > --
>> > Ben Wilson
>> > " Mundus vult decipi, ergo decipiatur"
>> > _______________________________________________
>> > Markdown-Discuss mailing list
>> > Markdown-Discuss@six.pairlist.net
>> > http://six.pairlist.net/mailman/listinfo/markdown-discuss
>> >
>>
>>
>> --
>> ----
>> Waylan Limberg
>> waylan@gmail.com
>> _______________________________________________
>> Markdown-Discuss mailing list
>> Markdown-Discuss@six.pairlist.net
>> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>>
>
>
> -- 
> Ben Wilson
> " Mundus vult decipi, ergo decipiatur"
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss

From pagaltzis at gmx.de  Sat May 13 21:33:59 2006
From: pagaltzis at gmx.de (A. Pagaltzis)
Date: Sat May 13 21:33:43 2006
Subject: A Single Test File?
In-Reply-To: <738083B9-D027-46FC-9AF7-491CA915B1F3@ucl.ac.uk>
References: 

	<738083B9-D027-46FC-9AF7-491CA915B1F3@ucl.ac.uk>
Message-ID: <20060514013359.GS10370@klangraum>

* Mark Eli Kalderon  [2006-05-14 03:30]:
> John Gruber has a test suite. Not a single file, but useful
> nontheless:
> 
> http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip

His first mail said he knew about that and it wasn?t what he
wanted?

Regards,
-- 
Aristotle Pagaltzis // 
From dausha at gmail.com  Sat May 13 22:16:37 2006
From: dausha at gmail.com (Ben Wilson)
Date: Sat May 13 22:16:39 2006
Subject: A Single Test File?
In-Reply-To: <20060514013359.GS10370@klangraum>
References: 

	<738083B9-D027-46FC-9AF7-491CA915B1F3@ucl.ac.uk>
	<20060514013359.GS10370@klangraum>
Message-ID: 

True. I'm looking for a single file. However, I suppose the _smart_
thing for me to do would be to apply all those tests in one file with
a lot of "ipsum" tossed in.

If nobody chimes in with a test page, then I'll make one and post it
myself. :-) It will take a few days. Exam week at ye old law school.

Ben

On 5/13/06, A. Pagaltzis  wrote:
> * Mark Eli Kalderon  [2006-05-14 03:30]:
> > John Gruber has a test suite. Not a single file, but useful
> > nontheless:
> >
> > http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip
>
> His first mail said he knew about that and it wasn't what he
> wanted?
>
> Regards,
> --
> Aristotle Pagaltzis // 
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From dausha at gmail.com  Tue May 16 15:27:55 2006
From: dausha at gmail.com (Ben Wilson)
Date: Tue May 16 15:27:57 2006
Subject: A Single Test File?
In-Reply-To: 
References: 

	<738083B9-D027-46FC-9AF7-491CA915B1F3@ucl.ac.uk>
	<20060514013359.GS10370@klangraum>

Message-ID: 

Okay, here's the test file thus far.[1] I am using it to evaluate my
effort to convert a PmWiki site to recognize Markdown markup. I
basically cut & pasted from the Perl test suite, but I elaborated a
bit in the inline to put the emphasis markup to the test.

Now I can get Markup to perform. I was pleased to see how much it
already handled.

Ben

[1]: http://dausha.net/Markdown/TestFile?action=source

On 5/13/06, Ben Wilson  wrote:
> True. I'm looking for a single file. However, I suppose the _smart_
> thing for me to do would be to apply all those tests in one file with
> a lot of "ipsum" tossed in.
>
> If nobody chimes in with a test page, then I'll make one and post it
> myself. :-) It will take a few days. Exam week at ye old law school.
>
> Ben
>
> On 5/13/06, A. Pagaltzis  wrote:
> > * Mark Eli Kalderon  [2006-05-14 03:30]:
> > > John Gruber has a test suite. Not a single file, but useful
> > > nontheless:
> > >
> > > http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip
> >
> > His first mail said he knew about that and it wasn't what he
> > wanted?
> >
> > Regards,
> > --
> > Aristotle Pagaltzis // 
> > _______________________________________________
> > Markdown-Discuss mailing list
> > Markdown-Discuss@six.pairlist.net
> > http://six.pairlist.net/mailman/listinfo/markdown-discuss
> >
>
>
> --
> Ben Wilson
> " Mundus vult decipi, ergo decipiatur"
>

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From dausha at gmail.com  Wed May 17 13:06:18 2006
From: dausha at gmail.com (Ben Wilson)
Date: Wed May 17 13:06:20 2006
Subject: Announcement: Markdown-0.2 for PmWiki
Message-ID: 

Announcing a new release of the PmWiki Markdown extension.[1] This
release introduces an improvement in page rendering, examples of
syntax,[2] and better support for Atx (up from none). I have also
established a page to help keep interested parties informed of
changes, to include a discussion group.[3] There are still problems
with loose lists and blockquotes, but this is a 0.2 release. The
syntax page helps show the degree of integration between Markdown and
PmWiki.

Changes in v.0.2
----------------

   * Fixed problem with freezing page loads when
     combining bullet lists and asterisk-based emphasis
   * Added (limited) Atx heading support. You must
     trail the heading with at least one pound symbol.
   * Created syntax page.
   * Updated documentation.

[1]: http://pmwiki.org/wiki/Cookbook/Markdown
[2]: http://dausha.net/Markdown/Syntax
[3]: http://dausha.net/Markdown/

Ben Wilson
From drdrang at gmail.com  Thu May 18 01:28:41 2006
From: drdrang at gmail.com (Dr. Drang)
Date: Thu May 18 01:28:44 2006
Subject: Announcement: Markdown-0.2 for PmWiki
In-Reply-To: 
References: 
Message-ID: 

I see you're extending the setext headers to a third level by using a
row of tildes as the underline. I like the idea of another level of
headers, but I wonder if tilde is the right character. Because it's
about as "dark" as a row of hyphens, it does not provide the visual
clue that it's a lower level of header. What would you think of a row
of periods, leaving us with

Section
=======

Subsection
----------

Sub-subsection
..............

As with many things Markdown, the example above looks better with a
monospaced font than with a proportional font.

-- 
Dr. Drang
From dausha at gmail.com  Thu May 18 09:41:52 2006
From: dausha at gmail.com (Ben Wilson)
Date: Thu May 18 09:41:55 2006
Subject: Announcement: Markdown-0.2 for PmWiki
In-Reply-To: 
References: 

Message-ID: 

I extended the Setext headings in accordance with Grutatxt,[1] which
was one of the inspirational sources for Markdown.[2] The difference
in headings in Grutatxt and Setext is the third "tilda" heading. So, I
was trying to keep within the inspirational range of Markdown. I
typically only use two levels in a document myself, but do have
occasion to go the third level.

It is worth noting that adhering to Grutatxt allows me a justification
for retaining "#" as ordered list items, and the use of apostrophies
for emphasis. I see how Grutatxt influenced PmWiki markup. (Besides,
it also allows me to let PmWiki handle the lists, although not without
some difficulty as I presently do not have loose lists.)

I had also thought of periods. I agree that tildas would seem to be
"as dark" as hyphens. In use, though, they feel like they are closer
to the heading than hyphens, which seemed to mellow them out a bit.
Once the reader is familiar with the distinction between the three, I
opine the mind will fill in the blanks.

In reviewing my code in this matter, I saw that I could raise the
issue to one of local configuration. PmWiki is very localization
friendly by nature, and I'm trying to keep the code close to that
philosophy. So, if there is interest for this feature, I could make it
to where individual administrators could substitute tilda for period,
or add period--either intended as a substitute or as a fourth level of
heading. However, uniformity would suggest maintaining the status quo.

[1]: http://www.triptico.com/download/README_grutatxt
[2]: http://daringfireball.net/projects/markdown/syntax

On 5/18/06, Dr. Drang  wrote:
> I see you're extending the setext headers to a third level by using a
> row of tildes as the underline. I like the idea of another level of
> headers, but I wonder if tilde is the right character. Because it's
> about as "dark" as a row of hyphens, it does not provide the visual
> clue that it's a lower level of header. What would you think of a row
> of periods, leaving us with
>
> Section
> =======
>
> Subsection
> ----------
>
> Sub-subsection
> ..............
>
> As with many things Markdown, the example above looks better with a
> monospaced font than with a proportional font.
>
> --
> Dr. Drang
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss@six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>

-- 
Ben Wilson
" Mundus vult decipi, ergo decipiatur"
From michel.fortin at michelf.com  Fri May 19 14:35:36 2006
From: michel.fortin at michelf.com (Michel Fortin)
Date: Fri May 19 14:35:37 2006
Subject: [ANN] Object-Oriented PHP Markdown/SmartyPants
Message-ID: <3166C1B0-755C-4C31-8236-F3FE78535FC6@michelf.com>

This is something that I've been asked for many times. So today I'm  
announcing that all future versions of PHP Markdown and PHP  
SmartyPants will be encapsulated in a parser class. This has two  
major benefits:

1.  It should make extensions to the syntax easier to create and
     maintain as it is now possible to now extend the parser by
     replacing (overriding) only the relevant parts without modifying
     the existing PHP Markdown code.

2.  It allows the use of many parsers in the same PHP script.

Today I'm releasing the new object-oriented counterparts to PHP  
Markdown 1.0.1c, PHP Markdown Extra 1.0.1, and PHP SmartyPants  
1.5.1e, named respectively PHP Markdown 1.0.1oo, PHP Markdown Extra  
1.0.1oo, and PHP SmartyPants 1.5.1oo. Please consider them beta for now:

PHP Markdown 1.0.1oo

PHP Markdown Extra 1.0.1oo

PHP SmartyPants 1.5.1oo

They should yield identical results than their non-object  
counterparts. If not, that's a bug, please tell me.

These new versions feature the same programming interface as before  
-- you can still call the Markdown or SmartyPants functions. These  
functions will create and use the parser themselves, but you can also  
use the parser directly. This:

     $html = Markdown($text);

is now equivalent to this if you're using PHP Markdown:

     $parser = new Markdown_Parser;
     $html = $parser->transform($text);

or this if you're using PHP Markdown Extra:

     $parser = new MarkdownExtra_Parser;
     $html = $parser->transform($text);

PHP Markdown and PHP Markdown Extra are still both packaged as one  
"markdown.php" file, each of them containing a Markdown function; so  
they're still mutually exclusive. But the "markdown.php" file of PHP  
Markdown Extra contains both the Markdown_Parser and the  
MarkdownExtra_Parser classes. Hence, by calling directly the parser,  
you can filter text using both syntaxes.

For SmartyPants, attributes are (optionally) specified while  
constructing the parser and not while calling the transform method:

     $parser = new SmartyPants_Parser('q');
     $html = $parser->transform($html);

This is equivalent:

     $html = SmartyPants($html, 'q');

I'll release an object-oriented beta for PHP Markdown 1.0.2 later,  
probably when John comes out with a new beta; the same for SmartyPants.

Michel Fortin
michel.fortin@michelf.com
http://www.michelf.com/

From elfin at elfden.co.uk  Tue May 23 17:01:20 2006
From: elfin at elfden.co.uk (Rich Pedley)
Date: Tue May 23 17:02:22 2006
Subject: [ANN] Object-Oriented PHP Markdown/SmartyPants
In-Reply-To: <3166C1B0-755C-4C31-8236-F3FE78535FC6@michelf.com>
References: <3166C1B0-755C-4C31-8236-F3FE78535FC6@michelf.com>
Message-ID: <44737820.1010807@elfden.co.uk>

On 19/05/2006 19:35, Michel Fortin wrote:

> PHP Markdown 1.0.1oo
> 

Before I start work on trying to extend this... which I have never 
done before, please accept my thanks for releasing a version that will 
make it possible.

But a quick question, I want to add the ability to add a
'class="Foo" ' - specifically in my case to images

is this something that is likely to happen in the near future? As I do 
not want to replicate/duplicate any work that might be in progress.

Rich

From kraai at ftbfs.org  Wed May 24 09:29:24 2006
From: kraai at ftbfs.org (Matt Kraai)
Date: Wed May 24 09:29:44 2006
Subject: two lists without separating text are messed up
Message-ID: <20060524132922.GB2254@localhost.localdomain>

Howdy,

The following bug in Markdown was reported to the Debian bug tracking
system.

----- Forwarded message from Pierre THIERRY  -----

From: Pierre THIERRY 
To: Debian Bug Tracking System 
Subject: Bug#368413: markdown: two lists without separating text are messed up
Date: Mon, 22 May 2006 03:20:31 +0200

Package: markdown
Version: 1.0.1-3
Severity: normal

The attached code is rendered with only one big unordered list (see
attached rendered HTML).

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (501, 'stable'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages markdown depends on:
ii  perl                          5.8.8-4    Larry Wall's Practical Extraction 

markdown recommends no packages.

-- no debconf information

-- 
nowhere.man@levallois.eu.org
OpenPGP 0xD9D50D8A

Content-Description: Testcase source
Test case
=========

This should be an unordered list followed by an ordered one:

 - foo
 - bar

 1. first
 1. second

Content-Description: Testcase output
Test case

This should be an unordered list followed by an ordered one:

foo
bar
first
second

----- End forwarded message -----

-- 
Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://six.pairlist.net/pipermail/markdown-discuss/attachments/20060524/ea6347b8/attachment.pgp
From michel.fortin at michelf.com  Wed May 24 09:38:30 2006
From: michel.fortin at michelf.com (Michel Fortin)
Date: Wed May 24 09:38:34 2006
Subject: [ANN] Object-Oriented PHP Markdown/SmartyPants
In-Reply-To: <44737820.1010807@elfden.co.uk>
References: <3166C1B0-755C-4C31-8236-F3FE78535FC6@michelf.com>
	<44737820.1010807@elfden.co.uk>
Message-ID: <114D4D03-B806-42A8-BB2E-884AF5261659@michelf.com>

Le 23 mai 2006 ? 17:01, Rich Pedley a ?crit :

> But a quick question, I want to add the ability to add a
> 'class="Foo" ' - specifically in my case to images
>
> is this something that is likely to happen in the near future? As I  
> do not want to replicate/duplicate any work that might be in progress.

This is certainly planned for PHP Markdown Extra, but I haven't  
started work on that yet. If/when it ships it will probably include  
support for a little more than images, and more than the class  
attribute.

But I don't know when I'll do it, if I do it, so I suggest you go for  
it.

Michel Fortin
michel.fortin@michelf.com
http://www.michelf.com/

From elfin at elfden.co.uk  Wed May 24 14:15:50 2006
From: elfin at elfden.co.uk (Rich Pedley)
Date: Wed May 24 14:18:37 2006
Subject: [ANN] Object-Oriented PHP Markdown/SmartyPants
In-Reply-To: <114D4D03-B806-42A8-BB2E-884AF5261659@michelf.com>
References: <3166C1B0-755C-4C31-8236-F3FE78535FC6@michelf.com>
	<44737820.1010807@elfden.co.uk>
	<114D4D03-B806-42A8-BB2E-884AF5261659@michelf.com>
Message-ID: <4474A2D6.40401@elfden.co.uk>

On 24/05/2006 14:38, Michel Fortin wrote:
> Le 23 mai 2006 ? 17:01, Rich Pedley a ?crit :
> 
>> But a quick question, I want to add the ability to add a
>> 'class="Foo" ' - specifically in my case to images
>>
>> is this something that is likely to happen in the near future? As I  
>> do not want to replicate/duplicate any work that might be in progress.
> 
> This is certainly planned for PHP Markdown Extra, but I haven't  
> started work on that yet. If/when it ships it will probably include  
> support for a little more than images, and more than the class  
> attribute.

Well of course :-) Plus my efforts are extremely novice orientated.

> But I don't know when I'll do it, if I do it, so I suggest you go for  
> it.

I have finally managed to wrangle a class for an image by extending a 
couple of portions of your script. So I'm off and running with it.

Rich