Problems with incorporating markdown into a project
Ryan Booker
ryanbooker at gmail.com
Sun May 8 06:31:21 EDT 2005
Wouldn't that mean that everything would fail?
If I type the reference as:
[1]: http://blah.com/ (title)
instead of
[1]: http://blah.com "title"
it works.
I going to check "escaping" of characters when I get home. It seems
to work fine on the command line, so it must be something to do with
the quality of data passed from the html form to the markdown script.
As for new line characters, I don't quit follow what you mean? The
input for the Markdown script etc comes from an html form. Are you
suggesting that the script files them selves have had their new line
characters corrupted?
On 5/8/05, A. Pagaltzis <pagaltzis at gmx.de> wrote:
> * A. Pagaltzis <pagaltzis at gmx.de> [2005-05-08 08:36]:
> > so if the text file contains newlines that don't like as expected
> > by both the respective system, it will fail to find the
>
> That is, "that don't look as expected by both respective systems."
>
> Regards,
> --
> #Aristotle
> *AUTOLOAD=*_=sub{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1};
> &Just->another->Perl->hacker;
> _______________________________________________
> Markdown-Discuss mailing list
> Markdown-Discuss at six.pairlist.net
> http://six.pairlist.net/mailman/listinfo/markdown-discuss
>
More information about the Markdown-Discuss
mailing list